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.

  • CAF: Plan, Ready, Adopt
  • Well-Architected: Reliability, Cost Optimisation

The problem

Most migrations stall between the business case and the first workload. The assessment said lift and shift, the estate says otherwise, and every month in between is paid for twice: the datacentre that was supposed to close and the cloud that was supposed to replace it.

You probably need this if

  • The migration business case was approved and the datacentre contract has been renewed anyway
  • Nobody can say which workloads are rehost, which are replatform, and which should be retired instead
  • The last migration attempt moved the easy servers and then stopped
  • Dependencies live in a spreadsheet that predates the people now running the estate

Recognise more than one of those? A CAF readiness assessment gives you a baseline in three to four weeks, before you commit to anything longer.

What the service covers

  • Migration assessment: discovery and dependency mapping with Azure Migrate, then a disposition we assign per workload: rehost, replatform, refactor, retire or retain
  • Landing zone readiness before the first wave, so workloads arrive into governance rather than being retrofitted into it
  • Wave planning your change board can approve: bounded groups, stated downtime, and a rollback path per wave
  • Cutover runbooks that are rehearsed before the move, not written the week of it
  • A cost model per wave against the run rate it replaces, so finance can see the crossover point
  • Decommissioning evidence for the estate left behind, so the saving is real rather than assumed

Which workloads would actually move, and which should be retired instead?

If the plan says all of them, it is a guess. Book a 30-minute call and we will look at what the estate itself says.