Exchange 2013 Migration Batch Completes Successfully, But Mailbox is Not Moved
“I was trying to transfer 1600 mailboxes from MS Exchange 2013 to 2016. Around 700 mailboxes moved easily without any failure but, one mailbox was repeatedly getting failed. So I tried to exhibit migration on Exchange Credit Program that at the end of the entire process displayed the complete procedure report. The main problem arose with this report because it is shown that 0 mailboxes were synced, 0 failed, and 0 finalized. Shocking thing was that I also got an email message showing that migration is successfully completed. Currently, I am literally in a state of big confusion where I cannot find a way to come out of this hurdle. What to do? Please help me!”
Sometimes a condition comes in front of the Exchange Server user where he/she is performing mailbox migration. After completion of all steps, they find the Exchange 2013 migration batch completed successfully, but the mailbox is not moved. This blog will help such Exchange users to troubleshoot this problem on their own.
Error Description
When you will open the batch migration description in Exchange management shell, you will notice following things:
- The value of ValidationWarningCount is 1.
- Few error statements are present in the ValidationWarning row.
Method to Resolve This Exchange Error
There is an object in Microsoft Exchange server named as “MigrationUser”. This object is available for each user who is involved in the procedure of being migrated or in the incomplete migration process. Both these conditions keep the MigrationUser in syncing state. When you will execute ‘Get-MigrationUser’ cmdlet, you will find that mailboxes are stuck since certain time duration in the migration without any major issue.
So, in order to resolve ‘Exchange 2013 migration batch completes successfully, the mailbox is not moved’ problem, you have to fix the stuck migration. This can be done by using the ‘Remove-MigrationUser’ cmdlet. You have to execute this command in Exchange Management Shell. If your request no more exists, use the ‘-Force’ parameter along with the command.
Conclusion
The removal of ‘stuck’ state from the migration procedure will help you in resolving ‘Exchange 2013 migration batch completes successfully, but the mailbox is not moved’ issue. Now the Microsoft server users will be able to transfer mailboxes and also archive them successfully. This will prevent mailboxes from migrating to Office 365 or other databases.
