User query: “I need to migrate approx. 200 Exchange Online mailboxes into a new environment, making sure there is no data lost. The new servers are set up and ready to go; however, I’m not entirely sure of the process. Has anyone done this before and can they tell me the exact steps?”
Introduction: Microsoft 365 provides email boxes to millions of organisations using Exchange Online. As businesses grow, merge, or consolidate, they need to perform Exchange Online to Exchange Online mailbox migrations between Microsoft 365 tenants. If not done correctly, it can cause issues with emails and permissions, and previous emails will be lost. This can cause issues with productivity, compliance, and how they communicate with their clients. It is important to take a well-planned and tested approach to ensure your mailbox data is protected. In this guide, we will look at how to move mailboxes from Exchange Online to Exchange Online using both native Microsoft methods and the SysInfo Microsoft 365 Tenant-to-Tenant migration tool.
Before you start planning, as an administrator, it is important to know what is in your mailbox. When you are moving a mailbox between Exchange Online (Microsoft 365) instances, you should include the following items below in full.
Mailboxes for online archives, public folders, and groups are not managed through the mailbox process and will need to be planned separately. In addition, Teams' private chats will remain behind. There are also gaps at an item level using the native option, and this is discussed in a later section. Check what item types can be supported.
These problems recur across projects, so plan for each one early.
Complete this Microsoft 365 migration checklist in both tenants before moving any mailbox.
A finished migration is not a verified migration. Complete these checks before Exchange Online to Exchange Online Mailbox Migration decommissioning anything in the source tenant.
Items may fail or be skipped during your carefully planned project. These are highlighted in the migration report. Once you have identified the cause of the failure, you can retry only the objects that failed. As the source data has not changed during the process, this is safe to do.
| Issue | Likely Cause | Recommended Fix |
|---|---|---|
| Cannot connect to a tenant | Wrong credentials or missing permissions | Use a Global Administrator and reconnect |
| Authentication fails | Expired session or incomplete MFA | Sign in again and complete MFA |
| Mailbox not listed | Not created, licensed, or synchronized | Confirm the mailbox exists and is licensed |
| Migration is slow | Large volume, low bandwidth, or throttling | Use smaller batches and filters |
| Migration stops unexpectedly | Network interruption or service issue | Check connectivity and restart |
| Duplicate items appear | Existing destination data | Enable duplicate detection beforehand |
| Failed or skipped items | Unsupported items or temporary errors | Review the report and rerun failed objects |
Follow this retry sequence during Exchange Online to Exchange Online Mailbox Migration:
Follow these practices regardless of the method selected:
| Criteria | Native Cross-Tenant Migration | SysInfo Tenant to Tenant Migration Tool |
|---|---|---|
| Setup | Entra app, migration endpoint, organization relationship, PowerShell | Guided desktop interface; no scripts |
| Target preparation | MailUser per mailbox with ExchangeGUID, ArchiveGUID, and X.500 | Destination mailboxes created and licensed beforehand |
| Mailbox mapping | CSV file listing target addresses | Manual or automatic mapping in the interface |
| Scope control | Mail-enabled security group limits movable mailboxes | Mailbox selection plus date-range filter |
| Workloads | Mailbox data only | Mailboxes, SharePoint, OneDrive, Teams, PST/OST restore |
| Teams data | Teams chat folder not migrated; Groups unsupported | Teams channels, private chats, and Planner |
| Monitoring | Migration cmdlets and move reports | Active Tasks window with live progress |
| Error recovery | Fix each exception in PowerShell, then resume or resubmit | Review the report and rerun failed objects |
The successful Exchange Online to Exchange Online mailbox migration requires three stages: preparation, migration, and validation. Using the built-in cross-tenant migration option from Microsoft is ideal for admins, comfortable using PowerShell and only want to migrate mailbox data. The Microsoft 365 Tenant to Tenant Migration Tool provides a guided option to complete this project. This provides advanced filtering and handling options for mailboxes. A pilot should be run, then a staged migration performed. You can go through the demo version with its guide to migrate and evaluate it yourself before purchasing.
Can I migrate Exchange Online mailboxes from one tenant to another?
Ans. Definitely. The migration of mailboxes between tenants is possible using the Mailbox Replication Service. The migration application, endpoint, and relationship between the organisations are configured by admins, and mailboxes are migrated in batches. Mailboxes can be moved directly between tenants using an automated tool.
What mailbox data can be transferred during migration?
Ans. This will include migration of emails (including attachments), contacts, calendars, events, and shared mailbox information. The folder structure will be maintained. Group mailboxes, public folder mailboxes, and online archive mailboxes will need to be handled separately. We will also need a plan for Teams' private chats.
Can I migrate multiple Exchange Online mailboxes at once?
Ans. Surely. The tenant-to-tenant migration software allows multiple mailboxes to be migrated at a time. Simply select your mailboxes and map them to their equivalent mailbox on the destination. However, migrating users in smaller batches will reduce the risk of issues occurring and will make it easier to identify any issues.
Will users lose access to their emails during Exchange Online migration?
Ans. Users generally keep access to the source mailbox while data synchronizes in the background. SysInfo M365 Tenant to Tenant migration utility is recommended to use for secure and seamless migrations.
Can Exchange Online to Exchange Online migration preserve folder structure?
Ans. Definitely. The original folder structure (including subfolders and custom folders) will be retained using the native approach and by using quality migration tools. Check the structure on your pilot mailboxes before migrating the rest of your users.
Is Exchange Online to Exchange Online migration suitable for mergers and acquisitions?
Ans. Absolutely. Mergers and acquisitions are among the most common reasons for tenant-to-tenant moves. Consolidating mailboxes into a single tenant simplifies administration, licensing, and security management. The dedicated tool is designed to exactly handle these cases with its several advanced features and functionalities.
Can duplicate emails be removed during mailbox migration?
Ans. Duplicate items are not removed in the native method. However, using a specialist migration tool will skip over any duplicates. This will ensure that your target mailbox is clean and you are not wasting any extra storage.
What is the safest approach for Exchange Online to Exchange Online mailbox migration?
Ans. The most reliable way is to plan and validate. Audit the source tenant, licence the target users, backup the data, and run a pilot. Migrate in batches, leave the source tenant active until you’ve validated everything, and review the reports after each batch. This applies to both native and tool-based methods.
Does date-range filtering help with large Exchange Online mailboxes?
Ans. Yes. Filtering by date range limits the transfer to relevant items, which shortens migration time and reduces the load on large mailboxes. The native method lacks this option, whereas a professional tool applies the filter during the transfer. Administrators can later move older items in a second pass if needed.
Was this article helpful?