Introduction
When teams realize they need a Notion backup, the first instinct is often to go to Settings → Export → Export All Workspace Content. The process completes, a ZIP arrives, and it feels done. It isn't. Notion's export is designed for data portability, not disaster recovery, and the distinction matters. A meaningful slice of your workspace — relational structure, formulas, database views, comments, file contents, permissions — doesn't survive the export. Knowing exactly what gets dropped is what separates a backup plan that works from one that only looks like it works.
What Exports Cleanly
To be fair, Notion's export does the basics reasonably well. Page text comes through as Markdown or HTML. Database rows export as CSV with their property names as column headers. Simple property types — text, numbers, dates, checkboxes, single-selects — transfer intact. Nested pages reflect their hierarchy through folder structure in the ZIP. If your workspace is mostly flat documentation with simple databases, the export gives you something genuinely usable as a starting point.
Relations and Rollups Don't Survive
Relations between databases are where the export starts to break down in ways that aren't obvious until you need them. When you export a database that has a relation column, that column appears in the CSV as a plain text string — typically the page title of the linked row. The actual relationship is gone. There's no ID, no link, no way for a receiving system to know that a row in one table should connect to a row in another. Rollup columns, which derive their values from those relations, come through as static numbers or vanish entirely depending on the property configuration. For teams that have built relational databases — a CRM linked to a projects database linked to a contacts database — the export captures the rows but destroys the graph.
Formulas Export as Their Last Computed Value
Formula properties export as whatever value they computed at the moment of export, not as the formula expression itself. A formula that calculates days until a deadline, derives a priority score from multiple fields, or concatenates text across columns becomes a static number or string in the CSV. The logic doesn't travel. If you restore this database and need those computed values to stay current, you'll rebuild every formula from scratch — assuming anyone documented them anywhere other than inside Notion itself.
Database Views Are Not Included
Notion databases support multiple views: table, board, calendar, gallery, timeline. Each view can have its own filters, sorts, hidden properties, and grouping configuration. None of this is captured in any export format Notion offers. The rows export; the views don't. For teams where a carefully configured sprint board or pipeline kanban is a central part of how they work, rebuilding that view configuration from raw row data is a multi-hour manual task — not a restore.
File Contents Require Explicit Opt-In — and Can Still Break
Files and images uploaded to Notion are stored at internal URLs that expire. When you export, Notion offers the option to include files — but only if you explicitly check that box, and only as a point-in-time download. Any backup tool or script that captures page content without downloading the actual files will end up with dead links that stop resolving weeks or months later. During a restore, those embedded images won't render and those attached PDFs won't open. Check whether your backup process downloads actual file bytes, not just the URLs Notion uses to serve them.
Comments Are Excluded
Page comments — including inline comments tied to specific text selections — are not part of any Notion export. For teams that use comments for review cycles, decision trails, client approvals, or stakeholder sign-offs, this means the collaborative context around a document disappears even when the document itself is preserved. If a comment thread is the record of why a decision was made, the export gives you the decision but not the reasoning.
Permissions and Sharing Settings Are Gone
Workspace membership, page-level permissions, guest access, and team space configurations aren't exported. After a major incident requiring a workspace rebuild, you'll also be rebuilding the access control model from memory. Teams with complex permission hierarchies — where certain pages are restricted to finance, others to engineering, others to external clients — face significant manual work to re-establish those boundaries correctly.
What to Ask When Evaluating a Backup Tool
The gaps in Notion's native export are the gaps every backup tool should be measured against. The questions worth asking: Does the tool use the Notion API directly, or does it drive the export UI? API-based tools can capture the actual data model — including relation IDs and formula expressions — rather than just the rendered output. Does it download file contents or just URLs? Does it capture database view configurations? Does it store metadata that would let you reconstruct permissions? A backup that answers yes to these questions is substantively different from a scheduled export, even if both produce files on a regular cadence.
Conclusion
Notion's export is a useful feature for moving data out of the platform. It isn't a backup strategy. The gaps — relations, formulas, views, file contents, comments, permissions — are real, and they compound each other when you need to actually reconstruct a workspace rather than just retrieve some text. Understanding what the export misses is the prerequisite for choosing a backup approach that genuinely covers your workspace, not just the parts that are easy to serialize.