Cloud Migration Contract Planning: The Complete Checklist for Enterprise Buyers

Contract Timing: The Critical Sequencing Error

The most expensive mistake in cloud migration is starting the migration before the commercial contract is in place. This is far more common than it should be — technology teams kick off migration projects months before procurement engages with cloud providers, and by the time contracts are being negotiated, the organization is already running workloads on on-demand pricing and the technical team is committed to the platform.

On-demand pricing for compute is typically 3-4x more expensive than equivalent Reserved Instance or Savings Plan pricing. For a migration that takes 12-18 months to complete — common for complex enterprise environments — this means paying a significant premium during the entire transition period, when your cloud consumption is at its peak complexity and cost.

The commercial value of correct sequencing: a 12-month migration of a $2M/year cloud environment begins consuming approximately $1M in cloud resources during the migration period itself (infrastructure running in parallel during cutover). Migrating under on-demand pricing versus pre-negotiated Savings Plans pricing can cost $200-300K more than necessary — money that funds provider revenue, not your migration.

Pre-Migration: On-Premise Contract Exit

The cloud migration contract planning process begins with your existing on-premise contracts — hardware, software licenses, maintenance, and colocation. Exit obligations here directly determine your migration timeline flexibility and total transition cost.

Software License Portability

Before migrating any workloads, confirm with each affected software vendor: (1) whether your existing licenses permit cloud deployment (Bring Your Own License / BYOL); (2) what mobility rights apply across cloud providers; (3) whether cloud deployment requires additional license purchases or triggers additional compliance obligations.

Oracle and Microsoft have particularly complex cloud licensing rules. Oracle's position on VMware virtualization in cloud environments has caused significant compliance exposure for enterprises that assumed on-premise licenses transferred cleanly to cloud deployment — they frequently do not. Microsoft's Software Assurance is required for most BYOL rights in Azure. Confirm all of these in writing before migration, not mid-migration when your leverage is minimal.

Hardware Exit Timing

Owned hardware exit and cloud migration must be coordinated. If you exit hardware too early, you're paying for cloud resources before migration is complete with no on-premise fallback. If you exit too late, you're paying for both on-premise hardware and cloud simultaneously for an extended period. Model the parallel running costs across migration scenarios and build this into your migration business case.

Colocation Agreement Exit

Enterprise colocation agreements typically require 6-12 months' notice for capacity reduction or exit. Colocation providers frequently include minimum power commitment terms that extend beyond physical equipment removal. Review your colocation agreement before finalizing migration timelines — many organizations discover that their colocation agreement prevents them from achieving the cost savings case that justified the migration in the first place, because they're locked into facility costs for 12-24 months post-migration.

Cloud Commitment Sizing During Migration

Commitment sizing during a migration is fundamentally different from steady-state sizing — because your consumption profile is changing throughout the migration period, often non-linearly.

The phased commitment approach is the correct commercial structure for migrations:

1. Baseline commitment (pre-migration): Negotiate an initial EDP or Savings Plan commitment based on your confirmed steady-state consumption for already-migrated or cloud-native workloads. This establishes your discount structure from day one of the contract without over-committing to workloads that haven't migrated yet.
2. Migration period buffer: Negotiate a temporary consumption buffer above your committed level, at a defined rate, to cover the period when workloads are running in parallel in both environments. This prevents on-demand pricing penalties during the most expensive phase of the migration.
3. Commitment step-up options: Negotiate contractual step-up options that allow you to increase commitment levels at defined intervals (quarterly or bi-annually) as migration milestones are reached. This mechanism locks in discount levels for post-migration consumption without requiring you to over-commit during migration.
4. Commitment rebalancing: Negotiate the right to rebalance your Reserved Instance or Savings Plan portfolio as your workload mix evolves during migration — for example, converting instance-family reservations as your architecture decisions are finalised.

Migration Incentives and Credits to Negotiate

Cloud providers invest substantially in migration incentives because migrations create long-term committed customers. These incentives are only available during the pre-migration commercial negotiation window — once you've started migrating, your leverage to request incentives diminishes significantly.

