Cloud migrations that overrun usually share a cause: workloads were moved before anyone fully understood their dependencies. A disciplined approach front-loads that understanding and moves in predictable waves.
1. Discover before you decide
Inventory applications, infrastructure, data flows and owners. Automated discovery tools help, but conversations with application teams reveal the undocumented batch job or hard-coded IP address that would otherwise break on migration day.
2. Pick a strategy per workload
- Rehost when speed matters and the application is stable
- Re-platform to managed databases and containers for quick operational wins
- Re-architect where the application is strategic and change is frequent
- Retire or replace what no longer earns its keep
3. Build the landing zone first
Identity, networking, logging, security guardrails and cost tagging should exist before workloads arrive. Defining them as infrastructure as code means every new account or subscription starts compliant.
4. Migrate in waves and measure
Group applications by dependency and risk. Start with lower-risk workloads to prove the process, then accelerate. Track cost, performance and incidents after each wave so the next one improves.
Migration is a one-time project. Operating well in the cloud is a permanent capability — plan for both.