Trying to troubleshoot a mailbox move request that's been sitting in 'Queued' for far too long. Removing and re-adding the move request didn't help, so I went ahead looking for what actually happens during the process.
There's an older article here, which goes in very much detail. However that was written for Exchange 2010, so a couple of things need to be taken into consideration - one is that the Microsoft Exchange Mailbox Replication service (MRS) is no longer deployed with the CAS role component, but with the Mailbox one. Also in that article it's mentioned that "When a move mailbox request is issued, the command creates a message in the System mailbox of the target database". I might be wrong here, but I though that on Exchange Server 2010+, System mailboxes refer to arbitration mailboxes; yet if this is the case then it presents a problem, since by default all arbitration mailboxes are located in the first ever created mailbox database. Conversely there won't be a 1-to-1 mapping between system mailboxes and target databases.
Taking a look at the move request itself (Get-MoveRequestStatistics -Diagnostic) it's visible that a MRS server isn't even selected, so the whole flow brakes in my case before that selection.