When a migration is blocked by an exit clause: what to do first
An exit clause that blocks migration is rarely broken; it is being read narrowly by one side. The first task is to locate the exact clock the clause starts — notice period, data-return format, or assistance-fee trigger — because each has a different remedy and a different deadline that is already running.
The legal basis
An exit clause is a contractual mechanism. No EU act sets its notice period, its data-return format, or its fee schedule; those terms come from the contract and the governing law the parties chose. Two EU acts bear on what surrounds the clause, without governing the clause itself.
If migration involves copying, adapting, or accessing the vendor's software to achieve interoperability with a replacement system, the baseline protection for that software sits in Directive 2009/24/EC. That protection does not disappear because an exit clause is disputed.
If either party qualifies as an essential or important entity within the scope of Directive (EU) 2022/2555 (NIS2), risk-management and incident-reporting duties keep running on their own statutory clock, independent of what the contract says about timing. A vendor cannot use a live exit dispute as a reason to delay a report that NIS2 requires.
What changes in your timeline and risk
While the parties argue over wording, three separate clocks keep moving. Treat the legal disagreement and the operational deadline as two different tracks, because conflating them is how deadlines get missed.
| Clock | Starts running when | What can reset it |
|---|---|---|
| Notice period | A written notice invoking the exit clause is served | An incomplete notice, if the clause sets minimum content |
| Data-return window | The notice period ends, under most exit clauses | A written extension agreed by both sides |
| Assistance-fee trigger | The vendor confirms migration assistance is due | A separate dispute over the fee schedule itself |
A dispute over the wording of the clause does not pause any of these three clocks by itself. Only a written agreement to extend does that.
What to do first
- Your operations lead pulls the exact notice period from the contract and confirms the date on which it started running.
- The IT lead freezes further configuration changes to the system under migration, so there is no later dispute over what state must be returned.
- Legal counsel sends a written notice invoking the exit clause by its clause number in the contract, without paraphrasing what the clause says.
- Procurement requests, in writing, the data-return format and any conversion assistance the clause promises.
- IT preserves logs, correspondence, and configuration snapshots before the vendor's access to the system is reduced.
- Legal counsel escalates to the dispute-resolution forum named in the contract once the notice period lapses without cooperation.
The evidentiary problem is not unique to platform migrations: the same fracture appears when a fork duplicates the token and the evidence splits between two records, and the fix is the same in both cases — freeze first, argue afterwards.
Who decides, and on what evidence
The forum is whatever the contract names, usually arbitration or the courts of the jurisdiction stated in the governing-law clause. That forum decides on documents, not on intent: the notice as sent, the timestamp it was received, the configuration snapshot taken before access changed, and the correspondence about the return format.
A decision on a blocked exit typically turns on three questions: was the notice validly given under the clause's own requirements; does the offered return format match what was promised; and was the fee schedule invoked correctly, or invoked at all. Whoever can show a clean paper trail on these three points controls the timeline, regardless of which side is technically correct on the underlying dispute.
If you are in one of these situations
If the vendor claims the notice period has not started because the notice went to the wrong address, serve a fresh, clearly compliant notice immediately and treat the first notice as protective only.
If the exit clause ties migration to payment of an outstanding invoice, keep the payment dispute and the data-return obligation in separate correspondence threads. Conflating the two lets the vendor delay both at once.
If the vendor is an essential or important entity under NIS2 scope and refuses cooperation during the dispute, note that its incident-reporting duty under Directive (EU) 2022/2555 (NIS2) continues regardless of the contract disagreement, and raise that point separately with your own risk team rather than inside the exit negotiation.
What this page does not resolve
This page does not draft the exit notice, does not calculate a fee under a specific clause, and does not replace a careful reading of your own contract's governing-law and dispute-resolution terms. For how this firm is set up and its limits, see how the firm is set up and its limits.
Sources and limits
Checked: this page reflects the two EU acts cited above as currently published; Directive (EU) 2022/2555 (NIS2) took effect on 18 October 2024, and its national implementation varies by member state. Directive 2009/24/EC has been in force since 25 May 2009 and has not been substantively revised.
Where the vendor is registered in Denmark, a corporate check narrows part of this uncertainty within a day: Counterparty in Denmark and its limits in detail.
A parallel check on the contract itself, including whether the version you hold is the signed one, is covered separately: Document in Denmark and who decides.
Related situations
A related fracture appears on the data side of the same migration: When personal data flows to a new subprocessor walks through the parallel notice problem when a subprocessor changes mid-contract.
Frequently asked questions
What is the first step when a migration is blocked by an exit clause?
Identify which clock the vendor is relying on — notice, data-return format, or fee trigger — and confirm the date it started. Everything else follows from that date.
Which deadline is already running?
Usually the notice period, counted from the date a compliant written notice was served. If no compliant notice has been served yet, no deadline has started, and that is itself worth confirming in writing.
Who decides, and on what evidence?
The forum named in the contract, usually arbitration or the courts under the governing-law clause. It decides on the notice, the timestamped correspondence, and the configuration record taken before access changed.