Exchange Online to Exchange Online Migration: Secure Migration Guide

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.

Why Organizations Migrate Exchange Online to Exchange Online?

Tenant-to-tenant moves are rarely optional. They are usually triggered by a business event that changes how the organization is structured. The most common scenarios include the following:

  • Mergers and acquisitions: The acquirer consolidates the acquired company's mailboxes into one tenant.
  • Divestitures: A business unit leaves and needs its own tenant.
  • Rebranding: New primary domains are required when you change your brand
  • Tenant consolidation reduces licensing costs and reduces security issues.
  • Data location: Some regulations may require a tenant to be located in a certain area.
  • Compliance boundaries: Keep regulated mailboxes inside a separate tenant
  • IT environment cleanup: Start fresh in a governed tenant
  • Business unit realignment: Internal reorganizations change mailbox ownership

What Mailbox Data Can Be Transferred during Exchange Online to Exchange Online Mailbox Migration?

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.

  • Emails: Inbox, Sent Items, Drafts, Deleted Items, and custom folders
  • Attachments: Embedded files and inline images
  • Calendars and events: Default and custom calendars, including recurring events
  • Contacts: Names, phone numbers, job details, and photos
  • Shared mailboxes: Migrated alongside primary mailboxes
  • Folder hierarchy: Original structure preserved

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.

Common Challenges in Tenant-to-Tenant Migration

These problems recur across projects, so plan for each one early.

  • Conflict of identity - rarely match proxy addresses
  • Routing issues - may bounce before DNS changeover.
  • Profiles - Everyone will need new Outlook profiles.
  • No licence - The destination mailboxes will have no licence, so they will be inaccessible.
  • Unsupported data types - Archive & Public Folders will need bespoke handling.
  • Large volumes - Batching required.

Pre-Migration Checklist for an Exchange Online to Exchange Online Mailbox Migration

Complete this Microsoft 365 migration checklist in both tenants before moving any mailbox.

  • Export users and record mailbox sizes
  • Clear holds before native migration
  • Create and license destination mailboxes
  • Verify domains; resolve UPN conflicts
  • Confirm Global Admin on both tenants
  • Register Entra app; open port 443
  • Pilot and back up before cutover

Methods to Perform Exchange Online Migrations between Tenants

In this section of the current article, we will look at two different methods of performing the migrations and compare them to each other. Each migration method will have its own method, capabilities, limitations, and flexibility.

Method 1: Native Cross-Tenant Migration for Exchange Online to Exchange Online Mailbox Migration

Microsoft's native mailbox migration across tenants uses the Mailbox Replication Service (MRS) to migrate mailboxes directly between tenants. This includes migrating email, contacts, calendar entries, tasks, and notes. This would be a good method for administrators who are comfortable using PowerShell and the Microsoft Entra admin centre.

The general steps:

There are several SharePoint Online migration challenges:

  • Prepare Both Tenants: the Entra migration app, consent, an organization relationship in each tenant, and the mail-enabled security group that scopes which mailboxes can move.
  • Configure Target MailUsers: ExchangeGUID, ArchiveGUID, and X.500 addresses. It warns that licensing before the ExchangeGUID is set creates a new empty mailbox.
  • Create the Migration Endpoint: this heading keeps your Microsoft link, and the step adds a Test-MigrationServerAvailability check.
  • Create Migration Batches: the CSV lists target-tenant addresses. Batches stay under 2,000 mailboxes and go in about two weeks before cutover.
  • Monitor the migration using the monitoring cmdlets, checking for common issues such as mailboxes out of scope and no ExchangeGUID.
  • Verify the mailboxes have been migrated. The source mailbox will be converted to a mail user. Check that mail is flowing, folders, contacts, calendars, and that Outlook profiles have been recreated.

Limitations of the Native Method

Administrators should weigh these constraints before performing an Exchange Online (Microsoft 365) to Exchange Online (Microsoft 365) Mailbox Migration, choosing the native route:

  • Complex setup: Requires Entra app registration and PowerShell
  • No selective filtering: Date-range or folder filters are unavailable
  • Public folders: Not supported by cross-tenant migration
  • Strict attribute matching: Mismatched GUIDs cause failures
  • Limited reporting: Granular item-level logs are scarce
  • No built-in deduplication: Duplicate emails migrate as-is

This can add some risk, effort, and time to any native migrations. Large projects are likely to be the most affected, as all issues have to be resolved manually. Many of these issues can be solved with a specialised tool which can filter, deduplicate and provide detailed reporting.

Method 2: Exchange Online to Exchange Online Mailbox Migration Using a Professional Migration Tool

SysInfo's Microsoft 365 Tenant-to-Tenant Migration Tool is a Windows and macOS desktop application that allows connection between two tenants using the Microsoft Graph API for secure authentication. It can be run on the local host to help reduce any sync errors. Data is transferred directly between the tenants using TLS-encrypted HTTPS. As it uses the Graph, it is unaffected by Microsoft retiring EWS. There is also a single console that can be used to manage a number of other Microsoft 365 workloads.

