Microsoft 365 tenant-to-tenant migration in Adelaide
A carefully planned move between Microsoft 365 tenants when ownership, company structure or the business name changes.
Last updated
Part of: Microsoft 365
The short answer
Businesses that have been sold, merged, split or rebranded can have WaTo Consulting move their mailboxes, OneDrive, SharePoint, Teams data and domains from one Microsoft 365 tenant to another. Data is copied ahead of time, the domain cutover is usually set for a Friday night or weekend, and the Adelaide team checks Outlook, phones and shared links with staff afterwards.
What does Microsoft 365 tenant-to-tenant migration involve?
A tenant-to-tenant migration moves users, mailboxes, OneDrive and SharePoint content, Teams data and domains out of one Microsoft 365 tenant and into another. The tricky part is that a domain can only live in one tenant at a time, so the cutover has to be timed and the mail flow, sign-ins and shared links all checked once the move is done.
What WaTo can help with
Discovery first
Map users, mailboxes, domains, files and dependencies before moving anything.
Migration plan
Stage the work around the people and systems that cannot stop.
Domain & identity
Move domains, accounts and access with a controlled handover.
Post-move support
Check mail, files and staff access after cutover and resolve loose ends.
Who it is for
- A business that has been bought and needs to fold into the new owner's Microsoft 365
- A partnership splitting up, where each side needs its own tenant and its share of the files
- A company that rebranded and wants a clean tenant under the new name instead of the old one
- A group that ended up with several tenants over the years and wants to consolidate them into one
How it works
- We audit both tenants. Users, mailbox sizes, shared mailboxes, SharePoint sites, Teams, domains and any apps signing in with Microsoft accounts all get listed.
- We build the target and pre-stage data. Accounts and licences are created in the new tenant and the bulk of mail and files is copied across ahead of time.
- We cut over the domain on a set date. The domain is removed from the old tenant, added to the new one, mail records are updated and a final sync picks up recent changes.
- We fix what turns up afterwards. Outlook profiles, phones, Teams and shared links are checked with staff in the first few days after the move.
Why WaTo for Microsoft 365 tenant-to-tenant migration
- We map every service using the domain before moving it, not just email, so websites and third-party apps do not break
- Cutovers are usually planned for a Friday night or weekend to keep the working week clear
- Staff get simple instructions for reconnecting Outlook and their phones on the Monday
- An Adelaide team working with local businesses since 2001 is still on the phone after the move
Microsoft 365 tenant-to-tenant migration questions
Will we lose email during a tenant-to-tenant migration?
Mail is not lost, but there is usually a short window during the domain cutover when new mail is delayed or queued. We plan that window for a quiet time and copy existing mail across beforehand, so people arrive Monday with their history in place.
What happens to our Teams chats and channels?
Channel conversations and files can usually be moved, though some migration tools handle private chats differently. We check what your tenant has and explain what will come across intact before you commit.
Can both companies keep working while the migration is planned?
Yes. Most of the preparation and data copying happens in the background while staff keep using the old tenant. The disruption is mostly limited to the cutover itself and reconnecting devices afterwards.
Guides on this topic
Ready to get Microsoft 365 tenant-to-tenant migration sorted?
Tell us why you are moving tenants and which domains and mailboxes are involved. We will plan the cutover so email and files arrive in the right place.
Mon to Fri, 8:30am to 5pm
