Leaving a notes app: what export actually gets you

Every notes app has an export button, and every export button technically works. The gap between “my notes exported” and “I can still use my notes” is where the disappointment lives.

The right time to test this is before you move in, not when you are trying to leave.

What export actually preserves

Text usually survives

Plain body text is the safest thing in any export. If your notes are mostly paragraphs, most tools will give you something readable.

Formatting often degrades

Headings, tables, checkboxes and callouts are app-specific constructs. On export they become whatever the target format supports. A checklist may arrive as a bulleted list where every item is a literal [ ].

The text is there. The behaviour is gone.

Attachments are the real risk

Images and files are usually exported as separate assets with links pointing at them. Whether those links still resolve depends on how the export was structured and where you unpack it.

A common outcome: a ZIP containing the notes and a folder of assets, with relative links that work only if you keep the exact folder structure forever.

Internal links break

If your notes link to each other, those links point at the old app’s identifiers. In a different app they lead nowhere.

This is the single most damaging part of a migration, and it is not visible until you try to navigate your own archive.

The test to run before you commit

Do this with a small set of notes rather than your whole archive:

1. Create five notes that include a heading, a table, a checklist, an image and a link to another note.
2. Export them.
3. Open the export in a different app or a plain text editor.
4. Try to navigate from one note to the other using your own link.

If the link works and the attachment still opens, the export is genuinely portable. If not, you have learned something important for the price of ten minutes.

Markdown is the pragmatic middle

Markdown is not perfect. It cannot represent every app-specific feature, and complex databases do not survive the trip.

What it does offer is that your text stays readable in almost anything — a text editor, a code repository, another notes app. For notes you intend to keep for years, that durability is usually worth more than feature fidelity.

The trade-off is honest: plain Markdown loses the structure that made the app pleasant. You are choosing longevity over convenience.

Sync versus ownership

A subtle trap: some apps sync your notes but do not export them in a useful form. The data is technically available and practically locked in.

The question to ask is not “can I see my notes?” but “if this service shut down tomorrow, could I rebuild somewhere else in an afternoon?” For many modern note tools, the honest answer is no, because the value is in the structure and links, not the words.

What to do about it

• Test export before you migrate in. Ten minutes now versus a weekend later.
• Keep anything irreplaceable in a format you can read without an app. A plain text file will outlive almost every company.
• Avoid deep proprietary structures for archival material. Databases and relational links are convenient and fragile.
• Re-test the export once a year. Export quality changes, and it usually changes without an announcement.

How we examined this

This piece is built from documented export formats, the structure each app exports to, and the migration failure patterns that recur across note tools. It is not based on a personal migration of a full archive.

What that analysis surfaces:

• Plain text survives everywhere. Nothing in a text export is ever lost.
• Structure degrades in every migration. Checkboxes, tables and callouts simplify to whatever the target format supports.
• Internal links fail consistently. Links point at the old app’s identifiers and lead nowhere in a different tool.
• Attachments survive only with the original folder structure intact. Unpack carelessly and the images are orphaned.

The ten-minute export test above is the practical way to verify this against any specific tool.

Caveats worth stating

This is a study of export mechanics, not a ranking of apps. Export quality varies by tool and changes with versions, so verify the current behaviour rather than relying on any general claim.

This covers text-based notes. Notebooks with embedded databases, formulas or detailed page structure may behave very differently, and often worse.

And the honest conclusion is uncomfortable: there is no fully portable notes app for complex structure. If portability matters more than features, choose a plain format and accept fewer features. If features matter more, accept that leaving will cost you something.