Exit and transition planning: documents to prepare
Exit and transition planning starts before a technology contract ends, not after notice is served. The client needs an asset and data inventory, an agreed transition plan with dated checkpoints, and a fallback route if the provider does not cooperate. The documents to prepare cover data return, licence termination, and knowledge transfer to the incoming team.
What changes once exit planning starts
A technology contract usually names an exit period during which both sides prepare for termination. Once that period opens, the timeline for data return, system migration, and handover of documentation becomes fixed by the contract, not by either side's preference. Missing a step inside this window shifts risk onto the client, because most contracts treat silence as acceptance of the provider's proposed terms.
The window is short in practice. Teams that start document preparation only after notice is served lose weeks they do not have, and the receiving team then inherits gaps rather than a clean handover.
Documents to prepare
| Document | Purpose | When to prepare |
|---|---|---|
| Asset and data inventory | Lists systems, data sets, and access rights held by the provider | Before notice is served |
| Transition plan | Sets out migration steps, responsible teams, and target dates | Within the first weeks of the exit period |
| Data return and deletion confirmation | Confirms data has been returned in a usable format and copies deleted | Before the contract ends |
| Licence and access termination notice | Closes accounts, keys, and integration credentials | On or shortly after the end date |
| Knowledge transfer record | Documents configuration, workflows, and known issues for the incoming team | Throughout the exit period |
What to do
- The contract owner reviews the notice period and confirms the exit window in writing.
- The technical lead compiles the asset and data inventory before the provider is notified.
- The project manager agrees a transition plan with the provider and sets dated checkpoints.
- The legal contact checks the data processing terms for return and deletion obligations; see the Data processing agreement overview and the deadline.
- The receiving team tests migrated data and systems before sign-off.
- The contract owner confirms termination of licences and access once migration is verified.
Who decides
The client's contract owner decides when notice is served and confirms the exit date. The provider's account manager confirms the transition plan on its side. Disputes over scope or cooperation typically go first to the escalation contacts named in the contract, then to the forum set out for dispute resolution there. The length of the exit period comes from the contract itself, not from either side unilaterally.
Scenarios
If part of the service runs through a subcontractor abroad, the transition plan needs a parallel handover from that subcontractor, not a single handover from the main provider alone.
If a subprocessor requires separate approval before data can move to the new provider, that approval step runs alongside the main transition plan, not after it.
If the provider does not respond to the transition plan, the client documents each attempt and escalates through the named contacts before treating the silence as a breach.
What this page does not cover
This page sets out the documents and steps for exit and transition planning. It does not resolve a substantive dispute if the provider refuses to cooperate, and it does not cover separate filings triggered by a change of processor. It does not name a jurisdiction or a fixed notice period, because both come from the contract in question, not from a template.
Related reading
The subprocessor approval process runs as a parallel track when the incoming provider is a group company or a chain vendor; see Subprocessor approval process: documents to prepare.
Verified
Reviewed 20 March 2025. Sources: contract exit clauses reviewed in practice and provider transition schedules as filed with the client.
Where a report already exists on a specific counterparty, the underlying check is handled separately from this planning page; see Counterparty in Switzerland and its limits in practice.
The same separation applies to document types encountered during a transition; see Document in Italy explained.
Next steps
If enforcement is already being sought against a data holder connected to the exit, treat that as a separate track from the transition plan; see When enforcement is sought against a holder step by.
If the outsourcing provider subcontracts abroad, check the limits of that arrangement before signing off the transition plan; see When the outsourcing provider subcontracts abroad and its limits.
Get in touch and a partner responds within minutes during business hours. A quote follows within one business day.
FAQ
How long does exit and transition planning take in practice?
The length of the exit period is set by the contract, not by a general rule. The transition plan runs inside that window, and the checkpoints agreed at the start decide whether the handover finishes on time.
Which documents are needed to start?
Work begins with the asset and data inventory, since every later document depends on knowing what the provider holds. The transition plan, return and deletion confirmation, and knowledge transfer record follow from that inventory.
What happens if the other side does not respond?
The client records each attempt to contact the provider with dates and channels used. Escalation follows the contacts named in the contract before the silence is treated as a breach, since an undocumented attempt carries little weight later.