Why do large mailbox migrations to M365 fail?
Migrating large mailboxes to the cloud often fails because storage add-ons cannot be applied to mailboxes that are not yet present in the tenant, and tools like Purview throw generic errors during the chunk download process. These roadblocks prevent users from successfully transferring their data and lead to persistent export failures.
Core Friction Pattern
Analysis of 4 peer accounts across online developer and community forums reveals that “Why do large mailbox migrations to M365 fail?” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+6 alternative community-tested workarounds cataloged below.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Why do large mailbox migrations to M365 fail?
- 1Temporarily using a higher-tier license with a native 100GB cap to perform the migration, then switching the license back.Did this help you?
- 2Turn off automapping via PowerShell and manually add the mailbox to download the local file.Did this help you?
- 3Run SCANPST to check for and fix database errors.Did this help you?
- 4Create a blank PST file and manually copy folders or use drag-and-drop while disconnected from the internet.Did this help you?
- 5Use third-party paid conversion or mailstore software like CodeTwo or MailStore.Did this help you?
- 6Manual clean up before migrationDid this help you?
- 7Checking with support for migration thresholdsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Jose has a 38 GB mailbox. Tried it on Purview, I get generic errors when trying to download the largest allowable chunk size of 10GB. I can't seem to get around it and Purview is notoriously like this.”source ↗
“Export is around 33GB and it fails, same error, different email/folder.”source ↗
“Apparently Intermedia has no limits on Exchange and it resulted in some crazy counts. I don't think we can simply migrate out without cleaning up first, or can we?”source ↗
“Calendar 17,172 items / 6.82 GB and 65,167 items / 114 GB”source ↗
“Mailbox sizes over 200GB”source ↗
“I have a mailbox I want to migrate to M365 using the M365 Business Standard License. It appears the 50GB additional add-on does not apply to mailboxes that are not yet present in M365.”source ↗
“this happenend to me, iirc it happens because for some odd reason some email may be too large (might be completely wrong)”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
How to migrate company email from Google Workspace to Microsoft 365
Migrating email between cloud office platforms requires moving all messages while managing user accounts and running both systems concurrently during the transition. Without a clear migration path, businesses risk losing access to their company email for sending and receiving, resulting in months of locked-out accounts and disrupted operations.
Gotchas when migrating user files to OneDrive
Standard migration tools often skip orphan files and local computer directories, forcing sysadmins to run time-consuming scripts across thousands of users to move the remaining data. Once migrated, traditional recovery workflows break because admins can no longer rely on file server backups like Veeam to restore overwritten files. It also remains unclear whether the cloud client forces users to re-authenticate automatically when their domain password changes.
Migrating a child Active Directory into a parent domain
Users need to keep their child domain logins while accessing parent systems, but split email environments break directory visibility. Because Exchange Online does not know about them, remote mailboxes cannot see on-prem contacts. This stops administrators from recreating distribution groups in the cloud, since on-prem users still need to email those groups.
Why is there a file size limit on email attachments?
Email providers cap attachments tightly around 20MB, which makes sending bulk PDFs or large media impossible without failing. This mismatch forces people to deal with sudden upload rejections and floods support teams with tickets asking for alternatives.
How to fix sync problems on large Outlook mailboxes
Excessive mailbox size, high item counts, and deep folder structures cause Outlook to fail to synchronize properly because users treat mailboxes like filing cabinets. While switching shared mailboxes to online-only mode can resolve these sync failures, large mailboxes continue to suffer from severe performance bottlenecks.
Moving a virtual domain controller without a USN rollback
Official guides offer conflicting advice on how to move a virtual machine domain controller to new hardware safely. This leaves administrators stuck guessing whether they have to completely demote and rebuild the DC from scratch.