Email migrations fail less often because of a dramatic technical event than because the team did not know what was connected to the old system. Mailboxes, shared addresses, calendars, mobile devices, website forms and DNS records can all depend on details that are easy to overlook.
Inventory identities before changing anything
List active and former employees, shared mailboxes, distribution groups, aliases, forwarding rules and the administrators responsible for both systems. Verify control of the domain and DNS provider. Plan for emergency administrator access and multifactor authentication before making the tenant production-critical.
Check licensing needs for every user and application. Not every organization needs the same Microsoft 365 plan; choose based on security, device management and collaboration requirements rather than mailbox capacity alone.
Understand how mail actually flows
Mail flow may involve website forms, line-of-business systems, scanners, accounting tools and third-party services that send as the domain. Review SPF, DKIM and DMARC as part of the migration, along with any connectors or accepted domains.
Coordinate MX changes and migration phases carefully. A DNS change does not automatically transfer old messages, calendars or every application connection. Preserve an understood rollback or contingency path where technically feasible.
Plan the employee experience
Users need to know when to expect changes, whether Outlook or mobile email requires a new sign-in, how MFA enrollment will work, and whom to contact for help. Shared mailbox permissions and calendar delegation deserve explicit testing.
For SharePoint and OneDrive work, review file structure, ownership and external sharing. Moving a disorganized file share into the cloud without governance can preserve the very problems the migration was meant to solve.
Verify and document after cutover
Test inbound and outbound mail, external domains, delegated access, calendar invitations, mobile devices and any systems that send notifications. Verify DNS records and monitor rejected or misrouted messages.
Record tenant ownership, subscriptions, recovery procedures and the new operating process. A migration is complete when employees can work and administrators know how to support the environment—not when the MX record changes.
What to have in place
This article is general information, not a substitute for an environment-specific assessment. Requirements and service availability vary.
Explore related services