Most cloud migrations that run over budget skip the same few steps. Here is what to confirm before the first workload moves.
Cloud migrations rarely fail because of the cloud. They struggle because of what was not understood before the move: an undocumented dependency, a licensing term, a team that was never trained to operate the new environment. A few weeks of preparation prevents most of these problems.
1. Know what you run
Build an inventory of applications, servers, databases and the connections between them. Include owners, business criticality and current costs. Automated discovery tools help, but interviews with the people who support each system are what surface the surprises.
2. Decide what should move, and how
- Rehost workloads that are stable and simply need a new home
- Replatform where a managed service removes real operational effort
- Refactor only where the business case is clear
- Retire anything nobody can justify keeping
- Retain what is cheaper or safer to leave in place, for now
3. Build the foundation first
Before migrating a single application, set up the landing zone: account structure, networking, identity, logging, security guardrails and cost tagging. Teams that skip this step end up retrofitting controls later, which is slower and riskier.
A landing zone is the part of the migration nobody sees and everybody depends on.
4. Plan for operations, not just the move
Who will be paged at 2 AM? How will patches, backups and cost reviews happen? Write runbooks and set up monitoring before go-live, and make sure the team that will operate the platform has been part of building it.
5. Start small and learn
Pick a first wave of low-risk, well-understood workloads. Use it to test your tooling, your runbooks and your rollback plan. Each wave after that will move faster because the hard lessons were learned when the stakes were low.
None of this is glamorous, but it is the difference between a migration that delivers savings and agility and one that simply moves the same problems to a more expensive address.
Written by the Cloud Practice