Overview with affiliate links. We receive a commission if you click through via us. Read how
Compare

Cloud exit plan: how to make data and applications portable

An exit plan describes in advance how you get data and applications out of a cloud environment, under which conditions and with which costs and risks.

Door de redactie van ClouwinoGepubliceerd Laatst bijgewerkt

Short answer

A cloud exit plan describes how you get your data and applications out of a service and put them back into use elsewhere, under which conditions and within what time. You draw it up before you sign a contract and test it with regular trial exports.

Who is it for: Architects, buyers and risk managers who want to keep a cloud dependency manageable, including in regulated sectors.

Why do you need an exit plan?

Reasons to leave vary: a contract that expires, a supplier that changes course, an incident, a merger or a new rule. Anyone who only thinks about the route at the moment of leaving is in the weakest negotiating position.

For some sectors and frameworks, such as financial regulation, an exit plan may even be mandatory or expected. Whether and how this applies depends on the sector, the service and the region; have it checked legally and by your security and compliance team.

What belongs in an exit plan?

The plan is usable if it is specific. Describe per service what needs to happen, by whom and in which order.

How do you make data and applications portable?

Portability is created at the design stage, not at the moment of leaving. Store data in open, documented formats and avoid export routes that only work through the graphical interface. Describe infrastructure and configuration as code, and keep applications as separate as possible from specific platform services.

Also take into account what falls outside the data: identities, keys, log files, settings and the knowledge in the team. Without those elements, a restored dataset is not yet a working system.

How do you test the plan?

An exit plan that has not been practised is an assumption. Test it in steps.

  1. Run a trial export of a representative dataset and measure duration and completeness.
  2. Restore the export in another environment and check integrity and access permissions.
  3. Run a test version of an application on the alternative platform.
  4. Document findings, costs and bottlenecks, such as data traffic.
  5. Repeat after major changes and when the contract is renewed.

Components of the exit

What you arrange per component and why.
ComponentWhat you recordRisk if you miss it
DataFormat, completeness, metadataUnusable or incomplete export
ApplicationsPortable configuration and dependenciesLengthy rebuild
ContractCooperation, deadlines, deletionNegotiating under time pressure
CostsData traffic, parallel running period, project costsUnexpected expenses
SecurityKeys, access and erasure of dataResidual data or loss of access

Who is it not ideal for?

Frequently asked questions

When do you start on the exit plan?

At selection, before signing. You can then include conditions in the contract and let the results of trial exports weigh in on the choice.

How do you make sure data is really deleted?

Record in the contract how and when deletion takes place and ask for written confirmation. Encryption with keys under your own control can help in addition.

Who owns the exit plan?

Usually the owner of the service, with input from architecture, security, procurement and legal. Schedule a fixed annual review.

Ask us
Compare Get in touch

Are you sure?