Microsoft 365 Tenant-to-Tenant Migration
Move between Microsoft 365 tenants without losing mail or files.
Mergers, rebrands, and divestitures mean moving users, mailboxes, files, and Teams from one Microsoft 365 tenant to another. We plan it, test it, and verify it so nothing gets left behind.
Tenant-to-tenant migration, answered directly
By Joe Engelking, CEO. Updated October 2026.
What is a Microsoft 365 tenant-to-tenant migration?
It is moving users, mailboxes, OneDrive files, SharePoint sites, and Teams content from one Microsoft 365 tenant to another. Companies do it after a merger or acquisition, a rebrand, a divestiture, or when consolidating several tenants into one. Each tenant is a separate environment, so the move has to be planned and carried out carefully.
When does a business need one?
When two companies combine, when a business is split or sold, when a new legal entity or brand needs its own environment, or when old tenants were created by mistake and need to be merged. If staff are working in two tenants today, a migration usually saves time and security headaches.
What is easy to migrate and what is tricky?
Mailboxes, calendars, and contacts are the most straightforward. Harder pieces are Teams chat history, SharePoint permissions and sharing links, shared mailboxes, licensing, and custom apps. Planning identifies these early so nothing surprises you at cutover.
How long does it take, and will there be downtime?
It depends on the number of users and amount of data. Most migrations run in phases, with data copied ahead of time and a final cutover at a quiet hour. Staff should be able to work normally, with short, planned moments when mail routing or sign-in changes.
| Workload | What moves | What to watch |
|---|---|---|
| Mailboxes | Email, calendars, and contacts | Mail routing timing and Outlook reconnection |
| OneDrive | Personal files and folders | Sharing links that stop working |
| SharePoint | Sites, libraries, and documents | Permissions and site structure |
| Teams | Channels and files | Chat history limits and meeting links |
| Licenses and security | User licenses, multifactor authentication, policies | Settings must be recreated in the new tenant |
What happens when a migration is left half done
Prairie Contractors in Frankfort, Illinois had an outside technician set up Office 365 and move them to the cloud. He failed midstream. Nothing had been migrated, and the team lost access to all of their old email.
We took over, ran the full migration properly, and set up Office 365 the right way, then added RMM automations, backups, security, and help desk.
Joe Engelking, CEO
More questions about tenant-to-tenant migrations
No. A domain can be active in only one Microsoft 365 tenant at a time, so the move includes a planned step to release the domain from the old tenant and add it to the new one. That step is timed carefully because it affects mail delivery.
Usually yes, at least once. After cutover, Outlook needs to connect to the new mailbox, and users may need to sign in again on phones and other devices. We plan the cutover, communicate what to expect, and help staff reconnect.
Teams content moves with more limits than email. Files and channel structure can be migrated, but chat history and recurring meeting links often need extra attention. We tell you before the move what will transfer and what will need to be recreated.
We set multifactor authentication, restrict admin accounts, configure email protection, review sharing settings, and confirm backups before staff move over. Setting security up first prevents the new tenant from starting life with weak defaults.
Often yes for larger or more complex moves, since specialized tools handle mailboxes, files, and permissions in bulk and report on progress. For small moves, native tools can be enough. We choose based on the size and complexity of your environment.
You should own your tenant and have admin access. If a vendor or former provider controls it, getting admin rights comes first. We have handled uncooperative handoffs by working through your ownership rights and direct contact with Microsoft.
It depends on the number of mailboxes, the amount of data, and how clean the source environment is. We migrate in stages, test along the way, and schedule the final cutover outside business hours where possible so email keeps flowing.