Migration and modernisation

CloudMove

CloudMove is the engineering side of a move to AWS, Microsoft Azure, or Google Cloud. The pattern is chosen per workload.

How the work is sequenced

  1. 01 DiscoverWhat exists, and what depends on what.
  2. 02 AssessWhich pattern fits each workload.
  3. 03 MobiliseLanding zone, access, and a pilot scope.
  4. 04 PilotOne representative workload before a wider wave.
  5. 05 MigrateThe agreed wave, with a rollback path.
  6. 06 ValidateThe workload works, and the operators can run it.
  7. 07 OptimiseCost, performance, and the next wave.

What a scoped engagement can include

Rehost

Move largely as it is.

Replatform

Move and make a limited set of cloud improvements.

Refactor

Redesign an application for a cloud-native shape.

Repurchase

Replace a legacy system with a cloud service.

Retain

Keep a workload where it is for now.

Retire

Turn off a system that is no longer needed.

Moves we can scope

  • Virtual machines and databases
  • Application and Microsoft workload moves
  • Data-centre exit planning
  • VMware-to-cloud and cloud-to-cloud moves
  • Containers, serverless, and infrastructure as code

AWS, Microsoft Azure, and Google Cloud name the technology in the work and in the courses. They are not a claim of official partnership. Completing a course does not award a vendor certification or an accredited qualification. Duration and fees are confirmed when an engagement or a class is scheduled.