A recent merger has left our IT team with the task of moving several hundred Microsoft 365 users from an existing tenant into a newly established environment. The migration looks straightforward initially, but once we considered mailbox size, user mapping, attachments, calendars, folder hierarchy, and the final cutover, it became clear that detailed planning would be necessary.
Our biggest priority is to Migrate Emails from Office 365 Tenant to Tenant without affecting day-to-day communication. Employees will continue receiving new messages during the migration, so we’re considering a staged approach where historical mailbox data is transferred first and a final incremental pass captures anything that changed afterward. This seems more practical than keeping everyone offline for a long migration window.
We’re also preparing a test group before moving the complete user base. The plan is to select a few representative mailboxes from different departments, including users with large mailboxes and complicated folder structures. After the test migration, we’ll compare message counts, attachments, folders, contacts, and calendars between the source and destination. Any problems identified during testing can then be resolved before the larger batches begin.
Another area we’re paying attention to is source-to-destination mapping. In an M&A situation, users may have different email addresses or domains in the destination tenant. A clear mapping file should help administrators avoid transferring data to the wrong accounts. We’re also planning migration batches based on department and mailbox size so that the IT team can monitor performance and investigate failures without affecting the entire project.
Reporting is equally important. When hundreds of mailboxes are involved, manually checking every migrated item isn’t realistic. We need reports that show successful transfers, skipped items, failed items, and migration status. This information will help us validate the project and provide management with evidence that the migration has been completed successfully.
We’re also considering SharePoint and OneDrive because moving Exchange Online alone wouldn’t complete the tenant consolidation. Ideally, the same project should cover all major Microsoft 365 workloads while maintaining appropriate permissions and organizational structure. Authentication and security are additional considerations because both tenants need to be connected without compromising administrative controls.
While comparing different approaches, I came across the DRS Softech O365 Tenant to Tenant Migration Tool. Its documented capabilities include Exchange Online, SharePoint, and OneDrive migration, mailbox mapping, Modern Authentication, incremental migration, filtering, deduplication, active task monitoring, and detailed reports. These options appear useful for a large enterprise migration, although I’d still like to hear from administrators who have used similar tools in real projects.
For those who have completed a Microsoft 365 cross-tenant migration, how did you organize your migration batches? Did you use a pre-stage and final delta approach? Also, how did you handle DNS changes, user communication, validation, and failed items during the final cutover? Practical experiences would be especially useful for teams planning an M&A-driven tenant consolidation.