Tenant-to-Tenant Microsoft 365 Migration Checklist

Tenant-to-tenant migrations are business-change projects disguised as technical projects. Identity, domains, mail, SharePoint, Teams, OneDrive, Power Platform, compliance, external users, and support all need coordinated planning.

The migration often supports an acquisition, divestiture, rebrand, consolidation, or carve-out. The business event determines timing, access, separation, communications, and risk tolerance.

Define the business event

Clarify:

• Why the migration is happening
• Which users, groups, departments, and workloads are in scope
• Whether the move is a consolidation, separation, or staged coexistence
• Which domains must move and when
• Whether users need same-day cutover or phased access
• What must remain confidential between organizations

Inventory the tenants

Capture:

• Users, groups, shared mailboxes, resource mailboxes, and service accounts
• Domains, DNS, MX, SPF, DKIM, DMARC, and mail routing
• OneDrive storage and sharing links
• SharePoint sites, Teams, channels, tabs, and apps
• Guests and external sharing
• Power Apps, Power Automate flows, connectors, and environments
• Retention, labels, legal holds, audit requirements, and eDiscovery
• Security policies, Conditional Access, and privileged roles

Plan identity and domains early

Domain release, DNS, mail routing, federation, sync, MFA, Conditional Access, and privileged access decisions can drive the whole cutover schedule.

Questions to resolve early:

• Which tenant owns the primary domain after cutover?
• How will users authenticate during coexistence?
• What happens to UPNs, aliases, and mail routing?
• How will guests and external users be handled?
• How will service accounts and applications authenticate after migration?

Validate collaboration workloads

Teams, SharePoint, OneDrive, sharing links, guests, apps, tabs, and Power Platform dependencies need explicit validation. Do not assume mailbox migration covers the collaboration experience.

Validation should include:

• Executive users and critical departments
• Team owners and channel owners
• Shared files and links
• Meeting rooms and calendars
• Apps, tabs, and connectors
• Workflows and forms tied to migrated content

Prepare support

Executive users, high-touch departments, help desk scripts, escalation channels, and hypercare windows should be ready before the migration wave begins.

Support planning should include:

• Communications timeline
• User action checklist
• Help desk triage scripts
• Known issues page
• Rollback or contingency plan
• Executive escalation path

Next step

Use the Tenant-to-Tenant Migration Timeline Estimator, then consider the Microsoft 365 Tenant Migration Assessment for a fixed-scope roadmap.