'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Exchange IMAP Migration Batch Stuck in Removing State
Question details
The user is unable to delete an IMAP migration batch, which is stuck with pending mailboxes and cannot be cleared using standard tools.
- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- Attempting to remove an Exchange IMAP migration batch via the Exchange admin center or PowerShell.
- Observed behavior
- The migration batch remains stuck in the Removing state. PowerShell commands like Remove-MigrationBatch fail and return a MigrationPermanentException error.
Ensure you have global administrator or Exchange administrator privileges, and verify your connection to the Microsoft 365 admin center before troubleshooting.
Check Microsoft Service Health and Await Deployment
Use this solution first, as the issue is typically caused by a known Microsoft service regression affecting Mailbox Replication Service API calls.
When a service regression occurs on Microsoft's backend, API calls may return incorrect results, preventing migration batches from completing their removal process. In this state, local administrator commands will not work until Microsoft resolves the infrastructure issue.
Navigate to the Microsoft 365 Admin Center using your administrator credentials.
Click on 'Health' in the left-hand menu, then select 'Service health'.
Look for any active advisories or incidents related to Exchange Online, specifically mentioning IMAP migrations or Mailbox Replication Services.
Wait for Microsoft to deploy the fix to the affected infrastructure. Once resolved, the batch should automatically clear from the Removing state.
Contact Microsoft Support for Stuck Batches
If the global service incident is marked as resolved but your migration batch remains stuck in the Removing state.
Boost Your Productivity with WPS Office
While waiting for Microsoft to resolve Exchange migration issues on their backend, ensure your team stays productive with WPS Office. It is a highly compatible, free, and lightweight office suite that handles all your daily document needs without relying on expensive cloud subscriptions.
- 1. Download the Installer: Visit the official WPS Office website and download the setup file for your PC or Mac.
- 2. Install WPS Office: Run the installer and follow the quick setup wizard to install the software in minutes.
- 3. Open Your Files: Launch WPS Office and open your existing Microsoft Office documents without losing any formatting.
Frequently Asked Questions
Why does Remove-MigrationBatch return a MigrationPermanentException?
This exception usually occurs when backend services, such as the Mailbox Replication Service API, return incorrect data or experience a regression. It prevents the PowerShell command from successfully modifying or deleting the batch state.
How long should an IMAP migration batch stay in the Removing state?
Under normal conditions, an IMAP migration batch takes only a few minutes to be removed. If it remains in this state for several hours, it is likely stuck due to pending mailboxes or a service disruption.
Can I start a new migration batch while the old one is stuck?
It is not recommended to start a new migration batch for the same users if their previous batch is still stuck. Overlapping mailboxes can cause conflicts, duplicated emails, or further migration errors.
