Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Agents
  • Computers
  • Drive
  • Automations
  • AI Gateway
  • All features →
  • LLM cost calculator
  • Token counter
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Benchmarks
  • Demos
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
Blog

Move Your Notes From Obsidian or Notion Into idapt

ITidapt Team·July 2, 2026·Last reviewed July 16, 2026

The idapt Knowledge Base is markdown-first: notes organized in folders, [[wikilinks]] with backlinks and a force-directed graph, live collaborative editing, and agents that can read and write your notes. Both major sources, Obsidian vaults and Notion exports, come in through one folder import.

From Obsidian

An Obsidian vault is already the right shape: a folder tree of markdown files with wikilinks.

  1. Open your workspace's Knowledge tab.
  2. Click Import folder in the Knowledge sidebar and pick your vault directory.
  3. Done. The folder hierarchy is recreated, and because wikilinks resolve across the whole Knowledge Base, [[links]] work immediately no matter which folders the notes landed in. Backlinks and the graph light up on first open.

Good to know:

  • Titles are unique per workspace. Two Ideas.md files in different folders collide; the second is skipped with a clear message. Rename and re-import those few.
  • Text only. Images and PDFs aren't part of the notes import yet; upload them to Drive alongside.
  • Caps: 256 KB per note, 2,000 notes per workspace, and a per-workspace Knowledge quota (10 MB free, up to 5 GB on Max). An over-quota import fails cleanly before writing anything.
  • No plugins. Canvas, Dataview, and community plugins have no equivalent, though agents cover a surprising amount of that ground (ask one to build an index note or extract every TODO).

From Notion

Notion's export splits documents from databases. Import the document tree into Knowledge first; database CSVs can stay in Drive until the structured data product is generally available.

  1. In Notion: Settings → Export all workspace content, format Markdown & CSV. Unzip it.
  2. Pages → Knowledge: import the export folder into the Knowledge Base with Import folder. Nested pages arrive as folders.
  3. Database CSVs → Drive: keep each exported database CSV beside the imported notes in Drive. That preserves the data while structured database import remains pre-GA.

Good to know:

  • Notion appends an id hash to exported file names ("Project Notes 8f3a….md"). A title-cleanup pass is on the roadmap; today a quick rename does it.
  • Relations, rollups, and formulas export as plain CSV values; keep those CSVs with the notes so the computed values stay available.
  • Comments, page history, and granular permissions aren't in Notion's export at all.

Getting back out

The exit is as easy as the entrance: the Knowledge Base exports as a ZIP of markdown keyed by folder path. Your notes stay yours.

The mapping tables live on the Obsidian and Notion migration pages; the help article covers every cap and edge case.

GuideObsidianNotionNotesImport

Found this helpful? Share it:

  • From Obsidian
  • From Notion
  • Getting back out

Continue reading

  • How to Import Your ChatGPT History Into idapt

    A five-minute guide: export your ChatGPT data, upload the ZIP, and get your whole conversation history (branches, tool calls, and images) in idapt.

  • Fix a Failing Test on Your Own Machine From a Chat

    A worked idapt Code run: two permissions, one prompt, and an agent that reproduces a failing test on your laptop, fixes it, and hands back the diff.

  • Cancel ChatGPT Plus Without Losing Your History

    The switcher's checklist: export your ChatGPT archive, import every conversation into idapt in minutes, and know exactly what maps where before you cancel.

  • The Model Treadmill

    The best AI model changes every few months. Chasing it by switching apps is the treadmill; the exit is infrastructure that outlives any model.

  • Explore idapt

    • Every migration path

      What moves from each app and how, in one index.

    • Custom AI agents that actually do work.

      Skills, scoped permissions, persistent memory: any model you pick.

    • A file-first AI workspace.

      Folders, previews, and lightweight versioning for AI work.

    • Computers your agents can drive.

      Daemon-connected machines with real filesystems and agent-friendly controls.