Leaving Notion for plain text: a calm migration

Leaving Notion for plain text means moving your pages out of Notion's database and into ordinary Markdown files in a folder you control. You export your workspace to Markdown, clean up the output, reorganize the pages as files, and rebuild a few workflows. The process is reversible, and the work is mostly mechanical. For a small workspace it is closer to an afternoon than a weekend.

This guide is deliberately fair to Notion. Notion is a genuinely good product, and some people should not switch. The goal is to help you decide honestly, then make the move clean if you choose to.

Why people are leaving Notion

The reasons people give for leaving Notion are usually not complaints about the app. They are about where the data lives. A few patterns come up again and again:

• The writing matters more than the database, and a database app starts to feel like overhead.
• A backup question comes up, and the only honest answer is "Notion has it."
• The app feels slow, or it needs a network round trip for things that should be instant.
• An AI tool, a script, or a search needs the raw text, and there is an export step in the way every time.

None of these mean Notion is bad. They mean the work has drifted toward plain writing, and plain writing doesn't need a database. If that describes you, the rest of this guide walks you through the move.

Should you actually be leaving Notion?

Start with the question most migration guides skip. Notion is strong at things plain text is not, and pretending otherwise leads to regret.

Notion is a good fit when:

• Your work is fundamentally a database: relational tables, linked records, rollups, filtered views.
• You rely on real-time collaboration, comments, and shared permissions across a team.
• You use Notion as a lightweight CRM, project tracker, or team wiki where the relationships between records are the point.
• You want everything (docs, tasks, calendars, dashboards) in one connected workspace.

Plain Markdown files are a better fit when:

• Your work is mostly writing: notes, drafts, journals, research, documentation, meeting notes.
• You want to own the files and not depend on any one app to read them in five years.
• You want fast local search, your own backups, and sync through tools you already trust.
• You are tired of the app feeling slow, or you simply want something quieter and offline.

A useful rule: if the relationships between records are the point, a database wins. If the words are the point, files do the job better. Many people use Notion for both, and the honest answer is often a split: keep the team database in Notion, move your personal writing to files. Leaving Notion is not all-or-nothing.

What does "Notion lock-in" really mean?

Lock-in is not a conspiracy. It is a consequence of how Notion stores data. Your pages live in Notion's database, not as files on your disk, so the app is the only thing that can read them directly. That is fine until the day you want to leave, raise a backup question, or run your own search across everything.

The practical effects:

• You cannot open a Notion page in a plain text editor without exporting first.
• Your "backup" is really trust that Notion's servers and export feature stay available.
• Databases, relations, and rollups have no clean plain-text equivalent, so they need rework on the way out.
• Anything outside the app (Git history, ripgrep, a script, an AI tool reading raw text) needs an export step in between.

None of this is unique to Notion. Most note apps that store data in a database carry the same trade-off. It is the cost of database features. The point of moving to files is to stop paying that cost for the writing that never needed a database in the first place.

How do you export Notion to Markdown?

Notion has a built-in export, and it does the heavy lifting. The short version:

1. Open the page or workspace you want to move.
2. Use the ... menu → Export (or Settings → Export all workspace content for everything).
3. Choose Markdown & CSV as the export format.
4. Decide whether to include subpages and create folders for subpages (turn the folder option on so your hierarchy survives).
5. Download the .zip and unpack it somewhere safe.

What you get back:

• Each page becomes a .md Markdown file.
• Nested pages become folders, so your tree structure mostly carries over.
• Each database exports as a .csv file, plus a folder of .md files for the rows that were full pages.
• Attached images and files come down alongside the Markdown, referenced by relative paths.

Because the export is standard Markdown, you are already in the format you want, with no second conversion step. Keep the original .zip until you are happy with the result, so you always have a clean copy to redo from.

How do you clean up the exported Markdown?

Notion's export is good, not perfect. A few rough edges are normal, and most are quick to fix. Here is what to expect and what to do about it.

Export quirk	What you'll see	Fix
Long filenames	Page name plus a long hex ID, like Meeting Notes 8f3c1a....md	Strip the trailing ID; rename to something clean
Database as CSV	Tables become .csv, not Markdown tables	Keep as CSV, or paste into a note as a Markdown table
Notion-only blocks	Toggles, callouts, synced blocks flatten to plain text	Re-mark the important ones as headings, quotes, or lists
Internal links	Page links point to old file paths with IDs	Re-link the few that matter; leave the rest
Image paths	Relative paths into per-page folders, with long encoded filenames	Keep images beside their notes, or gather into /assets and update the paths

