Frank
A company that won’t let you export your data doesn’t believe you have the right to leave. That’s it. That’s the whole thesis.
Everything else, the slick UI, the “free” tier, the “we care about your privacy” landing page copy is noise. The export button tells you the truth.
I wish someone had drilled this into me five years ago, before I wasted real time building things inside platforms I didn’t actually own.
The Lock-In Is the Product
Here’s what I got wrong for a long time: I thought vendor lock-in was a side effect of bad platform design. It isn’t. For a lot of companies, lock-in is the deliberate architectural goal. The harder it is to export your data, the more painful it is to leave, and the longer you stay. That’s not an accident. That’s a retention strategy.
I’ve seen it in enterprise IT too, not just consumer apps. After nearly 17 years at the same health system, I’ve watched vendors make their migration path deliberately painful enough that “staying” starts to feel like a technical decision. It isn’t. It’s just inertia they engineered.
The tell is always the same: data goes in fast, easy, frictionless. Getting it out requires a support ticket, a 30-day wait, a CSV with half the fields missing, or a premium plan.
That asymmetry is intentional.
What I actually check now, before I invest time in any platform:
- Can I export everything, not just some things, in a format I can actually use?
- Does the export work without contacting support?
- Is the exported format open or proprietary?
- If the company disappeared tomorrow, what would I lose?
That last question is the sharpest one. I run Emby for my personal media library across four NAS units at home. I use Trilium Notes for my AI music catalog, over a thousand songs tagged, organized, lyrics and metadata attached. Both are self-hosted. My data lives on hardware I own. If either project went dark tonight, I’d lose a UI, not my work.
That’s the distinction that matters.
The “but switching is hard” excuse works in their favor, not yours. I hear people defend bad export tools by saying the data is complex, migration is complicated, or it’s just “how the industry works.” That’s rationalizing on behalf of a company that has no particular loyalty to you.
Switching should be your call, made on technical merit. Not a punishment for wanting to leave.
I’m not saying every platform with a mediocre export tool is malicious. Some of it really is just bad engineering, and I’ve written enough clunky code myself to give credit for that. But there’s a difference between a rough export experience and a platform that structurally makes leaving expensive.
When a company patents their data format, buries the export option four levels deep in settings, or hands you a file that requires their own tools to read, that’s not an accident. That’s a wall they built and called a feature.
Five years ago I would have shrugged and kept building. Now it’s one of the first things I check.
The exit door tells you more about a company than the front page ever will.
