Vendor lock-in can almost only be avoided before a contract is signed; it is virtually impossible to avoid once the contract is in effect. As soon as data, processes, and employee knowledge become tied to a system, the customer loses its bargaining power. The vendor knows this. Price increases therefore usually occur only after switching has become practically impossible.
Vendor lock-in must be prevented before signing the contract, not after. Three Clauses have the greatest impact: data delivery in an open format, documented interfaces, and the ability to terminate the contract without penalty fees. In addition, a reserve of the right to change prices and an escrow agreement further limit the risk.
Why Protection Against Vendor Lock-in Begins Before a Contract Is Signed
Protection against lock-in must be negotiated before the contract is signed, not after (credativ, 07/2026). Once the contract is signed, the customer has little leverage left, because switching providers involves costs, time, and risk—factors the provider is well aware of. Anyone who waits to negotiate these clauses until the price increase notice has already arrived in the mail is negotiating from a position of weakness.
price increase for many VMware customers after the takeover by Broadcom and the switch to a subscription model. Anyone deeply integrated on the technical side had no short-term alternative.
EntekSystems, 2025
This example is instructive because it had nothing to do with poor technology. The companies involved were satisfied with the software. They simply didn't have a contract that provided them with an affordable way out.
The Three Most Effective Safeguards
According to an analysis by credativ, there are three clauses that make the biggest difference (credativ, 07/2026).
- Data output in a machine-readable, open format. The contract must specify that all data can be exported at any time in a standard format, not just in the provider’s proprietary format. Without this clause, your data is effectively locked into the provider’s system.
- Interoperability via documented APIs. The provider must disclose how other systems can be technically integrated. Without this documentation, any subsequent integration becomes a guessing game or results in a paid add-on order from the same provider.
- Cancellation without penalty fees. A clear, time-limited notice period with no hidden termination fees prevents switching from being made artificially unattractive from a financial standpoint.
| Clause | What It Covers | What happens without it |
|---|---|---|
| Data release | Export to CSV, JSON, or XML—anytime and at no extra charge | Your data remains in the provider's system |
| Interoperability | documented, open interfaces | Each integration will be a paid add-on order |
| Termination | fixed notice period without penalty fees | Exit is made financially unattractive |
| Price adjustment clause | Upper limit or index-linked | The provider raises its rates as soon as switching becomes expensive |
| Escrow | The source code is held by an independent third party | If the provider goes bankrupt, operations come to a halt |
A price change clause should be limited or tied to a transparent index, rather than giving the provider free rein (credativ, 07/2026). For proprietary software whose source code remains with the provider, it is also recommended to enter into an escrow agreement, under which the source code is deposited with an independent third party and released in the event of the provider’s insolvency.
The Value of Clauses Against Vendor Lock-in in Negotiations
Not every provider accepts all three clauses without hesitation. Larger providers with a strong market position are often reluctant to negotiate data export formats because it is precisely this lock-in that underpins their business model. In this case, it helps to treat the clauses as part of the basic request for proposals, rather than as an optional add-on. A provider that categorically rejects open data export should be required to openly justify this refusal. Often, the extent of the lock-in risk becomes apparent even before the contract is signed.
How far an existing legacy system landscape has already aggravated this risk often only becomes visible when a modernization decision is due, as described in our article on modernizing legacy software . And anyone who puts exit costs into the budget from the outset will find the matching line items in the article on hidden costs.
Review the Draft Contract for Lock-in RisksSend us the draft. We'll let you know which of the five clauses are missing and how you can renegotiate them.
Frequently Asked Questions
What, specifically, should be included in the data disclosure clause?
The clause should specify that data can be exported at any time in an open, machine-readable format such as CSV, JSON, or XML, without any additional fees or waiting periods. It is also important that metadata and history be included in the export, not just the raw data (credativ, 07/2026).
What is an escrow agreement, and when is it needed?
An escrow agreement deposits the source code with an independent third party. If the provider goes bankrupt or ceases operations, the code is released, and the customer can continue operations on their own. This is particularly advisable for proprietary software from a smaller or financially unstable provider (credativ, 07/2026).
Does open source automatically protect against vendor lock-in?
Open source reduces risk because the source code is generally accessible and can often be further developed, even without the original provider. However, it does not provide complete protection. Knowledge, configuration, and operational experience often remain tied to a specific service provider unless this is actively documented.
The Next Step
torck builds custom software so that data and source code stay with the client, with development teams in Maxhütte-Haidhof, Vienna, and Rabat for industry and retail. We negotiate escrow and export clauses before the project starts. The contract runs with the German torck GmbH. In the Initial Consultation we talk about the contract structure that fits your project.
German 
English 
French