Microsoft 365 mailbox migration guide: Ensuring a smooth transition

Mailbox migration takes careful planning, the right tools, and precise execution. If you don’t get it right, you’ll soon be untangling a flood of user support tickets.

This guide to Microsoft email migrations will walk you through the best practices to follow as you transition away from legacy systems.

What is mailbox migration?

Mailbox migration means the transfer of email accounts, shared mailboxes, calendar items, contacts, and permissions. 

It’s typically part of a wider business strategy, like supporting modernization or cloud adoption. You’ll also need to migrate mailboxes when your organization restructures, whether that’s during a merger or as part of a bigger strategic shift. 

Migrations involving Exchange Online are one of the most common forms of mailbox migration scenarios, since many organizations rely on it for corporate email.

What are the best methods for mailbox migrations?

Here’s a quick overview of the most commonly used methods for mailbox migration.

On-premises to Exchange Online

If you’re running an email system on-premises and want to carry out a Microsoft 365 migration, you have a few options:

• Cutover migration: A single batch movement transfers all of your mailboxes and connected assets at once. While you can technically use this method to move up to 2,000 mailboxes, Microsoft recommends keeping it to 150 users or less because of the time it takes to create and migrate large numbers of users and mailboxes.
• Staged migration: If you’re using Exchange Server 2003 or 2007, you can use a staged migration to move mailboxes over time. This might be a good option if you’re looking to move a large number of mailboxes and want to minimize user disruption, but keep in mind that this strategy can’t be used for Exchange 2010 or 2013 mailboxes.
• Hybrid migration: A hybrid migration strategy is a phased approach where you connect your on-premises Exchange Server to Exchange Online. Mailboxes can then exist in both environments, making this a useful option for complex moves. 

Tenant to tenant

If your company restructures or goes through a merger, you’ll need to migrate mailboxes from one M365 tenant to another. Tenant-to-tenant migration is one of the more complex mailbox migrations, as you’ll have to deal with mailboxes, company-wide permissions, shared data, and contact information across two or more environments—in other words, things can get hectic fast. And while Microsoft provides some native cross-tenant mailbox migration capability and support for these scenarios, many organizations find that using third-party tools to simplify planning, automation, and reporting makes the migration process simpler and more efficient.

Third-party email migration services cut out the manual work. Automated tenant-to-tenant migration simplifies the process to a handful of steps, helping you migrate without the headache.

From non-Exchange systems

Migrating to M365 from another provider is definitely possible, but the process includes a few extra steps. Moving from an Internet Message Access Protocol (IMAP)-based system like Gmail means you’ll need to first create the corresponding Exchange Online mailboxes in Microsoft 365 before migrating the email content into them, because IMAP migration only transfers email messages and does not create the mailboxes for you.  Since standard IMAP migration doesn’t migrate  calendars, contacts or tasks, these items will need to be migrated separately.

You’ll set up new mailboxes in M365 for each user, migrate their emails, and then import the final touches afterwards.   While in limited scenarios, organizations may ask users to import specific email data themselves, you’ll want to have your administrator manage your migrations for consistency and data integrity. Third-party tools like ShareGate can save you a great deal of time by automating much of the process.

Pre-migration planning and preparation

Taking stock of everything you’ll be migrating before you get started will minimize potential errors and keep downtime as low as possible. 

Here’s what to include in your Microsoft 365 migration prep: 

