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
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| Assess | Application and dependency inventory | 14 days | Day 1 | Nothing (starts first) |
| Assess | Migration approach per application | 7 days | Day 15 | Application and dependency inventory |
| Assess | Cost estimate and business case | 5 days | Day 22 | Migration approach per application |
| Foundation | Landing zone, networking and identity | 21 days | Day 27 | Cost estimate and business case |
| Foundation | Security baseline and monitoring | 10 days | Day 48 | Landing zone, networking and identity |
| Migrate | Pilot application migration | 10 days | Day 58 | Security baseline and monitoring |
| Migrate | Wave one migration | 21 days | Day 68 | Pilot application migration |
| Migrate | Wave two migration | 21 days | Day 89 | Wave one migration |
| Migrate | Final cutover window | 3 days | Day 110 | Wave two migration |
| Optimize | Right-sizing and cost review | 14 days | Day 113 | Final cutover window |
| Optimize | Decommission on-premises servers | 10 days | Day 127 | Right-sizing and cost review |
Durations are examples to replace with your own estimates, not benchmarks. Every task waits for the one before it, so the whole chain is the critical path until you overlap work that can run in parallel.
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 Use this template.
- 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 and guides
- Data Migration Plan Gantt chart template
- IT Network Upgrade Gantt chart template
- ERP Implementation Plan Gantt chart template
- Disaster Recovery Test Plan Gantt chart template
- Sprint planning on a Gantt chart
- Microsoft Project alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.