A Practical Cloud Migration Checklist for Mid-Size Enterprises
Every cloud provider will happily show you a migration diagram with four tidy arrows. Reality, especially for a mid-size enterprise with a decade of accumulated systems, is messier: undocumented dependencies, licences that behave differently in the cloud, a database nobody has patched since the person who installed it left. The migrations that go smoothly are not the ones with the best tooling — they are the ones with the most honest preparation.
What follows is the working checklist our cloud practice uses, organised into the three phases where projects are actually won or lost: before, during, and after the move.
Before: discovery and decisions
- Inventory everything, then map dependencies. The application list is easy; the surprise is always the connections — the reporting job that reads a database directly, the shared folder three departments quietly rely on.
- Classify each workload: rehost (lift-and-shift), replatform (small changes, e.g. database to a managed service), refactor (rearchitect), retire, or retain on-premise. Resist the urge to refactor everything — pick your battles.
- Baseline current performance and cost. Without a before picture, you cannot prove the after, and finance will ask.
- Check licences and compliance early. Some enterprise licences are not portable to cloud VMs, and regulated industries may have data-residency requirements that dictate your region choice on day one.
- Decide your landing zone before the first workload moves: account structure, network topology, identity integration, tagging standards, and guardrails. Retrofitting governance is ten times harder.
The dependency map is the project
If we could give one instruction to every migration team, it would be this: the dependency map is not documentation, it is the project plan. Migration waves should be cut along dependency boundaries, so tightly coupled systems move together and loosely coupled ones move independently. Most mid-migration emergencies trace back to a dependency nobody drew.
During: execution discipline
- Move a low-risk, representative workload first and treat it as a rehearsal — validate the runbook, the rollback, and the communication plan, not just the technology.
- Keep a rollback path for every wave. Blue-green cutover with continuous data replication costs a little more and removes most of the fear.
- Freeze scope during each wave. Migration is the worst possible moment to also upgrade the application version.
- Test restores, not backups. A backup that has never been restored is a hope, not a strategy.
- Communicate cutover windows to business users even when you expect zero downtime — surprises destroy trust faster than outages.
After: the phase everyone underestimates
The migration is not done at cutover. The first ninety days in the cloud determine whether you realise the benefits that justified the project. Cloud bills are shaped by behaviour, and behaviour only changes with visibility and ownership.
- Right-size aggressively after four to six weeks of real utilisation data — initial sizing is always conservative and usually 30-40% over.
- Put cost visibility in front of the teams who create the cost. Tag-based dashboards by product or department change behaviour in weeks.
- Automate what the data centre never let you: patching windows, scaling schedules, environment shutdown outside business hours.
- Revisit disaster recovery. Cloud makes warm-standby DR affordable for mid-size firms — take the option your old infrastructure never gave you.
A migration that lands workloads but not operating habits just relocates your problems — at a different monthly price.
— 7x Technologies cloud practice
Treat the checklist as a floor, not a ceiling. Every environment adds its own items — a factory with OT systems, a lender with regulator notifications, a retailer with a peak-season freeze calendar. The constant across all of them is sequencing: honest discovery, disciplined waves, and a deliberate first ninety days. Get those right and the cloud delivers what the brochure promised.