After the Last Workload Moves: Five Cloud Contract Terms That Shape the Estate
Photo: Foreign, Commonwealth & Development Office, CC BY 2.0, via Wikimedia Commons
Migration projects are usually judged on go-live. The more consequential test arrives months later, when the project team has dispersed and the cloud estate is simply part of the operating model. At that point, the contract is no longer a procurement document. It is the rulebook for support, cost, data handling and exit.
For UK SMEs, the risk is rarely a single dramatic clause. It is the accumulation of ordinary-looking terms that were accepted because the migration timetable was tight. In 2026, cloud contracts are often longer and more layered than the services they describe. The following five clauses deserve scrutiny before signature, not after the first invoice dispute.
Exit assistance is a service, not a courtesy
Exit assistance is the provider's obligation to help you retrieve data and move to another environment. In weaker contracts, it is vague: reasonable assistance, agreed in good faith, at prevailing rates. That language can become expensive and slow when you actually need it.
Operationally, exit assistance affects how quickly you can change strategy. If the clause does not define export formats, transition periods, named responsibilities or the cost of assistance, your bargaining position weakens at the moment you are least able to tolerate delay.
Questions to ask before signing:
- What specific export formats and APIs will be available during exit?
- How many days of transition assistance are included, and at what day rate does additional help apply?
- Will the provider continue to support data extraction after termination notice is served?
- Which teams are responsible for what, and who coordinates the exit plan?
Data deletion needs a timetable and a receipt
Data deletion clauses often promise deletion after termination, subject to backups and legal retention. That is reasonable in principle. The practical question is whether deletion is verifiable. A clause that permits indefinite retention in backup systems, without a defined maximum period, creates uncertainty for UK organisations handling customer, employee or commercial data.
This is not only a legal issue. It affects how confidently you can respond to due diligence, insurer questions and internal audit. If a former provider still holds copies of your data, your data map is incomplete.
Questions to ask before signing:
- What is the maximum retention period for backups after termination?
- Will the provider supply written confirmation of deletion, including backup copies?
- How are legal retention obligations separated from ordinary commercial backups?
- Can deletion be evidenced at a stated date, or only described as a process?
Price escalation is a design decision
Price escalation clauses are frequently presented as standard inflation protection. In practice, they can be wide in scope. A clause may allow increases linked to a broad index, provider list prices, renewed infrastructure costs or discretionary adjustments with notice. The issue is not whether prices can rise. It is whether the mechanism is predictable and bounded.
For budgeting, escalation terms matter more than the initial quote. A modest starting price with an open-ended adjustment mechanism is not a stable cost base. UK finance teams should be able to model the maximum plausible increase over a three-year term.
Questions to ask before signing:
- Which index or pricing benchmark applies, and why is it appropriate for this service?
- Is there a cap on annual increases, and does it apply to all charges?
- Can the provider increase prices outside the stated renewal cycle?
- What notice is required, and what termination rights apply if an increase is unacceptable?
Support boundaries define the real service
The support clause is where commercial promises meet daily operations. Many contracts distinguish between incident, request, problem and change, but the definitions can be broad enough to move ordinary work into a chargeable category. A support boundary that excludes configuration, identity changes or integration troubleshooting may leave your team with more internal effort than expected.
This matters because support models are often sold as a single service level. The clause should make clear what is included, what is excluded, how severity is assigned and how disputes about classification are resolved.
Questions to ask before signing:
- Which common tasks are explicitly included, and which are chargeable?
- Who assigns severity, and can the customer challenge a downgrade?
- Are support hours aligned to UK business hours, extended hours or a follow-the-sun model?
- What happens when a third-party dependency is the suspected cause?
Liability caps should match operational exposure
Liability caps limit what a provider must pay if something goes wrong. They are normal in commercial contracts, but the cap should bear some relation to the service and the risk. A very low cap may be acceptable for a peripheral tool; it is less comfortable for identity, backup or core infrastructure services.
UK buyers should also check what the cap excludes. Data protection breaches, confidentiality failures and intellectual property claims are sometimes treated differently. The wording matters because the most damaging incidents are rarely simple outages.
Questions to ask before signing:
- How is the cap calculated, and does it vary by service?
- Which liabilities are excluded from the cap, and are those exclusions mutual?
- Does the cap apply per incident, per year or across the whole term?
- Is insurance evidence available for the risks that remain uncapped?
A contract is an operating manual
The strongest cloud contracts are not the ones with the most clauses. They are the ones where the clauses describe how the service will actually operate when pressure arrives. Exit assistance, deletion, escalation, support boundaries and liability caps are not legal decoration. They are the terms that determine whether the cloud estate remains manageable after the migration project has ended.
For UK SMEs, the practical discipline is to read these clauses with the operations team, not only procurement. Ask what each term would mean in a real incident, a budget review or a change of provider. If the answer is unclear before signature, it will be more expensive to clarify afterwards.