Featured
- Get link
- X
- Other Apps
Leaving Notion Without Losing the Workspace: The Six Things the Export Breaks
Leaving Notion Without Losing the Workspace: The Six Things the Export Breaks
Every "I am leaving Notion" post starts the same way and ends the same way. It starts with a workspace you have spent two years building, and it ends three weeks later with a folder of Markdown that nobody opens, because the thing you exported is not the thing you had.
The official export is not a scam and it is not broken. It does exactly what it says: every page becomes a .md file, every database becomes a CSV, images land in an /images/ folder. What it does not do is tell you which parts of your workspace it quietly dropped, and that is where most migrations die — not at export day, but a month later, when someone needs a relation that is now a line of plain text.
We sell a kit that handles that gap, so read this as a biased walkthrough: the useful part is the loss list, the file manifest, and the cases where you should close the tab and use a free tool instead.
The six features that do not survive
This is the section worth reading even if you never buy anything. As of October 2026, the official Markdown & CSV export carries plain text, headings, to-dos, basic tables, ordinary links and images by path well enough. These six it does not carry:
- Relations. A relation linking a row in one database to rows in another arrives as the plain text names of the linked pages. No link, no pointer back to the other CSV. The structure is gone and only the label survives.
- Rollups. A rollup only ever existed between databases. Once the relations are labels, there is nothing left to aggregate — at best you get one static value frozen at export time.
- Formulas. Computed columns usually arrive as their computed values. The value is useful, the logic is gone, and you will re-derive it by hand for whichever columns earn their keep.
- Synced blocks. A block that stayed identical across twenty pages becomes twenty independent static copies that no longer sync. Edit one and the other nineteen go stale.
- Embeds. Live frames — Drive files, Figma, video, spreadsheets — do not arrive as live frames. What lands ranges from a bare URL to nothing at all.
- Database views. The kanban, calendar and filtered views are gone. The CSV behind them is not.
Comments, page history and shared-space permissions are also absent. None of this is a secret; it is in Notion's own export documentation, in pieces, and it is why a converter that converts files cannot finish a migration that is really about decisions.
What NotionEscape actually contains
Fourteen files, and the manifest is the honest sales pitch. Five are the migration project as documents: a runbook that names every decision point, plus a pre-flight audit checklist (18 boxes), an export-day checklist (11), a post-migration QA checklist (11) and a decommission checklist (11). Three are small Python utilities. Four are landing templates for the receiving vault. One is a worked example. One is the README.
| File | What it does |
|---|---|
01_Migration_Runbook.md | Pre-flight audit → official export → land in _import/ → normalize → QA → decommission, with the six-stage order and its decision points written out. |
02_PreFlight_Audit_Checklist.md | 18 boxes: inventory databases with row counts, count relations, rollups, formulas, synced blocks, embeds, attachments — before you export anything. |
03_Export_Day_Checklist.md | 11 boxes for taking the export and proving the zip is complete against the audit's row counts. |
04_PostMigration_QA_Checklist.md | 11 boxes that prove the vault before anything is deleted. |
05_Notion_Decommission_Checklist.md | 11 boxes in the right order, after a retention window you choose during the audit. |
06_csv_to_moc.py | Database CSV → a Map of Content note, one wikilink per row, in file order. |
07_link_embed_rewriter.py | Rewrites notion.so URLs, broken relative .md links and absolute /images/ references so they resolve inside the vault. |
08_frontmatter_normalizer.py | Puts one canonical front-matter block on every imported note. |
09_vault_landing/ | Four templates: root index MOC, inbox note, project note, and the archive decision record that holds your keep / rebuild / leave-behind verdicts. |
10_Worked_Example_Fake_Workspace.md | A fictional 11-page workspace with two database CSVs, an image reference and a four-deep sub-page chain, migrated end to end with every command and output shown. |
The three-way classification is the actual product
A checklist sounds like filler until you try to write one. The audit forces a single verdict on every database and page cluster, and there are only three:
keep-as-export — the CSV plus a generated MOC note is genuinely enough. Client lists, reading lists, flat trackers with no relations live here. rebuild — what mattered was the structure, and the export cannot carry it, so it gets a vault-native note rebuilt by hand from the CSV's values. leave-behind — stale wikis, expired projects, duplicated databases that stay in the archived zip and never enter the vault.
That third option is the one people skip, and it is the reason migrations take three weekends instead of one. Leaving something behind is a migration outcome, not a failure.
What we verified before publishing this
The three utilities are the only executable part of the bundle, so here is exactly what they do and what we checked on 22 November 2026. Each ships a --selftest that touches no files: 06_csv_to_moc.py reports selftest: PASS (9 checks), 07_link_embed_rewriter.py reports PASS (10 checks), 08_frontmatter_normalizer.py reports PASS (9 checks). They need python3 3.8 or newer and nothing else — no pip packages, no accounts, no API tokens, and no network calls at any point. None of them deletes a file; they overwrite only the output path you hand them. The CSV converter is deterministic: the same input bytes produce byte-identical output.
The install, the price, and the disclosure
Unzip it anywhere, read README.md, then read the runbook once end to end before you touch Notion. Call the three scripts by path, or copy them next to your export and run them from there. The pre-flight audit is meant to run before export day, because its row counts are the baseline you check the zip against.
NotionEscape — The Notion-to-Obsidian Migration Kit is available at the NotionEscape listing on Gumroad. The current intro price is $1.00, verified live on 22 November 2026. It is an intro price on a launch ladder and can move; re-check the page before you buy rather than trusting this paragraph.
Disclosure: This post links to a product we made. If you buy through it, we may earn a commission at no extra cost to you.
On evidence: there is no verified review, rating, testimonial or sales figure for this product that we could cite, so none is cited here. The claim that the Notion export drops the six features above is sourced from Notion's own export behaviour as of October 2026 and from the two free converters named below, both of which document the same gaps — not from a market study.
Who it is NOT for
Skip it if you only need file conversion. Two free, open-source tools already do that well and we name them on the front page of the bundle: obsidianmd/obsidian-importer, the official Obsidian plugin for importing Notion exports directly into a vault, and connertennery/Notion-to-Obsidian-Converter, a standalone converter. If conversion is the whole job, use those and keep your dollar.
Skip it if you expect the databases to arrive as databases. They arrive as CSV plus a generated MOC note. Relations, rollups and views are not reconstructed by anything in this kit — they are counted in the audit and decided on, by hand.
Skip it if you want software. Nothing runs as a service. Three scripts are run by you, from a terminal, at the points the checklists name. There is no app, no dashboard and no sync.
Skip it if you are not actually leaving. The kit is a one-time project with a hard external deadline for most people. If you are only tidying a workspace, this is the wrong shape of work.
Skip it if you want the migration done for you. The checklists tell you what to verify; they do not verify it. A workspace where the relations mattered will still take hours of rebuilds.
Skip it if Notion has already changed its export. Every menu label and format detail in the runbook is stamped "as of October 2026" on purpose. Verify against your own export — Notion changes these details without warning, and a kit that pretended otherwise would be lying to you.
Honesty block
Example figures are illustrative planning inputs — not market rates and not earnings.
No legal, tax, insurance, licensing, veterinary, automotive-repair, or financial advice.
No claims of CRM/map/API/invoicing integrations the bundle does not ship.
Corrections and questions are welcome. If we got a fact wrong, write to nandminc2020@gmail.com and we will fix it.
- Get link
- X
- Other Apps
Popular Posts
Best AI Music Generators in 2026: Free Tiers, Text-to-Song Tracks and the Tools Worth Paying For
- Get link
- X
- Other Apps
Best AI Video Generators in 2026: Free and Paid Tools Compared
- Get link
- X
- Other Apps
Comments
Post a Comment