Hope you like it..

Unable to move mailboxes via ECP/EAC

April 10, 2023 at 3:21 pm Leave a comment

When you are migrating from Exchange 2013 to Exchange 2019 you may notice that you are not able to migrate the mailboxes from the Exchange 2013 to Exchange 2019 via the EAC.

The workaround in this situation is to use the New-MoveRequest or New-MigrationBatch Exchnage Powershell commands. Even though , when you these commands the move request may fail in some cases and may not appear in the EAC. You could refer MS articles on how to create the CSV for migration batches and use it with these command line tools.

In breif:

• Create a CSV file using the EAC

Then modify the CSV file as below:

Run the below commands to initiate the migration and get the statistics

New-MigrationBatch –Name –CSVData ([System.IO.File]::ReadAllBytes(“”)) –Local –TargetDatabase

Get-MigrationUser | Get-MigrationUserStatistics

Let’s go back to the original problem and let’s see how can we fix it. You need to find out the System Mailboxes (especially the Migration mailbox) from the older version of Exchange server and transfer it to a database in the newer version of exchange.

Get-Mailbox -Server “OLD Exchange Server ” -Arbitration | New-MoveRequest -TargetDatabase “”Database in the Newer Exchange”

That’s it you can happily use the EAC to migrate the mailboxes.

Source: https://m365security.eu/2012/10/28/using-new-migrationbatch-to-perform-local-mailbox-moves-in-exchange-server-2013/

Entry filed under: Exchange and O365. Tags: arbitration, eac, exchange 2013, exchange 2019, migration mailbox, new-migrationbatch, new-moverequest.