Skip to content

Migrate to cloud

Migration architecture, landing zones, networking, IAM, deployment patterns and a phased workload migration.

The situation

Today

  • The move is decided; the how is not.
  • Dependencies are undocumented, the estate is bigger than anyone remembers, and the wrong first step turns into months of hybrid pain.

After the engagement

  • A wave plan with dependencies resolved and dates that hold
  • Workloads landing on patterns the team will keep using
  • An estate that is smaller, not just elsewhere
Specific numbers depend on the estate, which is what the assessment measures.

How we approach it

  1. 01

    Discover the estate and map dependencies

  2. 02

    Give every workload a disposition: rehost, replatform, refactor, retain or retire

  3. 03

    Build the landing zone, networking and identity before the first wave

  4. 04

    Migrate in waves with rehearsed cutovers and rollback

  5. 05

    Decommission what was left behind