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.

OverviewLatest thread: Sep 2026
People affected4 accounts (1 forum)
Workarounds found7 items recorded
Discussion timelineSep 2026
Freshness statusActive Consensus
Editorial ConsensusSynthesized across r/sysadmin · Sep 2026
Verification standards →

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.

Top Peer-Reported Fix
Temporarily using a higher-tier license with a native 100GB cap to perform the migration, then switching the license back.

+6 alternative community-tested workarounds cataloged below.

Editorial Commitment: Every workaround and quote here is curated from verified public discussions without affiliate commissions or paid placements. Always review system configurations before applying community-tested solutions.

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.

Active Consensus (Latest: Sep 2026)Indexed across peer discussions from Sep 2026 to Sep 2026
Evaluated against breaking changes & deprecations
  1. 1
    Temporarily using a higher-tier license with a native 100GB cap to perform the migration, then switching the license back.
    Did this help you?
  2. 2
    Turn off automapping via PowerShell and manually add the mailbox to download the local file.
    Did this help you?
  3. 3
    Run SCANPST to check for and fix database errors.
    Did this help you?
  4. 4
    Create a blank PST file and manually copy folders or use drag-and-drop while disconnected from the internet.
    Did this help you?
  5. 5
    Use third-party paid conversion or mailstore software like CodeTwo or MailStore.
    Did this help you?
  6. 6
    Manual clean up before migration
    Did this help you?
  7. 7
    Checking with support for migration thresholds
    Did this help you?
Tried another approach not listed above?+ Share your workaround ↑

In their words

Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.

r/sysadmin4 people · September 2026

“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/sysadminSep 2026· 81 upvotes

“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 ↗

LoveBirdNibbles · r/sysadminSep 2026· 7 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/sysadminSep 2026· 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/sysadminSep 2026· 1 upvotes

Where this came up

People with this problem also raised

Related community dilemmas clustered by discussion consensus

6 related topics

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.

14 workarounds8 accounts · 2 forums

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.

5 workarounds2 accounts · 1 forum

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.

6 workarounds8 accounts · 2 forums

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.

7 workarounds5 accounts · 1 forum

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.

10 workarounds3 accounts · 1 forum

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.

7 workarounds4 accounts · 1 forum