Assessing cloud portability: Your migration and exit strategy checklist

Moving your data out of the cloud should be part of your buying decision, not an afterthought. Before you sign, look at what you’ll be able to take with you, what leaving will cost, and how long you’ll pay for two systems at once. New rules such as the EU Data Act will remove some switching fees by 2027, so compare vendors carefully. Use this checklist to evaluate portability before you sign.
What is cloud data portability?
Cloud data portability means you can move your data from one cloud service to another, or back to your own systems, and still use it when it gets there. Getting your files out is only half the job. They also have to work in the new system.
The international standard ISO/IEC 19941 breaks portability into three parts:
- Format: Can the new system open the files?
- Meaning: Does the new system understand what each piece of data represents?
- Rules: Do the policies attached to your data, such as how long you keep it and who can see it, come along too?
A move can pass the first test and still fail the other two. Your data arrives, but it’s confusing, incomplete, or less secure than before.
Why should portability be a selection criterion?
The cost of leaving a cloud provider is part of the cost of choosing one. If you only compare today’s prices, you’re missing part of the bill.
NIST, the US standards body, makes this point in its cloud guidance. It says you can only know whether the cloud saves you money once you count all the costs, including the cost of moving away later. UK regulators agree that leaving can be hard. In July 2025, the Competition and Markets Authority concluded that fees for moving data out, along with systems that don’t work well together, make it harder for customers to switch providers or use more than one.
In short, a platform that’s cheap to join can be expensive to leave.
Which export formats should you ask about?
Ask each provider exactly what format your data will come out in. Then ask whether that format is open, well documented, and usable without the provider’s own software.
This matters because an export can meet the wording of your contract and still be hard to use anywhere else. NIST warns that export formats often don’t match between software platforms. It also notes that custom workflows, business rules, settings, and scripts are often built for one provider only.
Don’t take the provider’s answer at face value. During your trial, export a sample of your data and load it into another tool. You’ll quickly see what makes it through and what gets lost.
Will your metadata survive an export?
Metadata is the information that describes your data, and it can decide whether your exported data is still useful. Think of timestamps, owners, permissions, version history, tags, and the links between records. Lose these details and you can lose your audit trails and access controls too. That leaves you with gaps in your records and weaker security on the new platform.
Lawyers at DLA Piper note that in complex cloud services, the line between your data, its metadata, your settings, and system logs isn’t always clear. So get it in writing. Ask the provider which metadata you can export and in what format, then check it in your test export.
How to map migration dependencies
Your data rarely stands alone. It’s usually tied to other tools, logins, automations, and services that only work on one provider’s platform. Every one of these will need to be rebuilt or replaced if you leave, which means together they decide how long and how hard a move will be.
Start by listing:
- Every integration with other software
- How users sign in and get access
- Automated tasks and workflows
- Any services unique to the provider
NIST adds two more things to watch. Providers usually keep the right to change or remove the connections other systems rely on. Also, large exports can take a long time over a slow network. Write down which of your systems connect to the provider, and estimate how long a full export would take on your connection.
How to estimate future switching costs
To estimate switching costs, add up everything it would take to leave: transfer fees, staff time, months of paying for two platforms, contract penalties, and retraining. Doing this before you sign gives you a fair way to compare providers whose prices look alike today.
| Cost | What to check |
|---|---|
| Data transfer fees | Exit fee waivers and their conditions |
| Notice and transition | How long the contract allows for exit |
| Early termination | Penalties for leaving mid-term |
| Parallel running | Months of paying for both platforms |
| Labor | Rebuilding integrations and testing |
The rules are starting to change in some markets. According to DLA Piper, the EU Data Act will stop providers serving EU customers from charging switching fees, including fees for moving data out, from January 12, 2027. But DLA Piper also points out that providers’ own fee waivers often come with conditions. Read the fine print closely.
Before you sign, ask every provider on your shortlist to answer your questions on formats, metadata, and exit costs in writing.
Keep your options open
The best time to plan your exit is before you commit. Our cloud advisory team can help you test your exports, map what your data depends on, and estimate the true cost of switching, so you can choose a platform without getting locked in. Talk to our team today to check your portability before you sign.