--- title: "Cloud migration" description: "Best for moving a defined application or workload portfolio to an approved cloud target with cutover controls." canonical: "https://ganttfather.com/templates/cloud-migration/" locale: "en" category: "product" --- # Cloud migration [Software & technology](https://ganttfather.com/templates/#software-technology) Project timeline template # Cloud migration Best for moving a defined application or workload portfolio to an approved cloud target with cutover controls. Best for moving a defined application or workload portfolio to an approved cloud target with cutover controls. [Use the Cloud migration template free](https://app.ganttfather.com/projects/new?template=cloud-migration&entry=template-library) Make the sequence from Discovery, Migrate and Cutover explicit before work starts. Keep Inventory workloads, Prepare landing zone and Confirm cutover readiness connected instead of tracking them in separate documents. ## Cloud migration: connect Discovery to Cutover without losing a handoff. # Cloud migration Cloud migration makes Inventory workloads, Prepare landing zone, and Migration complete explicit checkpoints in one working plan. Best for moving a defined application or workload portfolio to an approved cloud target with cutover controls. ## Execution path The sequence shows what must be ready between Inventory workloads and Migration complete, so the next owner can act on a defined decision rather than an assumed handoff. ### Discovery Inventory workloads → Design target environment → Migration approach approved ### Migrate Prepare landing zone → Migrate workloads → Validate migrated workloads → Ready for cutover ### Cutover Confirm cutover readiness → Switch production traffic → Verify cloud operation → Migration complete Included schedule ## 14 rows, 9 links, already sequenced. Use this Cloud migration plan to coordinate Inventory workloads, Prepare landing zone and Confirm cutover readiness in one dependency-aware schedule. Read-only preview Milestone Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 Day 16 Day 17 Day 18 Day 19 Day 20 Day 21 Day 22 Day 23 Day 24 Day 25 Day 26 Day Inventory workloads Design target environment Prepare landing zone Migrate workloads Validate migrated workloads Confirm cutover readiness Switch production traffic Verify cloud operation Replace relative days with the real start date and assign an accountable owner to every row. Read-only shared Gantt preview. Focus a bar and press Enter to inspect it. Schedule details ### Complete schedule table Make the sequence from Discovery, Migrate and Cutover explicit before work starts. Keep Inventory workloads, Prepare landing zone and Confirm cutover readiness connected instead of tracking them in separate documents. Work item Type Schedule Duration Depends on Discovery Phase Days 1–7 Derived rollup — Inventory workloads Task Days 1–3 3 working days — Design target environment Task Days 4–6 3 working days Inventory workloads Migration approach approved Milestone Day 7 Milestone Design target environment Migrate Phase Days 8–18 Derived rollup — Prepare landing zone Task Days 8–11 4 working days — Migrate workloads Task Days 12–17 6 working days Prepare landing zone Validate migrated workloads Task Days 14–17 4 working days Prepare landing zone Ready for cutover Milestone Day 18 Milestone Validate migrated workloads, Migrate workloads Cutover Phase Days 19–26 Derived rollup — Confirm cutover readiness Task Days 19–20 2 working days — Switch production traffic Task Days 21–22 2 working days Confirm cutover readiness Verify cloud operation Task Days 23–25 3 working days Switch production traffic Migration complete Milestone Day 26 Milestone Verify cloud operation ## Who it helps - Cloud program managers sequencing migration waves - Platform, security, and operations leads planning cutover ## What is included - Discovery: Inventory workloads, Design target environment and Migration approach approved - Migrate: Prepare landing zone, Migrate workloads, Validate migrated workloads and Ready for cutover - Cutover: Confirm cutover readiness, Switch production traffic, Verify cloud operation and Migration complete ## Adapt after creation - Add the team-owned access, data, or operating details represented by Cloud console credentials and Production secrets. - Replace relative days with the real start date and assign an accountable owner to every row. - Add review gates, rollback steps, or evidence required by your organization. How to use this template ## Make the sequence from Discovery, Migrate and Cutover explicit before work starts. Keep Inventory workloads, Prepare landing zone and Confirm cutover readiness connected instead of tracking them in separate documents. - 1 ### Discovery Move through Inventory workloads, Design target environment and Migration approach approved while keeping the Discovery handoff visible before the next stage begins. - 2 ### Migrate Move through Prepare landing zone, Migrate workloads, Validate migrated workloads and Ready for cutover while keeping the Migrate handoff visible before the next stage begins. - 3 ### Cutover Move through Confirm cutover readiness, Switch production traffic, Verify cloud operation and Migration complete while keeping the Cutover handoff visible before the next stage begins. Not included ## Planning aid This public planning aid contains no live access or production data. Add Cloud console credentials and Production secrets only inside your secured project. - Backup archives - Cloud console credentials - Customer data - Network configurations - Production secrets - Vendor contracts Template FAQ ## Good to know What does the Cloud migration template include? + It covers Discovery, Migrate and Cutover and sequences concrete work such as Inventory workloads, Prepare landing zone and Confirm cutover readiness. Who should use the Cloud migration template? + It is designed for Cloud program managers sequencing migration waves and Platform, security, and operations leads planning cutover. How should I adapt the Cloud migration plan? + Set real dates and owners after creation, then add operational details such as Cloud console credentials and Production secrets; those are deliberately excluded from the public starter. Related templates ## Related templates [Templates →](https://ganttfather.com/templates/) [Sales & customer success 21 working days CRM implementation Best for implementing one CRM instance through approved scope, data preparation, configuration, testing, training, and adoption verification.](https://ganttfather.com/templates/crm-implementation/)[Software & technology 19 working days Software Release Timeline Plan a software release from scope through deployment with a practical 19-working-day schedule.](https://ganttfather.com/templates/software-release-timeline/) ![](https://ganttfather.com/logo.png) ## Use the Cloud migration template free Make the sequence from Discovery, Migrate and Cutover explicit before work starts. Keep Inventory workloads, Prepare landing zone and Confirm cutover readiness connected instead of tracking them in separate documents. [Use the Cloud migration template free](https://app.ganttfather.com/projects/new?template=cloud-migration&entry=template-library) Make the sequence from Discovery, Migrate and Cutover explicit before work starts. Keep Inventory workloads, Prepare landing zone and Confirm cutover readiness connected instead of tracking them in separate documents.