One caution on images. Notion references images by relative path, and the image filenames themselves are long, URL-encoded strings. If you rename a .md file, move it, or gather images into an /assets folder, the relative links break unless you update the paths in the Markdown at the same time. So do the renaming and the path fixes together, or leave images next to their notes and only tidy the filenames you actually look at.

If you exported AI-written pages, the same cleanup principles apply to that output too; there is a fuller walkthrough in how to clean up AI Markdown.

A practical order of operations:

1. Unzip into a fresh folder that will become your note library.
2. Rename files to drop the trailing IDs. Many file renamers and a one-line script can batch this; by hand is fine for a small workspace.
3. Flatten where it helps. Notion nests deeply. Two or three folder levels are often enough.
4. Decide on databases. For a simple table, paste the CSV into a note and convert it to a Markdown table. A real database you still need is a sign it should stay in Notion.
5. Fix only the links you use. Don't spend an hour re-linking pages you will never open. Repair the few that carry your day to day.

You are not trying to reproduce Notion exactly. Keep the writing, and let the database parts go or stay behind.

How do you reorganize pages as files?

Once the Markdown is clean, you are looking at folders and files instead of a sidebar of pages. The structure you want is usually flatter and more boring than Notion's, which is the point.

A simple, durable layout:

• A top-level folder per area of life or work (work, personal, research, archive).
• Notes as .md files inside, named so you can read them in any file browser.
• A loose inbox folder for quick capture you will sort later.
• An assets folder for images, or images kept next to the note that uses them.

You do not need a perfect taxonomy on day one. Files are easy to move later, which is exactly the freedom you were missing. Open the folder in any Markdown editor and you get live preview that renders headings, tables, and code as you type, plus fast search across the whole library, over plain files you own. The folder is the library; the editor is just a lens over it.

How do you replace common Notion workflows?

Most Notion habits have a plain-text equivalent. A few do not, and both are worth naming.

• Quick capture. Replace the Notion inbox with an inbox folder or a daily note. New thought, new line or new file.
• Tasks and to-dos. Markdown checkboxes (- [ ]) inside a project note cover most personal task tracking. For shared, assignable tasks, a dedicated tool or Notion still does this better.
• Databases and tables. Simple tables become Markdown tables; complex relational databases are the case to keep in Notion or a real database tool.
• Sync across devices. Notion syncs for you. With files, put the folder in iCloud Drive, Dropbox, OneDrive, or Syncthing, and every device sees the same notes. It is a one-time setup.
• Sharing a page. Notion's share link is convenient. With files, you export to Word or PDF and send the document, or share the file through your normal cloud drive.
• Search. Spotlight, your editor's search, or grep/ripgrep run across a large library near-instantly, with no app required.

Be honest about the two or three workflows that were genuinely Notion-shaped. If you cannot live without linked databases and shared real-time editing, the better move may be a split, not a full exit.

What you gain, and what you give up

You gain:

• Ownership. Your notes are .md files in your folder, readable in any text editor, today and in a decade. That longevity is the whole argument for plain Markdown files.
• Portability. No export needed to leave next time; the files are already yours.
• Your own backups and sync, through tools you already use.
• Speed and offline. A local editor over local files, with no spinner waiting on a server.

You give up:

• Relational databases, rollups, and filtered views.
• Real-time multiplayer editing and granular permissions.
• The all-in-one workspace feel, in exchange for a folder and an editor you choose.

For a side-by-side breakdown, the Noteline vs Notion comparison goes deeper on where each tool fits.

The short version

Export your workspace to Markdown, rename the files, keep the writing, and let the database parts go or stay behind in Notion. Reorganize into plain folders, set up sync once, and rebuild the few workflows you actually use. Leaving Notion for plain text is reversible, mostly mechanical, and far less dramatic than it sounds.

Notion remains a strong tool, and there is no shame in keeping it for the work it does best. But if your real goal was the writing, files give you something a hosted database does not by default: notes that sit on your own disk in a format any editor can read. You can try the workflow in the free web editor before installing anything, or get the desktop app for offline Word and PDF export and a license that is a one-time purchase rather than another subscription.