In this guide
For a safe email migration to Microsoft 365, we first record accounts, domains, mail flow and applications that send email. We then choose the appropriate migration method, run a pilot, prepare DNS and users, carry out the cutover and check mail flow, Outlook and mobile clients, aliases and security settings before considering the project complete.
1. Assess the environment before making changes
The user list is only the beginning. Record aliases, shared mailboxes, distribution lists, forwarding rules, domains, mailbox sizes and accounts used by applications or devices for SMTP. A scanner, ERP system or website form that sends email may need a different approach from a regular user.
Also record the current DNS settings and who has access to the registrar or DNS provider. Without that access, even a well-prepared migration can stall at the simplest step.
2. Choose the migration method
Microsoft supports different migration paths depending on the current system. On-premises Exchange, IMAP, other hosted email and hybrid environments are not migrated in the same way. The choice must consider user numbers, data volumes, identities and how gradually the migration needs to take place.
In every case, distinguish data copying and synchronisation from the final mail flow cutover.
3. Run a pilot before the general cutover
A small representative group helps test sign-in, Outlook profiles, mobile devices, shared mailboxes, permissions and applications. The pilot should include real daily use as well as a test email.
This is also the right time to identify MFA issues, older clients or applications using unsupported authentication methods.
4. DNS, MX and the final cutover
The MX record determines where incoming email is delivered. Plan its change alongside TTL, Autodiscover and the other required DNS records. After cutover, test incoming and outgoing messages from different domains, as well as internal accounts.
Then review SPF, DKIM and DMARC against the new mail flow. Migration is complete when users and applications have been confirmed to work correctly, beyond the MX change itself.
5. User communications and support
Users should know what will change, when migration will happen and where to ask for help. Short instructions for sign-in, MFA, mobile devices and Outlook can significantly reduce support requests on cutover day.
Frequently asked questions
Can migration take place with no downtime at all?
The goal is a controlled migration with minimal disruption, but the actual impact depends on the source, migration method, DNS and clients. A specific cutover window should be planned instead of making a general promise of zero downtime.
When do we change the MX record?
After the accounts are prepared and the migration has reached a stage where the new mail flow can be handled. The exact sequence depends on the method.
What about scanners and ERP systems?
Record them before migration. They may need SMTP relay, authenticated submission or another sending method, depending on the application and security policies.
Related services and guides
Discuss your next step with UniLoud
Send us your user count, current email platform and domains. We can prepare a migration plan with a pilot, cutover and user support.
