When a migration is blocked by an exit clause: what it costs to be wrong
An exit clause that blocks migration usually withholds one specific thing: data export, source-code access, or transition assistance, until stated conditions are met. Moving before those conditions are satisfied risks a breach claim, forfeited assistance, and exposure under software-protection rules. The real cost of being wrong is lost leverage and unplanned downtime, not legal fees alone.
The legal basis
Most exit-clause disputes in technology contracts turn on rights over software, not on the wording of the clause alone. Where the incumbent's platform is protected as a computer program, the relevant instrument is Directive 2009/24/EC. It sets out what a rightholder controls and what a lawful user may do with a program already in use, including limited interoperability access.
The directive does not fix a formula for what counts as sufficient assistance during a migration. That boundary is set by the contract itself and, where the contract is silent, by what the directive treats as inherent to lawful use rather than as a separate concession from the vendor.
What changes in practice
Two clocks start the moment an exit clause is invoked. The notice period set by the contract begins running immediately, and it does not pause for negotiation. A second, informal clock runs alongside it: an incumbent's willingness to cooperate tends to narrow the longer a scope dispute stays open.
Acting on an assumed right, before the vendor confirms it in writing, turns a contractual disagreement into a live claim. That claim is harder and slower to unwind than the disagreement it replaced.
What to do, in order
Six actions matter here, and the order is not optional.
| Step | Action | Owner | Sign it is overdue |
|---|---|---|---|
| 1 | Read the exit clause against today's date and locate the notice period | Contract owner | Notice period already running |
| 2 | List every dependency the incumbent controls: data, credentials, source code, escrow | IT lead | Dependency undocumented |
| 3 | Request written confirmation of the assistance the clause actually promises | Procurement | No written scope after first request |
| 4 | Hold off extracting code or data outside the channel the clause names | Engineering | Extraction attempted informally |
| 5 | Where personal data moves as part of the migration, check the lawful basis; our Legitimate interest assessment overview sets out how to document it | Data protection lead | No documented basis |
| 6 | Escalate disputed points to the forum the contract names before notice lapses | Legal | Notice period near expiry |
Who decides
The forum is the one the contract names for disputes: an internal escalation committee, mediation, or the arbitration or court set out in the governing-law clause. Absent a named forum, jurisdiction follows the governing-law and forum-selection clauses in that same contract, not either party's preference.
Evidence that decides scope disputes is documentary: the notice sent, the date it was sent, and any written response confirming or denying the assistance requested. Verbal assurances carry little weight once a dispute is escalated.
If your situation differs
If the exit clause sets a fixed transition period, the countdown starts on the date notice was served, not on the date migration work actually begins.
If the vendor disputes what counts as assistance, put the disagreement in writing and escalate under the clause's own procedure rather than pausing informally while positions harden.
If part of what is being migrated includes tokenised records held on a distributed ledger, an exit clause drafted for off-chain systems may not reach it. A transfer on-chain is not recorded off-chain tokenised rights covers that gap separately.
What this page does not cover
This page does not value the migration itself, and it does not draft or renegotiate the exit clause on your behalf. It does not assess a specific vendor's conduct.
Before appointing a developer to build the replacement, a check on the counterparty can surface control issues before they turn into exit-clause disputes. Counterparty report before appointing a developer: what to do covers that check.
Where the underlying dispute traces back to contract dates that no longer match a public register, a separate check applies. Document report when dates do not match the register sets that out.
Related situations
The mirror case, where the trigger is a new processor rather than a blocked migration, is covered separately. When personal data flows to a new subprocessor step sets out that path.
Verified
Verified as at 10 March 2025. Source referenced by title: Directive 2009/24/EC. No article-level citation is made, because this analysis rests on the directive's overall allocation of rights between rightholder and lawful user, not on a single provision.
Frequently asked questions
What is the first step when a migration is blocked by an exit clause?
Read the exit clause against today's date and identify which notice period, if any, is already running. Confirm this before any other action.
Which deadline is already running?
The contractual notice period starts on the date the clause is invoked, not on the date migration work begins. Check the contract's own definition of that trigger.
Who decides, and on what evidence?
The forum named in the contract decides, based on documentary evidence: the notice served, its date, and any written confirmation or denial of the assistance requested.