Migrate Shared Mailboxes Between Office 365 Tenants: Admin’s Guide

“We are planning to consolidate two Microsoft 365 shared mailboxes after a recent acquisition. Around 150+ shared mailboxes with around 110 GB of emails are to be moved without any data loss, and several departments have this delegated access. Is there any way to do it with zero or near-zero downtime or data loss? What approach should I use, or are there any limitations or prerequisites that I must know of? How to handle the access and permissions, or are there any real-world experiences that give confirmation? Thanks in advance!”

-Mol, Microsoft Learn

Shared mailboxes are built to ease the task of admins and users by consolidating tasks from a single email address. Multiple users can simultaneously access emails, send communications, view archived history and records, and manage other departmental data, improving productivity. But mergers, acquisitions, divestitures, and rebranding demand that users migrate shared mailboxes between Office 365 tenants. But it is quite a complex and critical migration task to handle. Hence, this tenant-to-tenant shared mailbox migration guide states a free way and the SysInfo Microsoft 365 Tenant to Tenant Migration Tool for secure large-scale migrations.

It must be noted that unlike primary user mailboxes, shared mailboxes have delegated permissions, Send As rights, shared calendars, archives, and collaborative access patterns. If you don’t have a planned migration, then it can result in duplicates, broken permissions, missed folders, and extended disruptions in the business. 

Top Factors to Migrate Shared Mailboxes Between Microsoft 365 Tenants

Some of the popular business scenarios that demand users to transfer shared mailboxes are:

  • Mergers and acquisitions
  • Divestitures and rebranding
  • Tenant consolidation and restructuring
  • Domain and brand changes/relocation
  • Compliance and Microsoft standardization

In all of these situations, migration becomes critical. It is also due to the fact that this migration involves more than copying mailboxes. This involves emails, folders, hierarchy, permissions, delegates, shared calendars, archive mailboxes, compliance settings, metadata, etc. The reason this matters is:

  • Preservation of historical records and communications 
  • Departmental data organization and continued workflow
  • Long-term data retention and meeting compliance needs 

Prerequisites for Shared Mailbox Migration Without Data Loss

In order to have a secure and successful cross-tenant migration Microsoft 365 shared mailboxes, you need to fulfil this checklist:

  • Gather all shared mailbox names and aliases 
  • Document their size and locate archive mailboxes 
  • Verify admin roles and check available licences 
  • Validate domains and check DNS readiness
  • Record permissions for Send As and Send On Behalf
  • Plan pilot test migration batches and prepare cutover 

Manually Migrate Shared Mailboxes Between Office 365 Tenants

There are two methods for you to perform the shared mailbox migration. The first one is using Microsoft Exchange, and the other one via Outlook/PowerShell. We will discuss each one of them in detail as follows:

1) Exchange Online Microsoft 365 Shared Mailbox Migration

With the cross-tenant migration features of Microsoft, you can move shared mailboxes between tenants. However, it is suitable only for IT administrators and needs careful planning, permissions, and validation. Steps are:

  1. Initially, set up the destination shared mailboxes along with the target tenant.
  2. Then, edit the migration settings and cross-trust appropriately. Assign necessary permissions and roles. 
  3. Further, establish migration endpoints between both tenants.
  4. Also, create migration batches containing the shared mailboxes.
  5. Perform the first sync of Office 365 Tenant to Tenant Migration
  6. Afterward, recreate any delegated permissions for that shared mailbox post-migration.
  7. Verify that the mailbox contents, folders, and archive are correct.
  8. Finally, complete the final cutover and change email routing if necessary.

Key Considerations To Remember

  • Delegated permissions do not transfer automatically. 
  • Shared mailboxes under 50 GB do not need licences. 
  • If archive is enabled for shared mailbox, the total migrating data volume increases. 
  • If the mailbox is over 50 GB, assign Exchange Online Plan 1 or 2 and increase quota upto 100 GB.
  • Stripping a licence from a shared mailbox over 50 GB can hit quota limits and stop functioning. 

2) Outlook Migrate Shared Mailboxes Between Office 365 Tenants

