Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 11 tasks across 4 phases, about 19 weeks if every task runs in sequence.
What's in the template
Application and dependency inventory
Migration approach per application
Cost estimate and business case
Landing zone, networking and identity
Security baseline and monitoring
Pilot application migration
Wave one migration
Wave two migration
Final cutover window
Right-sizing and cost review
Decommission on-premises servers
| Phase | Task | Example duration |
|---|---|---|
| Assess | Application and dependency inventory | 14 days |
| Assess | Migration approach per application | 7 days |
| Assess | Cost estimate and business case | 5 days |
| Foundation | Landing zone, networking and identity | 21 days |
| Foundation | Security baseline and monitoring | 10 days |
| Migrate | Pilot application migration | 10 days |
| Migrate | Wave one migration | 21 days |
| Migrate | Wave two migration | 21 days |
| Migrate | Final cutover window | 3 days |
| Optimize | Right-sizing and cost review | 14 days |
| Optimize | Decommission on-premises servers | 10 days |
Durations are examples to replace with your own estimates, not benchmarks.
About this cloud migration plan
Cloud migrations go in waves: a low-risk pilot proves the landing zone and runbook, then groups of applications move in planned windows. This plan keeps the pilot, waves and on-premises decommission as separate rows so progress is visible.
It fits moving a set of business applications from a data center or hosting provider to a public cloud.
Who it's for: IT directors, cloud architects and managed service providers.
How to use it
- Open the plan. Click Open in the editor.
- Group apps into waves. Rename the wave rows with the applications in each, or add a row per application.
- Keep windows visible. Keep the cutover window as a bar so its full length shows.
- Share the schedule. Send a read-only link to application owners.
Planning tips
- Map dependencies before choosing waves; tightly linked apps should move together.
- Use the pilot to test the rollback plan as well as the migration.
- Plan a cost review shortly after migration.
Frequently asked questions
- What is a landing zone?
- The prepared cloud environment — accounts, networking, identity and security controls — that migrated applications move into.
- Why migrate in waves?
- Waves limit risk and let the team improve the runbook between groups.
- Can the plan run past a year?
- Yes. Plans can run up to two years.
Related templates
The free plan saves one project. Downloads (PDF, CSV) and more projects are on Solo, $12/month.