Migrate Exchange 2013 to 2016

Microsoft Exchange Server 2013 reached its end of life on April 11, 2023, which means Microsoft no longer provides security updates, bug fixes, or technical support for this version. If your organization is still using Exchange 2013, it’s time to upgrade to a newer version like Exchange Server 2016 or 2019 to maintain security, performance, and support. Delaying the upgrade can expose your business to data breaches and security risks caused by unpatched vulnerabilities. Performing an Exchange 2013 to 2016 migration ensures your email system remains secure and fully operational.

Manual migration methods such as using the Exchange Admin Center (EAC) or PowerShell scripts can be complex and time-consuming. These approaches require in-depth technical knowledge for tasks like exporting mailboxes, configuring databases, and managing migration batches. In many cases, migrating from Exchange 2013 to 2016 manually can lead to extended downtime, incomplete data transfers, or even data loss, especially in larger or hybrid environments. For a smooth and efficient migration, organizations often look for automated solutions that simplify the Exchange 2013 migration to 2016 process and ensure a reliable, step-by-step upgrade with minimal disruption.

To make this transition smoother and more reliable, EdbMails Exchange Migration Software offers an ideal solution. It simplifies the entire migration process, allowing for seamless migration from Exchange 2013 to newer versions such as Exchange 2016, 2019, or Office 365. With EdbMails you can be assured that the migration will be secure, fast, and free from data loss or downtime. The software ensures full-fidelity migration, preserving all mailbox data, including emails, contacts, calendars, tasks, public folders, archive mailboxes and their associated metadata and folder structures, guaranteeing a smooth, worry-free migration.

1. What’s new in Exchange server 2016?

   Exchange server 2016 introduced several new features and improvements over Exchange server 2013:

   1. Improved search and indexing: Exchange server 2016 comes with a new search and indexing engine that offers faster and more accurate searches of mailbox content. EdbMails Exchange migration ensures that all mailbox data, including emails and attachments, is transferred accurately, allowing users to take advantage of this improved search functionality immediately after migration. The software maintains the original folder structure and metadata, enhancing the user experience.
   2. Enhanced data protection: With enhanced data loss prevention (DLP) capabilities, Exchange server 2016 assists organizations in safeguarding sensitive information from unintentional sharing. EdbMails supports the secure migration of sensitive data, providing peace of mind regarding data protection.
   3. Improved email archiving: Exchange server 2016 features a new archiving system that enhances the efficiency of storing and retrieving archived email messages. EdbMails facilitates the migration of archived emails and other mailbox items, ensuring all archived content is correctly transferred to the new system, allowing users to benefit from improved archiving without losing historical data.
   4. Enhanced collaboration: Exchange server 2016 introduces collaboration tools, including support for Office 365 Groups and the ability to schedule Skype for Business meetings directly from Outlook. EdbMails focuses on migrating mailbox data, including emails, calendars, contacts, and tasks, enabling users to leverage the new features and functionalities of Exchange Server 2016 after the migration.
   5. Improved performance: Exchange Server 2016 introduces several performance improvements, ensuring faster mailbox access and more efficient resource utilization. EdbMails is designed for high-speed migration, enabling a seamless transition with zero downtime and no user disruptions. This allows organizations to take full advantage of Exchange Server 2016’s enhanced performance without affecting daily operations.
   6. Improved security: With upgraded security measures such as multi-factor authentication and enhanced data encryption, Exchange Server 2016 ensures a secure environment. EdbMails supports secure data transfer protocols during migration to maintain the integrity of the mailbox data being migrated.

      It's important to note that some features from Exchange Server 2013 have been phased out in 2016. EdbMails helps organizations navigate these changes by providing detailed migration reports and support, ensuring users are aware of any deprecated features. Additionally, extended support for Exchange Server 2016 will end on October 14, 2025. EdbMails provides ongoing support and resources to help organizations plan for future migrations or upgrades, ensuring they stay current with the latest technology.