This is another method available, but it is highly technical and needs manual effort. Also, you may need to temporarily convert the shared mailbox to a user account first for migration. Note that you need to assign a licence temporarily, which you can remove after the migration if the mailbox is under 50 GB. Follow these steps:

  1. First, open the source tenant and export all the permissions. 
  2. Get-MailboxPermission -Identity “MySharedMailbox” | Where-Object {$_.User -ne “NT AUTHORITY\SELF”} 

    Get-RecipientPermission -Identity “MySharedMailbox” | Where-Object {$_.Trustee -ne “NT AUTHORITY\SELF”} 

    Get-Mailbox “MySharedMailbox” | Select GrantSendOnBehalfTo 

  3. Next, convert your shared mailbox to a primary user mailbox using the command:
  4. Set-Mailbox “MySharedMailbox” -Type Regular 

  5. Further, assign the licenses. Now, sign in to your Microsoft Outlook with this account. 
  6. Export the entire data into the PST file for import into the target shared tenant mailbox later. 
  7. Afterward, create a new shared mailbox in the target tenant account with:
  8. Set-Mailbox “MigratedSharedMailbox” -Type Shared 

  9. Import the PST file into this mailbox on the target tenant via Outlook. 
  10. Later, re-map all the Full Access, Send As, and Send on Behalf permissions manually. 
  11. In the end, re-convert your source mailbox back to shared or delete it entirely as desired. 

Shortcomings of the Manual Method 

  • Permission mismatches resulting in data loss 
  • Duplicate emails increase the storage space 
  • Large mailboxes (100GB+) face throttling issues 
  • Failed migration batches mean extended downtime 
  • Slow syncs and folder mapping errors lead to incomplete transfers 
  • Licencing conflicts bring in migration interruptions 
  • Scheduled disruptions due to calendar permissions loss 
  • Auto-mapping is not restored, so double the labor 
  • Time-consuming, complex, and no built-in monitoring 

Smartly Migrate Shared Mailboxes Between Office 365 Tenants

Large organizations, businesses, and enterprises often prefer staged migrations or a reliable M365 Tenant Migration Software. This is where SysInfo Microsoft 365 Tenant to Tenant Migrator proves beneficial. It handles dozens or hundreds of shared mailboxes in GBs and TBs, reducing the administrative manual effort. With multiple capabilities and an intuitive GUI, it is suitable for technical and non-technical users on Windows and Mac OS. To understand its working, check out the simple steps below. 

Steps to Transfer Shared Mailboxes Between Microsoft 365 Tenants

  1. Launch the Microsoft 365 Migration Software and proceed with Copy Mailboxes. 
    Launch the Microsoft 365 Migration Software and proceed with Copy Mailboxes
  2. Then, enter your Shared Mailbox M365 ID and Authenticate your account. 
    enter your Shared Mailbox M365 ID and Authenticate your account
  3. Further, select your mailboxes to migrate and click on Continue to Destination
    select your mailboxes to migrate and click on Continue to Destination
  4. Afterward, choose the destination mailboxes and map them accordingly. 
    choose the destination mailboxes and map them accordingly
  5. Finally, use the filters that you want to customize results and click Start Migration. 
    use the filters that you want to customize results and click Start Migration

Comparing Solutions to Transfer Shared Mailbox with Emails and Folders

We know that there are multiple solutions out there delivering cross-tenant shared mailbox migration with ease. Here, we present a descriptive comparison of SysInfo with other top 2 solutions trusted by users globally. These are:

Basis 

SysInfo Microsoft 365 Tenant Migration Tool 

Cloudiway Microsoft 365 Tenant Migrator 

BitTitan Microsoft Tenant Migration Wiz 

Usable on 

Desktop (Win/Mac)

Cloud SaaS

Cloud SaaS

Migrate Shared Mailbox 

Yes 

Yes 

Yes 

Migrate OneDrive/SharePoint

Yes 

Yes 

Yes 

Pre-Migration Deduplication (Mailbox/SharePoint/OneDrive)

Yes 

No 

No 

Delta Syncs 

Yes 

Yes 

Yes 

Automatic Mapping 

Yes 

Yes 

Yes 

Manual Mapping 

Yes 

No

No 

OAuth 2.0 Modern Authentication

Yes 

Yes 

Yes 

GCC High Support 

Yes 

Yes 

Yes 

Advanced Filtering 

Yes 

Limited 

Limited 