The AWS Migration Acceleration Program (MAP) is the most mature migration incentive structure — providing funding for qualified migrations with detailed eligibility criteria tied to workload commitment value. MAP funding can cover a substantial portion of migration services costs for programs committing $500K+ in annual AWS consumption.

Lock-In Protection Provisions

Cloud migrations create the strongest vendor lock-in in the enterprise technology landscape. Unlike software licenses that can be redeployed, cloud infrastructure dependencies — proprietary services, data gravity, operational tooling investment — accumulate quickly and are expensive to reverse. Lock-in protection provisions negotiated at migration time are your primary commercial defence.

Data Export Rights

Negotiate explicit contractual rights to export all your data in open, standard formats throughout the contract term and during a defined post-termination transition period (minimum 90 days). The data export obligation should cover all data types: stored data, database exports, log archives, analytics outputs, and AI model outputs. Providers will agree to this — it is standard commercial practice in mature cloud contracts.

Egress Fee Waiver for Migration

Negotiate a waiver or cap on egress fees for the duration of any future migration away from the provider. Standard cloud egress fees make large-scale data migration prohibitively expensive — a well-known lock-in mechanism. A migration egress waiver, negotiated pre-migration, preserves your ability to move data in the future without a multi-million dollar bill. Providers will resist this but will accommodate it for significant commitments with strong alternatives in play.

Service Dependency Mapping

Before architecting migration workloads, conduct a proprietary service dependency assessment: identify every proprietary cloud service (e.g., AWS DynamoDB, Azure Cosmos DB, Google BigQuery, AWS Lambda) that will be used and the estimated cost and timeline to replace it with a provider-agnostic alternative. This isn't about avoiding proprietary services — it's about making informed architectural decisions with full understanding of the lock-in implications.

SLA and Performance Terms During Migration

Cloud migration periods require specific SLA provisions that standard cloud agreements don't include. The migration period is when your applications are most vulnerable — running in hybrid configurations, with dependencies split across on-premise and cloud environments. SLA terms must reflect this reality.

Negotiate specific provisions for the migration period: (1) support response time commitments for Severity 1 issues that apply from day one of migration, not only after full migration completion; (2) a dedicated migration support resource (beyond standard TAM support) for the duration of the migration program; (3) clear responsibility delineation for issues that arise in hybrid (on-premise + cloud) configurations; and (4) SLA credits that apply to hybrid environment issues, not only pure cloud outages.

Post-Migration Contract Optimization

The migration completion milestone is also the point at which your negotiating leverage is weakest — you've made the move, and switching costs are now highest. Avoid the natural tendency to treat contract optimization as a post-migration activity.

Instead, embed post-migration commercial checkpoints in your migration contract: a structured 90-day review of actual vs. projected consumption with a commitment rebalancing right; an annual commercial review clause that requires the provider to present updated pricing benchmarks and any new program eligibility; and a most-favoured-pricing clause that requires the provider to notify you within 30 days of offering equivalent customers materially better pricing on equivalent commitment structures.

The Complete Migration Contract Checklist

Phase 1: Pre-Migration Preparation

• Confirm BYOL rights for all on-premise software being migrated (Oracle, Microsoft, SAP, IBM)
• Review and model colocation agreement exit costs and notice periods
• Map hardware depreciation schedule against migration timeline
• Calculate parallel running cost ceiling for migration period
• Identify all workloads with proprietary cloud service dependencies
• Engage procurement before migration decisions are finalized

Phase 2: Commercial Negotiation

• Structure phased commitment with step-up options tied to migration milestones
• Request migration incentives (MAP, migration credits, technical support hours)
• Negotiate migration period consumption buffer at defined pricing
• Obtain commitment rebalancing rights for Reserved Instance portfolio
• Request training credits for cloud operations team upskilling
• Include enterprise discount programs from day one of migration period
• Negotiate migration egress fee waiver or cap
• Bundle support terms, SLA enhancements, and TAM engagement commitments

Phase 3: Contract Terms

• Confirm data export rights in open formats throughout contract term
• Define post-termination data retention and export period (minimum 90 days)
• Establish hybrid environment SLA and support responsibility terms
• Include post-migration commitment review and rebalancing provision
• Negotiate annual commercial review obligation
• Confirm support tier applies from migration start, not migration completion
• Include most-favoured-pricing notification clause