MS Exchange Server 2016 comes with advanced facilities that enterprises can’t wait to benefit from. Architecture simplicity, reliability, improved email-client features and cloud readiness are the hallmarks of this version. But when it’s time to upgrade to this new Exchange version, the existing Exchange data needs to be moved to it. So let’s go through the options available for mailbox migration, especially from Exchange 2010.
Is direct migration to Exchange 2016 possible from all previous versions?
Exchange 2016 supports direct migration from Exchange 2010 and Exchange 2013 only. Direct migration is not possible from Exchange 2007 and previous versions unless you use third-party migration solutions.
Why migrate from Exchange 2010 to Exchange 2016 now?
Exchange 2016 will possibly be the last Exchange version to which Exchange 2010 mailboxes can be migrated directly using the built-in features of Exchange.
What are the requirements for successful Exchange 2010 to Exchange 2016 migration?
Apart from hardware, OS, and email client requirements, co-existence between Exchange 2010 and 2016 Exchange versions is required for the migration. For co-existence with Exchange 2016, you should have Exchange 2010 RU11 or later (in all servers). You can get updates from Microsoft sites to fulfill these minimum criteria.
How to move mailboxes from Exchange 2010 to Exchange 2016 using Exchange Admin Center
You can use the Exchange admin center (EAC) as well as Exchange Management Shell (EMS) to move mailboxes from the Exchange 2010 database to Exchange 2016 database. Here we will show you the migration steps using EAC:
- Open Exchange admin center and sign in.
- Go to recipients>migration and click; select Move to a different database.
- Select the option, Select the users that you want to move; click and add users (you can add users in the Select Mailbox window).
Note: Users can be added using CSV file option too.
- Click Next when mailboxes are listed.
- Enter a name to the mailbox move. Under Archive, select the option Move the primary mailbox and the archive mailbox if one exists. Provide the target database name and bad item limit (ideally you can give bad item limit as 10). Click Next.
Note: The Browse button opens up the Select Mailbox Database window where you can select and add an Exchange 2016 server mailbox database.
- Enter the user to whom mailbox move reports are to be sent (the default entry can be modified using the Browse button); keep the option Automatically start the batch If you want to complete the migration automatically, keep the option Automatically complete the migration batch selected. Finally click New.
Note: To manually complete the mailbox move
In recipients>migration, select the mailbox migration batch that is to be moved; click Complete this migration batch in the details pane (available only when batch is ready for completion).
- Now in recipients>migration, you can check the mailbox migration status in the details pane by selecting the migration batch. Click View details to get more details.
Are there simpler ways to migrate Exchange 2010 to Exchange 2016?
Professional Exchange migration solutions make Exchange/Office 365 to Exchange/Office much simpler and easier. They support the latest as well as all popular versions of Exchange for migration. LepideMigrator for Exchange is a reliable and trusted solution used by many organizations across the world.
After the successful deployment of Exchange 2016, organizations have to move their Exchange 2010 mailboxes to the new Exchange. You can use EAC or EMS to accomplish this migration. However, because of the complexities involved, most of the organizations rely on Exchange migration tools.
Latest posts by Ajit Singh (see all)
- 3 Ways To Fix Oversized .EDB Files - November 23, 2016
- A quick overview of migrating from Exchange 2007 to Exchange 2016 - September 21, 2016
- Migrating to Exchange 2016 using the Exchange Admin Center - February 24, 2016