Table of Contents

Microsoft 365 Migration Throttling: How to Resume Failed Mailbox Transfers Without Migrating Emails Again

Microsoft 365 migration throttling may delay the transfer of the mailbox or even stop it before all emails are delivered to the new location. The issue appears due to overloading of the requests and limitations of the resources of Exchange Online. Some mailboxes will remain in sync status. Restarting the entire migration is not always necessary. Administrators can verify the migration status, rectify the problem, and continue the migration process through incremental synchronization. This article explains how to troubleshoot throttling errors and continue a Microsoft 365 tenant to tenant migration without transferring the same emails again.

A Common Microsoft 365 Migration Scenario

You start migrating 300 mailboxes to Microsoft 365 on Friday evening after business hours. When you check the migration status on Saturday morning, some mailboxes have been stuck at "Syncing" for hours, while others show "Failed." Your planned cutover is Monday, and you still have several mailboxes to complete.

What should you do next? Should you restart the entire migration?

Not always. There might be cases where Exchange Online is delaying your migration request because of throttling. In such a scenario, restarting all the mailboxes may not be the appropriate solution. Start by analyzing the migration report to see if the problem is caused by throttling, and then perform the Office 365 Delta Migration after solving the issue.

Why Does Microsoft 365 Migration Throttling Occur?

  • Data migration throttling occurs when the migration process sends too many requests to the destination server, causing resource limitations and delays in data transfer.
  • Large Mailboxes: Those mailboxes having thousands of emails along with large attachments consume more processing time.
  • Service Resource Limits: If Exchange Online is experiencing stress on its service resources, it may delay your migration request.
  • Too Many Mailbox Transfers: Migrating hundreds of mailboxes simultaneously can increase the number of requests and slow down transfers.
  • Network Disruptions: If there are problems with internet connections, then mailbox sync will not take place.
  • Background Processing Activities: The backup processes and email clients connected to Microsoft 365 consume more service resources.

How to Identify Microsoft 365 Migration Errors?

Migration error or symptom Possible reason
HTTP 429 – Too Many Requests API request throttling
HTTP 503 – Service Unavailable Temporary service unavailability
Mailbox stuck at Syncing Delayed processing, connection problems, or an ongoing transfer
Mailbox status shows Failed Authentication, permissions, configuration, or transfer error
Mailbox remains queued Migration endpoint connections are occupied
Migration speed decreases Throttling, network issues, or resource limitations
Emails are missing Skipped items, unsupported items, or incomplete synchronization

How to Prevent Microsoft 365 Migration Throttling

  1. Reduce Migration Concurrency
    Migration concurrency means the number of mailboxes being transferred at the same time. High concurrency can increase the number of requests sent to Microsoft 365. Start with a smaller number of simultaneous transfers and increase it gradually after checking the results.
  2. Divide Large Mailboxes into Smaller Batches
    Don’t initiate the transfer of all mailboxes at once. For instance, a company having 500 mailboxes can split those into several smaller groups by departments, mailbox size, etc.
  3. Schedule Migration During Low-Usage Hours
    Schedule mailboxes migration at times when fewer users will be accessing Microsoft 365. This may help avoid conflict with day-to-day business and other processes running in the background.
  4. Monitor Migration Reports
    Keep monitoring the migration logs during the transfer procedure rather than waiting for the whole batch to fail. Watch out for failed mailboxes, missed items, synchronization, and frequent connection failures.
  5. Use Incremental Migration
    Incremental migration becomes helpful where the first-time mailbox migration is complete, but there have been subsequent additions to the source mailbox. Rather than performing another migration of the entire mailbox, incremental migration will synchronize any new or modified items with support from that migration technology.
  6. Test the Migration Before Moving All Mailboxes
    Do a pilot migration for a handful of mailboxes prior to the full migration process. Analyze the transfer rates, mailbox architecture, attachments, and error logs. Utilize the analysis to determine the batch size and schedule of migration.

How to Resume Mailbox Migration without Duplicates?

