EdbMails EDB Recovery and Migration software
  • Reseller
  • Free Trial
  • Video Tutorials
  • Support
  • FAQ
  • Free Tools
  • Knowledge Base
  • Products
    Exchange EDB / Email Recovery Tools
    • EDB Recovery and MigrationRecover EDB to PST, EDB to Office 365 and Exchange NO Duplicate Migration
    • OST Recovery and MigrationRecover OST to PST, OST to Office 365 and Exchange Migration
    • PST Recovery and MigrationRecover Outlook PST, PST to Office 365 and Exchange Migration
    • MBOX Export and MigrationExport MBOX to PST, MBOX to Office 365 and Exchange Migration
    • NSF Export and MigrationExport NSF to PST, NSF to Office 365 and Exchange Migration
    Exchange and Office 365 Migration
    • Exchange Server MigrationMigrate Exchange 2007, 2010, 2013, 2016, 2019 to Office 365 tenants. Also, migrate between Exchange servers and PST
    • Office 365 MigrationMigrate Source Office 365 tenants to Destination Office 365 tenants. Also, migrate to Exchange Server and PST
    • IMAP Email Backup & MigrationMigrate all IMAP email servers (Gmail, Zimbra, Zoho, Yahoo etc.), Office 365, Exchange and Backup to Outlook PST
    • SharePoint Online MigrationMigrate documents, files and folders from SharePoint sites
    • OneDrive for Business MigrationMigrate documents, files and folders from OneDrive
    • Microsoft Teams MigrationMigrate Teams, documents, files and folders etc.
    Exchange and Office 365 Backup
    • Office 365 BackupIncremental, Granular, Encrypted and Compressed Office 365 Mailboxes Backup
    • Exchange Server BackupIncremental, Granular, Encrypted and Compressed Exchange Mailboxes Backup
    • SharePoint, OneDrive & Teams BackupBackup Online site collections, Team sites, Office 365 groups, all documents etc.
    • Duplicate Remover - Office 365 & Exchange Remove duplicate emails, calendars, contacts, journal etc. from Office 365 and Exchange
    • GAL and All Address Lists migrationDirectly migrate Exchange and Office 365 Global address list and Address Lists items
    Go to products
  • Pricing
  • Features
  • Download
  • Account
    1. Home
    2. Product
    3. How to perform a direct Exchange 2013 to 2016 migration?

    Exchange 2013 to 2016 migration

    Steps to migrate Exchange 2013 to 2016

