Cloud Migration Framework

Prove the move.Then migrate in waves.

Move workloads into, out of or between clouds. We compare destinations against your requirements, test the chosen path with a real workload, and plan each cutover around what the pilot shows.

Technology partners

[ Migration paths ]

What needs to move, and where?

The framework starts with your workloads. We compare public cloud, private cloud and on-premises options against cost, dependencies, data location and your team's ability to run them.

  1. 01Path

    Move into cloud

    From on-premises infrastructure to public or private cloud.

    Check which applications can move as they are, which dependencies need to change and what the receiving environment must provide.

  2. 02Path

    Move out of public cloud

    Bring selected workloads back to private cloud or your own infrastructure.

    Compare the cost of staying with the cost and effort of moving. Keep cloud-native services where replacing them would outweigh the benefit.

  3. 03Path

    Move between platforms

    Switch providers or consolidate virtualisation and Kubernetes estates.

    Map the differences in identity, networking, storage and platform services before committing to a cutover.

Or retainSome workloads may be better left where they are.
  1. Step 01

    Discover

    Inventory applications, owners, data and dependencies. Record current cost, performance and recovery needs.

    Deliverable

    Workload and dependency map

  2. Step 02

    Compare & plan

    Compare viable destinations with staying put. Classify each workload: move as is, adapt, rework or retain.

    Deliverable

    Target recommendation and pilot criteria

  3. Step 03

    Define the landing zone

    Design and build the target foundation: identity and access, networking, storage, security policies and observability. Connect the delivery pipeline and validate the setup before moving the pilot workload.

    Deliverable

    Landing zone design and a validated pilot environment

  4. Step 04

    Pilot

    Move one representative workload to the target. Check behaviour, data integrity, performance and recovery against the baseline.

    Deliverable

    Pilot results and decision on the first wave

  5. Step 05

    Migrate in waves

    Group by dependencies and risk. Rehearse the cutover and recovery procedure, then validate each wave before starting the next.

    Deliverable

    Wave plan, cutover record and sign-off

  6. Step 06

    Stabilise & hand over

    Monitor the workloads on the new platform, transfer runbooks and retire the source only after agreed checks and sign-off.

    Deliverable

    Operations handover and retirement plan

Before each cutover, agree:

  1. Who makes the go or no-go decision
  2. How long rollback remains feasible
  3. How to recover if writes on the target cannot be reversed safely

[ Illustrative cloud-native use case ]

Move a Kubernetes application while both platforms are live

Imagine an order platform on Amazon Elastic Kubernetes Service (EKS). The team wants to bring steady workloads back to private infrastructure. It needs to keep serving customers while the two environments run side by side.

  1. 01

    Choose where each service belongs

    For private infrastructure, compare VMware vSphere Kubernetes Service (VKS) and Red Hat OpenShift. If the business case favours another public cloud, evaluate Google Kubernetes Engine (GKE) or Azure Kubernetes Service (AKS). Use the existing EKS setup as the baseline, and keep services there when replacing an AWS dependency costs more than moving would save.

  2. 02

    Design the landing zone for both platforms to coexist

    This is often the hardest part. The target has to fit the application and work alongside the source. Map workload identity, secrets, DNS, ingress, network policies and storage before deciding how the clusters connect.

    Use CI/CD to build and test one image, then deploy it through GitOps with configuration for each cluster. Where service-to-service traffic needs shared identity and traffic controls, evaluate a full multicluster service mesh with mutual TLS. Test service discovery, latency and failure behaviour before using it in production.

  3. 03

    Pilot traffic and rehearse the data cutover

    Pilot a stateless order API and shift a small share of traffic to the target. Check error rates and latency before expanding. For services with persistent data, rehearse replication and restore, verify consistency and agree when writes switch to the target. Once the target accepts writes, recovery may require data reconciliation rather than a simple traffic reversal.

One release, two live clusters

The same application version is deployed to both environments. Customer traffic shifts independently as the target passes its checks.

Deployment

CI/CD + GitOps

Build and test one image. Deploy it to both clusters with environment-specific configuration.

Customer traffic

Weighted ingress gateway

Route requests to the source and target at the agreed split.

Source

Amazon EKS cluster

Current order API remains live during the pilot.

Target landing zone

Private Kubernetes cluster

Pilot order API on the chosen platform, with identity, networking, policies and monitoring in place.

Source ↔ Target: optional multicluster service mesh. Mutual TLS and service-to-service traffic policies for calls that cross clusters.

Example traffic progression for the stateless API

Advance only if error rate, latency and application checks pass. Pause or shift API traffic back if they fail. Stateful services follow a separate data cutover and recovery plan.

[ Inside the pilot ]

Make the first move count

Choose a workload that exposes a real migration risk, such as a stateful service, a critical integration or a tight cutover window. Keep the source available where feasible while the target is tested.

What the pilot should tell you

  1. Which dependencies carry over and which need work
  2. Whether application behaviour and data meet the agreed checks
  3. How long the cutover takes and whether recovery meets your requirements
  4. Which workloads belong in the first wave and what must change before they move

[ Business requirements ]

What to know before you move

Start with the event driving the decision and the conditions a move has to meet. That gives you a way to compare staying, moving selected workloads or migrating the estate.

  1. Trigger 01

    A renewal or cloud commitment is coming up

    Licences, hosting or committed spend are due for renewal. You need time to compare terms and test a viable alternative.

    What to establish

    The decision deadline, current commitments and the full cost of each option, including migration and the period when both platforms run.

  2. Trigger 02

    The cost of running steady workloads is rising

    Predictable workloads may cost less elsewhere, while burst capacity or managed services may still make sense on the current platform.

    What to establish

    Cost per workload, usable capacity, data transfer charges and the payback period after migration and operating costs.

  3. Trigger 03

    A customer or policy sets new data requirements

    New residency, access or audit requirements may change where an application can run or who can operate it.

    What to establish

    Which data and services are in scope, where they can live and what evidence the security or risk owner needs before sign-off.

  4. Trigger 04

    A platform is losing support or getting harder to run

    End of support, duplicate platforms or stretched teams can make consolidation or a move to managed Kubernetes worth evaluating.

    What to establish

    The support deadline, acceptable downtime and data loss, and who will own the platform after cutover.

Use these requirements to set the pilot’s pass criteria and decide which workloads should move first, move later or stay.

[ Get started ]

Find the first workload worth moving

Start with a migration review. Bring your current environment, your reason for moving and any deadline or target you already have.

  • Identify the constraints that could change the decision
  • Discuss a candidate workload and what the pilot should prove
  • Agree what information is needed to scope the next step