The Hidden Cost of Switching Apps Is Your Data

The longer you use an app, the less its price tells you about the cost of leaving it.

A notes app can hold five years of excerpts. A tracker can contain thousands of observations. A reading app can accumulate highlights and annotations. At some point the software is not merely a tool you know how to use. It is also the container for work you have already done.

That accumulated data creates a switching cost.

The expensive part is reconstruction

Suppose a new app is clearly better and takes two hours to learn. That sounds like a cheap switch. But the old app contains 2,000 notes, carefully dated logs, or years of highlights. If those records cannot move, the real choice is different: abandon the history, keep two systems indefinitely, or spend time rebuilding the old collection by hand.

The price of the new app may be the smallest number in the decision.

“Export” can mean very different things

An app may offer a backup file that perfectly restores the collection into another copy of the same app. That is useful. It protects against device loss and failed upgrades.

It is not necessarily portability.

For switching, the relevant question is whether unrelated software can read the output. A proprietary backup whose structure only the original app understands may be excellent for recovery while doing almost nothing to reduce the cost of leaving.

A portable export usually uses a common, documented, broadly supported format such as CSV, Markdown, plain text, JSON, HTML, or another format appropriate to the data. The exact format matters less than whether there are multiple realistic destinations for it.

Usable data matters more than perfect migration

No export format preserves every feature. A tag hierarchy may flatten. Rich formatting may simplify. Links between records may need repair. An app-specific status field may become an ordinary column.

That can still be a successful exit.

The right standard is not “Can the new app reproduce every screen exactly?” It is “Can I retain the information that would be expensive or impossible to recreate?” For a clipping archive, that may be text, source, notes, tags, and dates. For a personal log, it may be timestamps and entries. For highlights, it may be book, location, quotation, and annotation.

Test the exit before the collection becomes valuable

The best time to discover that an export is unusable is when an app contains twenty records, not twenty thousand.

Before committing heavily to software that will hold durable information, make a small export. Open it outside the app. Inspect the fields. Try importing or analyzing it somewhere unrelated. A button labeled Export is less informative than the file it produces.

Switching cost can change the economics of a cheap app

A free tool can become expensive to leave. A paid tool with strong exports can remain relatively cheap to replace.

This is why purchase price and exit cost should be evaluated separately. Software that holds trivial or temporary data may not need elaborate portability. Software that is expected to hold years of intellectual work, records, or personal history should face a higher standard.

The OECD has examined data portability as a competition issue because usable portability can reduce switching costs and lock-in. Its 2024 review also makes an important qualification: portability works only to the extent that receiving services can effectively use the transferred data. The OECD paper is here.

A five-minute exit test

1. Export a small sample.
2. Identify the file format.
3. Open it without the original app.
4. Check whether the important fields are present.
5. Ask what other programs could realistically use it.
6. Keep a copy somewhere independent of the app.

If the answer to step five is “only this app,” you may have a backup system. You do not yet have much of an exit path.