on the 2013 server open Exchange powershell and run the following:
Get-MoveRequest "MailboxName" | get-moverequeststatistics |fl DisplayName,Message
This will give you a reason why the mailbox is queued.
You could also try to restart the Microsoft Exchange Mailbox Replication Service as well to see if it kicks off the migration.
Thanks,
Jason
Hi,
I recommend you use the Get-MailboxStatistics -Identity "the affected mailbox" | fl to check the result.
Please move this mailbox to another mailbox database on Exchange 2010, then move it to Exchange 2013 to check the result.
In addiction, please check the application log to see if there is any related events.
I suggest you can Login to EAC to complete the migration.
Regards,
David
I would like to confirm about David given suggestion.
Using "Get-MailboxStatistics", you should be able to find out some clue as why mailbox migration is under queue.
Moreover, if the issue still persist, you may consider on this proficient application too (http://www.exchangemigrationtool.com/) that seems to be a suitable approach in order to get migration task done with no downtime or any further interruption.