2. What Is the Best Way to Migrate Exchange 2013 to 2016?

   The most reliable way to migrate Exchange 2013 to 2016 is by using a dedicated and automated migration tool such as EdbMails Exchange Migration software. It simplifies the complex process of transferring mailboxes, public folders, shared mailboxes, and archive mailboxes while preserving complete data integrity. All essential mailbox items, including emails, contacts, calendars, permissions, tasks, journals, and notes, are securely migrated without downtime or data loss.

   EdbMails offers several advanced features that make the Exchange 2013 to 2016 migration process faster and more efficient. Its incremental migration ensures that only new or modified items are transferred in subsequent migrations, preventing duplication. The concurrent migration option enables multiple mailboxes to be migrated simultaneously, significantly reducing the overall migration time. With automatic mailbox mapping, the software intelligently matches source and target mailboxes, minimizing manual effort. Additionally, advanced filter options allow you to migrate specific folders, date ranges, or item types based on your organization’s needs.

   By combining security, flexibility, and performance, EdbMails provides an ideal solution to migrate from Exchange 2013 to 2016. It ensures a smooth, reliable, and fully compliant migration experience, helping organizations upgrade to Exchange Server 2016 with confidence and minimal disruption.

3. Exchange 2013 and 2016 Coexistence scenario

   Exchange Server 2013 and Exchange Server 2016 can coexist within the same Active Directory (AD) environment. However, a direct upgrade from Exchange 2013 to 2016 is not currently supported. For successful coexistence, Exchange 2013 must be updated to Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.

   With the EdbMails Exchange Migration Tool, you can directly migrate from Exchange 2013 to Exchange 2016, eliminating the need for complex coexistence setups. The software ensures a smooth and secure migration, preserving all your mailbox data, folder structures, and permissions.

   Here is a general overview of the steps you can follow to migrate Exchange 2013 to 2016 in the same AD environment:

   1. Install Exchange Server 2016 in a new organization

      If you are planning to introduce Exchange Server 2016 into an existing Exchange Server 2013 organization, it is recommended to create a new Exchange organization and install Exchange Server 2016 into it. This will allow you to gradually transition to Exchange Server 2016 while keeping Exchange Server 2013 in place.

   2. Upgrade the AD schema

      Before installing Exchange Server 2016, you will need to upgrade the AD schema to include the new attributes and objects introduced in Exchange Server 2016. To do this, you will need to run the following command on a domain controller

      Command: Copy & Paste

      setup.exe /PrepareSchema

   3. Prepare the AD domains

      After upgrading the schema, prepare the AD domains in which you plan to install Exchange Server 2016. To do this, you will need to run the following command on a domain controller:

      Command: Copy & Paste

      setup.exe /PrepareAD /OrganizationName:<Contoso ABC>

   4. Install Exchange Server 2016

      After preparing the AD domains, you can proceed with the installation of Exchange Server 2016. Run the Exchange Server 2016 setup program and follow the prompts to install the software.

   5. Configure the mail flow

      After installing Exchange Server 2016, configure the mail flow between the two Exchange servers. You can do this by creating a send connector in Exchange Server 2016 that routes mail to Exchange Server 2013.

   6. Migrate from Exchange 2013 to 2016

      Set up EdbMails software for Exchange migration and directly migrate all of your mailbox data from the source to the target. Test and verify the migration and add MX records for proper mail flow.

   In the following sections, we describe in detailed steps to configure Exchange 2016, the pre migration tasks, Exchange 2013 to 2016 migration steps and post migration activities.

4. Exchange 2013 to 2016 Migration Checklist

   Before you migrate Exchange 2013 to 2016, it’s essential to have a well-structured plan to ensure a seamless transition with minimal disruption. Below is a detailed checklist to guide you through each stage of the migration process.

   1. Prepare Users for the Migration

      Start by informing and training your users about the upcoming Exchange 2013 to 2016 migration. Help them understand the new features, updated interface, and workflow changes. Communicate clearly with all stakeholders to ensure everyone is aware of the migration schedule and expected outcomes.

   2. Plan the Migration

      Define the scope and type of migration based on your organization’s needs. Decide which mailboxes, public folders, and Exchange objects will be migrated and establish a clear timeline. Proper planning helps reduce downtime and ensures a smooth Exchange Server 2013 to 2016 migration.

   3. Prepare the Target Environment

      Make sure that the Exchange 2016 server is installed and configured properly, and that all necessary prerequisites are met.

   4. Migrate Mailbox Data

      Migrate all mailbox content, including emails, folders, contacts, calendars, and tasks from Exchange 2013 to the Exchange 2016 server.

   5. Migrate Other Exchange Objects

      Migrate additional Exchange components such as room and equipment mailboxes, public folders, distribution lists, and shared mailboxes. This ensures that all essential communication and collaboration resources are available in the new environment.

   6. Configure Outlook Clients

      Update and reconfigure Outlook profiles on user computers to connect to the new Exchange 2016 server. Verify that users can access their mailboxes and that all data is synchronized correctly.

   7. Test the migration:

      Test the migration to ensure that everything has been migrated properly and that users can access their mailbox data on the Exchange 2016 server.

   8. Decommission the Exchange 2013 Server

      Once testing is complete and all data has been validated, safely decommission the Exchange 2013 server. Remove it from the network and update DNS records and connectors to point to Exchange 2016.