User Manual

  • Exchange Migration Overview
  • Initial Setup
  • System Requirements
  • Installation
    • Installation process
    • Reinstall or Upgrade
    • How to uninstall
  • FAQ
    • General
    • Migration Free Trial / Demo
    • Migration License
    • Before Migration
    • Migration - Steps
    • After Migration
  • Videos
    • Exchange to Exchange
    • Exchange to Office 365
    • Exchange to PST
    • Public Folder to Office 365
    • Archive Mailbox to Office 365
    • Public Folder to Exchange
    • Archive Mailbox to Exchange
  • Screenshots
    • Exchange to Exchange
    • Exchange to Office 365
    • Exchange to PST
  • How it works?
    • Exchange to Exchange
    • Exchange to Office 365
    • Exchange to PST
    • Exchange Public Folder to Office 365
    • Exchange Public Folder to Exchange
    • Exchange 2010 to 2016 Public folder
    • Exchange 2013 Public folder to Office 365
    • Exchange 2016 Public folder to Office 365
    • Exchange Public Folder to Shared Mailbox
    • Archive Mailbox to Office 365
    • Archive Mailbox to Exchange
    • Hosted Exchange Migration
    • Hosted Exchange to Live Exchange Migration
    • Hosted Exchange to Office 365 Migration
    • Live Exchange to Hosted Exchange Migration
    • Hosted Exchange Public Folder to Office 365 Migration
    • Cross-forest migration from Exchange 2013 to Exchange 2019/2016
    • Hybrid Migration
    • Public folder Migration in Hybrid Environment
    • Migrate GAL and all address list
    • Disable msExchMailboxGuid
  • Connect to Exchange server for multiple mailboxes migration
    • Connect with Global Admin
    • Connect to Multiple users using CSV file
    • Connect using full access permission
    • Connect individual users for Single / Specific user Migration
  • Connect to Hosted Exchange for its Migration
    • Connect with Full Access permissions
    • Connect to multiple users using CSV file
    • Connect to Individual user for migration
  • Connect to Office 365
    • Modern Authentication Using OAuth 2.0
      • Microsoft 365 modern authentication
      • Automatic Registration
      • Manual Registration
    • Connect with Global Admin
    • Connect to Office 365 with full access permission
    • Connect to Office 365 with CSV file option
    • Connect to Office 365 as single user mailbox
  • Set Exchange Server Impersonation rights
    • Exchange 2007 and below
    • Exchange 2010, 2013, 2016 and 2019
    • Set using Exchange Server GUI
  • Understanding the Application
    • Program's Component
    • Migration
    • Incremental Migration
    • Exchange Throttling Policy
  • Set Office 365 Impersonation rights
    • Using PowerShell commands
    • Using Office 365 GUI
  • Migration Types
    • Cutover Migration
    • Staged Migration
    • Hybrid Migration
  • Map the Mailboxes
  • Migration Walkthrough
    • From Exchange 2003
    • From Exchange 2007
    • From Exchange 2010 to Exchange 2019
    • From Exchange 2010 to Exchange 2016
    • From Exchange 2010 to Office 365
    • From Exchange 2013 to Exchange 2019
    • From Exchange 2013 to Exchange 2016
    • From Exchange 2013 to Office 365
    • From Exchange 2016 to Exchange 2019
    • From Exchange 2016 to Office 365
    • From Exchange 2019 to Office 365
    • From Office 365
  • Multifactor Authentication
    • Enable MFA in Office 365
    • Create App password for MFA
    • Disable Security Defaults

What you need to know about Exchange server 2013?

Microsoft Exchange Server 2013 will reach the end of its life on April 11, 2023. This announcement means that Microsoft no longer provides technical support, security updates, or fixes for Exchange Server 2013.

If your organization plans on using Exchange Server 2013, it is important to upgrade to a newer version of Exchange, such as Exchange Server 2016 or Exchange Server 2019, in order to continue receiving technical support and security updates from Microsoft.

Exchange 2013 to 2016 migration

QUICK LINKS

Steps to export Exchange 2013 mailbox to PSTMigrate Exchange 2013 Public folder to Office 365Migrate mailbox from Exchange 2010 to 2016Exchange 2016 to Exchange 2019 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 versionCoexistence scenarioRequirement Migration
    Exchange 2016Possible. Can coexist with Exchange 2013Install Cumulative Update 21 (CU21) or later on Exchange 2013EdbMails 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 requirementIdeal migration approachMigration 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 migrationIn 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 weekendsStaged Exchange migrationIn 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 environmentMigrate from Hybrid Exchange to Office 365In 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

II. Exchange 2013 migration to Exchange 2016