• Mailbox inventory: Flag every mailbox you’ll be migrating, such as user and shared mailboxes, and identify any inactive mailboxes, which require separate compliance handling and aren’t migrated like standard mailboxes.
• Permissions and compliance policies: Check for any existing compliance policies like data retention or data loss prevention (DLP), and verify that the permissions in your new environment are correct. You can use the Microsoft Purview compliance portal to confirm these ahead of time, helping make sure your migration is smooth and stress-free. 
• Technical readiness check: Email systems can be surprisingly complicated under the hood. Make sure technical elements like your Domain Name System (DNS), Autodiscover, Sender Policy Framework (SPF) records, and Active Directory are all working ahead of time. 
• Decommissioning and data retention: Establish how long you’ll keep your old environment live, and create a data deletion framework. Once everything is safe and verified in an Exchange mailbox, you can begin decommissioning your legacy platform.
• Let your end users know: Let users know what you’re doing. Offer rough timelines, support lines to help them through the transition, and training sessions to bring them up to speed on their new mailbox environment.

Step-by-step mailbox migration process

Once you’ve wrapped up your pre-migration prep, you’re ready to get started. Here’s how to perform the migration (and what to do after).

Performing the migration

Every migration is unique. A tenant-to-tenant move will look different from an on-premises to Exchange Online migration. But they still share plenty of steps, including:

1. Connect migration endpoints: Depending on the migration method, you’ll either configure migration endpoints (IMAP, cutover, staged) or create migration batches for remote mailbox moves in hybrid or cross-tenant scenarios.
2. Manage batches and schedules: Unless you’re overseeing a small migration, you’re probably going to need to work in batches. Schedule chunks of migration for weekends or downtime when people won’t be using their email. 
3. Handle large mailboxes: If you’re migrating large mailboxes that contain years of data, consider archiving anything outdated before the move. Migrating a large volume of mailboxes can migration throughput and completion times due to service throttling.
4. Troubleshoot common issues: Verify that each mailbox works as expected ‌before you hand it back over to the user. Check for missing permissions, broken access, and lost folders. Fixing these common issues will help you avoid sticky situations, like someone having unauthorized access to another’s emails.

Post-migration tasks

During post-migration, you’ll check that everything’s working as it should, verify data integrity, and fully cut away from your legacy environment. Here are the main post-migration tasks: 

1. Inspect licenses: Check to see if users have working M365 licenses and that their mail systems work as expected. Send out some test emails from internal and external accounts to verify. 
2. Validate mailboxes: Make sure that everything remains intact during the migration. Test that permissions are all still correct, and check that access settings, contacts, events, and email folders all transferred over correctly.
3. Provide support: Offering quick-start guides, tutorials about the new email environment, or even just a helping hand can bring people up to speed much quicker than just sending their new account details.
4. Decommission old environments: Once the migration is complete, it’s time to wind down your legacy email system. Archive anything you might need, revoke permissions, and remove access.

Mailbox migration best practices

As the saying goes: Fail to prepare and prepare to fail. Staying one step ahead can make all the difference between a smooth migration and a support headache.

Here are a few best practices to keep in mind when migrating to Exchange Online:

• Ensure data integrity: Check and double-check that mailbox data migrated correctly before decommissioning your legacy environment. 
• Minimize downtime: Use scheduled and phased rollouts to minimize disruption and downtime, especially for large-scale migrations.
• Maintain compliance and security: Check that your new mail environment follows any required regulatory compliance configurations—DLP, multi-factor authentication, and data retention policies should all be squared away.
• Keep an eye on network performance: Look for unstable connections or inconsistent transfer speeds to spot potential issues.

Simplify your mailbox migration with ShareGate

Mailbox migration can be a complex job, but through strategic planning, precise execution, and reliable tooling, you can make the process far more manageable. 

ShareGate Migrate supports mailbox migration from Microsoft 365 tenant to tenant and from Google Workspace (Gmail) to Exchange Online. With ShareGate, you can map source and destination mailboxes, select what content to copy (emails, calendars, contacts, mailbox rules), and review post-migration reports to verify success. This makes it easier to migrate user and shared mailboxes, move messages, calendars, contacts, and mailbox rules with less manual scripting—increasing predictability and reducing risk. 

Mailbox migration doesn’t have to feel risky. With ShareGate, you can plan ahead, move what matters, and double-check results before you call it done. Start a free trial or request a demo today.