What does a cloud migration involve, how long does it take and what does it cost?
A migration has four stages: list everything you run, decide each system's route, build a secure landing zone, then move systems in waves and test each one. Time and cost follow from that list, so get the inventory and the per-system plan before you accept a fixed price.
Each system's route
AWS's migration guidance names 7 routes, often called the "7 Rs":
| Route | What it means |
|---|---|
| Retire | Switch off what nobody needs |
| Retain | Keep it where it is, for now |
| Rehost | Move it as it is to a cloud server, sometimes called lift and shift |
| Relocate | Move a whole virtual environment to the cloud without changing it |
| Repurchase | Replace it with a cloud service, such as moving an on-site mail server to Microsoft 365 |
| Replatform | Move it with small changes, such as a managed database in place of a self-run one |
| Refactor or re-architect | Rebuild it to use cloud services fully |
The steps
- Inventory: every server, application, database and the connections between them.
- Decide each system's route, and which can move first.
- Build the landing zone: accounts, networks, identity and logging, written as code.
- Move in waves, starting with something low-risk, and test each before the next.
- Switch off what has moved, so you stop paying twice.
What it costs
- The migration work itself.
- Cloud usage, which starts before the old systems are switched off.
- Running two environments during the move.
- With us: the 21-day cloud DevSecOps and vCISO sprint builds the landing zone for $17,250; on Managed Cloud & AI for Business, the 30-day managed cloud and AI sprint builds your private cloud, from $13,800 at 5 seats.
- Cloud compute and AI model usage bill directly to your own cloud account. Moving existing servers and applications is planned system by system; work beyond the sprint bills at the hourly rates in the price table.