Said It Here

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.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Temporarily using a higher-tier license with a native 100GB cap to perform the migration, then switching the license back.
  2. 2
    Turn off automapping via PowerShell and manually add the mailbox to download the local file.
  3. 3
    Run SCANPST to check for and fix database errors.
  4. 4
    Create a blank PST file and manually copy folders or use drag-and-drop while disconnected from the internet.
  5. 5
    Use third-party paid conversion or mailstore software like CodeTwo or MailStore.

In their words

Unedited, most upvoted first, 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 ↗

CeC-P · r/sysadmin · 81 upvotes

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 ↗

L3TH3RGY · r/sysadmin · 2 upvotes

this happenend to me, iirc it happens because for some odd reason some email may be too large (might be completely wrong)source ↗

PeakWeekly9995 · r/sysadmin · 1 upvotes

Where this came up

People with this problem also raised