Microsoft 365 comes with a suite of applications and services like SharePoint, OneDrive, PowerApps, Power BI, just to name a few, that cater to your critical business needs. One such service is Exchange Online which is a one stop solution to your organization’s communication needs. TrnDigital offers seamless Exchange Online Migration services. Whether you are using an On-premise exchange server or you are on a third-party mail server, migrating to Exchange Online is what you should be considering.
We put forth the various scenarios that an organization may have to choose from for their specific business needs.
Exchange online migrations
Office 365 supports a variety of approaches for migrating email to Exchange Online. They are cutover migration, staged migration, hybrid migration, IMAP migration, and the use of third-party tools to facilitate migrations. We will have a high-level look at how each of these migration approaches work.
Cutover migration is supported when migrating from any on-premises version of Exchange such as Exchange 2003, 2007, 2010, 2013, 2016 or 2019 to Office 365 in a single migration batch. Cutover is supported for up to 2,000 users. But migrating 2000 users at a time would be a bit of a challenge, due to which even Microsoft recommends a maximum of 150 users to be considered at a time. A cutover migration will migrate all mailboxes, contacts, and distribution groups from an on-premises Exchange organization. Cutover will not migrate any public folders or dynamic distribution groups.
Shortfalls of Cutover Migrations:
- All or No migration
- Incremental sync does not handle moves and changes well.
- DNS caching and TTL impacts the cutover.
- One way migration only
- Distributing new passwords to users
- Outlook clients and mobile devices need new profiles.
Staged migration is supported when migrating from on-premises versions of Exchange that do not support hybrid configuration, that is Exchange 2003 and 2007. Exchange 2010 and later support hybrid configuration. It migrates mailboxes in batches, allowing to migrate just a few users at a time instead of all users at once. When performing a staged migration, we need to install and configure directory synchronization, which synchronizes your users, their hash passwords, and other Active Directory objects into Azure AD using Azure AD connect.
Points to be considered during a Staged migration:
- Basic mail flow co-existence is not a full hybrid experience, not suitable for long term co-existence.
- Outlook Clients and mobile devices need new profiles.
- Migration batch interrupts user at beginning of the process.
- One way migration only
Hybrid migration is supported when migrating from on-premises versions of Exchange that support hybrid configuration, that is Exchange 2010 and later. Hybrid migrations have no minimum or maximum number of mailboxes that you can migrate and is suitable for organisation of any size. A hybrid migration will migrate all mailboxes and modern public folders, which means public folders hosted on Exchange 2013 or later. It does not migrate any contacts or distribution groups because those are synchronized using directory synchronization instead, which is a prerequisite for hybrid configurations. Nor does it migrate legacy public folders, which are public folders hosted on Exchange 2010 and earlier.
Advantages of Hybrid Migrations:
- Mailbox moves are Online, minimal user interruption.
- Outlook and mobile device profiles redirect to Exchange Online automatically
- Some technical pre-requisites to meet, but Hybrid Configuration Wizard handles most of the setup.
Unlike above migration methods, IMAP (Internet Message Access Protocol) migration supports users to migrate from Gmail, Yahoo, Hotmail, Outlook, or any other email system that supports IMAP migration. It uses the standard IMAP protocol.
Shortfalls of IMAP Migrations
- Limited to 500000 items
- Limited to 50000 total mailboxes
- Subject to throttling by source servers.
Third Party Migration Tools
Third party migration tools are helpful in
- Scenarios where the native migration methods will not work, such as moving between two separate Office 365 tenants,
- Scenarios when native migration methods do work, but a third-party tool can provide a better experience.
Some of the ways that third-party migration tools can make the experience better is
- Pre-sync oldest mailbox content first to reduce disruption during migration.
- Provides scripts or agents to reconfigure outlook automatically.
- Additional features for migrating PST files, public folders and OneDrive.
- Project management features
Deciding the Right Approach
The below table explains which identity models support which migration methods.
|Identity Model||Cutover||Staged||Hybrid||IMAP||Third Party|
|Cloud-only||Yes||Yes + #1||Yes + #1||Yes||Yes|
|Directory sync with password hash sync||No||Yes + #2||Yes||Yes + #2||Maybe + #3|
|Directory sync with pass through authentication||No||Yes + #2||Yes||Yes + #2||Maybe + #3|
|Directory Sync with federation||No||Yes + #2||Yes||Yes + #2||Maybe + #3|
#1: Requires provisioning directory sync for the migration period.
#2: Check current support requirement for on-premises Exchange Server when using directory synchronization.
#3: Check third party vendor documentation.
TrnDigital very well understands which migration approach is best suited for which business scenario. We have helped numerous organizations sift this change with utmost ease and comfort.