← Solutions
CloudPopular

Cloud migration

Move workloads to the cloud in rehearsed waves, modernising where it pays and rehosting where it does not, with no big-bang weekend.

Typical timing
12–26 weeks
Engagement
Phased programme
Delivery framework
User researchDiscoveryAlphaBetaLive

Migrate an application estate to the cloud safely and on budget. Each wave is planned by dependency, rehearsed, cut over with rollback ready, and optimised after it lands so run costs match the business case.

  • A data centre exit date is fixed
  • The assessment is done and the business case is approved
  • Previous migrations overran or were rolled back
How it runs

Activities, step by step

The plan follows our delivery framework. Steps that do not apply to this kind of work are left out rather than padded.

  1. 02 · Discovery2–3 weeks

    Mobilise

    • Wave plan confirmed with application owners
    • Migration tooling and landing zone readiness checked
    • Cutover, rollback and communication plans
  2. 03 · Alpha3–4 weeks

    Pilot wave

    • Low-risk applications migrated first
    • Runbook refined from real cutovers
    • Performance and cost compared with forecast
  3. 04 · Beta6–16 weeks

    Migration waves

    • Rehost, replatform or refactor by workload
    • Rehearsed cutovers with business sign-off
    • Hypercare after each wave
  4. 05 · Live2–3 weeks

    Optimise and close

    • Rightsizing and reserved capacity
    • Source infrastructure decommissioned
    • Operations handed over

Deliverables

What you keep at the end.

  • Migrated workloads running in production
  • Wave plans, runbooks and cutover records
  • Post-migration cost optimisation report
  • Decommissioning certificates for source systems

Outcomes

What it is built to change.

  • Data centre exit on the agreed date
  • Run costs in line with the business case
  • Minimal downtime, with every cutover reversible