Beyond Lift-and-Shift: A Practical Framework for Successful Cloud Migration

For most organisations, the hardest part of cloud migration isn’t moving the technology, it’s avoiding the hidden risks and costs that show up after the move.

Cloud promises speed, flexibility, and resilience. Yet many programmes stall (or disappoint) because migration is treated as a one-off infrastructure relocation. “Lift-and-shift” is fast, familiar, and sometimes necessary, but on its own it rarely delivers the outcomes leaders actually want: stronger security, predictable running costs, faster delivery, elastic scalability and long-term control.

True migration is a programme: a staged approach that aligns business outcomes, prepares secure foundations, migrates safely in waves, and then modernises and optimises continuously. The move itself is a milestone, not the finish line.

Lift-and-shift (also referred to as “rehost” in the 6 Rs) can be a sensible choice when timelines are tight, you need a data-centre exit, or you’re minimising risk by changing as little as possible.

The issue isn’t lift-and-shift as a concept – it’s treating it as the whole strategy.

The new cloud hosting may reproduce challenges from a current operating model. This creates a growing backlog of “we’ll fix it later” remediations such as:

True migration is a staged programme that builds readiness before accelerating execution. It starts with clarity on outcomes, then creates the foundations (platform, governance, security and operating model) required to migrate safely at pace.

In practice, this means aligning business priorities, discovering and rationalising the estate, builds secure cloud foundations, and then migrating and optimising in a controlled way.

Stage 1: Align on outcomes and constraints

Start with what matters to the business: resilience targets, compliance needs, delivery speed, cost transparency, and risk appetite. Define what success means and what trade-offs are acceptable.

Stage 2: Discover and select the right approach per workload

Discovery should identify dependencies, criticality, and the best migration path per workload (not a one-size-fits-all approach). The goal is a prioritised work backlog and a clear treatment decision for each workload.

Stage 3: Build the runway, secure cloud foundations (landing zones)

A landing zone is the governed foundation workloads inherit: identity and access, network topology and connectivity, resource organisation, and controls for security, automation governance and operations.

Do this early, and teams move faster with fewer surprises; skip it, and you pay the price later.

Stage 4: Migrate in waves (repeatable, testable, low risk)

Build on the foundations: migration should run as a repeatable delivery engine: group workloads into waves, automate where possible, and use clear entry/exit criteria (testing evidence, cutover planning, rollback readiness).

Stage 5: Modernise and optimise (where the value shows up)

After workloads are stable, modernise where it pays: move to managed runtime, improve resiliency patterns, implement cost controls, and embed better operational practices.

This is where measurable improvements in resilience, audit readiness, and cost control typically appear. This stage can be conducted in line with stage 4 for certain workloads, which would be determined during discovery.

If you’re planning an on‑premises or private cloud migration, we can help you turn it into a structured programme, from discovery and business case, to landing zone foundations, wave migration, and modernisation.

Understand your current estate and define the right approach to move beyond lift-and-shift with a free cloud migration assessment →