Can anyone suggest the best way to migrate shared mailboxes between Microsoft 365 tenants with zero downtime?

Question

We’re planning a Microsoft 365 tenant-to-tenant migration and need to move shared mailboxes from the source tenant to the target tenant without impacting users.

Has anyone done this successfully with zero or near-zero downtime?

What approach or tools did you use?

Are there any prerequisites or limitations to be aware of?

How did you handle access and permissions during the migration?

Any real-world experience or best practices would be greatly appreciated. Thanks!

---

Moved from: Community Center | Discuss the Q&A site | Get started on Q&A

Answer 1

To migrate shared mailboxes between Microsoft 365 tenants with minimal or zero downtime, consider the following best practices and approaches:

1. Use a Third-Party Migration Tool: Many organizations have successfully utilized third-party migration tools designed for tenant-to-tenant migrations. These tools often provide features to minimize downtime and streamline the migration process.
2. Prepare the Target Tenant: Before migration, ensure that the target tenant is fully prepared. This includes creating the necessary shared mailboxes in the target tenant and assigning appropriate licenses. You may also want to configure autodiscover settings and ensure that all mail flow rules and permissions are set up in advance.
3. Directory Synchronization: If using Azure AD Connect, ensure that the shared mailboxes are synchronized to the target tenant. This helps maintain user access and permissions during the migration.
4. Change MX Records Strategically: To ensure that emails are directed to the new mailboxes without downtime, consider changing the MX records at a time that minimizes impact on users. You can temporarily point the MX record to an unreachable domain to queue emails until the migration is complete.
5. Handle Permissions Carefully: During the migration, ensure that access permissions for shared mailboxes are preserved. This may involve reassigning permissions in the target tenant after the migration is complete.
6. Testing and Verification: After migration, conduct thorough testing to verify that mail flow is functioning correctly and that users can access their shared mailboxes without issues.
7. User Communication: Keep users informed about the migration process, including any changes they may need to make, such as clearing their Auto-Complete lists in Outlook after the migration.

By following these steps and utilizing appropriate tools, you can achieve a successful migration of shared mailboxes with minimal disruption to users.

---

References:

• How to migrate mailboxes from one Microsoft 365 or Office 365 organization to another
• Microsoft 365 and Office 365 email migration performance and best practices

Answer 2

Hi mol,

Thank you for posting your question in the Microsoft Q&A forum. 

For cross‑tenant migrations that include shared mailboxes, Microsoft provides a native approach called Cross‑tenant mailbox migration (CTMM). This method is designed for larger migrations and is secure and reliable because it’s built into Microsoft 365. However, it requires purchasing the Cross‑Tenant User Data Migration (UDM) license (one‑time per user/object) to perform the migration. Microsoft does not promise or confirm zero downtime but you can minimize user impact by pre‑staging and completing cutovers outside business hours.

More details & guidance:

• https://learn.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide
• https://www.codetwo.com/admins-blog/native-cross-tenant-mailbox-migration/
  Note: Microsoft is providing this information as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

If your organization has ≤500 users or only a small number of mailboxes to migrate and you prefer not to purchase additional licenses you can consider a manual PST‑based method using Outlook. It’s workable for small, one‑time moves, but it’s not very scalable.

Steps Involved:

1. Temporarily convert the shared mailbox to a user mailbox in the source tenant.
2. Assign a license to that mailbox (so Outlook sign‑in/export can work).
3. Export data from Outlook to a PST file.
4. Create a new shared mailbox in the target tenant.
5. Import the PST into the new mailbox via Outlook.
6. Re‑allocate permissions in the destination tenant for each person who previously had access (Full Access, Send As, Send on behalf, folder‑level ACLs).
7. Convert the mailbox back to Shared once all data is imported.

Limitations of the manual method:

• Time‑consuming for multiple shared mailboxes
• Higher risk of missing permissions or data (permissions do not travel with PST)
• Requires manual mapping and validation
• No built‑in real‑time monitoring/instrumentation
• Possible downtime or disruption during export/import and client reconfiguration

I hope this helps. If you have any further questions, please feel free to share.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.