Avoiding vendor lock-in: what to look out for
Vendor lock-in is the situation in which switching to another supplier becomes so expensive, time-consuming or technically difficult that in practice you no longer do it, even if an alternative is better or cheaper. The risk applies to SaaS packages and cloud platforms, but also, often underestimated, to custom software. This page shows which forms of lock-in exist, how to recognise them before you sign, and which measures actually protect your freedom of choice. Torn between a package and your own platform? Also see our build-vs-buy assessment.
Discuss your situation Go to the checklistWhat vendor lock-in actually is and why it matters
Vendor lock-in doesn't arise on the day you sign a contract, but in the years afterwards, as data, processes and team knowledge accumulate within one supplier. At that point the balance shifts: you no longer decide whether to stay; the costs and risks of leaving decide for you. It is most evident with SaaS packages (CRM, ERP, HR systems) and cloud infrastructure, but at least as often with custom software whose architecture only the builder understands.
Why is this more than a theoretical risk? Three reasons come up most often in practice. First, negotiating position: a supplier that knows switching is unrealistic has little incentive to keep prices competitive. Second, agility: if a new business process or integration doesn't fit within the limits of your current system, you can't simply switch to make it possible. Third, continuity: suppliers get acquired, discontinue a product line or change their roadmap; without a way out, you carry that risk entirely. The Microsoft 365 outage of November 2026 showed what that looks like in practice.
Four forms of vendor lock-in
Lock-in is not a single, clear-cut risk. It arises at four different layers, and each layer calls for a different measure.
Data lock-in
Years of records, reports and customer data end up stored in a system that offers no usable export, or only in a proprietary, undocumented file format. Without re-entering that data by hand, you can't leave.
Technical lock-in
Proprietary architectures and closed formats make integration with other systems difficult. A counterexample shows how it can be done differently: the Amazon S3 API has become the de facto standard for object storage, which makes S3-compatible storage from other providers possible without rebuilding everything.
Contractual lock-in
Long contract terms, high termination fees or the absence of a clause on data transfer when a contract ends. This lock-in lies not in the technology but purely in the legal agreements. What a standard SLA does and doesn't cover during an outage is explained in the article on SLAs and compensation for Microsoft 365.
Knowledge lock-in with a single party
The architecture, code and workings of a system exist only in the head of one supplier or development partner. This is most pronounced with custom software without handed-over documentation; we go into this in more detail below.
Signs that you're already locked in
Four questions that, in practice, quickly show how locked in you are with your current supplier.
No usable export
You can only view data within the system itself and can't export it in a standard format such as CSV or JSON.
Unilateral price increases
The supplier raises rates and you have no realistic alternative within a reasonable timeframe.
Nobody else understands it
There is no up-to-date documentation and the knowledge of how the system works sits with one person or party.
Penalties for leaving
Termination fees or data transfer costs that bear no relation to the actual effort involved.
Custom software can cause lock-in too
Custom software is often presented as the answer to vendor lock-in: no off-the-shelf package, so no dependency. That is not automatically true. If you do not own the source code, if there is no up-to-date architecture documentation, or if only one small development agency genuinely understands the application, you are just as locked in as with a SaaS package. The only difference is that your supplier is called a development partner rather than a software vendor, and the dependency is often less visible because there is no annual licence invoice to remind you of it.
So ask every party that builds for you, whether that is us or another partner, the same questions you would ask a SaaS vendor: who owns the source code and documentation, does the codebase use mainstream, widely used technology rather than a unique in-house framework, is there up-to-date technical documentation that another party could take over, and what exactly happens if the collaboration ends. Low-code platforms carry a comparable risk at platform level: Mendix, OutSystems and Power Apps offer speed, but the application you build runs within their runtime and licensing model. Not sure whether low-code or custom development suits you better? Read our comparison of low-code and custom development.
Practical measures to prevent lock-in
None of these measures is a guarantee, but together they reduce the chance of ever being stuck without an alternative.
Choose open standards
Wherever possible, use systems with open, documented APIs. The S3 API is a good example: because it became the de facto standard for object storage, you can buy S3-compatible storage from multiple providers without rebuilding everything.
Require data portability
Ask for exports in common formats such as CSV, JSON or Parquet rather than a proprietary format. For personal data processed automatically on the basis of consent or a contract, you also have the right to data portability in the EU under Article 20 of the GDPR.
Put exit arrangements in writing
Reasonable notice periods and, where the impact of leaving is significant, a source code escrow agreement: the source code is deposited with an independent third party and released if the supplier stops trading or no longer meets its obligations.
Make documentation a delivery requirement
Architecture documentation, data model and API specification belong in the delivery, not in a separate appendix that will be added later. Without that documentation, every switch costs more than it needs to.
Checklist for a new software partner or package
Five questions to ask before you sign, whether it concerns a package, a SaaS subscription or a custom development project.
Export without help?
Can you export data in a standard format without depending on the supplier's cooperation?
Who owns it?
With custom software, do you own the source code and documentation, or do you only have a right to use the result?
What does leaving cost?
What are the notice periods, and what costs are involved in switching to another party?
Does documentation exist?
Is there up-to-date technical documentation that another party could genuinely take over?
If you do not get a satisfactory answer to any of these questions, that is not necessarily a reason to rule out the collaboration, but it is a signal to define the arrangements more precisely upfront rather than trusting that it will work out.
Frequently asked questions about vendor lock-in
An independent view of your software architecture
We build custom software and integrations with existing packages, and from the design stage we consider open standards and data portability, so you don't get stuck when you switch in the future.
Schedule a no-obligation conversation