Workbook
Tenant migration planning workbook
Work through each section with your team to plan a Microsoft 365 tenant-to-tenant migration. Each answer you can't give yet is something to find out before the first wave.
1. Scope and dates
- Why is the migration happening: acquisition, divestiture, rebrand or consolidation?
- What dates are fixed, and what sets them?
- Which users, domains and workloads are in scope?
2. Inventory
- Users, shared mailboxes, resource mailboxes and groups
- Mailbox and archive sizes
- OneDrive and SharePoint volumes, sites and permissions
- Teams, channels and the chat history people need to keep
- Devices by type, join state and Autopilot registration
- Applications using single sign-on or sending mail
- Licences in both tenants
Read the rest of this workbook
Enter your work details to unlock this and every other guide on the site. We'll also send you a note in case you want to talk it through with an engineer.
3. Coexistence
- Free/busy and address list sharing
- Cross-tenant access and synchronisation settings
- Teams federation and external access
- The date coexistence ends
4. Waves
- Pilot group chosen and scheduled.
- Waves grouped by teams that work together.
- Pre-staging dates for mail and OneDrive.
- Cutover dates, communications and support for each wave.
5. Domains and devices
- Every object using the domain listed, with a removal script
- DNS TTLs lowered in advance
- Mail routing plan for the cutover window
- Device approach: reset with Autopilot, or unjoin and rejoin
- Autopilot registrations moved between tenants
6. Decommission
- Retention, legal hold and eDiscovery obligations checked
- Licences consolidated
- Source tenant retired on an agreed date
Next step
This guide supports Tenant-to-tenant migration. Talk to an engineer if you want it worked through for your environment.
Start a conversation
Fill in the gaps before the first wave.
Talk to an engineer about your tenant migration.
Talk to an Engineer