Forum Discussion
Groups: Tenant to tenant migration
- Feb 01, 2017
Groups use special forms of mailboxes that not all migration tools even reveal let alone access... That is my warning.
Just as an example, try using the Get-Mailbox cmdlet to list group mailboxes. They don't exist. You have to use Get-UnifiedGroup. But you can feed a group mailbox id into Get-MailboxStatistics... So it's inconsistent, hence the warning.
Microsoft said (at Ignite 2017) that they will support tenant to tenant mailbox moves. In other words, you create a migration endpoint in one tenant that points to the other and can then schedule migration batches to move mailboxes from one to the other. This is what I think you want, but while Microsoft has said they will deliver this functionality, I have seen no formal announcement of its availability. This will be free; third party software is not.
However, when you move a mailbox, you do not keep it in the source tenant. Why would you want to keep it?
- hot_techsurfJan 05, 2026Copper Contributor
email address removed for privacy reasons
- AusSupport180May 12, 2022Brass ContributorQuest on demand is very simple and easy to migrate and bittitan required more prep work and complicated
- AusSupport180May 06, 2022Brass ContributorHi All,
I’m also looking for T2T migrate 200 mailboxes.
Can someone share the trail licenses to evaluate? - Paresh_ParmarFeb 04, 2022Copper Contributor
@All
best way to tenant to Tenant Migration with Veeam Office 365 Tools.
for process of moving as much content as possible from one tenant to new tenant.
The process a copying a emails, one drive, SharePoint team channels, Chats .
- Evaluate which email ids of domains should be migrated.
- Create the corresponding Email ids with different domain in the new tenant and provide password to each users before migration.
- Use a Veeam backup for Microsoft Office 365 migration tool to take existing users backup with organization connect.
- Use a Veeam Backup tools to take backup and restore, Emails, Calendar, Agenda, contacts, Sharepoint, Microsoft Teams channel, Chats in new tenant.
- First time full backup at veeam backup tools take times after run again with incremental backup it will take very less time.
- Before migration do backups of all Email ids and Team channels. then restore it on new tenant which is created with same ids from current tenant. start restoring data on the new tenant.
- once data restore successfully you need to remove groups and change current email ids to different one on tenant and make it primary that id.
- Remove domain from current tenant.
- add domain on new tenant and make primary id which created with different domain to migration domain.
- once primary id done in new tenant change DNS , MX Entry and use your migrated domains uses in new tenant with all the data.
- its done successfully.
Planner migration (which I suspect will be a manual process)
Any thoughts, tips and pointers will be appreciated.
Regards
Paresh
- TonyRedmondMar 18, 2020MVP
Paul Garlick None. I would use a third-party solution like Quadrotech Cloud Commander.