Exchange 2013 to 2016 migration

If you do not upgrade from Exchange Server 2013, your data may be at risk of being compromised by security vulnerabilities that have not been fixed. It is recommended that you upgrade to a newer version of Exchange as soon as possible to ensure the security and stability of your email system.

What’s new in Exchange server 2016?

There are several new features and improvements in Exchange Server 2016 compared to Exchange Server 2013:

1. Improved search and indexing: Exchange Server 2016 includes an updated search and indexing engine, which allows for faster and more accurate searches of mailbox data.
2. Enhanced data protection: Exchange Server 2016 includes improved data loss prevention (DLP) features, which help organizations protect sensitive information from being sent accidentally.
3. Improved email archiving: Exchange Server 2016 includes an updated archiving system, which allows for more efficient storage and retrieval of archived email messages.
4. Enhanced collaboration: Exchange Server 2016 includes new collaboration features, such as support for Office 365 Groups and the ability to schedule Skype for Business meetings directly from Outlook.
5. Improved performance: Exchange Server 2016 includes various performance improvements, such as faster mailbox access and better resource utilization.
6. Improved security: Exchange Server 2016 includes improved security features, such as support for multi-factor authentication and data encryption.

   In addition to the improvements, there are also certain features from 2013 that have been discontinued in 2016. Consider that the extended support end date for 2016 is October 14, 2025.

Exchange 2010 and 2016 coexistence scenario

It is possible for Exchange Server 2013 and Exchange Server 2016 to coexist in the same Active Directory (AD) environment. Note that, Exchange 2013 to 2016 in place upgrade is not supported at the moment. The coexistence is supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.

Here is a general overview of the steps you can follow to migrate Exchange Server 2013 and Exchange Server 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 Exchange 2016 migration steps and post migration activities.

What is the best way to migrate from Exchange 2013 to 2016?

EdbMails is an excellent choice for Microsoft Exchange server migration. It can transfer mailboxes, public folders, and can help you upgrade from Exchange 2013 to Exchange 2016. It enables you to migrate all of your email data, including user folders, contacts, calendars, permissions, mail header data, tasks, journals, and notes, while maintaining complete data consistency. Additionally, EdbMails supports migrating to Exchange 2019, Office 365, Live Exchange, and Hosted Exchange servers and allows for direct migration without any intermediate hops, downtime, or data loss.

Exchange 2013 to 2016 migration checklist

Here is a checklist of steps that you should consider when migrating from Exchange 2013 to Exchange 2016:

1. Backup the Exchange 2013 data: Perform a full Exchange mailbox backup of the 2013 server and its data to ensure data safety.
2. Prepare your users for the migration: When you transfer your email data to a new system, it is important to train all your users for the change so that they are familiar with the new features and working flow. Also communicate the changes to your stakeholders.
3. Plan the migration: Determine the scope of the migration, migration type, including which mailboxes and other Exchange objects will be migrated and the timeline for the migration.
4. Prepare the target environment: Make sure that the Exchange 2016 server is installed and configured properly, and that all necessary prerequisites are met.
5. Migrate the mailbox data: Migrate all your emails, mailboxes and folders from Exchange 2013 server to the Exchange 2016 server.
6. Migrate other Exchange objects: Migrate other Exchange objects, such as room and equipment mailboxes, public folders, distribution lists, and contacts, from the Exchange 2013 server to the Exchange 2016 server.
7. Configure Outlook: Configure Outlook on the client computers to connect to the Exchange 2016 server.
8. 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.
9. Decommission the Exchange 2013 server: After the migration is complete and has been tested, decommission the Exchange 2013 server and remove it from the network.

I. 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	Possible. 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 2013 migration to Exchange 2016

  Consider if you want to migrate all your mailboxes at once or migrate it in phases. EdbMails can help you with a complete 2013 to 2016 Exchange 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 of your mailboxes from Exchange 2013 to 2016 in a single event and in a limited time frame.	Full Exchange 2013 to 2016 migration	In this approach, you set up the Exchange 2016 server and migrate everything in a single sitting. Suitable for large mailbox migration
  You have little time and want to migrate mailboxes from 2013 to 2016 in phases or over the weekends	Staged Exchange migration	In this approach, you migrate your mailboxes and mail data in stages and transfer the most recent data first, followed by the others.
  You want to migrate from Exchange 2013 to a Hybrid 2016 and Office 365 environment	Migrate from Hybrid Exchange to Office 365	In this approach, you 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.

  Note: If you have already installed and configured Exchange 2016 in the target environment, skip to point 4 in this step.

  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 Exchange

     You must create mailboxes and mail-enabled Public folders on the target for the migration. Also, assign suitable licenses to them.

     1. Steps to create mailboxes in Exchange server
     2. Steps to create Public folder in Exchange server
  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. Change the EWS throttling settings on Exchange server
     2. Change message size limits on target Exchange 2016