4 MIN READ · PRACTICAL GUIDE
A cloud contract can promise portability while the practical route out remains uncertain. Before relying on an exit clause, test whether another team can use the exported information to continue a real business process.
This is an operational planning guide for European business buyers. It does not determine whether a particular contract or service falls within a legal requirement.
Understand what rules can and cannot solve
The European Commission’s Data Act explainer describes requirements intended to reduce obstacles to switching data-processing services. It says switching charges, including relevant data-egress charges, are to be removed from 12 January 2027. The scope and exceptions matter, and this is not a promise that every migration task or replacement service is free.
The same guidance distinguishes portability expectations for different service types. Do not interpret a general right to switch as a guarantee that a new application will reproduce every proprietary workflow. Check the current law and the actual contract with an adviser when the legal position affects a material decision. The EU position should not automatically be assumed to apply to a UK-only contract.
Build an inventory around business continuity
Start with a simple question: what would be missing if access to the old application ended tomorrow? The answer usually includes more than the main transaction table. Think about attachments, comments, audit events, custom field definitions, approval states, identity mappings and references between records.
For an illustrative purchasing system, an exported invoice without its purchase-order relationship may be readable but operationally incomplete. Similarly, a list of users without their permissions does not reconstruct an access-control model. Identify which data is necessary for operations, which must be retained for a legitimate reason and which should not be migrated at all.
| Exit item | Question to prove | Suggested owner |
|---|---|---|
| Business records | Can the receiving system interpret IDs, currencies and dates? | Process owner |
| Files and attachments | Do links still point to accessible files? | Application team |
| Access and permissions | Who can see or change each class of information? | Security owner |
| History and evidence | Can a past decision be reconstructed? | Record owner |
| Deletion and closure | What remains after termination, and why? | Contract and privacy owners |
Run a small exit rehearsal
Choose a limited but representative dataset. Include one ordinary transaction, one correction and one record with an attachment. Export it using the method the vendor commits to support. Have someone who did not create the export attempt to reconstruct the workflow from the documentation.
Record row counts and a few meaningful totals before and after transfer. Where values differ, investigate rather than assuming the file format is the explanation. Test how timestamps, decimal separators, currencies and character encodings are handled. These details can matter to teams working across European entities and languages.
Next, test dependencies. A scheduled report may depend on a proprietary calculation. An integration may use a provider-issued identifier. A workflow may rely on a person whose account will be deactivated during the change. Document the replacement decision for each dependency, including the cases in which a manual temporary process is acceptable.
Set a go/no-go decision point. If acceptance tests fail, decide whether the transition pauses, access is extended or a reduced service is used. The person with authority to make that decision should not discover the responsibility on the cutover weekend.
Separate contractual charges from your own transition effort
A reduction in provider switching charges does not remove the cost of your staff’s time, a new implementation, data correction or parallel operation. Model those costs explicitly. Our three-year SaaS cost model includes an exit allowance to make the issue visible rather than to predict an exact bill.
Ask how long read-only access remains available, how final exports are delivered and what evidence confirms the agreed closure. A termination letter is not the same thing as a completed operational handover.
Frequently asked questions
Is a CSV export enough?
Only when it contains the data and relationships your next process needs. The file extension alone does not establish completeness or usability.
How often should an exit plan be checked?
Revisit it when the service scope, integrations or data model changes, and before renewal. The appropriate interval depends on how critical and changeable the service is.
Source and scope
Primary source checked 14 November 2026: European Commission: Data Act explained, Chapter VI. The inventory and rehearsal process are our operational suggestions. Obtain legal advice on the requirements applicable to a specific contract.