Migrating Exchange Server 2010 to 2016 using Exchange Admin Center (EAC)

Exchange Server 2016 comes with many impressive features such as reliability, architecture, simplicity, improved emailing features and cloud approach. If you are looking forward for Exchange 2016 migration, this guide would definitely help you in accomplishing the same.

Exchange 2010 and 2013 mailboxes can directly be migrated to Exchange 2016. This facility is offered only for these two versions whereas migration from Exchange 2007 is only possible via third party apps. Exchange 2016 is the last version to which you can directly migrate MS Exchange 2010 mailboxes by using integrated migration features. For migrating to Exchange Server 2019 from Exchange Server 2010, among other things, you would need to first hop to Exchange Server 2013 or 2016.

Requirements for Exchange 2010 to Exchange 2016 Migration

Other than Operating System, compatible emailing platform, hardware requirements, integration between Exchange 2016 and 2010 platforms is also required for successful migration. It is vital to have Exchange 2010 RU11 or later versions in service to maintain synchronization with Exchange 2016 edition. Updates can be accessed from Microsoft site on how to fulfill the minimum requirements.

Why Migration to Exchange 2016 is Needed?

Apart from the fact that the Exchange Server 2010 has been reached its end-of-life and support, Exchange Server 2016 has many new and updated features that can be a major reason for migration. These features include:

  • SHA-2 compliance: Microsoft has updated certificate that Outlook on the web uses; it is now SHA-2 compliant.
  • Multiple Language Support: 17 new languages have been added to Outlook on the web (formerly Outlook Web App)
  • Enhanced Downloading: Begin with CU1 Exchange 2016 edition is available to download as ISO file instead of EXE files that are self-extracting.

The client application (Outlook on the Web) includes following new and updated features

  • Improved email with all new single line view of Inbox with advanced archiving, emojis, reading panel, with ability to undo mailbox actions such as moving or deleting a message
  • Platform definite experience for both Android and iOS phones
  • Optimized search refiners and suggestions for improved search experience that assist users in finding the accurate and exact information they are looking for
  • Thirteen new themes are added with graphic design
  • Improvement in performance can be analyzed through calendar events, loading messages, contacts, startups, popouts, reading pane, switching folders, search, etc
  • An all new OWA action pane that enables user to click those actions that are commonly used such as Reply all, Delete, New, Undo, Sweep, Archive, etc
  • Pins allow keeping important mails on the top of the Inbox are now folder specific and Flags mark rest emails as follow ups are quickly accessible
  • Calendars are available with updated looks and revised features that include reminders for email events

Apart from the above mentioned, there are some other features as well that compel medium to large-sized organizations to upgrade to Exchange 2016.

Migration to the Exchange Server 2016 can be done through Exchange Admin Center.

Migrate Exchange 2010 to Exchange 2016

Exchange Admin Center and Exchange Management Console can be used for migrating Exchange 2010 to Exchange 2016 mailbox. In this blog, we will discuss migration procedure using Exchange Admin Center.

  • Launch Exchange Admin Center (EAC) and sign in with correct credentials
  • Go to Recipients, click on Migration, and then select ‘Move to a different database’
  • Select the ‘Select the users that you want to move’ option and then add users in the Select Mailbox window

Note: Alternatively, you can select ‘Specify the users with a CSV file’ option to add user.

  • Once all the users are added, click on the Next option
  • Enter name for move mailbox operation. Select Move the primary mailbox and the archive mailbox if one exists under Archive
  • Provide a name for Target Database and enter bad item limit. Then, click on Next
  • Enter user details to which mailbox move reports are to be sent
  • Next, if you want to automatically migrate mailboxes, select Automatically start the batch
  • Also, select Automatically complete the migration batch under preferred option to complete the batch
  • And then, click on New

For Manual Batch Selection:

In case, you’ve selected the ‘Manually select the batch later’ option available under preferred option to start the batch, follow the given procedure:

  • In Recipients, click on Migration and manually select the mailbox migration batch that needs to be moved, and then click on Complete this migration batch under details pane
  • Next, click on Recipients and then click on Migration, and check mailbox migration status within the details pane via selecting the desired migration batch
  • Next, click on View Details, if you wish to access more detailed information

When the migration of all databases is done, you must then decommission the Exchange Server 2010. However, before that take care of some other things such as,

  • Pointing the router to the new Exchange Server
  • Install or check all the certificates
  • Point the scanners and multifunction printers to the new server

Tips to Flawless Migration of Exchange Mailboxes

For easy and error free migration, Stellar Converter for EDB software can be employed effectively in any business setup – be it small, medium or large-sized. The tool extracts mailboxes from offline Exchange database (.EDB file) and directly migrate them to a live Exchange environment or an Office 365 tenant. The software supports all the versions of Exchange Server including Exchange 2019, so you won’t face version incompatibility issue during the migration. Apart from extracting mailboxes and saving them into PST, the tool can also convert and save mailbox items into other file formats such as EML, MSG, and PDF.


  1. Alan June 28, 2018
    • Eric Simson June 29, 2018
  2. Carter June 22, 2018
    • Eric Simson June 25, 2018
  3. Garrett March 27, 2018
    • Eric Simson March 28, 2018
  4. Patrick October 29, 2017
    • Eric Simson October 31, 2017
  5. Shirley August 29, 2017
    • Eric Simson September 1, 2017
  6. bobdev November 15, 2016

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.