Migrating from on-premises Exchange to Microsoft 365

Moving from Exchange Server (on-premises) to Exchange Online is one of the most common Microsoft 365 migrations. The mechanics are mature, but the right approach depends on size, version, and how long you'll coexist.

The four main migration types

1. Cutover migration

For tenants with fewer than ~150 mailboxes on Exchange 2003–2019. All mailboxes move at once, no coexistence, simple to plan and execute.

• Microsoft moves all mailboxes via Outlook Anywhere over a few days.
• Users get a brand-new Microsoft 365 account on cutover day.
• No directory sync; user accounts are fresh in Entra ID.
• Simple, fast, but disruptive on the cutover day.

2. Staged migration

For larger Exchange 2003 / 2007 organisations (legacy versions). Migrate mailboxes in batches with cross-premises coexistence. Increasingly rare as these versions are long out of support.

3. Hybrid migration

The modern enterprise default. Set up an Exchange hybrid deployment (covered in its own guide), then move mailboxes in waves over weeks or months while users keep working. The recommended path for organisations with 150+ mailboxes or Exchange 2010+.

• Free/busy works across on-prem and cloud during coexistence.
• Mailbox moves are seamless from the user's perspective.
• Email flow continues to work through the hybrid namespace.
• Move at your own pace; pause if needed; reverse if necessary.

4. PST import / IMAP migration

For unusual cases — third-party mail systems, departed users, archived content. Move data via PST files or IMAP rather than direct mailbox move. Slower and less complete, but flexible.

What needs to happen

Regardless of migration type, the typical steps:

1. Plan and licence. Buy Microsoft 365 licences. Decide on identity model (cloud-only, hybrid).
2. Set up identity sync. Install Entra Connect or Cloud Sync, sync users.
3. Set up hybrid (for hybrid migration). Run the Hybrid Configuration Wizard.
4. Configure DNS for hybrid mail flow if relevant.
5. Pilot migration. Move IT mailboxes first; verify everything works.
6. Wave migration. Migrate users in batches (typically 50–200 per wave).
7. Update DNS — final MX cutover at the right point.
8. Decommission on-premises Exchange (mostly).

Co-existence period

During hybrid migration, both Exchange Online and Exchange Server are live. Mail flows between them transparently. Users in the cloud calendar correctly with users on-prem. The co-existence can last weeks or months.

This is the period when most operational complexity lives. Plan for:

• A help desk that supports both clients.
• Documentation for both worlds.
• Migration-status dashboards.
• Communication to users at their wave.

Decommissioning on-premises Exchange

After all mailboxes are in Exchange Online, the on-premises Exchange Servers can be mostly decommissioned. Microsoft historically required keeping at least one Exchange server for managing mail-attribute objects on AD-synced accounts. The newer Exchange Server SE Management Tools and growing Entra ID support for managing recipient attributes have eased this — full on-prem-Exchange-free is increasingly viable.

Common pitfalls

• Public folders are a pain. Plan their migration carefully or migrate to Microsoft 365 Groups.
• Mailbox quotas in Microsoft 365 differ from on-prem; very large mailboxes (>50GB) need archive policies.
• Outlook profile reconfiguration at cutover — Autodiscover handles most, but plan for help-desk volume.
• OWA URL changes — communicate the new URL.
• Mobile devices need to re-authenticate; Exchange ActiveSync clients can be quirky.

For most organisations, a hybrid migration over 2–6 months is the right answer. The work is well-understood, the tooling is mature, and the destination is meaningfully better than running your own mail.