Skip to content

What we do

Cloud Migration

We plan the move, build the landing zone it arrives into, and migrate workloads in waves your change board can approve.

Frameworks
CAF: Plan, Ready, Adopt · Well-Architected: Reliability, Cost Optimisation
Good first step
Microsoft CAF Readiness Assessment, a baseline in 3–4 weeks

The problem

Most migrations stall between the business case and the first workload. The assessment usually assumes lift and shift, and the estate turns out to be more varied than that. While the plan is reworked you pay twice: for the datacentre that was due to close and for the cloud that was meant to replace it.

You probably need this if

  • The migration business case was approved and the datacentre contract has been renewed anyway
  • It's unclear which workloads should be rehosted, which replatformed and which retired
  • The last migration attempt moved the easy servers and then stopped
  • Dependencies are recorded in a spreadsheet that predates the people now running the estate

What the service covers

  1. 1Migration assessment: discovery and dependency mapping with Azure Migrate, then a disposition we assign per workload: rehost, replatform, refactor, retire or retain
  2. 2Landing zone readiness before the first wave, so workloads arrive into governance that is already in place
  3. 3Wave planning your change board can approve: bounded groups, stated downtime, and a rollback path per wave
  4. 4Cutover runbooks written and rehearsed well before the move
  5. 5A cost model per wave against the run rate it replaces, so finance can see the crossover point
  6. 6Decommissioning evidence for the estate left behind, so finance can confirm the saving

The first piece of work

Before any wave is planned, we run a migration assessment with Azure Migrate so that every workload has a disposition. It also shows how much of the original business case still holds, which is useful to know before the datacentre contract comes up again.