Key Mailbox Capabilities:

  • Secure sign-in: OAuth 2.0 and MFA; no passwords stored
  • Admin Impersonation: Log in with Client ID and Secret ID
  • Mailbox items: Emails, calendars, contacts, and shared mailboxes (Standard copy)
  • Exchange environments: Exchange Online, on-premises, and hybrid
  • Mapping: Manual or automatic source-to-destination mapping
  • Batch migration: Bulk mailbox mapping in one run
  • Date-range filter: Set start and end dates for phased moves or legal holds
  • Duplicate detection: Compares subject, body, sender, and recipients
  • Duplicate filters: Date, sender, subject; incremental scans
  • Safe duplicate handling: Preview, then delete, bin, or custom folder; metadata and headers kept
  • Skip previously migrated: Enables incremental passes without repeats
  • Folder options: Mapped default folders or one custom parent folder
  • Attachment control: Migrate with or without attachments
  • Mailbox permissions: Supported; secret-based sign-in needs a certificate
  • Live tracking: Active Tasks shows speed, time, and data transferred
  • Detailed reports: Total, migrated, skipped, and failed counts
  • PST export: Custom names, destination folders, and size splitting

Beyond Mailboxes: Other Workloads

The same tool also handles data outside the task to Migrate Exchange Online to Exchange Online, which suits tenant consolidations that include more than email.

  • SharePoint: Sites, document libraries, and standard lists
  • SharePoint exact copy: Permissions, sensitivity labels, and folder colors within a tenant
  • OneDrive Migration: Files and folders between tenants
  • OneDrive exact copy: Versions, metadata, and permissions within a tenant
  • OneDrive and SharePoint: Move files in either direction; existing files count as skipped
  • Mapping options: Drives by UPN or name; sites by URL or ID
  • HTML archive: Source-matching copy for verification
  • File filters: Size, extension, and content type (documents or lists)
  • File deduplication: SharePoint sites and OneDrive accounts
  • PST/OST restore: Restore PST and OST (emails, contacts, calendars, tasks, and folder structure); flags corrupted PSTs
  • Teams Migration: Channels, private chats, files, tabs, and apps
  • Teams destination: New team or existing channel; names configurable, ownership kept
  • Planner: Plans, buckets, tasks, assignments, and checklists
  • Teams selection: Choose specific teams or channels
  • Teams mapping: Drag-and-drop or bulk CSV; auto-mapping for private chats
  • Teams delta sync: Skip previously migrated items

Supported Plans and Requirements:

  • Plans: E1, E3, E5, Business, Academic A1–A5, Frontline F1
  • Memory: 4 GB RAM; 8 GB recommended
  • Disk space: 1 GB minimum
  • Platforms: Windows 11, 10, and earlier; Apple M-series Macs
  • Editions: Single, Administrator, Technician, Enterprise
  • Network: Outbound HTTPS port 443; VPN for high latency

Steps to Exchange Online to Exchange Online Mailbox Migration:

  1. Launch the tool and click Exchange < Mailboxes.
  2. Sign in(Source), then click Connect and Verify.
  3. Select the source mailboxes, then sign in (destination).
  4. Map each source mailbox to a destination mailbox
  5. Apply Filters and Click Start Migration.
  6. Open All Reports to review migrated, skipped, and failed counts.

This tool’s step-by-step instructions are mentioned in its complete software guide to understand it completely. You can also customize it as per your needs.

Need a Customized Migration Application?

If you need to have some extra features developed for your organization, we can develop custom applications for you. This will include a Customization Plan. We will have a team of engineers working on designing a solution for you. The application will be built to fit with your infrastructure and brand. Here is a detailed breakdown of what this means. To get started, contact our support team and share your requirements

Limits to Plan For

  • Mailbox types: Primary and shared mailboxes only
  • Not covered: Online archive, public folder, group mailboxes
  • Destination mailboxes: Must exist and be licensed beforehand
  • Free demo: 500 emails per folder
  • Teams chats: Plan separately from mailbox moves

White-Label Migration Service for IT Vendors and MSPs

IT vendors and MSP's who manage tenant migrations can use our white-label email migration service. We will handle migration of the mailboxes whilst you manage the relationship with your client. This is a great option for those who only migrate on an occasional basis and do not want to have a dedicated team. If you are migrating from other platforms, please see our Email Migration services, or speak to our technical team to explain your requirements.

Post-Migration Validation Checklist

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.

  1. Compare report counts
  2. Match folder item counts
  3. Spot-check calendars and contacts
  4. Test mail flow both ways
  5. Confirm Outlook connectivity
  6. Verify licenses and sign-in
  7. Retain the source tenant

Handling Migration Errors and Retries

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:

  1. Navigate to All Reports and note how many items have failed and skipped.
  2. Use the table above to identify the cause.
  3. Correct the permission/licensing/mapping issue.
  4. Try migrating again, using the option to skip migrating emails already migrated.
  5. If this does not help, then please contact support and provide the report and version number.

Best Practices for a Safe Exchange Online Migration

Follow these practices regardless of the method selected:

  • Migrate in phases
  • Schedule off-peak cutovers
  • Lower DNS TTL in advance
  • Keep the source tenant active
  • Confirm Outlook connectivity
  • Test mail flow
  • Reconfigure Outlook profiles
  • Document everything
  • Review security settings
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

Conclusion

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.

Frequently Asked Questions

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?

0 out of 0 found this helpful