Notion Lock-In: What the Export Actually Loses

Notion lock-in is not about whether there is an export button. There is one, it works, and it will hand you a zip file. The real question behind every Notion lock-in export argument is narrower and more useful: do the exported files still run your GTD system on Monday morning, or do you now own a folder of readable text and a broken machine?

The honest conclusion, up front. Your words travel fine. Your structure does not. Databases flatten into CSVs, relations become page-title strings, formulas export as whatever number they happened to show on the day, and the graph you spent two years building is the part you rebuild by hand. That rebuild time, measured in hours, is your actual exit cost. Licence fees are a rounding error next to it.

What people actually mean when they worry about lock-in

Lock-in gets argued in the abstract on Reddit and Hacker News, and explained mechanically in Notion’s own help docs. Neither helps you decide anything. A GTD system holds the open loops you have agreed to stop carrying in your head, so the question is a trust question: if this workspace disappeared on Thursday, would you still know what you had committed to?

Notion’s position is reasonable enough. Import and export both exist, and the company documents the process in its help centre guide to exporting content. What most people miss is the other half of that page: a workspace owner can switch export off entirely under Settings then Security. If you keep your personal GTD system inside your employer’s workspace, you may have no export route at all, and no warning until you need one.

Worth knowing, and worth not over-claiming: the UK GDPR right to data portability, explained by the ICO, covers personal data you provided to a controller. It is not a legal lever for prising your team’s project notes out of a company workspace. Assume the technical route is the only route.

The three export formats, and which one you actually want

Notion offers Markdown and CSV, HTML, and PDF. They are not interchangeable.

Markdown and CSV is the one to use as your working archive. Plain text pages, tables as CSV rows, attachments in folders. Every serious note app imports Markdown, which makes it the sane base for a move to Obsidian, Apple Notes, Bear, Craft or anything else on a shortlist of Evernote alternatives with real migration costs.

HTML preserves more of what you see: callouts, toggles, columns, and internal page links that still resolve between the exported files. Lovely to read, miserable to edit. Take it as a second, read-only archive, not as the thing you migrate into.

PDF is presentation only. It is also the format with a plan dependency: whole-workspace PDF export sits behind paid plans, per Notion’s documentation at the time of writing. Do not build a backup strategy on it.

Three toggles decide whether your hierarchy survives: include sub-pages, create folders for sub-pages, and include databases (choose everything, not just the current view). Miss the sub-pages toggle and you export the top of your tree and none of the branches. People do this, notice six months later, and by then the workspace has moved on.

What survives the export, and what quietly does not

Survives in usable shape

Page text, headings, bullet and numbered lists, checkboxes as Markdown checkboxes, tables as CSV rows, most file attachments, and the folder hierarchy if you ticked the right box. Read the export and you can still tell what you were thinking. That matters more than people give it credit for.

Degrades

Databases become flat CSV files. One file per database, one row per page, columns for properties. Everything you built on top of that data (views, filters, sorts, grouping, board layouts, calendar overlays) does not exist in a CSV. A GTD workspace with an Inbox database, a Projects database and a Next Actions database exports as three unrelated CSVs plus a folder tree of Markdown files. Your single trusted inbox is now three spreadsheets that no longer talk to each other.

Breaks outright

Relations and rollups are the real lock-in, not the text. Take a freelance consultant with a client database of 40 rows, each client linked to project pages, with a rollup showing invoiced totals. The export gives you 40 rows of plain text, a rollup column showing numbers with no live source underneath them, and client-to-project links reduced to page titles. The numbers are a photograph. The links are a suggestion.

Formulas behave the same way: they export as their computed value. That looks completely fine on export day and is dead the moment your data changes. If you run formula-driven “due today”or “available now”views for your next actions, assume those views do not travel. Not degraded. Gone.

Also on the casualty list: synced blocks, which duplicate their content into every location rather than staying one source; database templates; button automations; and anything driven by Notion AI.

The forgotten stuff

Comments, page history, reminders, and @mentions of people. Meeting notes where the decision lives in a comment thread export as a page with the decision missing. Internal links inside Markdown exports frequently point back at notion.so URLs rather than at your local files, so your carefully cross-referenced reference library becomes a set of dead ends the day your access ends.

Score the export against the five jobs your system has to do

This is the part nobody runs. Do not ask “did everything export”. Ask whether the export can do the five jobs a GTD system exists to do, the same five used to compare note-taking apps for GTD.

