Company email is usually the first thing a business moves to the cloud. An in-house mail server has to be patched, backed up and protected from spam. Microsoft support for Exchange Server 2016 and 2019 ended in October 2025. Microsoft 365 takes the server off your hands, but the move itself needs a plan. Change the MX record the wrong way and customers’ emails bounce. Forget a scanner or an accounting system and invoices stop arriving.
Below: how to move email to Microsoft 365 — migration methods, preparation, DNS records, security and a checklist. We draw on Microsoft’s documentation.
Migration methods
The method depends on where your email is now:
| Source | Method | What moves | Notes |
|---|---|---|---|
| Exchange 2003–2013, up to 2,000 mailboxes | Cutover migration | email, calendars, contacts | all mailboxes move in one batch; Microsoft recommends moving no more than 150 mailboxes this way |
| Exchange 2013 and later | Hybrid migration | email, calendars, contacts | on-premises and cloud mailboxes work side by side, users move in batches |
| Google Workspace | Google Workspace migration | email and rules, calendars, contacts | users move in batches; shared calendars and room bookings don’t move, rules arrive turned off |
| Hosting or another IMAP server | IMAP migration | email only | mailboxes must be created in Microsoft 365 first; contacts and calendars are moved separately |
| PST archives | PST Import Service | archived email | files are uploaded over the network or shipped on a drive |
The 150-mailbox figure for a cutover migration is a recommendation, not a technical limit: Microsoft explains that creating and migrating more users takes too long.
If you have Active Directory and users should sign in to Microsoft 365 with the same credentials, plan account synchronisation in advance. That makes it a hybrid setup — see “Hybrid cloud: what it is and when you need it”.
Preparation
- Inventory. Mailboxes, shared mailboxes, distribution groups, aliases, forwarding rules, mailbox and archive sizes.
- Everything that sends email. Scanners and multifunction printers, accounting systems, the website, CRM, monitoring systems. For these, Microsoft describes separate options: sending through an authenticated mailbox, relaying through a connector, or Direct Send. Microsoft is retiring sending with Basic authentication (username and password) and recommends modern OAuth authentication. The device must support TLS 1.2 or later, otherwise sending through a mailbox won’t work. Check older devices in advance.
- Domain. Add the domain to Microsoft 365 and prove ownership with a TXT record.
- Licences. Choose a plan and assign licences to users. After a cutover migration, a mailbox without a licence is disabled when the 30-day grace period ends.
- Caching time. Before the move, lower the TTL of the MX record to 3,600 seconds (one hour). Senders’ mail systems will then pick up the new delivery address sooner.
- Users. Tell them the date of the move, about the new Outlook profile and about setting up email on their phones.
Cutover: DNS records
| Record | Purpose | Watch out for |
|---|---|---|
| MX | where email for the domain is delivered | change it once the mailboxes exist; delete the old MX or give it a lower priority |
| CNAME autodiscover | automatic setup of Outlook and mobile clients | Microsoft calls it optional but highly recommended |
| TXT (SPF) | which servers may send email on behalf of your domain | a domain must have a single SPF record: add the Microsoft 365 value to the existing one instead of creating a second |
| CNAME (DKIM) | a digital signature on outgoing email | two records, selector1 and selector2, then turn on signing in Microsoft 365 |
| TXT (DMARC) | what to do with email that fails the checks | start in monitoring mode with reports |
Microsoft warns that it can take up to 72 hours for your customers’ and partners’ mail systems to see the new MX record. So don’t delete the migration batch for at least 72 hours. Before deleting it, make sure the mailboxes have synchronised once more after email started arriving in Microsoft 365. Otherwise messages that reached the old server in the meantime won’t make it to the new mailboxes.
How to set up SPF, DKIM and DMARC and gradually move to blocking spoofed email — see “Anti-spam: the first line of email defence”.
Security from day one
- Multi-factor authentication. Microsoft Entra ID has security defaults: all users register a second factor, administrators complete it at every sign-in, and legacy protocols that can’t do multi-factor authentication, such as IMAP and POP3 with a password, are blocked. Security defaults are turned on by default for new tenants. More flexible Conditional Access policies require a Microsoft Entra ID P1 licence. More in “Two-factor authentication for business”.
- Administrators. Separate accounts for administration and everyday work. Microsoft also recommends two cloud-only emergency Global Administrator accounts for when regular accounts can’t be used.
- Filtering. Email in Microsoft 365 is checked by the built-in Exchange Online Protection. Whether that is enough and when a separate gateway is needed — see the anti-spam article.
- Backups. Under the shared responsibility model, Microsoft is responsible for running the service, while data and accounts are yours. Decide how and where to back up email — see “3-2-1 backup rule: protecting business data”.
After the move
- Make sure all new email arrives in Microsoft 365, and only then delete the migration batch.
- Check that every user has a licence.
- Check scanners, accounting systems and the website: does their email get through?
- Remove the old server from the SPF record once it no longer sends email.
- Using DMARC reports, move the policy from monitoring to quarantine and then to reject.
- Decide what to do with the on-premises Exchange. Microsoft warns that decommissioning Exchange can have unintended consequences and recommends contacting support first.
Common mistakes
- Changing the MX record before the mailboxes exist — email bounces back to senders.
- Creating a second SPF record instead of extending the existing one.
- Forgetting a scanner, accounting system or website that sends email.
- Not lowering the TTL in advance — and waiting longer for the switch.
- Shutting down the old server right after changing the MX record.
- Putting multi-factor authentication off “until later”.
Email migration checklist
- There is a list of mailboxes, groups, aliases and forwarding rules
- There is a list of devices and systems that send email, with a sending method for each
- A migration method has been chosen for your mail system
- The domain is verified and licences are assigned
- The MX record’s TTL was lowered to one hour in advance
- Users know the date and the new settings
- MX, autodiscover, SPF, DKIM and DMARC are set up
- Multi-factor authentication is on and legacy protocols are blocked
- There is a decision on how to back up email
- The migration batch was deleted only after checking delivery and a final sync
How Bereg-IT can help
As part of IT infrastructure we work with Microsoft Exchange and Office 365. We inventory mailboxes and everything that sends email, choose the migration method and plan the DNS cutover. Then we move the email, set up SPF, DKIM, DMARC and multi-factor authentication, and support the system after the move. If you need a separate filtering gateway, we deploy FortiMail. Events from Microsoft 365 can be sent to SOC as a Service. For moving to the cloud more broadly, see cloud solutions and “Cloud migration: a step-by-step plan for business”.
The first consultation is free. Send a request and we’ll suggest how to move your email.
Sources
- Microsoft Learn, Ways to migrate multiple email accounts to Microsoft 365 or Office 365 — migration methods: https://learn.microsoft.com/en-us/exchange/mailbox-migration/mailbox-migration
- Microsoft Learn, Migrate email to Exchange Online using the Exchange cutover method — limits, TTL, 72 hours, licences, decommissioning Exchange: https://learn.microsoft.com/en-us/exchange/mailbox-migration/cutover-migration-to-office-365
- Microsoft Learn, Perform a Google Workspace migration to Microsoft 365 or Office 365 — what moves from Google Workspace: https://learn.microsoft.com/en-us/exchange/mailbox-migration/perform-g-suite-migration
- Microsoft Learn, Connect your domain by adding DNS records — MX, autodiscover, SPF, DKIM: https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider
- Microsoft Learn, How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 — sending email from devices and applications: https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365
- Microsoft Learn, Configure Security Defaults for Microsoft Entra ID — security defaults, emergency access accounts: https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults
- Microsoft Lifecycle, Exchange Server 2016: https://learn.microsoft.com/en-us/lifecycle/products/exchange-server-2016; Exchange Server 2019: https://learn.microsoft.com/en-us/lifecycle/products/exchange-server-2019
- Microsoft Learn, Shared responsibility in the cloud — who is responsible for what: https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility