AboutFree templates
Migration methodology

The cloud migration methodology, on one page

Six phases, a gate at the end of each, and the workstreams that run all the way through. Click any phase, gate or workstream for the detail, or download the diagram.

6 phases6 gates5 workstreamsFree download
Download the diagramStart with phase 1
Click a phase, gate (G1 to G6) or workstream. On a phone, scroll the diagram sideways.
Cloud migration methodology: six phases with gatesAssess, Plan, Design, Execute, Cut over and Close, each ending in a gate, with continuous workstreams for governance, risk, communication, security and testing.Cloud migration methodologySix phases, a gate at the end of each, and workstreams that run the whole way through. Works for email, files, servers, websites and apps.cloud-migrations.au/projectFree templates for every deliverable · General guidance, adapt to your projectRoll back if a trigger is hitPHASE 1AssessKnow what you have and decide whatmovesKEY ACTIVITIESInventory users, data and appsName an owner for everythingMap dependenciesCheck identity, licences, DNSPick a path per workload (7R)KEY DELIVERABLESMigration readiness assessmentApplication inventory and dep…Workload 7R decision matrixMailbox and data inventoryG1Readiness verdictPHASE 2PlanGet an approved scope, schedule,budget and teamKEY ACTIVITIESBusiness case and charterStakeholders and RACISchedule and budgetRisk register and RAID logCommunications and governanceKEY DELIVERABLESMaster migration project planRisk registerBusiness case and ROIProject charterG2Approved planPHASE 3DesignDecide where everything lands andhow to prove itKEY ACTIVITIESTarget-state architectureIdentity and data mappingWave planDNS, network and URL changesSecurity baseline and runbookKEY DELIVERABLESTarget-state architectureIdentity and licence mapping…Migration wave planNetwork and DNS worksheetG3Signed-off designPHASE 4ExecutePilot, then copy data in waveswhile users get readyKEY ACTIVITIESPilot with real usersUser acceptance testingBulk copy in wavesValidate data every waveTrain and communicateKEY DELIVERABLESPilot test planUAT test scripts and sign-offChange request (CAB)Daily status reportG4Pilot passed, data validatedPHASE 5Cut overSwitch over in a timed, reversiblesequenceKEY ACTIVITIESRunsheet and rollback planGo / no-go decisionFreeze and final syncSwitch DNS and routingSmoke test, then declare liveKEY DELIVERABLESCutover runsheetGo / no-go checklistRollback planDNS cutover record sheetG5Go-live confirmedPHASE 6CloseStabilise, hand over, switch offthe old systemKEY ACTIVITIESHypercare and issue logHandover to operationsCheck nothing uses the old oneDecommission safelyReview and lessons learnedKEY DELIVERABLESHypercare issue logDecommission checklistPost-implementation reviewLessons learned registerG6Project closed↻ REPEAT PER WAVEWORKSTREAMS THAT RUN ALL THE WAY THROUGHGovernance and reportingSteering meetings, status reports and decisions logged from day one to closure.Risk, issues and change controlRisk register and RAID log kept current; every production change goes through change approval.Communication and trainingTell people what changes, when and what to do: announcements, guides, training and support.Security and compliancePrivacy, data location, retention, holds and the security baseline checked at every gate.Testing and validationTest strategy, pilot, acceptance tests, per-wave data validation and post-cutover checks.Lessons learned feed the next migration
G1Readiness verdict
G2Approved plan
G3Signed-off design
G4Pilot passed, data validated
G5Go-live confirmed
G6Project closed
Workstreams throughoutGovernance and reportingRisk, issues and change controlCommunication and trainingSecurity and complianceTesting and validation
View the full diagram

Download the diagram

PDF posterA3 landscape, print-ready · 176 KBPNG imageHigh resolution, for slides and wikis · 733 KBSVG vectorScales to any size, editable · 27 KB

Free to use in your own project documents and presentations. Please keep the cloud-migrations.au credit.

How to use it

Every migration goes through the same six phases, whether you are moving 20 mailboxes or 2,000 virtual machines. Small projects move through them in days; large ones in months. Skipping a phase does not save time: it moves the work to cutover weekend, where it is most expensive.

  • Gates stop bad surprises. Do not start the next phase until the sponsor agrees the gate criteria are met. Each phase page has the full gate checklist.
  • Execute repeats. Run a pilot first, then the same copy, validate and communicate cycle for each wave.
  • Cutover is reversible until you declare live. Agree the rollback triggers and who decides before the go / no-go meeting.
  • Workstreams never stop. Governance, risk, communication, security and testing run from start to finish, not as one-off tasks.

Every deliverable has a free template in the template library, and each playbook under Migrate follows these phases for a specific move.