web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

How do I move our Microsoft 365 tenant without losing data?

(6) ShareShare
ReportReport
Posted on by 24

Our organization is planning to move from our current Microsoft 365 tenant to a new tenant, and I am mainly concerned about losing or duplicating data during the migration. We have multiple user mailboxes along with OneDrive, SharePoint sites, Teams data, and shared mailboxes.

The user accounts in the new tenant will have different addresses, so I am also trying to understand the best way to handle mailbox mapping. I do not want users to end up with missing emails, attachments, folders, or incorrectly transferred data.

Another concern is that some users will continue working in the source tenant during the migration. Is there a reliable way to perform an initial migration and then transfer only the newly added or changed data instead of copying everything again?

I have also seen Microsoft 365 tenant-to-tenant migration tools that provide options for incremental migration, duplicate handling, OneDrive and SharePoint filtering, and migration reports. Has anyone used a tool such as the SysInfo Microsoft 365 Tenant to Tenant Migration Tool for this type of project?

I would particularly like to hear from administrators who have handled a tenant move because of an acquisition, restructuring, or domain change. What approach did you use to preserve mailbox data, OneDrive files, SharePoint content, Teams data, and shared mailboxes without creating duplicates or missing items?

  • Suggested answer
    OussamaSabbouh Profile Picture
    20,851 Super User 2026 Season 2 on at

    Hello,
    For this type of project, I would use Microsoft’s tenant-to-tenant migration capabilities first rather than relying immediately on a third-party tool: map each source identity to the new target account, migrate in controlled batches, and validate each workload separately. Exchange supports pre-sync before cutover, so users can continue working during preparation, and shared mailboxes are supported; however, Microsoft’s native OneDrive and SharePoint cross-tenant moves are one-time moves and do not support incremental/delta passes, so if repeated incremental synchronization is a hard requirement, that is where a third-party migration product may be useful. Also note that Teams chats/meetings and Teams/SharePoint shared content have different migration scopes, so plan them separately. I would test any tool such as SysInfo in a pilot first and verify exactly what it preserves for permissions, versions, Teams, shared mailboxes, and duplicate handling before using it for production.

    Regards,
    Oussama Sabbouh

  • Suggested answer
    Ben Baxter Profile Picture
    7,313 Super User 2026 Season 2 on at

    You will probably get more tracking if you post this in a Microsoft 365 forum, not the D365 Business Central forum.

     

    Microsoft has some built in tools for this, but I have also used a product called BitTitan with great success as well.  Worth investigating if the base tools don't work the way you're needing.

     

    Best Regards,

    Ben Baxter

    Accent Software Inc

  • Suggested answer
    D365BC_AmanKr Profile Picture
    291 on at

    Hi,

    For migrating a Microsoft 365 tenant to another without data loss or duplication requires careful planning, proper identity mapping, and the right migration tools.
    The migration process typically begins with a comprehensive discovery and assessment phase, where administrators identify and document all users, user accounts, mailboxes, shared mailboxes, OneDrive accounts, SharePoint sites and libraries, Teams teams and channels, permissions, security groups, distribution lists, and other relevant Microsoft 365 dependencies in the source tenant. This inventory helps determine the volume of data, user-to-user mappings, permission requirements, application dependencies, and any potential migration challenges before the actual migration begins. Once the discovery phase is completed, organizations generally conduct a pilot migration with a small, representative group of users and workloads. The pilot is used to validate identity and data mapping, mailbox and file migration, permissions, sharing access, folder structures, Teams functionality, and overall data integrity. Any issues identified during the pilot can then be addressed and the migration strategy refined before proceeding with the full tenant-to-tenant migration.


    Hope it will help you.
    Please Verify if you found the answer helpful so that it will help others.

    Many Thanks
    Aman 

  • Suggested answer
    Teagen Boll Profile Picture
    4,348 Super User 2026 Season 2 on at

    Hi @CU01070704-0, this is more of an M365 question than a BC question and you might get better answers here: Dynamics Community Forum Thread

     

    If you have questions about BC migration between tenants you can actually transfer environments between tenants without much issue: Transfer Environments - Business Central | Microsoft Learn

     

    You will just run into problems usually with permissions and workflows, ISV apps (if you have any) and customizations. But most standard functionality is good to go.

     

    @OussamaSabbouh and @D365BC_AmanKr  - Both of these answers look like AI answers, this question isn't a BC specific question. Please label answers as AI assisted where used.

     

    Teagen Boll, CPA

     

  • Suggested answer
    YUN ZHU Profile Picture
    104,117 Super User 2026 Season 2 on at

    For Business Central, there are standard out-of-the-box methods available to transfer the tenant. This carries no risk.

    More details: Business Central 2023 wave 2 (BC23.4): Transfer environments between Microsoft Entra tenants (formerly Azure Active Directory tenant)

    https://yzhums.com/47566/

    As for the Microsoft 365 side, I'd suggest posting it on the Microsoft 365 Forum. I'm sure the experts over there can give you better advice!

     

    Thanks

    ZHU

     

     

  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    3,888 Super User 2026 Season 2 on at

    Hi, I'm more a Business Central person than M365 admin, so take this with some salt. I would look at the native Microsoft way before any tool. The cross-tenant mailbox migration is a move, not a copy, so duplicates are not really a topic there. The batch syncs in the background while people still work in the source, you can start it two weeks before, and at cutover only the changes go over. Mapping is done through a MailUser in the target with the ExchangeGUID and x500 address from the source, so the different address is no problem. Shared mailboxes move too. There's a per-user license for it, same one covers OneDrive.

    Where it bites is Teams channels and SharePoint sites. They're outside the user migration, as far as I know SharePoint has a separate path and channels have no native one. Mailboxes on hold are blocked also.

    Glad to help - follow up if anything is unclear.   

    â–º  If this solved it, marking it verified helps others too.       

    Regards,
    Grigorios Mavrogeorgis
    Business Central Consultant & AL Developer

    Work: Gmsoft Limited
    Blog:  insidebusinesscentral
    LinkedIn: linkedin.com/in/gregorymavrogeorgis

  • Suggested answer
    johnmax2592 Profile Picture
    14 on at

    I had this conversation with a friend who manages Microsoft 365 for his organization. His concern was exactly the same, users were still creating emails and files while the tenant was being moved. He recommended testing with a few users and validating the incremental migration before full cutover. Veelead also approaches tenant migrations with that kind of phased planning.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 645 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 432 Super User 2026 Season 2

#3
Teagen Boll Profile Picture

Teagen Boll 248 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans