Exchange Mailbox Moves: ‘FailedOther’ Stops at 95%

KB ID 0001376


If you don’t see this happen at least once in a migration I would be surprised!


  • StatusDetail: FailedOther
  • PercentComplete: 95%



 You can remove the move request and start it again, with both a BadItemLimit and AcceptLargeDataLoss flag, (these might seem scary, but I’ve migrated many thousands of mailboxes, and never seen a problem.)

But the mailbox is massive and it had been moving for hours! OK, we can change the parameters, and resume the move as well!

Option 1 (Remove and Restart the Move)

Remove-MoveRequest -Identity user-name

New-MoveRequest -Identity “user-name” -TargetDatabase “target-mailbox-database” -BatchName “user-name” -BadItemLimit “200” -AcceptLargeDataLoss

Option 2 (Resume Existing Mailbox Move)

Get-MoveRequest | ?{$_.DisplayName -eq “user-name“} | Set-MoveRequest -BadItemLimit 200 -AcceptLargeDataLoss

Get-MoveRequest | ?{$_.DisplayName -eq “user-name“} | Resume-MoveRequest

PowerShell - Resume Move Request

The move should now restart/resume.


Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. How can i move a disconnected mailbox from Exchange 2010 to Exchange 2013 without connecting that mailbox again ? We are retaining disconnected mailboxes for 365 days, so there s a lot of mailboxes that we don t want to loose. Thanks.

    Post a Reply
    • Try

      Get-Mailbox | ?{$_.ExchangeUserAccountControl -eq ‘AccountDisabled’ -and $_.database -ne “The-2013-Database-Name” } | new-moverequest -targetdatabase “The-2013-Database-Name”

      Post a Reply
  2. I’ve inherited an e-mail migration, and someone tried to migrate a mailbox from 2010 to Exchange Online through the WebUI and it stopped at 95% with FailedOther, specific error points to Error: TooManyTransientFailureRetriesPermanentException/DataConsistencyTransientException: Error: The job encountered too many transient failures ‎(621)‎ and is quitting. The most common failure is DataConsistencyTransientException with the hit count 58. –> The data consistency score ‎(Investigate)‎ for this request is too low.

    I can “Approve this migration batch” from the UI, but it’s been sitting there for roughly 30 days now. Should I do a Remove-MoveRequest and redo it or can I just approve it? Will there be any repercussions since it’s been sitting there that long?

    Post a Reply
    • Theres something in there it does not like, I’d cancel, run a repair on the mailbox, then see if you can export it to a PST successfully, If that works, re-queue the mailbox move.


      Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *