Cloud Migration Plan Template
Put every system in the wave it moves, colour it by migration strategy, and keep its approach, risks and rollback one click behind it.
Free forever on the Personal plan
Cloud migration plans: an example
Waves at a glance
Every system in the wave it moves, from the foundation to the exit.
Strategy by colour
Rehost, replatform, rebuild, replace or retire, shown by colour with a key.
Exit conditions
Each wave ends when a condition is met, not when a date passes.
The basics
What is a cloud migration plan?
A cloud migration plan sets out how an organisation will move its systems to the cloud: which systems move, in what order, with which strategy, the dependencies between them, and how each move is tested, cut over and rolled back if needed. Most plans group systems into waves.
Strategies are often summarised as the 6 Rs: rehost, replatform, refactor, repurchase, retire and retain. A plan that shows each system's strategy and wave on one page lets a steering group see the size and order of the work before reading any detail.
In Blueprintr every system on the plan opens a stratum with its approach, cutover, rollback and risks, so the one-page view and the detail are kept together.
Why Blueprintr
Migration plans a steering group can follow
Every wave on one page, each move one click deep.
Waves as bands
Draw each wave as a container and each system as a card, coloured by strategy, with a key and an exit condition at the end of every band.
VellumApproach and rollback behind cards
Give every card a stratum with how it moves, the cutover window, the rollback, the risks and the owner.
StratumAn inventory to start from
On the Team plan, Continuum Cloud reads AWS and Azure; on Enterprise, Continuum Local discovers on-premise network devices and hosts over SNMP.
ContinuumDependencies on their own tab
Keep a dependency map as a second diagram tab in the same blueprint, so the order of the waves can be checked against it.
Steering group updates
On Premium, present progress wave by wave with Podium, from the same canvas the team updates.
PodiumCutover runbooks beside each move
Add the cutover steps to each card's stratum as a numbered procedure, so the plan and the runbook never disagree.
How to
How to build a cloud migration plan in Blueprintr
Create a blueprint
Sign up free and create a blueprint for the migration programme.
List the systems
Add a card for every system in scope and choose its migration strategy.
Group them into waves
Put the foundation first, retirements last, and every other system after what it depends on.
Write each move
Add a stratum to every card with its approach, cutover, rollback, risks and owner.
Track and present
Update the cards as moves finish, publish each week and walk the steering group through it.
FAQ
Questions about cloud migration plans
Is this cloud migration plan template free?
Yes. The Vellum editor and strata are on the free Personal plan. Continuum Cloud is part of the Team plan, Continuum Local is Enterprise, and Podium presentations need Premium.
What are the 6 Rs of cloud migration?
Rehost (move as is), replatform (move to a managed service with little change), refactor or rebuild, repurchase or replace with a cloud product, retire, and retain where it is. Many plans use five, as in the example above.
How do I decide which systems go in which wave?
Start with the foundation every system needs, then move systems after the ones they depend on, low-risk systems before critical ones, and anything time-bound, such as a contract or lease, before its deadline.
Can Blueprintr discover what I need to migrate?
In part. On Enterprise, Continuum Local discovers on-premise network devices and hosts over SNMP; on the Team plan, Continuum Cloud reads AWS and Azure. Applications and their owners you add yourself.
Does Blueprintr move the workloads?
No. Blueprintr plans and documents the migration; it does not copy data or move servers. Your migration tools do that, and the plan records what was moved and when.
Can I share the plan with the steering group?
Yes. Share the blueprint privately with named people, or present it with Podium on Premium. Every publish keeps a snapshot, so earlier versions of the plan are kept.