AboutFree templates
Free template · Design phase

Technical migration runbook template

Step-by-step technical procedure for each workload. Free download in Word.

CM-TPL-DES-06Design phaseWordFree
Download Word (.docx)
Free download

Download the technical migration runbook template

The step-by-step technical procedure for migrating each workload (mail, OneDrive, SharePoint, Teams and devices), written so any engineer on the team can execute it the same way every wave.

Download Word (.docx)

Free to use and adapt. Document ID CM-TPL-DES-06, version 1.0, November 2026.

What's inside

What the template includes

Document sections

  1. Scope and environment · Name source and target, migration tools, accounts used and the waves this runbook applies to.
  2. Prerequisites (complete before any wave) · List every one-off build task that must be complete and verified. Tick and date each.
  3. Mail and calendar migration · Each step: what to do, the exact command or path, and what you should see.
  4. OneDrive migration · Include pre-provisioning, pre-stage and delta passes.
  5. SharePoint and shared data migration · Cover site creation, permissions, migration passes and link fixes.
  6. Teams and collaboration · Teams chat history from other platforms usually does not migrate natively; state what moves and what does not.
  7. Devices and endpoint reconfiguration · Describe how each device type is reconfigured or re-enrolled, and the self-service steps users follow.
  8. Post-migration validation · Checks the engineer runs before handing the wave to hypercare.
  9. Rollback per workload · Describe how to reverse each workload and the point after which rollback is no longer possible.
  10. Known issues and workarounds · Keep this updated from the pilot and each wave.
How to use it

How to use this template

  1. Write the runbook during the build, then rehearse every step in the pilot and correct it before wave 1.
  2. Keep one row per step with the exact command, portal path or tool setting; avoid "configure as required".
  3. Record the expected result for every step so the operator knows what good looks like before moving on.
  4. Use the cutover runsheet for timing and owners on the night; this runbook is the how-to that the runsheet refers to.
  5. Version the runbook after each wave with lessons learned and any changed commands.
Built to a standard

Ready to share with your steering committee

  • Branded cover or instructions page with document ID and version
  • QR code linking to the latest version, and a Code128 barcode for your document register
  • Document control, approval block and a clear disclaimer
  • Example rows written for real migration projects, which you replace with your own
Use it with

Guides that use this template

How to migrate Microsoft 365 Groups and Planner plans to another tenantHow to migrate Power BI to another Microsoft 365 tenantPower Apps and Power Automate tenant-to-tenant migrationHow to migrate VMware and physical servers to AWSHow to migrate VMware, Hyper-V and physical servers to AzureHow to migrate VMware virtual machines to Hyper-V
FAQ

Questions about this template

Is the technical migration runbook template free?

Yes. Download it in Word and adapt it for your organisation. No sign-up is needed.

Can I use it in Google Sheets or Google Docs?

Yes. Upload the file to Google Drive and open it with Google Sheets or Docs. Dropdowns and most formulas carry across; check conditional formatting after converting.

Can I remove the Cloud-Migrations branding?

Yes. Replace the logo and footer with your own. Keep the disclaimer in mind: the template is general guidance and needs adapting to your project.

How do I know I have the latest version?

Scan the QR code on the cover or instructions sheet. It opens this page, which always links to the current version.