Demo Support 

500 Mails/Folder

100 Contacts & Calendar Events

Fewer

Fewer

Cost-Efficiency

$499-$1999 (4 licence options)

500

Custom-Pricing

This explains the core capabilities of the SysInfo software over the other competitors. Other than this, the other benefits that it offers are:

  • Retains all mailbox permissions, structure, and metadata 
  • 100% security and zero-downtime data access 
  • Handles large-sized mailboxes simply with Graph API
  • 24*7 expert support to deal with any complexities 

Whether you have @info, @support, or other mailboxes, every shared mailbox is managed simply with no risks or confidential data leaks. 

Migrate Shared Mailboxes Between Office 365 Tenants Case 

A regional healthcare group was handling a merger during which they needed to migrate around 137 Office 365 shared tenant mailboxes. It had almost 5.5 TB of data that needed to be preserved with no loss or downtime. Using the SysInfo Office 365 Tenant to Tenant Migration Software, they performed automated mailbox mapping and incremental sync migration in minimal time. The results achieved were:

  • No delay in mailbox access
  • Pilot test ensured trust and consistency 
  • No duplicacy and 100% preservation
  • Continued business operations 

Ideal Practices for Effective Migration

Migration teams and individuals often face several complexities. To ensure hassle-free transitions, ensure these:

  • Don’t make any alterations in the mailbox during the final sync.
  • Verify your ‘Send As’ and ‘Send on Behalf’ permissions before moving.
  • When migrating large batches, check for Microsoft limitations on speed and processing.
  • Pilot test a representative sample of shared mailboxes.
  • Generate reports after the end of the migration for audit purposes.
  • Keep your source account active until you verify migration was a success.

Summing Up

The migration of shared mailboxes is one of the most critical migrations when transitioning between Microsoft 365 tenants. A successful migration is achieved when the delegated access, folder hierarchies, and data fidelity are preserved while maintaining business continuity. Whether you use Microsoft Exchange Online or MS Outlook with PowerShell, you can migrate shared mailboxes between Office 365 tenants, but upto an extent. An ideal solution to keep everything maintained is through the SysInfo Tenant to Tenant Migration Tool. It is secure, scalable, reliable, and trusted by experts for large-scale professional migrations.

Frequently Asked Questions

Q1. Can I migrate shared mailboxes between Microsoft 365 tenants without losing data?

Ans. Yes, you can migrate shared mailboxes with no loss between M365 tenants with the SysInfo Office 365 Tenant Migrator. It offers proper planning, incremental synchronization, and permission validation. 

Q2. How can I migrate shared mailboxes larger than 100 GB?

Ans. Yes, you can definitely migrate 100 GB+ shared mailboxes with the dedicated software. It has no restrictions on the mailbox limits and allows you to move emails from multiple mailboxes at once. 

Q3. How do I avoid duplicate emails during shared mailbox migration?

Ans. You can avoid duplicate emails during shared mailbox migration with the Remove Duplicate feature of the O365 Tenant Migration Tool. It ensures that no redundant emails are transferred to the target mailbox. 

Q4. How do enterprises migrate hundreds of shared mailboxes between Office 365 tenants?

Ans. Enterprise softwares like the Tenant Migration Tool by SysInfo allows batch migrations. It even has specialized capabilities that can handle such large volumes without any risks or concerns. 

Q5. How do I migrate shared mailboxes during a merger or acquisition?

Ans. You can migrate your shared mailboxes during a merger or acquisition with specialized professional software. This is because they allow for incremental syncs and handle large mailboxes altogether. 

Q6. Is there a limit to the number of shared mailboxes that can be migrated simultaneously?

Ans. Usually, the practical limit is set by Microsoft network capacity and throttling policies, and the migration tool opted for. 

Q7. What are the most common reasons for shared mailbox migration failures?

Ans. The most common reasons for the failure of shared mailbox migration are permission mismatches, throttling issues, corrupted mailboxes, archive migration problems, incorrect mailbox mapping, and incomplete delta synchronization. 

Rate this post

About The Author:

Simran Bhatia is a technical content writer engaged in writing clear, concise, and SEO-optimized content. With a background in computer science and a passion for writing, I thrive to deliver complex technical content in simple layman terms.

Related Post