After you have completed the necessary prerequisites, you can use EdbMails to perform the actual migration. EdbMails is specifically designed for migrating email data between Exchange servers, and it offers several advantages over other methods. For example, it allows you to perform direct migrations to the target server without the need for PowerShell scripts or technical expertise.

 See the best practices for migration from Exchange 2010 to 2016

  • Method 1: Direct mailbox migration from Exchange 2013 to 2016

    • To migrate your Exchange server data, first download and install the EdbMails. You can install it on the source Exchange server (2013) or on any other non-Exchange server computer. The application is compatible with Windows 7, 8, 10 and 11.

    • Launch the application and click 'Login' or 'Start Your Free Trial'.

       See a detailed list of EdbMails system requirements for Exchange migration.

      Demo login EdbMails

      Note: If the Standard folders (such as Inbox, Calendar, Contacts) in your source Exchange server mailboxes are using a different language than the language of the target (destination) server, it is important to follow certain steps to ensure that these folders are properly matched and migrated.

      For example, if your source Inbox folder is named "Boîte de réception" in French and you migrate this folder directly to the target server, it will not be automatically mapped to the "Inbox" folder on the target server. In order to properly map the folder with the French name to the corresponding folder on the target server, change the regional settings on the target server to match the language of the source mailbox folder (in this case, French). This will ensure that the folder is properly mapped and will function as expected on the target server.

    • Step 1: Select the Exchange to Exchange migration option

      In the EdbMails migration window, select the 'Live Exchange migration' option and click 'Continue'

      Select Exchange Migration

    • Step 2: Enter the Exchange 2013 server details in the Source

      In the Connect to Exchange server (Source) window, select 'Connect using Global Admin User'. Ensure you have already set the impersonation rights and the appropriate permissions to migrate mailboxes.

      You can also connect to the mailboxes by loading a CSV file. With EdbMails, you can migrate mailboxes, public folders, and archive mailboxes from the source Exchange to the target server. See how to use the different Exchange server connection methods supported by the application.

      Source Exchange Server Conection

       Tip: With the Autodiscover Email option, you can resolve Exchange IP address conflicts by directly entering your user credentials. You can also enter the server name and IP address manually with the Default Connection option.

    • Step 3: Select the mailboxes and connect to Exchange 2016

      Select the mailboxes and folders from Exchange server 2013 to migrate to Exchange 2016. You can also choose to migrate mailbox from Exchange 2013 to Office 365 or specific folders and items based on your requirements.

       Tip: If this is the first time you’re migrating with EdbMails, the migration is a full migration. On subsequent migrations from the same source to the target, the migration is incremental. You can remove duplicate mail items, such as emails and contacts, from your Exchange 2010 mailboxes before the migration. Learn how to remove duplicate items in Exchange with EdbMails.

      Click 'Migrate to Live Exchange' to setup the connection with the target server

      Export Selected Mailboxes

       Tip: EdbMails provides the following additional options to help you customize the migration task and migrate selected mail items based on email properties, sender and recipient address, subject, attachments and so forth.

      1. Additional Include and Exclude Filter Options
      2. Filter emails by Date: Migrate to Exchange 2016 by applying the Date filter.
      3. Filter emails by Size: Exclude emails from migration larger than a specified size.

      Include exclude folders

    • Step 4: Enter the Exchange 2016 server details in the destination

      Connect to the target server by selecting the option 'Connect using Global Admin User' and the migration scenario as Mailboxes, Public folder or Archive Mailbox.

      Connect using Global Admin User

       Tip: The mapping activity in EdbMails can automatically match and map the mailboxes and folders between the two Exchange servers. This feature saves time when you’re migrating a large number of mailboxes.

    • Step 5: Start the Exchange 2013 migration to 2016

      Start and monitor the migration operation after you complete the mailbox mapping. Finally, verify the count of migrated emails, folders and mailbox items with EdbMails text-based log report.

      Migrate Source Exchange to Destination Exchange

  • Method 2: Exchange 2013 to Exchange 2016 migration with EDB file

    EdbMails enables you to migrate an Exchange 2010 EDB (Exchange Database) file to Exchange 2016. This is one of the best methods if you want to migrate arbitration mailboxes and discovery search mailboxes between your Exchange servers.

    EdbMails can repair any issues and restore the corrupted EDB file of the Exchange server. Ensure that your Exchange 2016 server is properly configured and that you have the necessary permissions to perform the migration. Create a backup of your EDB file and mailbox data before starting the migration operation.

    • Step 1: Select EDB to Office 365 and EDB to Exchange migration

      After you download and install EdbMails EDB to Exchange migration tool, select the EDB recovery and migration option as shown.

      EDB to PST, EDB to Office 365 & Exchange

    • Step 2: Select the offline Exchange 2013 database file

      Select the EDB file from Exchange 2013 that you want to migrate. If the file is damaged or corrupt, EdbMails can repair the EDB and recover any mailbox data such as emails, contacts, calendars, and public folders. You can also convert the EDB file to PST for exporting your mailboxes.

      Select EDB file

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

      After the EDB recovery operation, you can preview specific emails, notes, calendars, tasks, contacts and can also migrate Exchange 2013 mailboxes to another database. Select the required mailbox data and folders to migrate and click 'Migrate to Live Exchange' to select the target Exchange server. Enter the server details, including the server address, username, and password to log in.

      Migrate to Live Exchange

    • Step 4: Start the EDB to Exchange 2016 migration

      Match the mailboxes and folders between the source and the target and migrate mailboxes from EDB to Exchange. After the migration is complete, you can log in to Exchange 2016 and verify the migrated contacts, folders, emails and so on. For a quick migration overview, you can also use EdbMails text-based log report.

  • Method 3: Migrate Exchange 2013 to Exchange 2016 with PST files

    If you have PST (Personal Storage Table) files exported from your Exchange 2013 server, you can migrate the PST to Exchange 2016 by using EdbMails.

    Create a backup of your PST files before migrating them to the Exchange server to ensure that you have a copy of your mailbox data. Download and run EdbMails if it hasn’t been installed on your system. The following steps outline the PST to Exchange migration.

    • Step 1: Select the Exchange migration option in EdbMails

      On the EdbMails migration selection window, select the migration method as Live Exchange migration to add and transfer multiple PST files in bulk to the target.

      Exchange Migration

    • Step 2: Select and add multiple PST files PST files for Exchange migration

      To add the PST files in bulk, close the Connect to Exchange (Source) connection window and click 'Migrate PST to Live Exchange' as shown. Select the destination for the PST files. You can choose to migrate the PST files to an on-premises Exchange server or to Office 365.

      Migrate PST to Live Exchange

    • Step 3: Click Migrate to Live Exchange to connect to Exchange 2016

      After adding the PST files, define the connection to the target Exchange server. You can connect to a specific user account, load mailboxes with a CSV file, migrate to a Hosted Exchange server and migrate Public folder and Archive mailboxes. Select the mailbox connection option depending on your target migration preference.

      Source Exchange Server Conection

    • Step 4: Match the mailboxes and start the Exchange 2013 to 2016 migration

      The mapping activity in EdbMails can automatically match and map the mailboxes and folders from the PST file to Exchange. Set the Action to migrate and start the migration. Finally, verify the count of the migrated items, folders and mailboxes with the text based 'View Log' report.

