For large organizations with tens of thousands of mailboxes, an improperly executed migration from on-prem Exchange Server (e.g., Exchange 2013/2016/2019) to Microsoft 365 can result in an average downtime of 4 to 24 hours, leading to significant operational losses. A successful migration requires careful planning and a phased approach to ensure business process continuity.
Based on Softline IT’s experience, a common pitfall during this phase is underestimating the complexity of identity synchronization and lacking a detailed rollback plan. We always commence with an in-depth audit of the current infrastructure and meticulous planning.
Migration preparation: audit and requirements
The first and most critical step is a comprehensive audit of the current Exchange and Active Directory infrastructure. It’s essential to verify the health of the Exchange Server (using Health Checker, Best Practices Analyzer) and ensure all updates and patches are current. Confirm that all mailboxes and public folders are in working order. To migrate to Microsoft 365, Exchange Server 2010 SP3 or later is required. Additionally, the following are necessary:
- Identity synchronization: Implement Azure AD Connect to synchronize users and groups from the on-premise Active Directory to Azure AD. This enables Single Sign-On and simplifies management.
- Domain names: Add and verify domain names within Microsoft 365.
- Network bandwidth: Assess internet channel bandwidth. Migrating large data volumes (e.g., 10 TB of mailboxes) necessitates a stable channel with at least 100 Mbps, preferably 1 Gbps, to avoid delays.
- SSL certificates: Ensure all required SSL certificates are valid and correctly configured on the on-premise Exchange servers.
Choosing a migration method
Several primary migration methods exist, each suited for specific scenarios:
| Migration Method | Description | Advantages | Disadvantages | Recommended for |
|---|---|---|---|---|
| Cutover Migration | Migrates all mailboxes (up to 2000) simultaneously. | Simplicity, speed for small volumes. | Requires downtime, limited by the number of mailboxes. | Companies with up to 2000 users who can tolerate a short downtime. |
| Staged Migration | Migrates mailboxes in batches. | Minimal downtime, flexibility. | More complex implementation, only for Exchange 2003/2007. | Companies with 2000+ users on older Exchange versions. |
| Hybrid Migration | Establishes a hybrid environment between on-prem Exchange and Exchange Online. | Seamless transition, no downtime, coexistence of both systems. | Most complex implementation, requires maintaining hybrid configuration. | Companies with 150+ users requiring maximum flexibility and minimal downtime. |
| Third-party Tools | Utilizes third-party tools (e.g., BitTitan MigrationWiz). | Flexibility, advanced features, support for various sources. | Additional licensing costs, vendor dependency. | Companies with complex scenarios, migrating from other mail systems. |
For most medium and large enterprises aiming to minimize downtime, the hybrid approach is optimal. It allows for gradual mailbox migration while maintaining mail functionality throughout the transition.
Phases of hybrid migration without downtime
Implementing a hybrid migration involves these key steps:
- Configure hybrid connectivity: Use the Hybrid Configuration Wizard (HCW) to establish trust between the on-premise Exchange and Exchange Online. This allows mailboxes to be moved between environments without altering the mail client’s endpoint. HCW configures Free/Busy, MailTips, online archives, and other features.
- Identity synchronization: Implement and configure Azure AD Connect with the Exchange Hybrid Deployment option. This ensures the synchronization of user attributes necessary for Exchange Online to function correctly. It’s crucial to verify that the
msExchMailboxGuidandmsExchArchiveGuidattributes synchronize properly. - Pilot migration: Migrate a few pilot mailboxes to Microsoft 365. This verifies the correctness of settings, migration speed, and post-transition mail functionality. It’s recommended to test mailboxes with diverse content types and sizes.
- Phased migration: Migrate mailboxes in groups. This minimizes risks and allows for prompt response to potential issues. The migration process occurs in the background, and users can continue working with their mail without interruption.
- Update DNS records: After all mailboxes have been migrated, update the MX record and other DNS records (SPF, DKIM, DMARC) to route mail traffic directly to Exchange Online. This step is critical and must be carefully planned.
- Decommission on-premise Exchange: Following a successful transition and stable operation of all mailboxes in Microsoft 365, the on-premise Exchange servers can be decommissioned. It’s important to retain the on-premise Active Directory and Azure AD Connect for identity management.
Considerations for public folder and archive migration
The migration of Public Folders and Archive Mailboxes requires separate consideration. Public folders can be migrated using built-in migration tools or third-party solutions. For large volumes of public folders, batch migration is recommended. Archive mailboxes can be migrated along with primary mailboxes, or they can be configured as Online Archives within Microsoft 365.
It’s also important to consider integration with third-party systems, such as CRM, ERP, or document management systems, which may use Exchange for sending messages or accessing calendars. These integrations must be tested post-migration.
Before initiating the migration, ensure you have a clear understanding of your current Exchange infrastructure’s state, including all dependencies and integrations. Prepare a detailed migration plan encompassing the schedule, responsible parties, a rollback strategy, and a user communication plan. Pay close attention to selecting a vendor with proven experience in successful migrations, especially using hybrid scenarios, and who can provide references from other customers. Discuss testing possibilities and phased transitions with the integrator to minimize business risks.