The SysInfo Microsoft 365 Tenant Migration Tool helps users to transfer mailboxes with the Incremental Migration Features. This feature allows users to resume mailbox migration without transferring previously migrated emails again. The tool supports Mailbox migration, SharePoint migration, OneDrive migration, and Teams migration. Also, built in Deduplication module to remove duplicates.

Apart from that, this software offer several advanced features, such as data filter, modern authentication, attachment handling, and more. With its simple interface, technical and non-technical users can easily use it. This tool is highly compatible with all Windows, Mac, and Linux versions. Also, you can download the demo version to test its functions.

Note: For more information, check the software manual. It contains directions on how to perform the procedure, complete with screenshots. If you require further help or have any queries, please contact our technical support.

Exchange Online Migration Throttling

Throttling of Exchange Online migrations refers to the limitation of migration requests by Microsoft, aimed at controlling the usage of resources and ensuring optimal performance of the service. Throttling may affect migration speed, lead to the mailbox staying in the states of Syncing and Queued, and even result in migration failure for a limited time period.

Final Words

Microsoft 365 migration throttling can delayed migration of mailboxes; however, this does not necessarily mean that the migration has completely failed. Administrators have to check the migration reports, figure out the exact reason for the problem, and reduce concurrency, if required. In case the transfer is interrupted, the incremental migration will allow administrators to synchronize mailboxes containing either new or remaining data without performing the complete migration again.

Frequently Asked Questions

Why can't my Microsoft 365 mailbox migrate because it gets stuck at syncing?

Ans. There could be several reasons for the mailbox being stuck at syncing, such as Exchange Online working on the migration request, too much data in the mailbox, or poor connectivity.

Can network issues cause Microsoft 365 migration throttling errors?

Ans. The network problems may disrupt the mailbox synchronization process and lead to migration errors or delays. Nevertheless, these issues do not have anything in common with Microsoft 365 throttling. Analyze the error message to figure out what causes the issue.

Does a large mailbox increase Microsoft 365 migration time?

Ans. Yes. A large mailbox with thousands of emails, attachments, and folders usually takes longer to transfer. The migration time also depends on network speed, service availability, and the number of mailboxes being migrated simultaneously.

How do I check mailbox migration status in Exchange Online PowerShell?

Ans. Connect to Exchange Online PowerShell and run the following commands:

Can reducing migration concurrency help resolve throttling?

Ans. Yes. Reducing the number of mailboxes migrated simultaneously can lower the number of requests sent to Exchange Online. Administrators can use smaller batches and gradually increase concurrency after monitoring migration performance.

Does Exchange Online migration throttling affect every migration method?

Ans. No. Throttling can affect different migration methods in different ways. Its impact depends on the APIs, protocols, and Exchange Online services used by the migration process. For example, API-based migrations may receive throttling responses such as HTTP 429.

Can I resume mailbox migration without duplicates?

Ans. Yes, if the migration method supports incremental synchronization or a resume feature. These options can identify previously migrated items and transfer new or remaining data. Always check the migration report and the tool's deduplication settings before continuing.

Will restarting an Exchange Online migration transfer all emails again?

Ans. Not necessarily. The behavior depends on the migration type and the method used to restart it. Some migration workflows continue from the existing state or synchronize changes, while others may require additional checks to prevent duplicate items.

How does Microsoft 365 migration throttling affect large enterprise migrations?

Ans. In large migrations, throttling can slow down multiple mailbox transfers and delay the planned cutover. It may also increase migration time when many requests are sent simultaneously. Dividing mailboxes into smaller batches and monitoring reports can help administrators manage the process.

How should IT teams plan a Microsoft 365 migration to minimize throttling?

Ans. IT teams should perform a pilot migration, review mailbox sizes, plan smaller batches, and schedule transfers during low-usage hours. They should also monitor migration reports, check service health, and use incremental migration where supported to synchronize mailbox changes before cutover.

Was this article helpful?

0 out of 0 found this helpful