• Time-to-captured. In the target app, on your phone, locked screen, one hand: how many seconds from intent to saved? Under five is a practical working benchmark rather than an official rule, and it is the one that decides whether you keep using the thing. The mechanics of hitting it are covered in this guide to capturing an idea in under five seconds.
• One trusted inbox. Does the archive leave you with a single processing queue, or fifteen scattered CSVs and a folder tree? If you have to remember which file a loop lives in, you do not have an inbox.
• Retrieval from half a memory. This is where technically complete exports fail hardest. Every byte can be present and you still cannot find the thing, because you used to find it by scanning a board grouped by client, and now it is row 212 of a CSV with a filename like Untitled 3c8f2a.md. Test with three real items you half-remember, never with tidy demo content.
• Exit cost. Count the hours to rebuild relations and views. Then ask whether you would ever willingly do it twice. If the answer is no, you are not portable, you are just told you are.
• No daily admin tax. If the new home needs weekly tidying, tagging and status hygiene to stay trustworthy, the migration failed even if every file arrived.

Old lesson, still true: the system you trust is the one that survives changing tools. Index cards and plain text files have a zero exit cost, which is why hybrid paper setups like the hPDA keep outliving whichever app is fashionable that year.

The export and verification drill you can run this weekend

1. Run a full-workspace export as Markdown and CSV, with sub-pages included, folders for sub-pages on, and databases included in full.
2. Run a second export as HTML and keep it as your readable archive. Two formats, one afternoon.
3. Anything sizeable arrives as an emailed download link rather than an instant file, and that link expires. Check the current window in Notion’s help centre before you plan around it, and download it the same day.
4. Spot-check ten pages, chosen badly on purpose: one heavy database, one project page full of relations, one reference page with attachments, one meeting note where the substance is in the comments, and six at random.
5. Open the CSVs in a spreadsheet. Confirm relation columns, dates, checkbox fields and multi-select values came through in a shape you can actually use. Date formats are a common nasty surprise.
6. Then the real test: work from the archive for a week. Process one genuine inbox to zero using only the exported files. You will find the breakages in an hour instead of during a forced migration at the worst possible moment.
7. Set a repeat. A quarterly export, filed alongside your weekly review routine, takes minutes: one Markdown and CSV archive, one HTML archive, both dated, both dropped into cloud storage.

Build Notion so the exit stays cheap

You do not have to leave Notion to benefit from this. You have to build as though you might.

Keep projects and next actions in a simple structure and reserve relations and rollups for the places where they genuinely earn their keep, which is usually client work and money, not your reading list. Store real reference as files and plain text rather than as formula output or linked views of somewhere else. Name pages the way you would name a file on your hard drive, because that is exactly what they become: “2026-03 Acme rebrand scope”survives the export, “Untitled”does not.

Three signals it is time to move. The daily admin tax is rising and you are maintaining the system instead of using it. Search keeps failing you on things you know are in there. The whole thing only works when you are sat at a desk with two monitors.

Where people land varies, and the honest currency is rebuild hours rather than licence fees. Moving reference notes into a Markdown-native app is cheap, often an afternoon. Moving a project and action system into something like OmniFocus costs more, because you are recreating logic, though custom perspectives tend to replace the filtered views you lost. Moving everything to plain text and folders costs the least to maintain and the most in features you will miss for a fortnight and then forget.

Run the export this weekend. Work from it for a week. Whatever the Notion lock-in export debate says in the abstract, an hour spent finding the breakages now is the difference between a system you trust and a very tidy archive of things you used to be committed to.

Frequently Asked Questions

Does Notion’s export give you all your data?

It gives you all your page content, and not all of your system. Text, lists, tables and attachments come through; comments, page history, reminders, synced-block relationships, database templates and automations generally do not. Treat the export as a readable archive of what you wrote, not a working copy of what you built.

What happens to Notion databases, relations and rollups when you export?

Each database becomes a flat CSV file: one row per page, one column per property, no views, filters, sorts or grouping. Relations export as page-title text rather than live links, and rollups export as static numbers with nothing feeding them. Formulas export as whatever value they showed at the moment of export, so they are accurate that day and stale immediately afterwards.

Should you export as Markdown, HTML or PDF?

Markdown and CSV for anything you might migrate, because almost every note app imports it. HTML as a second archive if you want the visual structure and working internal links preserved for reading. PDF only for documents you intend to share or print, and note that whole-workspace PDF export is tied to paid plans.

Can a workspace owner stop me exporting my Notion data?

Yes. Notion’s documentation describes a “Disable export”setting under Settings then Security that a workspace owner can switch on. On a company workspace, that can leave you with no export route for anything you have stored there, which is a good argument for keeping your personal GTD system somewhere you control.

How often should I back up a Notion workspace I rely on for GTD?

Quarterly is enough for most people, tied to a weekly review you already do so it never becomes a separate chore. Export in Markdown and CSV plus HTML, date the folders, and keep at least the last two in cloud storage. If your work is client-billable or contractual, monthly is the safer cadence.