22 July 2026, 07:22 PM
Been down this rabbit hole for the past few weeks while planning our M365 tenant consolidation, and honestly, most tools out there talk a big game about "seamless migration" but fall apart the moment you check folder hierarchies, subfolders, or custom rules post-migration. A lot of admins on forums complain about flattened folder structures, broken permissions, missing metadata, and even duplicate emails after migration — which defeats the whole purpose if your org relies on nested mailbox organization for compliance, legal hold, or workflow reasons.
The problem usually shows up in one of a few ways: subfolders get merged into the root Inbox, read/unread status resets so users think they have hundreds of unread emails, calendar invites lose their original timestamps, or shared mailbox permissions simply vanish and someone from IT has to manually rebuild access controls afterward. None of that is acceptable when you're moving an entire org's mail system, especially during M&A activity or divestiture scenarios where downtime and data integrity both matter.
After testing a handful of options (including a couple of native tools and third-party ones), the one that actually held up in terms of preserving the exact mailbox structure — folders, subfolders, read/unread status, and even calendar/contacts mapping — was this DRS Softech Microsoft 365 Tenant to Tenant Migration Tool. It handled bulk mailbox migration without messing up the hierarchy, which was our biggest concern going in since we have some pretty deep folder nesting across departments, plus dozens of shared and archive mailboxes that needed to move without any structural changes.
What stood out was that it didn't just dump everything into a flat structure like some tools do — it mapped source and destination folders properly, retained permissions where possible, and gave decent pre-migration reporting so we knew what to expect before running the actual job. It also let us do a test batch on a handful of mailboxes first, which caught a couple of mapping issues early instead of discovering them after a full cutover.
Also appreciated that it supports incremental/delta migration, so we weren't stuck redoing the whole thing if something got interrupted midway or if users kept receiving new mail during the migration window. That alone saved us a ton of coordination headaches with end users, since we didn't have to freeze mailboxes for an extended period.
Not saying it's the only one that works, but if mailbox structure integrity is your top priority (like it was for us), it's worth putting on your shortlist before you commit to a full tenant migration plan. Would love to hear if others have had similar or different experiences with structure preservation, permission handling, or delta sync reliability on their own tenant-to-tenant migrations.
The problem usually shows up in one of a few ways: subfolders get merged into the root Inbox, read/unread status resets so users think they have hundreds of unread emails, calendar invites lose their original timestamps, or shared mailbox permissions simply vanish and someone from IT has to manually rebuild access controls afterward. None of that is acceptable when you're moving an entire org's mail system, especially during M&A activity or divestiture scenarios where downtime and data integrity both matter.
After testing a handful of options (including a couple of native tools and third-party ones), the one that actually held up in terms of preserving the exact mailbox structure — folders, subfolders, read/unread status, and even calendar/contacts mapping — was this DRS Softech Microsoft 365 Tenant to Tenant Migration Tool. It handled bulk mailbox migration without messing up the hierarchy, which was our biggest concern going in since we have some pretty deep folder nesting across departments, plus dozens of shared and archive mailboxes that needed to move without any structural changes.
What stood out was that it didn't just dump everything into a flat structure like some tools do — it mapped source and destination folders properly, retained permissions where possible, and gave decent pre-migration reporting so we knew what to expect before running the actual job. It also let us do a test batch on a handful of mailboxes first, which caught a couple of mapping issues early instead of discovering them after a full cutover.
Also appreciated that it supports incremental/delta migration, so we weren't stuck redoing the whole thing if something got interrupted midway or if users kept receiving new mail during the migration window. That alone saved us a ton of coordination headaches with end users, since we didn't have to freeze mailboxes for an extended period.
Not saying it's the only one that works, but if mailbox structure integrity is your top priority (like it was for us), it's worth putting on your shortlist before you commit to a full tenant migration plan. Would love to hear if others have had similar or different experiences with structure preservation, permission handling, or delta sync reliability on their own tenant-to-tenant migrations.