Leaving Notion for Obsidian: own your notes in an afternoon

People leave Notion for two reasons: lock-in worry (the data lives on someone else's servers, exports are messy, the offline experience is poor) and over-engineering fatigue (every database becomes a tinker project). Obsidian is plain Markdown files in a folder on your machine. Yours, portable, fast. Half a day of actual work gets you across; the harder question is which parts of Notion you should not try to replace.

What you are signing up for

Obsidian is not a Notion clone. It is a notes app built on top of a folder of Markdown files, with a plugin ecosystem that adds capability. What you get for free: local-first, full ownership, blazing speed, Git-friendly. What you give up: collaborative editing, the universal database-can-be-anything model, embedded Figma and Loom previews, and the slick web sharing.

If you collaborate live with anyone in Notion, Obsidian is the wrong destination. Stop here, look at Anytype or self-hosted AppFlowy instead.

If you mostly read and write notes solo, Obsidian is a permanent upgrade. The rest of this guide assumes that case.

Step 1: export from Notion

Workspace owner only. Settings → Workspace → Export all content. Pick Markdown & CSV format, include subpages and files. The export is a ZIP that can take 5-30 minutes depending on workspace size; Notion emails you when it's ready.

The ZIP unpacks to a folder where every page is a .md file and every database is a .csv plus a folder of the rows as Markdown files. Subpage relationships are preserved as folder nesting. Backlinks are not — Notion uses page IDs in URLs that Obsidian cannot resolve.

Step 2: clean up the export

Two cleanups before you point Obsidian at the folder.

Strip the page IDs from filenames. Notion exports filenames as Some Page Name abc123def456.md. Obsidian will work with these but the IDs in [[wikilinks]] are visual noise. Run a quick rename:

# Unix / macOS
cd ~/Downloads/notion-export
find . -name "* [0-9a-f][0-9a-f][0-9a-f]*.md" -exec rename 's/ [0-9a-f]{32}//' {} \;

If you don't have rename installed: a one-shot Python script does the same thing. Or skip this step entirely; the noise is liveable.

Fix the link format. Notion exports internal links as relative paths like ./Some-Page-abc123.md. Obsidian prefers [[Some Page]]. Run a search-and-replace across the folder (any decent text editor handles batch replace in a directory) to convert the few patterns that matter. If the workspace is small, do it as you encounter broken links instead of upfront.

Step 3: open the folder as an Obsidian vault

Install Obsidian, click Open folder as vault, point it at the cleaned export. The vault loads instantly. Browse for ten minutes. The notes are there; the structure is roughly what you had in Notion.

You'll spot things that broke: pages that referenced Notion-only blocks (toggles, callouts in non-Obsidian-compatible markup, embeds of external content). They look reasonable as plain text; fix the dozen most-visited pages, leave the rest.

Step 4: install the four plugins worth installing

The plugin ecosystem is the trap. People install 30 plugins, configure them for a week, and end up with the same over-engineered system they were trying to escape. The four that earn their place for almost everyone:

• Templater — for note templates with variables. Replaces the Notion template button.
• Dataview — turns frontmatter into queryable data. The closest thing Obsidian has to Notion databases. Use sparingly.
• Sync ($10/mo, official) or Git (free, plugin) — for syncing the vault between devices.
• Outliner — bullet-list keyboard shortcuts that match Notion.

Anything else, install only when you hit a real pain point. The vault works without any of them.

Step 5: rebuild your two most-used workflows

Don't try to recreate the entire Notion setup. Pick the two workflows you actually use weekly and rebuild them with Obsidian primitives.

The most common pair:

• The daily note. A template that opens when you create today's note. Time of day headings, a "what's open" frontmatter field, a "what shipped" section at the bottom. Templater handles the template; the daily-note plugin (built in) handles the date logic.
• The project tracker. In Notion this was a database with status, owner, next step. In Obsidian, it's a folder of project notes with frontmatter (status: active, next-step: x) and a Dataview query in your dashboard note that lists active projects with their next steps.

Resist the urge to set up more than two workflows in the first week. Each one is a configuration commitment.

Step 6: archive the Notion workspace

Don't delete. Set the Notion workspace to read-only by changing the workspace owner to a paused account, or simply stop opening it. After 90 days of not opening Notion, you'll know the migration took. Then you can downgrade the Notion plan to Free or cancel.

What you will miss

The visual database views. Obsidian's Dataview queries are powerful but text-only; the Notion Kanban and Timeline views genuinely do not exist in Obsidian. If you live in those views, this is the migration tax.

The web sharing. Sharing a Notion page is one click and produces a public URL. Obsidian has paid Publish ($96/year) or you build your own with a static site generator on top of the vault. Most solo operators don't actually need this and used Notion sharing maybe twice a year; if you used it weekly, factor it in.

The collaborator presence. Real-time co-editing is gone. If you have one project where this matters (a client doc, a co-authored piece), keep Notion alive just for that project and stop trying to migrate everything.

The honest summary

Notes get faster, more permanent, and yours. The configuration overhead of Notion goes away. The bright spots of Notion (databases, collaboration, sharing) are real losses; the price of escaping is owning the simpler tool. Most solos who switch report they don't miss Notion within three weeks. A minority miss it constantly and switch back. Knowing which group you're in takes a week of actual use.