Step by Step Procedure to Move Mailboxes from Exchange 2010 to Exchange Server 2016!!

Microsoft Exchange 2016 has been introduced with a lot of exciting features, including a new architecture, improved reliability, and cloud deployment that offer endless possibilities for today’s business environment.

If you are considering to migrate from Exchange 2010 to Exchange 2016, then it is probably the right time.

Prepare the System Before Heading Towards Migration

It is essential to verify the system requirements in order to successfully migrate to Exchange 2016:

  • Minimum memory requirement − 8GB (for server role) + 4GB for edge transport Must have
  • Windows Server 2012/2012 R2 Free disk on drive − at least 30 GB.
  • UCS API and .NET framework must be installed on the machine, before installing Exchange 2016.
  • Recommended screen resolution - 1024 X 768 pixels
  • Ensure paging file size must be set to physical RAM and has reached to maximum limit 32788 MB.
  • Make sure disk partitions are well formatted on NTFS file systems.

Migrating User Mailboxes

Performing a test migration will help you examine the issues that you are going to face during the actual migration. So it is advised that you migrate a group of few users first.

There are number of methods for moving Exchange user mailboxes from Exchange 2010 to Exchange 2016. The first method is feasible only if you have created equal number of databases to match with the source Exchange 2010 environment.

Use the following command to queue up mailboxes that are to be moved.

Get-Mailbox -Database | New-MoveRequest -TargetDatabase -BatchName

You can track migrations, using Exchange Management Shell. Use Get-MoveRequest cmdlet, and then monitor the BatchName, and then use Get-MoveRequestStatistics to obtain in-depth idea the batch migrations. Use the following commands.

Get-MoveRequest -BatchName "------” | Get-MoveRequestStatistics

You can also use Exchange Admin Center to co-ordinate the migration. You can use the New Migration Batch wizard to select mailboxes from Global Address List. While using the Exchange Admin center, then it is easier to test the progress by selecting the migration batch and View Details from the list.

Use the following command on Exchange 2016 Management Shell to validate that nothing is left on the old Exchange 2010 mailbox.

Get-Mailbox -Server

However, if any mailboxes are left, then use the following command (New-MoveRequest cmdlet) for the fresh migration batch.

Get-Mailbox -Server | New-MoveRequest -BatchName "Remaining Mailboxes”

Migrate system mailboxes from Exchange 2010 and then with the help of the Arbitration parameter, you can search them. As mentioned below:

Get-Mailbox -Server −Arbitration

Now send everything to Exchange 2016 by using the following command:

Get-Mailbox -Server -Arbitration | New-MoveRequest

Once all the user mailboxes are migrated from Exchange 2010, then delete the mailbox move request from Exchange 2016.

To perform delete request, now use the Remove-MoveRequest cmdlet along with this command Get-MoveRequest:

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

However, if you have chosen Migration Batch approach for data migrations, then delete the move request using Exchange Admin Center.

After completing this phase, you can then prepare to decommission Exchange 2010, and eliminate unused offline address books, and then delete databases and uninstall Exchange 2010. However, if the above-mentioned approach has not been successful for migrating user mailboxes from Exchange 2010 to Exchange 2016, then trust a third-party Exchange migration tool for safe-and-secured data migrations.

Perform a test migration before conducting the actual migration!! Be careful.

Free Microsoft Exchange tools that are worth your time

Being an IT admin, you must have always wished for a smooth and well-managed Exchange environment. Exchange troubleshooting and administration does not have to be expensive, there are numerous free resources available for Exchange administrators to test, manage, and deploy their MS Exchange environments.

Read full review