5. Exchange 2013 to 2016 migration prerequisites

   • Step 1: Check that your system meets the Exchange 2016 setup requirements.

     Before you migrate your mailbox data to Exchange 2019, ensure that your current environment and hardware is compatible for the transfer. The following links will help you to know about the network, hardware,.NET framework and operating system requirements for installing Exchange server 2016.

     1. Network and directory requirement for Exchange 2016
     2. Hardware Requirements for Exchange 2016
     3. Supported operating systems for Exchange 2016
     4. Supported .NET Framework in Exchange 2016
     5. Supported Outlook clients in Exchange 2016

     Exchange server version	Coexistence scenario	Requirement	Migration
     Exchange 2016	Can coexist with Exchange 2013	Install Cumulative Update 21(CU21) or later on Exchange 2013	EdbMails supports direct Exchange migration 2013 to 2016

     Note: Exchange 2016 requires Active Directory forest functional level of Windows Server 2008 R2 or higher and a .NET Framework 4.8 on a Cumulative Update (CU) of 15. The Mailbox and Edge Transport servers require Windows Server 2012 Standard or Datacenter and higher. See the Exchange 2016 server supportability matrix for more information.

   • Step 2: Prepare your system with the following prerequisites for Exchange 2016

     Ensure that you meet the following prerequisites for Active Directory, Windows 2016 Mailbox server and Windows 2016 Edge Transport servers for installing Exchange 2016.

     1. Prerequisites for preparing Active Directory (AD)
     2. Windows Server prerequisites for Exchange 2016
   • Step 3: Decide on the approach for Exchange 2013 migration to 2016

     Consider if you want to migrate all your mailboxes at once or migrate it in phases. EdbMails can help you with a complete Exchange 2013 to 2016 migration without affecting your users. The advantage with it is that you can keep using your mailboxes even during the migration without disconnecting your Exchange server.

     Current environment and requirement	Ideal migration approach	Migration flow
     You want to move all mailboxes from Exchange 2013 to 2016 in a single event and within a limited time frame.	Full Exchange 2013 to 2016 Migration	Set up the Exchange 2016 server and migrate all mailboxes in a single session. Suitable for large mailbox migrations.
     You have limited time and want to migrate mailboxes from Exchange 2013 to 2016 in phases or over weekends.	Staged Exchange migration	Migrate mailboxes and data in stages, starting with the most recent data, followed by the rest.
     You want to migrate from Exchange 2013 to a Hybrid Exchange 2016 and Office 365 environment.	Migrate from Hybrid Exchange to Office 365	Migrate from the source server to a Hybrid Exchange and Office 365 environment. See the prerequisites for a Hybrid deployment.

     Note: The specific migration method depends on the number of mailboxes, size of the data and your organizational requirements.

   • Step 4: Set up the target Exchange Server 2016 for migration

     Given below is a list of key points for installing and preparing the Exchange 2016 server for migration.

     1. Prepare the AD and domains
        1. Before installing Exchange Server 2016, you need prepare your Active Directory forest and its domains for the new version of Exchange.
        2. If you have a separate team to manage the Active Directory schema, you must extend the active directory schema, else proceed to the next step to prepare the Active Directory.
        3. If you have multiple domains you need to additionally prepare the Active Directory domains.
     2. Install Exchange server 2016

        Before installing the Exchange server 2016, ensure that you meet the server system requirements and prerequisites as outlined above. Next, follow the link to install Exchange 2016 mailbox server and edge transport server using the setup wizard.

     3. Prepare a clean Exchange 2016 target environment
        1. Install and upgrade Exchange to the latest cumulative update to keep your server up to date.
        2. Create and configure a Send connector to send mail outside the Exchange organization.
        3. By default, Exchange automatically creates receive connectors for inbound mail flow when the mailbox server is installed. However, if you want to configure custom receive connectors for certain mail flow scenarios, follow the steps in the link.
        4. Add accepted domains to allow recipients to send and receive email from another domain.
        5. Configure the default email address policy to add the accepted domain to every recipient in the organization.
        6. Configure external URLs (domains) on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internet (outside the organization’s network).
        7. Configure internal URLs on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internal network.
        8. Configure SSL certificates from a third-party certificate authority for services such as Outlook Anywhere and Exchange ActiveSync.
        9. Verify the Exchange server installation by running the command Get-ExchangeServer on the Exchange Management Shell (EMS)
     4. Create mailboxes and Public folder on the target 2016 Exchange server

        Ensure to create mailboxes on the target server and assign suitable licenses to them. You can choose EdbMails to automatically create mailboxes on the target Exchange server. However, if you want to create mailboxes manually follow the link below:

         Steps to create mailboxes in Exchange 2013 server.

        If you are planning to migrate to public folders, create mail-enabled Public folders on your target server and assign the admin permissions.

         Steps to create Public folder in Exchange 2013 server and assign admin permissions.

     5. Install cumulative updates (CU) on Exchange server 2013

        For migrating Exchange server 2013 to Exchange 2016, it is required that you have installed the latest cumulative updates (CU) on the source server (2013).

     6. Create trust relationship between forests (Optional)

        A forest trust is an authentication between two domains within the same Active Directory forest which creates a trust between two root domains for exchanging information. By creating a trust in advance, it is possible to address the trust issues during the cross-forest authentication. See steps for cross forest migration from Exchange 2013 to 2016.

        Note: Creating a forest trust relationship applies to Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012. It is not required for SBS based environments.

     7. Assign management roles to the admin account

        Ensure that you have set the following permissions to the admin account on the source (2013) and target server (2016)

        1. On the source
           1. ApplicationImpersonation
           2. View-Only Configuration - Run the cmdlet New-ManagementRoleAssignment using the Exchange Management Shell to assign the View-Only Configuration role to the admin.
           3. Organization Management role group. It is an elevated permission that is required to migrate Public folders.
        2. On the target
           1. ApplicationImpersonation
           2. View-Only Recipients
           3. View-Only Configuration
     8. Verify the mailbox of the admin account

        Check to see if the admin account that has been assigned management roles has a valid and non-hidden mailbox on the Exchange 2013 server. See how to configure user mailbox properties for the users from the Exchange admin center (EAC).

     9. Configure the throttling and message-size limits

        You can manually change the EWS throttling and message size limits on the target Exchange 2016 server by following the steps outlined in the links below.

        1. Custom EWS throttling policies on Exchange 2016 server.
        2. Message size limits on target Exchange 2016 server.

