Cloud Journey Roadmap: 6-Month Migration Template
8 min read ยท 2026-10-08
A cloud journey roadmap is a dated plan for moving your applications and data from on-premises or colocation into AWS, Azure or Google Cloud. It runs in a set order: agree on the business goal, assess the portfolio, pick a migration strategy for each workload, build a secure landing zone, prove it with a pilot, migrate in waves, then optimize. The cloud migration roadmap template below covers six months, which suits a first large migration.
It is written for infrastructure leads, cloud architects, PMOs and IT program managers who have to present the plan and then run it. For each phase you get an objective, concrete steps and a milestone you can check. After the phases come decision rules for the 7 Rs, a checklist for sequencing waves and rollback, the roles that need to sign off, and the view leadership expects to see.
The roadmap at a glance
Goal: Move the prioritized application portfolio to the cloud with no unplanned outages, a clear cost baseline and source hardware ready to retire. Duration: 6 months (26 weeks)
Envision and Business Case (Weeks 1 to 2)
Tie the migration to business outcomes and named sponsors before any technical work starts.
- Write down why you are moving: data center exit, contract end, resilience, speed of delivery.
- Name an executive sponsor, a roadmap owner and leads for security, finance and operations.
- Agree on 3 to 5 measurable success criteria, such as outage minutes, cost per application or decommission date.
- List hard dates you cannot move, like contract expiry, audits and peak trading periods.
Milestone: The sponsor signs a one-page charter with scope, success criteria and deadlines.
Discovery and Portfolio Assessment (Weeks 3 to 6)
Know every workload, dependency and constraint before you commit to migration dates.
- Run automated discovery to capture servers, utilization and network dependencies.
- Interview application owners about criticality, data sensitivity and downtime tolerance.
- Assign each workload one of the 7 Rs and record why.
- Flag licensing, compliance and data residency limits that rule out some options.
- Build a cost comparison between current spend and the projected cloud run rate.
Milestone: A portfolio register lists every workload with an owner, a strategy and a dependency group.
Landing Zone (Weeks 7 to 9)
Build the secure, governed foundation that every migrated workload will land in.
- Design the account or subscription structure, network topology and on-premises connectivity.
- Provision it with infrastructure as code, using Terraform or the provider's native tooling.
- Connect identity to the corporate directory and enforce least-privilege roles.
- Set up logging, monitoring, backup policies and security guardrails.
- Define tagging standards so costs map to applications and teams.
Milestone: A test workload deploys into the landing zone and passes the security review.
Pilot Wave (Weeks 10 to 12)
Move a small, low-risk group of workloads to prove your tooling and runbooks.
- Pick three to five workloads with few dependencies and willing owners.
- Write cutover runbooks with timings, go and no-go checkpoints, and rollback steps.
- Replicate servers or data with the provider's migration service or a third-party tool.
- Run acceptance and performance tests before switching DNS or traffic.
- Hold a retrospective and update the runbooks.
Milestone: Pilot workloads run in production in the cloud and their source systems are ready to switch off.
Migration Waves (Weeks 13 to 22)
Move the rest of the portfolio in dependency-aware waves at a pace the team can hold.
- Group workloads into waves by dependency cluster and business calendar.
- Schedule cutovers outside peak periods agreed with owners.
- Use replication for databases to keep downtime windows short.
- Track every wave on one dashboard: status, blockers, rollbacks.
- Decommission source servers as part of each wave, not at the end.
Milestone: All in-scope workloads are live in the cloud and source hardware has a retirement date.
Optimize and Operate (Weeks 23 to 26)
Right-size the new environment and hand it over to a stable operating model.
- Right-size instances using utilization data collected after migration.
- Buy savings plans or reservations for steady workloads.
- Set budgets, anomaly alerts and a monthly cost review with owners.
- Document operational runbooks and on-call duties.
- Shortlist replatform and refactor candidates for the next cycle.
Milestone: Owners review a monthly cost report by application, and the next modernization backlog is approved.
Cloud Strategy vs Cloud Migration Roadmap
A cloud strategy answers why and where: which business goals the cloud serves, which provider or providers you choose, and which principles apply to security and cost. A cloud migration roadmap answers when, in what order and who does it. It turns the strategy into phases, waves, owners and dates.
Keep both, but keep them separate. If the strategy is not signed, the roadmap stalls in the first phase while people argue about providers. If there is no roadmap, the strategy stays a slide deck. The envision phase above exists to lock the strategy decisions the roadmap depends on.
How the Phases Map to AWS and Azure Frameworks
The AWS Cloud Adoption Framework describes four iterative phases: Envision, Align, Launch and Scale. Envision ties initiatives to stakeholders and measurable outcomes, Align finds capability gaps, Launch delivers pilots in production, and Scale expands them. Microsoft's Cloud Adoption Framework for Azure uses seven phases: Strategy, Plan, Ready, Adopt, Govern, Secure and Manage. Each one answers a decision question.
You do not have to pick one vocabulary. Map your phases to the provider you chose so architects and partners recognize them.
- Envision and business case: AWS Envision, Azure Strategy.
- Discovery and assessment: AWS Align, Azure Plan.
- Landing zone: Azure Ready.
- Pilot and waves: AWS Launch and Scale, Azure Adopt.
- Optimize and operate: Azure Govern, Secure and Manage.
Choosing a Strategy per Workload with the 7 Rs
AWS lists seven migration strategies: Retire, Retain, Rehost, Relocate, Repurchase, Replatform and Refactor. Give each workload one of them during discovery. That lets you estimate effort and explain why some applications move fast while others wait.
Use these decision rules, based on the "About the migration strategies" section of the AWS Prescriptive Guidance guide for large migrations.
- Retire when an application has no business value left, or when your discovery data shows it is barely used. AWS gives examples: average CPU and memory use below 5 percent ("zombie" applications), average CPU and memory use between 5 and 20 percent over 90 days ("idle" applications), or no inbound connection in the last 90 days.
- Retain when compliance or data residency, hard dependencies, specialized hardware, a mainframe or a recent upgrade keep it on-premises for now.
- Repurchase when a SaaS product covers the need better than moving the old system.
- Rehost, relocate or replatform for most workloads in a large migration, then modernize once they are stable.
- Refactor only where the business case justifies it. The same AWS guide says refactor is not recommended for large migrations, because it is the most complex and costly strategy. Use it only when the other strategies are not acceptable, and modernize after migration whenever you can.
Sequencing Migration Waves and Planning Rollback
A wave is a group of workloads that move together. Build waves from dependency clusters, not from the org chart. Applications that talk to each other heavily should cut over together, or latency and broken integrations will show up on day one.
Before you lock a wave, check these points.
- Every dependency is confirmed by the owner, not only by the discovery tool.
- The cutover window avoids month-end close, releases and peak sales periods.
- Each runbook has a named decision maker for go or no-go.
- Rollback steps are tested, and the source system stays intact until sign-off.
- Users and support teams have been told the date and what changes.
Roles, Governance and Sign-Off
The sponsor owns the outcome and unblocks budget. The roadmap owner, usually a PMO or IT program manager, owns dates, scope changes and reporting. Security approves the landing zone before the pilot, finance agrees on the cost allocation model before optimization starts, and each application owner signs off their own cutover.
Run the plan as parallel workstreams so each has dates and an owner: platform engineering, application migration, security and compliance, FinOps, operations and skills, and communications. Skills belong on the roadmap too. Teams that have never run cloud workloads need training before the waves, not after.
Presenting the Cloud Journey Roadmap to Leadership
Executives want one page: phases on a timeline, the hard deadlines, the success criteria from the charter and the top risks with their owners. Keep wave detail in a separate view for the migration team.
After each wave, update the forecast with real numbers: how many workloads moved per week and how many rollbacks happened. If the forecast misses a hard deadline, say so early and move low-priority workloads to a later wave instead of squeezing testing.
Example: Exiting a Colocation Facility
Picture a company with about 120 virtual machines in a colocation facility whose contract ends in nine months. Discovery shows most servers are lightly used, a legacy ERP runs on a large SQL Server database, and some file shares hold sensitive HR data. Most VMs are rehosted, the databases are replatformed onto a managed service, and a set of unused servers is retired.
The landing zone separates production, non-production and shared services. The pilot moves internal tools first. Finance systems are kept out of month-end windows. After migration, many servers that were sized generously on-premises are right-sized.
Common mistakes to avoid
- Migrating before mapping dependencies breaks applications at cutover, so validate every dependency with its owner first.
- Deploying workloads without a landing zone creates security and cost sprawl, so finish the governed foundation before the pilot.
- Rehosting at on-premises sizing inflates cloud bills, so right-size using utilization data collected after migration.
- Skipping rollback criteria turns small issues into long outages, so write go and no-go checkpoints into every runbook.
- Leaving source systems running for months means paying twice, so schedule decommissioning inside each wave.
- Treating training as optional leaves operations unable to support the platform, so plan hands-on training alongside the waves.
Frequently asked questions
What are the phases of a cloud journey?
AWS uses Envision, Align, Launch and Scale, and Azure uses Strategy, Plan, Ready, Adopt, Govern, Secure and Manage. In practice, most roadmaps follow the same steps: business case, assessment, landing zone, pilot, migration waves, then optimization. Give each phase a milestone so progress can be checked.
How long does a cloud migration take?
It depends on the size of the portfolio, the strategies you choose and your team's experience. This template uses six months for a first large migration where most workloads are rehosted or replatformed. A small portfolio can compress discovery and the landing zone into a couple of weeks, but should not skip them.
What is in a cloud migration plan template?
A good cloud migration plan template holds a charter, a portfolio register with an owner and strategy per workload, a landing zone design, a wave schedule, cutover runbooks with rollback steps, and a cost baseline. It also lists owners and sign-off points for security, finance and each application.
Which applications should migrate first?
Start with workloads that have few dependencies, low criticality and willing owners, to prove your tooling and runbooks. Then move dependency clusters together. Keep the most critical systems for later waves, once the team has practiced.
How do I handle compliance and data residency in the roadmap?
Flag these constraints during discovery, before you assign strategies. Some workloads will be retained on-premises or need a specific region. Security and compliance should approve the landing zone design before any production data moves.