Microsoft 365 Tenant Migration Readiness Checklist
Planning to consolidate, separate or move users between Microsoft 365 tenants? Use this checklist to assess the identities, workloads, applications, devices and compliance requirements before approving the migration.
Planning to consolidate, separate or move users between Microsoft 365 tenants? Use this checklist to assess the identities, workloads, applications, devices and compliance requirements before approving the migration.
A Microsoft 365 tenant migration moves supported data. Identities, applications, devices, security and source-tenant closure still require separate control.
Business Case
- □ Define merger, acquisition, separation or restructuring reason
- □ Identify executive sponsor
- □ Confirm critical dates
- □ Record legal and contractual obligations
Tenant Control
- □ Verify source Global Administrator access
- □ Verify target Global Administrator access
- □ Confirm tenant IDs
- □ Confirm domain and DNS access
- □ Record delegated suppliers
Identities
- □ Inventory users
- □ Inventory guests
- □ Inventory groups
- □ Inventory privileged accounts
- □ Map source and target identities
Exchange
- □ Measure mailboxes
- □ Identify archives
- □ Record permissions
- □ Review connectors
- □ Review retention and holds
OneDrive
- □ Measure storage
- □ Review external sharing
- □ Review departed-user content
- □ Confirm target provisioning
SharePoint
- □ Inventory sites
- □ Record site types
- □ Measure storage and items
- □ Review permissions
- □ Identify Teams connections
Teams
- □ Inventory Teams and channels
- □ Review chats and meetings
- □ Locate recordings
- □ Record apps, tabs and voice services
Applications
- □ Inventory enterprise applications
- □ Inventory app registrations
- □ Record secrets and certificates
- □ Review SSO and provisioning
Devices
- □ Inventory Intune devices
- □ Review Autopilot
- □ Record certificates and VPN
- □ Plan re-enrolment
Security
- □ Configure target administrators
- □ Configure MFA
- □ Review Conditional Access
- □ Review external collaboration
- □ Confirm backup
Delivery
- □ Confirm migration licences
- □ Select pilot users
- □ Plan coexistence
- □ Document domain cutover
- □ Prepare communications and support
Validation
- □ Review migration reports
- □ Test mail and files
- □ Test applications
- □ Test devices
- □ Complete restore testing
Decommission
- □ Preserve compliance records
- □ Resolve source dependencies
- □ Remove delegated access
- □ Obtain written approval
- □ Close the source only after validation
Plain-English Takeaway
A Microsoft 365 tenant migration moves supported data. Identities, applications, devices, security and source-tenant closure still require separate control.
Downloadable guide
Microsoft 365 Tenant Migration Readiness Checklist
Download this checklist as a printable PDF to use with your team or migration partner.
Download PDF ChecklistFree to download. No registration required.
Want the full business explanation?
The Technology Intelligence article covers why this matters, where it helps and what to watch out for.
Read the full Technology Intelligence articleRelated Knowledge Centre resources
Google Workspace to Microsoft 365 Migration Checklist
A structured checklist for planning a move from Google Workspace to Microsoft 365. Covers business case, tenant ownership, users, email and calendars, files, applications, target design, security, pilot, cutover, validation and controlled decommissioning — with key reminders on permissions, backup and retention.
View guideSensitive Information and AI Checklist
A structured checklist for reducing information before using AI tools and deciding whether a service is appropriate. Covers classification, approval, data minimisation, file preparation, prohibited information, Temporary Chat steps, review and warning signs.
View guideVulnerability Patch Wave Readiness Checklist
A structured checklist for assessing whether your organisation can prioritise, test and deploy security patches as AI-assisted vulnerability discovery increases the volume and frequency of updates. Covers assets, exposure, updates, prioritisation, testing, deployment, exceptions and unsupported systems.
View guide