6. Exchange 2013 to 2016 migration using EdbMails Software

   • Step 1: Download and install the EdbMails software

     • Download and install the EdbMails application on your computer running on Windows OS.

       

         System requirements for Exchange 2013 to 2016 migration.

     • Launch the EdbMails software.
     • Log in with your email address and password, or select 'Start Your Free Trial' if you haven’t created an account yet.

       

     • Select ‘Live Exchange Migration' option.

       

     • Select ‘Live Exchange to Live Exchange Migration' option.

       

     • Keep the default job name or click 'New Job' to change it, then click 'Next'.

       

   • Step 2: Connect to source Exchange 2013 server

     • Click the ‘Add New Connection’ button to establish a new connection to the source Exchange server. To use a previous connection, select it from the connection list and click the ‘Connect to Existing’ button to proceed.

       

        EdbMails allows you to migrate mailboxes, public folders, and archive mailboxes from the source Exchange to the target server.

     • Select the required connection options and click the ‘Next’ button.

         Different options to connect to Exchange server in EdbMails.

       

     • Enter the source Exchange 2013 server details and click the ‘Login’ button.

       

     • Choose the option to load mailboxes. EdbMails will automatically load your mailboxes from your source Exchange 2013 server, or you can load them manually using a CSV file.

       

   • Step 3: Select Exchange server 2013 mailboxes to migrate to Exchange 2016

     • Choose the Exchange 2013 mailboxes you wish to migrate.
     • Click the ‘Next’ button.

       

   • Step 4: Connect to target Exchange 2016 server

     • To connect to the target Exchange Server 2019, click the ‘Add New Connection’ button to establish a fresh connection. If you wish to use a previously saved connection, simply select it from the list and click ‘Connect to Existing’ to continue.

       

     • Select the required connection options and click the ‘Next’ button.

        check Different options to connect to Exchange server in EdbMails

       

     • Enter the target Exchange server 2016 details and click the ‘Login’ button to continue.

       

     • Once you've successfully logged in, select the required option for loading the target Exchange 2016 server mailboxes.

       

   • Step 5: Exchange 2013 to 2016 mailboxes mapping

     • Select the required mapping option

       .

     • If you’ve installed EdbMails on your target Exchange 2016 server, you can opt to let EdbMails automatically create the necessary mailboxes for you—streamlining the setup and reducing manual work.

         Learn more about automatic mailbox creation.

       EdbMails also handles automatic mapping between source and target mailboxes. This is particularly useful when migrating a large number of mailboxes.

       

   • Step 6: Start Exchange 2013 to Exchange 2016 migration

     • After completing the mailbox mapping, click the ‘Start Migration’ button to initiate the migration process.

       

     • While the migration is running, you can monitor its real-time progress through the progress bar. When the migration finishes, a confirmation message will be displayed. To review the details of the operation, simply click the ‘View Logs’ button to access the complete migration report.

       

