If you can't export your data in a readable format, that data isn't really yours.

It sounds like a strong claim, but it holds up under testing: imagine wanting to leave a service where you've accumulated years of notes, and discovering that the only available export is a PDF of everything stuck together, or a CSV that loses the structure, or a proprietary format readable only by the app itself.

At that point, you're locked in. The data is there, but you can't move it. It's a form of lock-in that's invisible until you try to leave.

Markdown as a de facto standard

The simplest way to guarantee portability is to use a format that outlives services. Markdown is the natural candidate for text notes.

A .md file is readable on any operating system, in any editor, even fifty years from now. It doesn't require special software to be opened, edited, indexed. Basic formatting (headings, lists, links, bold) is understood everywhere.

A service that saves in markdown is implicitly declaring: your data is readable even without us. It's a silent promise of non-lock-in.

Services that save in proprietary format are saying the opposite, even if they don't say it out loud.

What "portable vault" means

A portable vault is a folder of files. Nothing more, nothing less.

You open that folder, there are .md files with your content. The filenames make sense (project-x.md, not note_2348234.bin). Internal links are normal markdown links or wikilinks ([[other-note]]), not opaque IDs. The folder structure reflects your organization, not one imposed by the service.

From that folder you can:

  • open it in any text editor,
  • load it into another compatible service,
  • version it with git,
  • back it up with any standard tool,
  • inspect it by hand, file by file, if needed.

That's real portability, not declared.

The day-1 rule: self-assessment test

The magic question: if I wanted to leave here tomorrow, where would my data end up?

Three possible answers, three clear verdicts:

  • ✅ Yes — "I export the vault folder to my computer." Structurally portable service.
  • ⚠️ Almost — "I use a proprietary export that generates a JSON dump I'd then need to convert." Less portable service.
  • ❌ No — "I write to support and ask politely." Effectively closed service.

This question should be asked on day one, not on the day you want to leave. The day you want to leave is already too late.

When export is an upsell

Some services put structured exporting behind a premium tier. It's a widespread practice, and worth attention.

Charging to export your own data means, in essence, charging to leave. Technically it's a business model; ethically it's a line worth watching. A service confident in its own value doesn't need to make leaving expensive: people who are happy don't leave.

When exporting is an upsell, it's reasonable to read it as a warning sign.

An example

A thousand notes in a cloud service, accumulated over three years of work. I decide to migrate.

Case A: the service exposes the vault as a folder of .md files. I download the folder, open it in another compatible tool. Ten minutes, zero loss.

Case B: the service offers a "complete JSON export". I download, open: each note is a mess of disordered code, readable only by computers, that destroys the layout of your text. Attachments with IDs, links replaced with internal references. To read the content I need a conversion script I have to write myself or ask someone for. Half a day, partial loss of formatting.

Case C: the service offers no structured export. I can screenshot, copy-paste by hand, or delete the account and accept losing everything. Weeks, or surrender.

Same user, same data. The difference is only in the architecture of the service.

Consequences

Portability isn't a nice-to-have. It's editorial infrastructure, and it should be treated as such: guaranteed by design, not granted case by case.

For those who build services, it's a silent promise made to the customer. For those who use them, it's the first thing to verify before investing one's work on top.

Try Timo free for 15 days — timoai.xyz. No credit card required.