Vendor lock-in and data portability: knowing your exit before you sign up

People choose software by its features and its price, and almost never by how hard it is to leave. That is backwards, because the cost of a tool is not just what it charges while you stay — it is what it costs to get out. Lock-in is the gap between those two, and it is decided long before you ever want to switch.

What actually creates lock-in

Three things, in increasing severity. The mild kind is inconvenience — your team's habits and integrations are built around the tool. The real kind is your data: if your work lives in a proprietary format with no clean export, leaving means losing or painstakingly converting it. The severe kind is architectural — the software is so woven into your processes that removing it is a project, not a switch. The first is survivable; the last two are what turn a reasonable tool into a trap.

The checks to run before you commit

Ask, in writing, before you sign: can I export all my data, in an open or documented format, at any time? Is there an API so I am not dependent on the vendor's export button? What happens to my data if I cancel — is it deleted, retained, or held hostage? And how portable is the format — could another tool import it? A vendor that answers these crisply is confident; one that is vague about export is telling you something. These are the same questions behind the right-to-portability idea in data security compliance, applied commercially.

Why it matters more than the monthly price

Software changes: prices rise, features get cut, companies get acquired or shut down. The subscription creep that quietly raises costs is covered in the subscription audit; lock-in is what stops you acting on it. A slightly dearer tool you can walk away from is often the cheaper choice, because it keeps the decision reversible — the same logic as preferring local control in the smart-home local-vs-cloud piece. Choose for the exit as much as the entrance, and no single vendor ever owns you.