Difference between New-MigrationBatch and New-MoveRequest Commands in Exchange Server

With the release of Exchange Server 2013, Microsoft has introduced new commands in the Exchange Management Shell (EMS). These includeNew-MigrationBatchandNew-MoveRequestPowerShell commands that can help the Exchange Server Admins to move mailboxes between on-premises Exchange Server and Exchange Online in a hybrid setup. Below, we will be discussing the differences between these two commands. We will also be discussing how to useNew-MigrationBatchandNew-MoveRequestPowerShell commands.

About New-MigrationBatch and New-MoveRequest Commands

TheNew-MigrationBatchandNew-MoveRequestcommands in PowerShell are used to move mailboxes from one Exchange Server to another, from one database to another in the same server, or tomigrate Exchange mailboxes to Exchange Online. If you have to move several mailboxes at the same time, the migration batch command is ideal.

In the case of migrating to a newer version of Exchange Server, you need to make sure that the current Exchange Server and the new setup can coexist. It is best to check with your Microsoft vendor or Microsoft coexistence matrix before proceeding.

Though both commands are used for moving mailboxes, here are some differences between these commands based on certain factors:

How to Use the New-MoveRequest Command?

Tomoveamailbox从一个数据库到另一个,你可以使用通讯and as given below.

New-MoveRequest -TargetDatabase”d“电子邮件地址”atabase name"

If you like tomovetheuser archiveto another database, use the command as given below.

New-MoveRequest -TargetDatabase”d“电子邮件地址”atabase name" -ArchiveTargetDatabase "database name"

Tomovethemailbox onlyand leave the archive as it is, use the below command.

New-MoveRequest -TargetDatabase”d“电子邮件地址”atabase name" -PrimaryOnly

Tomovethearchive onlyand leave the mailbox as it is, use the below command.

New-MoveRequest -TargetDatabase”d“电子邮件地址”atabase name" -ArchiveOnly

How to Use the New-MigrationBatch Command?

You need to specify the name of the batch and theCSVfile which has the mailboxes to move. After creating the batch, you need to start it.

New-MigrationBatch -Local -Name "name of batch" -CSVData ([System.IO.File]::ReadAllBytes("path to csv file")) -TargetDatabases "destination database name"

Start-MigrationBatch -Identity "name of batch"

Alternative Solution to Move Mailboxes

The above commands work fine when you have a good setup and everything is working well. However, they lack on part of reporting. Also, if something happens, there is no continuation and you need expertise and resources to resolve the issue. In addition, if something happens to the Exchange Server due to server or operating system failure, you will not be able to use these commands to move your data.

In such situations, you can look for a third-partyEDB to PST Convertersoftware. One of the best applications for moving mailboxes isStellar Converter for EDB. With this application, you can directly open Exchange Server Databases (EDB) files with no limitation on size and without having a running Exchange Server.

You can browse through the data stores and granularly export to PST and other file formats. You can use the application to export directly to a live Exchange Server database or an Office 365 or Microsoft 365 tenant. You can export users’ mailboxes, user archives, shared mailboxes, disabled mailboxes, and even public folders.

Conclusion

As you have seen,New-MigrationBatchandNew-MoveRequestare powerful commands, but you need resources and expertise to run these commands. However, these commands can only work if the Exchange Server is running and well configured. In case of a server failure or to export data from an orphaned server ordecommissioned Exchange Server, you will need to reconstruct the Exchange Server from scratch. In such cases, you can useStellar Converter for EDBto export mailboxes from EDB file to a live Exchange Server database or Office 365. With this application, you will be able to reduce the time of migration with much less resources.