Migrate Exchange 2010 to 2016 – Complete Step-by-Step Process
Overview: This blog will provide a detailed description of how you can migrate Exchange 2010 to 2016 in a step by step process. Not just the migration process, we have also explained the pre-migration steps that you need to complete the process in a seamless manner.
As Exchange Server 2010’s support ended on October 13, 2020, many organizations have upgraded their Exchange Server to the latest version. Now, there is an option to either migrate to Exchange 2016 or Exchange 2019 as these are the most preferred Exchange Servers by administrators.
If you haven’t upgraded to the updated Exchange Server and are looking for a way to migrate Exchange 2010 to 2016, this write-up is for you. Here, you will get all the detailed steps on how you can carry out the migration process in a seamless manner.
There are two ways using which a user can migrate Exchange Server 2010 to 2016 i.e. a manual solution and an automated way. First, we will discuss the manual way in a step-by-step manner.
A brief overview of migration steps manually:
- Exchange Server Sizing
- Fulfill Exchange Server Requirements
- Exchange Server Installation
- Exchange Server Configuration
- Creating Co-existence of Exchange Servers
- Mailbox Migration
Exchange 2010 to 2016 Migration Using a Manual Way
1. Exchange Server Sizing
As you are already running Exchange Server 2010, you might have an idea of the performance of the existing server. So, you can consider increasing the RAM, Disk Space, and Processor to ensure smooth working on the new Exchange 2016 Server.
You can also consider reducing or increasing the mailbox quotas and ensuring that you have enough storage space for mailbox and backup storage.
Furthermore, you can also give thought to separating Exchange logs, Exchange database, and Windows volume.
2. Comply with Exchange Server Requirements
It is necessary to have the right set of resources to set up a new Exchange Server and migrate Exchange 2010 to Exchange 2016.
- Windows Server 2012 onwards
- No less than .Net 4.5.2 (The latest version is recommended)
- Exchange 2010 Server must be updated to SP3 – Update Rollup 11
- Outlook 2010 SP2 with KB2965295 and KB2956191
- Functional AD 2008 or above
Once you fulfill all these requirements, you can now proceed with Exchange 2016 installation.
3. Exchange Server 2016 Installation
Now download the latest Exchange 2016 version and implement the following steps:
1. First change the directory to the Exchange’s download location.
2. Prepare AD Schema
setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
3. Now update Active Directory with new Exchange objects
setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
4. The next step involves domain preparation (You must perform this for all your domains)
setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms
5. Install Exchange 2016 on this Server
setup.exe /Mode:Install /Roles:Mailbox /IAcceptExchangeServerLicenseTerms
6. Finally, reboot the server.
Another step for Exchange 2010 to 2016 migration completes here. Now, go through the next section to proceed further.
4. Exchange Server Configuration
1. Now login to ECP to test that everything is running fine. For this, open a browser and type
2. Update the Service Connection Point in the Active Directory. Also, ensure that the Server Connection points to your existing autodiscover URL.
Eg. – autodiscover.domain.com/autodiscover/autodiscover.xml
Afterward, we will point this name to New Exchange 2016 Server.
3. Export your public SSL from the old Exchange Server and Import it into the new Exchange Server.
4. Now restart the IIS to apply the new SSL certificate.
5. Open EMS on your machine and run the following script to update all virtual directory URLs. Once all these steps are performed, you can proceed for Exchange 2010 to Exchange 2016 migration.
$Server = “ServerName” $HTTPS_FQDN = “mail.domain.com” Get-OWAVirtualDirectory - Server $Server | Set-OWAVirtualDirectory - InternalURL “https:// $( $HTTPS_FQDN ) /owa” -ExternalURL “https:// $( $HTTPS_FQDN ) /owa” Get-ECPVirtualDirectory -Server $Server | Set-ECPVirtualDirectory - InternalURL “https:// $( $HTTPS_FQDN ) /ecp” -ExternalURL “https:// $( $HTTPS_FQDN ) /ecp” Get-OABVirtualDirectory -Server $Server | Set-OABVirtualDirectory - InternalURL “https:// $( $HTTPS_FQDN ) /oab” -ExternalURL “https:// $( $HTTPS_FQDN ) /oab” Get-ActiveSyncVirtualDirectory -Server $Server | Set- ActiveSyncVirtualDirectory -InternalURL “https:// $( $HTTPS_FQDN ) /Microsoft-Server-ActiveSync” -ExternalURL “https:// $( $HTTPS_FQDN ) /Microsoft-Server-ActiveSync” Get-WebServicesVirtualDirectory -Server $Server | Set- WebServicesVirtualDirectory -InternalURL “https:// $( $HTTPS_FQDN ) /EWS/Exchange.asmx” -ExternalURL “https:// $( $HTTPS_FQDN ) /EWS/Exchange.asmx” Get-MapiVirtualDirectory -Server $Server | Set-MapiVirtualDirectory - InternalURL “https:// $( $HTTPS_FQDN ) /mapi” -ExternalURL https:// $( $HTTPS_FQDN ) /mapi
6. Finally, review the Exchange DB settings and ensure that you create DBs according to the disk configuration and requirements.
Read More – You can also read how to export Exchange mailboxes to PST format.
5. Co-Existence Setup
Now it’s time to link the new server to the old one.
- Point all the external DNS records for emails to the new server and update all firewall rules (if any). (The emails will now flow into the new Exchange Server and then to the old one).
- Remove ExternalURL Value from the previous server.
- Point all the Internal Exchange Records related to emails to the new server.
6. Migrate Exchange 2010 to 2016
- Launch Exchange Admin Center >> go to Recipients >> migration tab.
- Click on the Move to a different database option.
- Under the New Migration Batch window, choose the “Select the users that you want to move” option or the “Specify the users with a CSV file” option for bulk migration.
- Click on the Next button after adding all the users.
- Enter a Migration batch name.
- Now, select the “Move the primary mailbox and the archive mailbox if one exists” radio button under the Archive section.
- Click on the Browse button to select the target database where you want to migrate Exchange 2010 to 2016.
- Enter the mailbox details to which you want to send the migration details.
- You can either go with the “Automatically start the batch” option or select the “Automatically complete the migration batch” option to complete the batch.
- Following that, click on the New button.
- You can also choose a migration batch manually by selecting the “Manually select the batch later” option.
- For this, go to the Recipients tab >> migration tab and then manually select a batch. Afterward, click on the Complete this migration batch option.
- You can then open the migration tab to check the migration status by selecting that batch.
After completion of the migration process, now it is time to decommission the Exchange 2010 Server. For that, you need to take care of the following points:
- The router is pointing to the new Exchange Server after Exchange 2010 to Exchange 2016 migration.
- Point the external domain DNS to the new server. (If you have an external IP Address for the server)
- Point scanners and multi-function printers to the new server.
Once you have performed all these actions, you can perform the decommission process very smoothly.
Perform Exchange 2010 to 2016 Migration in an Automated Way
If you have set up Exchange Server 2016 on your system successfully and need a simple way using which you can perform the migration, then you can consider Exchange 2010 to 2016 Migration Tool. This advanced solution offers abundant features to make your entire process a breeze.
In this tool, you just need to add the EDB file from Exchange Server 2010 and choose Live Exchange Server as your destination platform. There are many additional filters and customization options to filter your data migration process.
There is a category-based filter that will help you migrate only selective mailbox items from Exchange 2010 to 2016. Additionally, there is a date-based filter if you want to migrate data from a specific time range.
Likewise, there are many useful features to make your job effortless. Additionally, the software comes with a demo version that will let you try all the features for free.
Commonly Asked Queries
Q. What are the steps to migrate Exchange 2010 to 2016 using this utility?
A. Simple and Quick Steps for Exchange 2010 to Exchange 2016 migration are:
Step 1. Download the advanced utility for free.
Step 2. Add Exchange EDB file to tool.
Step 3. Choose Live Exchange as an export option.
Step 4. Enter details for destination Exchange.
Step 5. Finally, start the migration process.
Q. Is this aforementioned utility free to use or need a license to perform migration?
A. This Exchange 2010 to 2016 migration tool is not free to use but offers a free trial version. If you want to try the demo version of this utility before purchasing the licensed version, then you can download and try the software for free. This software will help you migrate 25 items per folder from each mailbox stored in the EDB file. Additionally, you can also test all the features offered in this utility.
Q. Does this application support public folder migration as well?
A. Yes, this software to migrate Exchange 2010 to 2016 is advanced enough to migrate complete mailbox data to the destination platform including public folders as well. Moreover, it also keeps the data integrity intact throughout the process.
Q. Are there any chances of data deletion or modification during the migration process?
A. No, the advanced algorithms used in this software ensures that no changes are made to the data. Thus, you can rely on this application if you are planning to migrate from Exchange 2010 to 2016.
This is a detailed guide that will help you migrate Exchange 2010 to 2016 in a hassle-free manner. You can follow this step-by-step process and complete the migration process with 100% precision. However, if the Exchange database that you are migrating is damaged or has some issues in it, then going with the Exchange Admin Center to migrate the Exchange Server can be quite difficult. Thus, we have discussed an alternative solution to perform the migration with ease.