rohitpatwa
New member
We're preparing to migrate our company domain from one Microsoft 365 tenant to another, along with all user accounts, Exchange Online mailboxes, OneDrive data, and SharePoint sites. I've been researching the process, and while Microsoft's native tools and PowerShell scripts can handle some of the work, they seem fairly complex when it comes to user mapping, permissions, and maintaining folder structures.
One of my biggest concerns is preserving mailbox data, including emails, contacts, calendars, attachments, and shared permissions, while also ensuring OneDrive sharing settings and SharePoint document libraries remain intact. We also need to avoid downtime since employees rely heavily on Microsoft 365 throughout the day.
During my search, I came across MacSonik Office 365 Tenant to Tenant Migration and noticed it uses Microsoft's Graph API instead of traditional export/import methods. It claims to migrate Exchange Online, OneDrive, and SharePoint together while preserving metadata, permissions, timestamps, and the original folder hierarchy. The bulk migration capability also looks useful since we're moving several hundred users rather than migrating accounts individually.
Another feature that caught my attention is the automated user and mailbox mapping, along with detailed migration reports and activity logs. Having a clear record of completed and failed items would definitely make post-migration validation much easier. I also like that there's a demo version available, so we can test everything before performing the production migration.
Has anyone here migrated an entire domain between Microsoft 365 tenants recently? Did you use Microsoft's native approach, PowerShell, or an automated solution? I'd really appreciate hearing about any challenges you faced, especially regarding domain cutover, user mapping, and minimizing downtime.
One of my biggest concerns is preserving mailbox data, including emails, contacts, calendars, attachments, and shared permissions, while also ensuring OneDrive sharing settings and SharePoint document libraries remain intact. We also need to avoid downtime since employees rely heavily on Microsoft 365 throughout the day.
During my search, I came across MacSonik Office 365 Tenant to Tenant Migration and noticed it uses Microsoft's Graph API instead of traditional export/import methods. It claims to migrate Exchange Online, OneDrive, and SharePoint together while preserving metadata, permissions, timestamps, and the original folder hierarchy. The bulk migration capability also looks useful since we're moving several hundred users rather than migrating accounts individually.
Another feature that caught my attention is the automated user and mailbox mapping, along with detailed migration reports and activity logs. Having a clear record of completed and failed items would definitely make post-migration validation much easier. I also like that there's a demo version available, so we can test everything before performing the production migration.
Has anyone here migrated an entire domain between Microsoft 365 tenants recently? Did you use Microsoft's native approach, PowerShell, or an automated solution? I'd really appreciate hearing about any challenges you faced, especially regarding domain cutover, user mapping, and minimizing downtime.