How to Migrate from Exchange Server to Microsoft 365 (Complete Guide)?

The Hybrid migration requires the use of the Hybrid Configuration Wizard (HCW) along with the Microsoft Entra Connect, and is the recommended method for most organisations. The process typically takes 4–8 weeks depending on mailbox count and infrastructure readiness.

Quick Reference: You can refer the decision table in Section 2 that can help you identify the best migration path to use, based on your mailbox count and Exchange version.

Section 1: Which Migration Method is Right for You?

With the use of the decision table in this section, you can identify the migration method based on your Exchange Server version, mailbox count and other migration requirements like the migration method. Each method is linked to the full step-by-step guide.

Section 2  - Version-Specific Migration Paths

This section will aid you to choose the migration path, depending on the specific version of your Exchange Server. Each link will open the unique guide covering the supported Cumulative Update version and step-by-step migration path to choose. Although you should always have the Exchange Server updated to the latest Cumulative Update (CU) level, there are some technical constraints that might stop you from doing this. Then again, it’s very important to check the update level to ensure the compatibility with the chosen migration path.

Section 3 - Benefits of Migrating to Microsoft 365

There are several advantages and benefits when upgrading to Microsoft 365, which could improve productivity, security and integration. Let’s look at the most common ones.

No Infrastructure Maintenance or Server Cost

Because the infrastructure is cloud-hosted, all the maintenance, hardware, connectivity and resilience are taken care of by Microsoft, and all you need is just an internet connection. This eliminates the overhead of hardware, networking, and other maintenance.

Subscription-based Cost Model with Predictable Monthly Spend

Microsoft 365 is a subscription based service and licenses are not purchased upfront or pay for software assurance expense. You can have a mix and match of licenses depending on the needs and cost can be easily forecast and planned.

Built-in Redundancy, Disaster Recovery, and Security Updates managed by Microsoft

This is another example of shifting of responsibilities vis-a-vis the local infrastructure. Having the cloud counterpart, all the security updates, resilience, patching, and disaster recovery are taken care of by Microsoft. Despite this, you will need to take care of securing your tenant with tools, such as Multi-Factor Authentication (MFA), conditional access, and device lockdown, since Microsoft has a shared responsibility policy in place.

Section 5 — Pre-Migration Checklist

You must complete the below migration checklist to ensure a successful migration. Missing these prerequisites is the most common reason for the Hybrid Configuration Wizard (HCW) failure and migration batch errors. These can result in the project failure and missing data.

Section 6 - Methods to Migrate from Exchange to Office 365

Use the comparison table below to understand the key differences between each method.

Here are the full step-by-step instructions to perform these methods.

Method 1 — IMAP Migration

For an IMAP migration, you should take these steps.

1. Enable IMAP and check connectivity with the TCP ports - 143 and 993 for IMAP, while also verify with a login test.
2. Create the Microsoft 365 tenant, verify the domains, and add the users.
3. Preparation of the migration CSV for the migration batches.
4. Run the IMAP migration batches and monitor progress.
5. Cut over the DNS and complete the migration process.

For more details, refer to this (Microsoft Learn: IMAP Migration).

Method 2 — Cutover Migration

Cutover migration is the process to move the data using migration batches and change the DNS records after the migration of data is complete. Here are steps to perform this migration:

1. Prepare the on-premises server with the latest Cumulative Updates (CU).
2. Prepare and connect the Microsoft 365 to your Exchange Server with a migration endpoint.
3. Start the cutover migration batch and monitor it.
4. Complete the cutover and switch the DNS to point to Microsoft 365.

Here’s the (Microsoft Learn: Cutover Migration).

Method 3 — Staged Migration

This method uses migration batches and coexistence. It support only Exchange Server 2003 and 2007. Following these steps to perform this migration:

1. Prepare the on-premises server and ensure that Outlook Anywhere is functioning.
2. Set up Microsoft Entra Connect.
3. Create the migration batches and monitor progress.
4. Switch mail flow and complete migration.
5. Clean up and decommission the Exchange Server

Method 4 — Hybrid Migration (Recommended)

This is the recommended method for organizations using Exchange 2010–2019. It is suitable for more than 150 mailboxes. It involves zero-downtime and remote mailbox moves with full coexistence. To perform hybrid migration, follow these steps:

1. Prepare the on-premises server and fully update it.
2. Setup of Microsoft Entra Connect.
3. Setup and configuration of the Hybrid Configuration Wizard (HCW).
4. Remote move of the mailboxes.
5. Transition the mail flow and decommission the server.

Section 7 — Post-Migration Checklist

After a successful migration, below are the steps you should follow:

• Verify Email Flow: Test MX records, Autodiscover, internal and external email delivery.
• Complete User Configuration: Setup new Outlook profiles, reconfigure mobile device, and enable MFA.
• Update DNS Records: SPF, DMARC, DKIM, and Autodiscover CNAME.
• Monitor for 30 days: Keep on-premises Exchange running for minimum 30 days post-cutover as rollback window.
• Decommission on-premises Exchange: Decommission only after confirming all users are working correctly on Microsoft 365. See: full decommission guide.
• Monitor Mail Flow and Check for Common Post-migration Issues: See: mail flow issues guide.

Section 8 — Common Migration Errors Hub

The table below lists the most common Exchange to Microsoft 365 migration errors, their causes, and a link to the full fix guide. Use this as your starting point when troubleshooting migration issues.

Section 9 — Use Stellar Migrator for Exchange  

You can use Stellar Migrator for Exchange - a specialized Exchange migration tool to simplify and accelerate the Exchange to Microsoft 365 migration without requiring PowerShell or manual configuration. This tool supports all the versions of Exchange Server. Moreover, it features automatic mailbox matching, delta (incremental) migration, and real-time migration reporting.

The tool is ideal when there are issues with the current configuration due to constraints, incompatibility, or other issues. Here are some examples:

• Hybrid Configuration Wizard (HCW) prerequisites cannot be met (certificate expired, CU version too low, firewall restrictions, etc.).
• Mailboxes exceed 100 GB and M365 throttling causes repeated failures.
• Multiple migration batches need to be managed simultaneously across sites.

To Conclude

In this guide, we have explained different methods for migrating from an on-premises Exchange Server to Microsoft 365. Depending on your setup and requirements, you can use the native migration methods - IMAP, cutover, staged, and hybrid. However, you may face various errors and issues when using these methods. For quick and hassle-free migration, use Stellar Migrator for Exchange – a specialized tool for Exchange to Office 365 migration.