Exchange Server5 min read

How to Batch Move Mailboxes in Exchange 2019 and 2016

Anjali Rawat
Updated:

Quick Answer

Batch move mailboxes in Exchange 2013, 2016 and 2019 in 3 ways.

Use the Exchange Admin Center for a small group with clicks.

Use New-MoveRequest to move every mailbox in one database.

Use New-MigrationBatch with a CSV file for a chosen list.

Use Exchange EDB Recovery when a corrupt mailbox blocks the move.

Batch moves shift many mailboxes from one database to another while users keep working. Exchange keeps the mailbox online during the copy and locks it only for the last sync.

You choose between the admin center, the shell and a migration batch. The right choice depends on how many mailboxes you move and whether you work from a list.

This guide covers 3 methods for Exchange 2013, 2016 and 2019 with the commands in the order you use them.

What Exchange Mailboxes Can You Move in a Batch?

A local move shifts mailboxes between databases in the same Active Directory forest. It covers the move between two databases on one server and the move between two servers. Cross forest moves and remote moves to another organization use other cmdlets and need extra setup.

The methods below handle local moves. Check three things before you start.

  • The target database is mounted and has enough free disk space.
  • Your account holds the Recipient Management or Organization Management role.
  • You have a mailbox that receives the completion report.

How to Batch Move Mailboxes in the Exchange Admin Center?

Suits: Admins who move a small group. Needs: Exchange Admin Center and a mounted target database. Limit: Handles one selection at a time.

  1. Open Recipients, select Mailboxes and tick the mailboxes to move.
  2. Choose More, then Move to a different database.
  3. Give the migration batch a name and select the target database.
  4. Choose to move the primary mailbox, the archive or both.
  5. Enter the user who receives the completion report.
  6. Select automatic or manual completion and choose New.
  7. Track the progress under Migration.

Allow time for Active Directory replication after the move finishes.

How to Use New-MoveRequest to Move a Full Database?

Suits: Admins who empty a database. Needs: Exchange Management Shell and a target database. Limit: Moves everything in the source database.

Pipe the mailboxes of the source database to New-MoveRequest. The BatchName parameter groups the requests so you can find them later. SuspendWhenReadyToComplete stops every move before it finishes, so you can complete the batch after working hours.

Get-Mailbox -Database "DB01" | New-MoveRequest -TargetDatabase "DB02" -BatchName "DB01toDB02" -SuspendWhenReadyToComplete

Check the status and then complete the batch.

Get-MoveRequest -BatchName "DB01toDB02" | Get-MoveRequestStatistics
Get-MoveRequest -BatchName "DB01toDB02" | Set-MoveRequest -SuspendWhenReadyToComplete:$false
Get-MoveRequest -BatchName "DB01toDB02" | Resume-MoveRequest

Microsoft documents both cmdlets in its New-MoveRequest reference.

How to Use New-MigrationBatch With a CSV File?

Suits: Admins who move a chosen list. Needs: A CSV file and Exchange Management Shell. Limit: Local moves need Exchange 2013 or later.

Create a CSV file with one column. Name the header EmailAddress and list one mailbox address per row.

EmailAddress
user1@contoso.com
user2@contoso.com

Create the batch, start it and complete it. Replace the file path and the database name with your own values.

New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Temp\LocalMove1.csv")) -TargetDatabases DB02
Start-MigrationBatch -Identity LocalMove1
Complete-MigrationBatch -Identity LocalMove1

Add the Autostart and AutoComplete switches to skip the last two commands. Microsoft lists every parameter in the New-MigrationBatch reference.

New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBytes("C:\Temp\LocalMove1.csv")) -TargetDatabases DB02 -AutoStart -AutoComplete

How to Move Corrupt Mailboxes That Fail in the Batch?

Suits: Admins whose moves fail on damaged mailboxes. Needs: A copy of the EDB file and a Windows PC. Limit: The free demo previews every mailbox.

A damaged mailbox fails the move with corruption errors, and the standard methods skip it. Check the move report first. If the report names corrupt items, repair the mailbox with the repair request or export its data from the EDB file. Exchange EDB Recovery opens corrupt, dismounted and offline EDB files without a mount and exports the mailboxes.

Recover Mailboxes From a Corrupt EDB File

Exchange EDB Recovery scans Priv.edb and Pub.edb files and previews every mailbox. Export to PST, MSG, EML, PDF, HTML, MBOX, Office 365 or live Exchange.

Download Now Purchase Now

  1. Add the EDB file.
  2. Choose Quick Scan for light damage or Advance Scan for severe damage.
  3. Preview the mailboxes and folders.
  4. Export the mailboxes to PST or straight to a live Exchange server.

Choose a scan mode in Exchange EDB Recovery for a corrupt mailbox

Export mailboxes to PST after a failed Exchange batch move

A related guide shows how to repair a mailbox with New-MailboxRepairRequest.

Best Practices for Exchange Batch Mailbox Moves

  • Back up the databases before a large move.
  • Move a small test batch first and read the report.
  • Use SuspendWhenReadyToComplete and finish during off hours.
  • Check free disk space on the target database and the log drive.
  • Remove completed move requests to keep the list clean.

Author's Verdict

Use the admin center for a handful of mailboxes, New-MoveRequest for a full database and New-MigrationBatch for a chosen list. Test with a small batch first and finish the move after hours. Use Exchange EDB Recovery when a corrupt mailbox blocks the batch. Copy the EDB file before every repair.

FAQs on Batch Mailbox Moves in Exchange

Which Exchange Versions Support the Batch Move Methods?

New-MigrationBatch with the Local switch applies to Exchange 2013, 2016 and 2019. New-MoveRequest and the admin center also work on these versions.

What Header Does the CSV File Need?

Use one column with the header EmailAddress and one mailbox address per row.

Do Users Lose Access During a Batch Move?

No, the mailbox stays online during the copy. Exchange locks it only for the final sync.

How Do I Finish a Suspended Move?

Use Set-MoveRequest with SuspendWhenReadyToComplete set to false and then Resume-MoveRequest.

Why Does a Mailbox Fail in the Batch?

Corrupt items or a damaged mailbox stop the move. Read the move report and repair or export the mailbox.

Can I Recover a Mailbox From an EDB File?

Yes, Exchange EDB Recovery opens corrupt and offline EDB files and exports the mailboxes to PST or a live server.

Can I Preview Mailboxes Before I Buy?

Yes, the free demo previews every mailbox.