From Migration to Modernisation: Cloud Beyond Lift-and-Shift

Most large cloud programmes begin with migration, and many quietly end there. Applications are moved, the data centre contract is not renewed, and the programme is declared a success. Then the cloud bill arrives, larger than expected, and the promised benefits — agility, resilience, efficiency — are nowhere to be found. The systems simply run somewhere else now.

This is the predictable result of treating migration as the goal rather than the starting point. Lifting a system unchanged preserves its architecture, its inefficiencies and its operating cost, and adds the overhead of a new environment. The value of cloud is unlocked by what changes afterwards: how software is built, how it scales, how it is operated and paid for.

Modernisation is a choice, and it must be resourced

Modernisation does not happen by default. It requires a deliberate decision to invest beyond the migration — to re-architect what matters, retire what does not, and change how teams work. That decision is often the hardest part, because migration feels finished and the next phase looks like spending more to fix something that already works.

My advice to leaders is to be honest at the outset about which they are funding. A migration that is never followed by modernisation is a cost with little return. It is far better to modernise less, deliberately, than to migrate everything and modernise nothing — a theme I return to in cloud transformation more broadly.