Notion Data Export: What You Can Actually Take With You

Notion is the product people most often have the most trapped inside, because it absorbs everything — notes, projects, documentation, wikis, half a company's institutional memory. So the export question matters more here than almost anywhere.

The short version: Notion exports better than its reputation suggests, and the risk is timing rather than content.

The thing it does better than nearly everyone

Comments come out.

This sounds minor and is not. Comments are where the reasoning lives — why a decision was made, what was rejected, who raised the objection. Almost every product in this category drops them, because they are awkward to represent in a flat file, and the result is an export that contains the conclusions and none of the thinking.

Notion's HTML export carries comments "at both the page and block levels", including "resolved and unresolved comments and any files, pages, or users mentioned in them".

Resolved comments are the detail worth pausing on. Those are the ones a product could most easily justify discarding — they are closed, settled, done. They are also frequently the record of exactly how something was settled. Keeping them is a deliberate choice and it is the single strongest thing in this report.

The trap: it is a race against two clocks

Notion's documentation states that a workspace export "can take up to 30 hours to process, depending on the size of the workspace", and that the resulting download link expires after seven days.

Read those together and the failure mode is obvious. A team decides to leave, works notice on the subscription, remembers the export on the final Thursday, starts it, and discovers the archive is still building when access ends. Or downloads it eight days later and finds the link dead.

Neither limit is unreasonable. Both are entirely survivable with two weeks' notice and entirely unsurvivable with two days'. Start the export a fortnight before you plan to cancel, and treat the seven-day window as the real deadline.

Choose the format deliberately

This is the decision that most affects what you end up with, and it is presented as a small dropdown.

Markdown & CSV is the right default for content you intend to re-use. Non-database pages become Markdown, databases become CSV, and subpages come through as separate Markdown files. Callout blocks export as HTML, because as the documentation says, there is no Markdown equivalent.

HTML is the right choice if the discussion matters, because it is the only format that carries comments. If you are exporting for archival reasons rather than to import somewhere else, this is usually the one you want.

PDF is for reading, not for moving. It flattens structure into a document, and Notion is in the process of removing PDF workspace exports — its documentation flags this as happening between now and 31 August 2026, which is the day this report was checked. If you were relying on that route, verify it still exists before you plan around it.

The gap almost nobody checks: permissions

Notion states plainly that "pages that the exporter doesn't have access to, such as private pages of other users, will not be included in the export".

This is correct behaviour and a genuine hazard, because the absence is silent. Nothing in the archive tells you that eleven pages were skipped. A workspace with a culture of private drafts can produce an export that looks complete and is missing a meaningful fraction of the work.

If you are exporting on behalf of an organisation, run it as an administrator, or ask people to move anything that matters into shared spaces first.

What a database export actually gives you

A CSV. Which is to say, values.

A Notion database that computes things — relations pulling in linked records, rollups aggregating them, formulas deriving new fields — does not export as a working system. It exports as the numbers those systems produced on the day you ran it.

For simple tables this is a complete export. For an elaborate interconnected setup, the honest expectation is that you are exporting the data and rebuilding the logic. Worth knowing before you build something intricate enough that rebuilding it is a project.

The verdict

25 out of 30. Notion is one of the better exits in this category, and the reason it does not score higher has almost nothing to do with what comes out.

What comes out is good: open formats, comments included, files included, structure preserved as nested files. What costs it points is the operational shape of the thing — a 30-hour build, a seven-day link, an admin switch that can disable it, and a PDF route being withdrawn.

Those are all manageable. They are only manageable in advance, which is the entire argument for reading a page like this before you need it rather than during the week you are leaving.