Cloud migration is rarely a single decision. When it goes wrong, it's usually not because of the cloud itself — it's because the wrong things were modernised first.
For many organisations, "moving to the cloud" sounds like a single decision.
Pick a platform. Migrate systems. Turn off the old servers. Job done.
In reality, cloud migration is rarely that simple — and when it goes wrong, it's usually not because of the cloud itself, but because the wrong things were modernised first.
One of the most common questions we hear is: "Should we move our applications first, modernise identity, or focus on data?" The honest answer is: it depends. More importantly, it depends on whether you have a clear, realistic understanding of your current technology environment — and a strategy that sequences change in the right order.
Why "lift and shift" thinking causes cloud migrations to stall
Many organisations start their cloud journey by moving what they already have, as quickly as possible.
On paper, it looks efficient. In practice, it often leads to higher cloud costs, performance issues, security gaps, and legacy complexity reproduced in a new environment.
The problem isn't the cloud. It's that existing tech debt and design decisions are simply being relocated — not resolved. A modernisation strategy asks a different question first: "What needs to change before we move anything?"
Identity: the foundation most organisations underestimate
Identity is rarely the most exciting part of a cloud migration — but it is almost always the most important.
When identity is not modernised early, cloud environments become harder to secure and govern. Users struggle with access, admin privileges sprawl, and security teams lose confidence in who can access what.
A Technology Modernisation & Cloud Enablement Plan typically identifies identity as a foundational dependency, recommending it be stabilised before large scale application or data migration begins.
Applications: the temptation to move them too soon
Applications are usually where the pressure comes from. But without proper assessment, organisations often migrate systems that are poorly suited to cloud or tightly coupled to legacy infrastructure.
This leads to degraded performance, increased support effort, and loss of confidence in the migration.
A modernisation strategy assesses applications first — identifying which should be modernised, replaced, retired, or left alone. Not everything needs to move. And the sequence in which things move matters enormously.
Data: the most emotionally charged layer
Data migration raises concerns around security, compliance, and ownership. Data is often spread across systems, file shares, and SaaS platforms with inconsistent governance.
Rather than moving everything at once, a structured strategy prioritises what data needs to move, when, and why — reducing risk while improving accessibility and control.
The real problem: no shared view of the current state
Across identity, applications, and data, the biggest challenge is the same — there is no single, shared understanding of the current environment.
A Technology Modernisation & Cloud Enablement Plan provides that clarity, sequencing change in a way that balances risk, cost, and benefit. It creates a baseline that everyone — from the board to the ICT team — can work from with confidence.
Cloud migration isn't about speed — it's about direction
The most successful cloud journeys are guided by clear understanding, not urgency.
With the right strategy, organisations modernise with confidence, reduce risk, and avoid costly missteps that derail cloud initiatives.
Before deciding what to move first, the most important question is whether you understand why.