Migrating Exchange Online mailboxes between Microsoft 365 tenants is not just about moving emails from one place to another.
A mailbox contains much more than messages. It can include calendar events, contacts, tasks, inbox rules, mailbox permissions, archive content, and compliance-related settings. If these areas are not planned properly, users may face missing access, broken rules, failed replies, or incomplete mailbox functionality after migration.
This guide explains the major areas organizations should review before starting an Exchange Online tenant-to-tenant mailbox migration.
Why Exchange Online Mailbox Migration Is Complex
At first, mailbox migration may sound simple: move the mailbox from the source tenant to the target tenant.
In reality, the challenge is not only the mailbox data. The bigger challenge is preserving the surrounding configuration that makes the mailbox usable.
For example, users may depend on:
- Delegated mailbox access
- Send As and Send on Behalf permissions
- Inbox rules
- Shared mailboxes
- Online archive mailboxes
- Retention policies
- Calendar data
- Microsoft To Do tasks
- Reply and Reply All behavior after domain changes
If these dependencies are missed, the migrated mailbox may exist in the target tenant, but users may still experience issues.
Common Reasons for Tenant-to-Tenant Mailbox Migration
Organizations usually perform Exchange Online mailbox migration during major business or IT changes.
Common scenarios include:
- Mergers and acquisitions
- Company divestitures
- Microsoft 365 tenant consolidation
- Rebranding or domain changes
- Compliance-driven tenant restructuring
- Moving users from one Microsoft 365 environment to another
Each scenario can introduce different risks, especially when usernames, domains, or identities change during the migration.
Prerequisites Before Migration
Before starting the mailbox migration, the target tenant must be prepared properly.
Important prerequisites include:
- Creating matching MailUser objects in the target tenant
- Establishing an organization relationship between source and target tenants
- Configuring the required application registration and permissions
- Assigning the correct Exchange Online licenses
- Planning DNS and domain verification
- Preparing user and mailbox mapping
- Reviewing archive mailbox requirements
If the domain is moving from one tenant to another, the cutover must be planned carefully because a domain can only be verified in one Microsoft 365 tenant at a time.
What Usually Migrates
In a typical Exchange Online tenant-to-tenant migration, the following mailbox data can be migrated:
- Inbox, Sent Items, Drafts, and custom folders
- Emails and attachments
- Calendar items
- Contacts
- Tasks and notes
- Server-side inbox rules
- Mailbox permissions, when properly mapped
- Archive mailboxes, when enabled and licensed in the target tenant
However, admins should not assume that every mailbox-related setting will move automatically.
What May Not Migrate Automatically
Some items may not migrate or may require separate handling.
Examples include:
- Client-side Outlook rules
- Transport rules
- Retention tags and MRM policies
- Meeting response tracking metadata
- OneDrive-linked attachment URLs
- Some app-layer Microsoft To Do features
- Permissions that are not properly mapped
- Items blocked by size limits
This is why a migration checklist is important. It helps avoid surprises after cutover.
Inbox Rules Need Special Attention
Inbox rules are often overlooked during mailbox migration.
Server-side rules may migrate, but they can break if folder paths, recipient addresses, or target-domain mappings are not correct.
Client-side rules are different. These rules depend on Outlook and local client behavior, so they usually need to be recreated manually.
Admins should review:
- Server-side rules
- Client-side rules
- Rules that forward or redirect messages
- Rules that move messages to folders
- Rules using old recipient addresses
- Rules affected by domain changes
After migration, users should test important rules to confirm they still work.
Cross-Domain Migration and Reply Issues
Cross-domain migration can create additional issues.
For example, a user may move from:
*john.doe@companyA.com *
to:
If old addresses remain inside message headers, calendar items, or rules, Reply and Reply All actions may still point to outdated addresses.
This can cause replies to fail or route incorrectly.
For migrations involving domain and username changes, admins should plan address mapping carefully and validate reply behavior after migration.
Mailbox Permissions Matter
Mailbox permissions are one of the most important parts of an Exchange Online migration.
Many organizations rely on delegated access for daily work. For example:
- Executive assistants managing executive mailboxes
- Support teams using shared mailboxes
- Finance users accessing billing mailboxes
- HR teams managing recruitment or employee communication mailboxes
Important permission types include:
- Full Access
- Send As
- Send on Behalf
- Folder-level permissions
If these permissions are not migrated or reassigned correctly, business users may lose access after cutover.
Admins should export permissions before migration, map users correctly, and validate delegated access in the target tenant.
Shared Mailbox Migration
Shared mailboxes are commonly used by teams for addresses such as:
- support@
- billing@
- sales@
- hr@
- info@
These mailboxes are important because multiple users may depend on them every day.
When migrating shared mailboxes, admins should confirm:
- The mailbox exists in the target tenant
- Required permissions are preserved or reassigned
- Send As and Send on Behalf permissions work
- Members can access the mailbox
- Mail flow works after cutover
- Licensing requirements are understood
Shared mailbox migration should be tested carefully because it can affect entire departments, not just individual users.
Archive Mailbox Migration
Archive mailboxes require separate planning.
A user’s primary mailbox and archive mailbox may have different size, licensing, and performance considerations. Archive mailboxes must be enabled in the target tenant, and the correct license must be assigned.
Admins should review:
- Whether the source mailbox has an archive
- Archive mailbox size
- Target tenant licensing
- Auto-expanding archive requirements
- Migration performance
- Post-migration archive access
Archive migration is often missed during planning, but it can become a major issue for users who rely on historical email data.
Retention Policies and Compliance
Retention policies do not always move cleanly between tenants.
Organizations may be moving from older Exchange retention methods to Microsoft Purview retention. This requires careful compliance planning.
Admins should review:
- Existing MRM retention tags
- Personal retention tags
- Microsoft Purview retention policies
- Legal hold or compliance requirements
- Deletion and archive behavior
- User communication needs
Retention settings should be reviewed before migration, not after users report missing or unexpected email behavior.
Microsoft To Do and Mailbox Migration
Microsoft To Do is closely connected to Exchange Online because many tasks are stored as Outlook tasks inside the mailbox.
Core task data may move with the mailbox, such as:
- Task titles
- Due dates
- Reminders
- Categories
- Attachments
However, some Microsoft To Do app-level features may not migrate in the same way, such as list sharing, checklist steps, custom ordering, or My Day history.
Users who rely heavily on Microsoft To Do should be informed about possible limitations before migration.
EWS Retirement and Migration Planning
Another important consideration is the future of Exchange Web Services.
Microsoft is moving away from EWS, and migration tools that still depend on EWS need to plan for Microsoft Graph support. The original Apps4.Pro guide notes that EWS will be disabled by default on October 1, 2026, and permanently removed by April 1, 2027.
This is important for long-term migration planning. If your organization has large migrations scheduled around or after this period, confirm whether your migration tools support Graph API.
Post-Migration Validation Checklist
After migration, do not stop at confirming that the mailbox exists in the target tenant.
Admins should validate the full user experience.
A practical checklist includes:
- User can access the mailbox
- Emails and folders are available
- Calendar items are present
- Contacts are available
- Tasks are available
- Server-side rules work
- Delegated permissions work
- Send As and Send on Behalf work
- Shared mailbox access works
- Archive mailbox is accessible
- Retention behavior is correct
- Reply and Reply All work with the new domain
- Mobile and Outlook clients are reconfigured if needed
Validation should include both IT testing and business-user confirmation.
Best Practices for Exchange Online Tenant Migration
To reduce risk, follow these best practices:
- Start with a full mailbox inventory
- Identify shared and archive mailboxes early
- Export mailbox permissions before migration
- Map users and domains carefully
- Review server-side and client-side rules
- Prepare target tenant licenses in advance
- Plan domain cutover timing
- Communicate known limitations to users
- Test pilot users before large migration waves
- Monitor mail flow and mailbox access after cutover
A phased approach is usually safer than moving everything at once.
Final Thoughts
Exchange Online mailbox migration between Microsoft 365 tenants requires more than mailbox data transfer.
A successful migration must also account for permissions, rules, shared mailboxes, archive mailboxes, retention policies, Microsoft To Do tasks, domain changes, and future API changes such as EWS retirement.
The best approach is to plan early, document every dependency, test with pilot users, and validate the user experience after migration.
When these steps are handled properly, organizations can reduce disruption and give users a smoother transition to the new Microsoft 365 tenant.
Original Source
This article was originally published on Apps4.Pro:
Exchange Online Mailbox Migration Guide
Top comments (0)