III. Exchange 2013 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, change the DNS records known as 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.

Advantages of using EdbMails for Exchange migration

EdbMails provides compelling benefits if you are planning to migrate from Exchange 2013 to 2016.

  • Provision for granular brick level migration of specific items
  • Incremental migration to prevent migrating duplicate items
  • Support for Exchange 2013 Public folder migration to 2016
  • Migrate Public folders to Shared mailboxes
  • Direct mapping of mailboxes between the source and the target
  • You can perform Hosted Exchange to Office 365 migration from servers such as GoDaddy, Rackspace

Frequently Asked Questions (FAQ)

  1. What are the benefits of upgrading from Exchange 2013 to Exchange 2016?

    There are several benefits to upgrading from Exchange 2013 to Exchange 2016, including:

    1. Improved performance and scalability: Exchange 2016 has been designed to handle larger mailbox sizes and higher levels of concurrent user activity, making it a more robust and scalable solution for larger organizations.
    2. Enhanced security features: Exchange 2016 includes a number of security enhancements, such as anti-malware and anti-spam protection, data loss prevention, and support for multi-factor authentication.
    3. Improved user experience: Exchange 2016 includes a number of user-friendly features, such as a redesigned web interface, support for touch-enabled devices, and the ability to search for items across all folders.
    4. Greater integration with other Microsoft products: Exchange 2016 integrates seamlessly with other Microsoft products, such as Skype for Business and OneDrive for Business, making it easier for users to collaborate and share information.
  2. What are the hardware and software requirements for Exchange 2016?

    The hardware and software requirements for Exchange 2016 depend on the number of users and the workloads you expect to place on the server.

     Minimum hardware requirements for Exchange 2016 include

    • 64-bit processor with at least four cores
    • 8 GB of RAM
    • At least 100 GB of free hard drive space

     Minimum software requirements for Exchange 2016 include:

    • Windows Server 2016 Standard or Datacenter
    • .NET Framework 4.7.2 or later
    • Windows Management Framework 5.1

    It is important to note that these are the minimum requirements and you may need to use more powerful hardware and software depending on your specific needs and workloads.

  3. How do I migrate my users, mailboxes, and data from Exchange 2013 to Exchange 2016?

    There are several methods for migrating from Exchange 2013 to Exchange 2016.

    1. In-place upgrade: This method involves installing Exchange 2016 on the same server as Exchange 2013 and upgrading the existing server. It is typically only recommended for small organizations with a single server.
    2. Staged migration: This method involves setting up a new Exchange 2016 server and migrating users, mailboxes, and data to it in stages. It is typically recommended for larger organizations with multiple servers.
    3. Cutover migration: This method involves setting up a new Exchange 2016 server and migrating all users, mailboxes, and data to it in a single cutover. It is typically recommended for small organizations with a single server.
    4. Hybrid migration: This method involves setting up a new Exchange 2016 server and migrating some users, mailboxes, and data to it while keeping others on the existing Exchange 2013 server. This method is typically recommended for organizations with a mix of on-premises and cloud-based users.
  4. Can I migrate to Exchange 2016 in-place, or do I need to set up a new server?

    In most cases, it is not recommended to perform an in-place upgrade from Exchange 2013 to Exchange 2016. Instead, it is typically recommended to set up a new Exchange 2016 server and migrate users, mailboxes, and data to it using one of the methods described above.

    There are a few exceptions to this rule, such as small organizations with a single server and minimal customization. In these cases, an in-place upgrade may be possible, but it is important to carefully plan and test the process to ensure a smooth transition.

  5. How long will the migration process take and what downtime can I expect?

    The length of the migration process will depend on several factors, including the size of your organization, the number of users and mailboxes being migrated, and the method you choose for the migration. When you use EdbMails for the Exchange migration, you do not have any downtime issues.

  6. Can I perform a test migration before moving everything over to Exchange 2016?

    Yes, it is generally recommended to perform a test migration before moving everything over to Exchange 2016. This allows you to identify and resolve any issues before the actual migration, ensuring a smoother transition for your users.

  7. How do I ensure a smooth transition for my users during the migration?

    There are several steps you can take to ensure a smooth transition for your users during the migration to Exchange 2016:

    • Communicate the migration process to your users in advance, including the changes expected.
    • Test the migration process before moving everything over to Exchange 2016 to identify and resolve any issues.
    • Set up a support system to help users with any questions or issues they may have during the migration.
    • Provide training and resources to help users understand and get the most out of the new features and functionality in Exchange 2016.
    • Monitor the migration process closely and be prepared to troubleshoot any issues that may arise.
  8. How do I handle any issues that arise during the migration process?

    It is important to carefully plan and test the migration to minimize the risk of issues arising. However, if issues do arise during the migration process, there are several steps you can take to troubleshoot and resolve them

    • Check the Exchange 2016 documentation and EdbMails Exchange migration troubleshooting guide for common issues.
    • Use the Exchange Management Shell to run diagnostic commands and gather more information about the issue.
    • Use event logs and other tools to identify the root cause of the issue and determine the best course of action.
Free Download
Buy Now
hidden msg

EdbMails Demo / Trial Version

Step 1. Download and install EdbMails

Step 2. Click the 'Start Your Free Trial' button

Demo login EdbMails

  • Home
  • Features
  • Pricing
  • Support
  • Download
  • Sitemap
  • FAQ
  • Video Tutorials
  • Technical Support
  • Live Chat
  • Contact Us
Shifttocloud Inc.
Rehoboth Beach, DE
United States
+1 (302) 416-3056

Privacy Policy | Terms of Use | GDPR | Security | Press Releases

© 2023 Shifttocloud Inc.

Live Chat

Hi, May I help you?

Hide Chat Now