The Lift-and-Shift Hangover
Between 2018 and 2023, the dominant cloud migration pattern was deceptively simple: take what you have on-premises, move it to a cloud provider, and declare victory. Thousands of enterprises did exactly this — and many are now dealing with the consequences. Cloud bills that dwarf their former data centre costs. Applications that run in the cloud but were never designed for it. Operational models that replicated on-premises complexity in a new environment rather than eliminating it.
What Business-Led Migration Actually Means
The shift we are seeing in 2026 is not simply about modernising applications — it is about starting every migration conversation with a business outcome question rather than a technical one. Which business processes are constrained by current infrastructure? Where is time-to-market being lost? Which data assets are inaccessible because of architectural debt? These questions produce a fundamentally different migration backlog than a traditional application portfolio assessment.
The Six Rs Are Not Enough
The classic Gartner 6 Rs framework (Rehost, Replatform, Repurchase, Refactor, Retire, Retain) remains a useful vocabulary, but it is insufficient as a decision framework for business-led migration. We have found that enterprises need a seventh dimension: Reimagine — the deliberate question of whether a given capability should exist in its current form at all, or whether cloud-native patterns enable a fundamentally better approach. Organisations that skip this question consistently under-realise the value of their cloud investment.
The Role of Landing Zone Architecture
One of the most consequential early decisions in any migration programme is the design of the cloud landing zone — the foundational account structure, network topology, identity model, and governance framework that all workloads will inherit. Organisations that treat landing zone design as a technical checkbox rather than a strategic decision consistently encounter problems at scale: security gaps that are expensive to retrofit, network architectures that constrain workload placement, and governance models that create friction without adding control.
Measuring Migration Success Differently
The most forward-thinking organisations we work with have moved away from measuring migration success in terms of workloads migrated or percentage of infrastructure in the cloud. Instead, they track business outcomes: reduction in time-to-market for new features, improvement in system availability, reduction in unplanned downtime, and — critically — the speed at which the organisation can now respond to market changes. These metrics tell a very different story about cloud value than infrastructure KPIs.
Practical Recommendations
For organisations planning or mid-stream in a cloud migration, we recommend three immediate actions. First, conduct a value alignment audit of your current migration backlog — map each workload to a specific business outcome and deprioritise anything that cannot be linked to measurable value. Second, invest in landing zone remediation before migrating additional workloads — the cost of fixing foundational issues grows exponentially with the number of workloads on top of them. Third, establish a cloud centre of excellence that reports to business leadership, not just IT — the governance and prioritisation decisions in a migration programme are fundamentally business decisions.