7. Exchange 2013 to 2016 post migration tasks

   There are several post-migration tasks that you should perform after completing an Exchange 2013 to Exchange 2016 migration. These tasks can help ensure that your Exchange 2016 deployment is functioning properly and that your users are able to access their email, calendars, and other Exchange services.

   1. Verify that all mailboxes have been successfully migrated to the new Exchange 2016 server.
   2. Test the functionality of all client access protocols (e.g., Outlook Web App, Outlook Anywhere).
   3. Test the functionality of all Exchange services (e.g. Outlook calendar, contacts, tasks).
   4. Test the functionality of any third-party applications that integrate with Exchange (e.g., CRM, archiving).
   5. Update the domain name in the DNS records to point to the new Exchange 2016 server.
      • To receive messages on the Exchange server 2016, update MX records to enable email to work with the new server you have migrated to. In addition, configure the Autodiscover record to allow Outlook to connect to the migrated mailboxes.
   6. Create a new Outlook profile for users in the new domain
      • Ensure you have the latest version of Outlook installed to avoid compatibility issues. Configure the Outlook profile for each user in your domain if Outlook has problems connecting to the new Exchange server.
   7. Monitor the performance of the new Exchange 2016 server to ensure that it is functioning properly.
   8. Decommission and uninstall Exchange server 2013
      1. Remove the Exchange 2013 server from the load balancer, if you have one.
      2. Remove the Exchange 2013 server from the Exchange organization by using the Remove-ExchangeServer cmdlet.
      3. Remove the Exchange 2013 server from Active Directory. This can be done by using the Active Directory Users and Computers console or the Remove-ADObject cmdlet.
      4. If you want to completely remove Exchange 2013 from the server, you can use the Install-WindowsFeature cmdlet to remove the Exchange 2013 server roles.
      5. Once all these steps are complete, you can decommission the Exchange 2013 server and remove it from your network.
      6. Follow the instructions on the Microsoft’s website to decommission Exchange Server 2013

   It's important to thoroughly test your Exchange 2016 deployment after the migration to ensure that everything is working as expected and that your users are able to access their email and other services. It's also a good idea to document any issues that you encounter during the testing process so that you can troubleshoot them more effectively.

8. Exchange 2013 to 2016 migration troubleshooting guide

    Refer to the Exchange migration troubleshooting guide for effective solutions to common migration errors.

---

Additional resources:

• EdbMails Exchange migration software
• Exchange 2010 to 2019 migration
• Exchange 2013 to 2019 migration
• Exchange 2016 to 2019 migration
• Exchange 2010 to 2016 migration
• Exchange to Office 365 migration