About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The migration reports FailureType : TooManyLargeItemsPermanentException for one mailbox. Microsoft's cause: the source mailbox holds one or more messages that exceed the 150-megabyte (MB) message limit. The fix is to find those messages in the on-premises mailbox, save them elsewhere, delete them from the mailbox, and resume the migration.
What the error means
Microsoft's page describes migrating a user's mailbox data from an on-premises environment to Microsoft 365 with the New Migration Batch Wizard, the E-mail Migration wizard or Exchange Online PowerShell, and receiving an error that "resembles the following":
FailureType : TooManyLargeItemsPermanentException
FailureSide : Target
Message : Error: This mailbox exceeded the maximum number of large items that were specified for this request. --> MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)
The page shows FailureSide : Target and states the cause: "This issue occurs if the user's mailbox contains one or more messages that exceed the 150-megabyte (MB) message limit."
One point matters for anyone used to older on-premises move commands. Microsoft's New-MoveRequest page says LargeItemLimit and BadItemLimit are "deprecated from the cloud-based service" and that "Admins must review the Data Consistency Score and any skipped items before the move completes." The same note appears on New-MigrationBatch. Do not look for a switch that lets the move skip large items in Exchange Online; the documented remedy is to remove them at the source.
Three details in the error block help you read it. FailureType : TooManyLargeItemsPermanentException names the fault; Microsoft's page does not explain the word "Permanent", but its remedy is to change the source mailbox, not to run the request again unchanged. FailureSide : Target is what Microsoft's page shows; the page does not explain the label, so do not read it as saying the problem is on the Microsoft 365 side. The message text says the mailbox "exceeded the maximum number of large items that were specified for this request", which is why the remedy is a change to the source mailbox, followed by a resume.
The limit sits on each message, not on the mailbox total. Microsoft's Exchange Online limits page (dated 2026-11-11) lists a message size limit of 150 MB for Outlook and 112 MB for Outlook on the web. Limits change, so check the current page.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| One or more messages over 150 MB in the source mailbox | TooManyLargeItemsPermanentException for that mailbox only |
Sort the mailbox by size in Outlook; items above 150 MB are the cause |
| Skipped items (a place to look after the move, not a cause of this error) | Items not copied to the cloud mailbox | Get-MigrationUserStatistics ... -IncludeSkippedItems lists them |
Prove the cause before changing anything
- Read the failure text for the user. Microsoft's cmdlet page shows this form for detail:
Get-MigrationUserStatistics -Identity ayla@contoso.com.au -IncludeReport | Format-List Status,Error,Report
For skipped items, its example is Get-MigrationUserStatistics -Identity ayla@contoso.com.au | Format-List SkippedItemCount,SkippedItems. The same page also shows how to list each skipped item by date and subject, which helps you match an entry in the report to a message in Outlook:
Get-MigrationUserStatistics -Identity ayla@contoso.com.au -IncludeSkippedItems | Select-Object -ExpandProperty SkippedItems | Format-List DateReceived, Subject
These commands only read information. Run them before you touch the mailbox, and keep the output with the batch record.
- For a move request rather than a batch, use
Get-MoveRequestStatistics -Identity ayla@contoso.com.au -IncludeReport | Export-CSV C:\MRStats.csv, adapted from the form Microsoft shows (Tony@contoso.comin its example). The report keeps the detail for later. - Open the on-premises mailbox in Outlook. Arrange all items in all folders by size, largest first. Microsoft says to find items "larger than 150 MB".
- As a separate pre-check, not a step Microsoft gives for this error: for a hybrid migration, Microsoft describes a mailbox analysis request through Exchange Online PowerShell that produces folder paths with item counts and sizes, so you can identify oversized mailboxes before migration starts. Microsoft says it is available through Exchange Online PowerShell only, that the Exchange admin center does not support it, and that the hybrid migration endpoint must be set up and working. Its report lists folders by item count and size, not individual messages over 150 MB, so it does not replace the size sort in Outlook.
Fix
Large items. Microsoft's steps: use Outlook to access the on-premises mailbox, sort by size, and find items larger than 150 MB. "If these items contain important info, save them to another location such as the local computer or a local Personal Folders file (.pst). Then, delete the items that are larger than 150 MB from the user's mailbox."
Save first: save each large item to a .pst file, then confirm the file opens and the items are readable. Also keep the item list (name, size, folder).
Disruptive step: delete the confirmed items from the on-premises mailbox. Impact: they are gone from the live mailbox; if the .pst is damaged, there is no other copy. Back-out: import the saved items from the .pst file back into the mailbox. After the migration, Microsoft says "the data can be reimported to the Exchange Online mailbox", with the "Import email, contacts, and calendar from an Outlook .pst file" instructions, but Microsoft's Exchange Online limits page lists a message size limit of 150 MB for Outlook and 112 MB for Outlook on the web, so a re-import of an item that size may be refused.
Before you resume, repeat the size sort across all folders, as Microsoft's wording says ("all items in all folders"), and confirm that nothing above 150 MB is left. One missed item fails the mailbox again. Then return to the Exchange admin center and resume the migration, as Microsoft's final step says.
Confirm the fix
Resume or re-submit the failed mailbox and watch its status until it finishes, then run Get-MigrationUserStatistics -Identity ayla@contoso.com.au | Format-List SkippedItemCount,SkippedItems. Confirm the large items do not appear as skipped and that the user can open the mailbox. Ask the user to confirm the items in the .pst file are the ones they need.
Example (illustrative): a batch of 30 mailboxes has 1 failure, ayla@contoso.com.au, which is 3.3% (1 divided by 30). Sorting by size in Outlook finds three messages of 180 MB, 210 MB and 160 MB, a total of 550 MB (180 + 210 + 160). She saves them to a .pst on fs01, confirms it opens, deletes the three messages, and resumes. The batch then completes.
What to watch afterwards
- Add a size sort to the pre-migration checklist, since the page gives a 150 MB message limit. Limits change, so check the current page first.
- Run Microsoft's analysis pre-scan on large mailboxes before each batch, if you are in hybrid.
- Keep the
.pstfiles with the batch record until the user confirms the items. - If the same mailbox fails again for a different reason, read its
-IncludeReportoutput before changing anything else. - Tell the mailbox owner which items were removed and where the copies are kept, in writing, so a missing item is traceable to a decision rather than a mystery.
- After the whole batch completes, compare the number of failures with the number of mailboxes that had large items on your pre-migration size sort. A difference means the sort missed a folder, and the next batch needs a wider check.
Read next
Related articles you may want next.
- TroubleshootingCan't see free/busy information after a mailbox is moved to Microsoft 365: the 'Could not be updated' errorFree/busy blank after a mailbox move to Microsoft 365? Check the calendar's Default permission first; the opposite direction is a different fault.Read article
- HostingDesigning a pilot that actually predicts production migration riskHow to choose pilot users, workloads and success measures so a green pilot is not a false signal before production cutover.Read article
- HostingBusiness freeze windows and change blackouts before a migration cutoverHow long to freeze configuration and data changes before cutover, who may approve an exception, and what the freeze is meant to protect — distinct from replication lag and DNS mechanics.Read article
Risks and limits
These commands have not been run or lab-tested. Microsoft's pages for this fault are short; they give the cause and the removal step but not how to find large items without Outlook, or what other limits apply in Exchange Online. Microsoft's pages give no estimate of how long a resumed move takes, so plan the cut-over date with that gap in mind. The 150 MB figure is Microsoft's number on that page and on the Exchange Online limits page (dated 2026-11-11); check the current pages. The page links to Exchange Online limits for the wider list.
The page is written for a migration from an on-premises messaging environment. It does not say what happens to items that sit in a mailbox's archive or in a shared mailbox that is migrated separately, so sort those folders as well when they are part of the move, and treat any other result as untested.
Do not delete the large items before the .pst copy is proven. Do not delete the only copy of an item on the strength of a size column alone. Do not loosen other limits to push a move through, since Microsoft's page names removal at the source as the fix.
Sources
- This mailbox exceeded the maximum number of large items when migrating a user's mailbox data from the on-premises environment to Microsoft 365 — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Analyze source mailboxes before migrating from Exchange On-Premises to Microsoft 365 — Microsoft Learn, page dated 2026-08-21, accessed 20 November 2026
- Exchange Online limits — Microsoft Learn, page dated 2026-11-11, accessed 20 November 2026
- New-MoveRequest — Microsoft Learn, date not shown, accessed 20 November 2026
- New-MigrationBatch — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-MigrationUserStatistics — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-MoveRequestStatistics — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .