How to migrate mailbox data from Exchange 2010 to 2019?

Exchange 2010 migration to Exchange 2019

Steps to migrate Exchange 2010 to 2019 server

What’s new in Exchange server 2019?

Microsoft Exchange 2010 has reached the end of its support on October 13th 2020, which means that it is prone to bugs, security flaws, and sluggish behavior. Microsoft has released newer versions such as Exchange 2013, 2016, and 2019, but many of us still use Exchange 2010. Exchange server 2019 includes new features such as a meta cache database, dynamic database cache to increase cache space for active databases, search indexing, and support for non-English characters in mailboxes. It is considered to be more stable than its previous versions. Learn what has been discontinued in Exchange 2019 and the ways you can migrate Exchange 2010 to 2019 in the following sections.

Exchange 2010 to Exchange 2019 Migration

QUICK LINKS

Migrate Exchange 2013 to 2019 Migrate from Exchange 2016 to 2019 Hosted Exchange migration to Office 365 Exchange 2010 to Exchange 2016 migration

Can Exchange 2010 and 2019 coexist in the same Active Directory?

Migrating from Exchange 2010 to Exchange 2019 usually comes with the caveat that you must first migrate to Exchange version 2013 or 2016, and then to 2019. This is due to the fact that Exchange server 2010 and 2019 cannot coexist in the same Active Directory but the 2010 can coexist with the 2013 or 2016 versions, making the intermediate migration time-consuming and complex.
However, thanks to EdbMails Exchange migration software, you can perform a direct migration to the target server without requiring intermediate migration hops. In this guide we describe the pre-migration activities, the actual migration and post-migration tasks to migrate Exchange 2010 to Exchange 2019.

Why should you upgrade Exchange 2010 to Exchange 2019?

Exchange 2010 is no longer supported by Microsoft.
Data in the Exchange 2010 is highly vulnerable to hardware and software issues, corruption, and unauthorized access as Microsoft doesn’t support bug fixes or release security updates.
Exchange 2019 includes Meta Cache Database (MCDB) functionality.
Support for non-English characters to email addresses with EAI proxy to accepted domains in 2019.
Calendar features are updated with ‘Do not forward’, ‘Out of Office’, and other management provisions in Exchange 2019.
Exchange 2019 can be installed in Windows Server Core.
Exchange 2019 provides more cache memory for the active database.
Search Index for a mailbox is in the mailbox only instead of a dedicated database.

How to plan Exchange 2010 to Exchange 2019 migration?

Planning is one of the prime requirements to ensure that you transfer all the data to the target server safely. Here is a general checklist of points and migration strategy that you can follow.

Take a complete backup of all your mailbox data at the source.
Ask your users to backup important files, attachments and contact entries.
Communicate the changes to all your users and stakeholders.
Estimate the cost required to upgrade your hardware, operating system and consider the maintenance factors.
Prepare the target environment and ensure you have the required bandwidth to migrate.
Make a note of the inventory of items such as Active Directory association, operating system, firewall, network configuration, port numbers installed programs, and list of users.
Install Exchange 2019 and create suitable mailboxes and Public folders
Perform a test migration to a few mailboxes and check if you are ready for a full migration.
Migrate from Exchange 2010 to 2019 and configure the domains to receive emails.
Create a new Outlook profile for all users and test if you are receiving emails correctly.
Decommission Exchange 2010 after you verify and inform the changes to all the end users.

I. Exchange 2010 to 2019 migration prerequisites

Step 1: Check that your system meets the Exchange 2019 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 2019.

Exchange server version	Coexistence scenario	Requirement	Migration Possible
Exchange 2019	Exchange 2019 cannot coexist with 2010	Install Cumulative Update 32 for Exchange 2010 SP3	Yes! With EdbMails Exchange migration, you can migrate to any Exchange server version regardless of the coexistence issue

Note: If you have the Domain Controllers (DC) running on Windows Server 2008, ensure that you first transfer the roles to a DC running Windows 2012 R2 or higher before you decommission any of the earlier DC’s. Exchange 2019 requires Active Directory forest functional level of Windows Server 2012 R2 or higher. See the Exchange server supportability matrix.

Step 2: Prepare your system with the following prerequisites for Exchange 2019
Complete the following prerequisites for Active Directory, Windows 2019 Mailbox server, and Windows 2019 Edge Transport servers for installing Exchange server 2019.
1. Prerequisites for preparing Active Directory (AD)
2. Windows Server prerequisites for Exchange 2019

Step 3: Decide on the migration path for Exchange 2010 to 2019

Consider if you want to perform a staged, hybrid or a cutover Exchange migration. EdbMails can help you with the following migrations without downtime or data loss. The advantage with it is that you can keep using your mailboxes during the migration without disconnecting your Exchange server.

Current environment and requirement	Ideal migration approach	How does the migration take place?
You want to perform a complete Exchange 2019 migration in a single event and in a limited time frame.	Exchange 2010 to 2019 cutover migration	In this approach, you set up the target Exchange server and migrate everything in a single sitting. Suitable for large mailbox migration
You have little time and want to migrate mailboxes 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 2010 to a Hybrid 2019 and Office 365 environment	Exchange Hybrid migration	In this approach, you migrate from the source server to a Hybrid Exchange and Office 365 environment. See the prerequisites for a Hybrid deployment

Step 4: Setup the target Exchange Server 2019 for migration
Given below is a list of key points for installing and preparing the Exchange 2019 server for migration.
Note: If you have already installed and configured Exchange 2019 in the target environment, skip to point 4 in this step.
1. Prepare AD and domains
  1. Before you install Exchange Server 2019, 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 2019
  Ensure that you meet the server system requirements and prerequisites outlined in the preceding sections. Next, install Exchange 2019 mailbox server and edge transport server using the setup wizard.
3. Prepare a clean Exchange 2019 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 2010
  Ensure that you have installed the latest cumulative updates (CU) on the source for Exchange server 2010 to 2019 migration.
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 the trust in advance, it is possible to address the trust issues during or after the migration.
  Note: This step applies to Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012. Creating a trust relationship 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 (2010) and target server (2019)
  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 2010 server. This property also applies to all the other user mailboxes.
9. Configure the throttling and message-size limits
  You can manually change the EWS throttling and message size limits on the target Exchange 2019 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 2019

II. Migrate Microsoft Exchange 2010 to 2019

After you complete the pre-migration activities, use EdbMails Exchange migration tool to migrate directly from Exchange server 2010 to 2019.

Tip: One of the benefits of using EdbMails is that you can perform direct migrations to the target server without the need to migrate to an intermediate version. This saves a significant amount of time and effort when you want to upgrade older Exchange versions to the latest.

You can perform Exchange 2010 migration with the following methods

Method 1: Direct Exchange 2010 to Exchange 2019 migration
Install EdbMails Exchange server migration software setup
- Download EdbMails and install the application on the source Exchange 2010 server or any other computer. You can also perform the migration by installing EdbMails on a non-Exchange server computer.
- Launch the application and click 'Login' or 'Start Your Free Trial'.
  See a detailed list of EdbMails system requirements for Exchange migration.
  
  Note: If the Standard folders (such as Inbox, Calendar, Contacts) on your source Exchange server mailboxes are initialized with a different language, follow the details in the link to migrate these folders to the respective system folders on the target (destination) server.
  For Instance: If your source Inbox folder is named 'Boîte de réception', which is in French language and you migrate this folder directly to the destination server, then by default it will not be mapped to the 'Inbox' folder on the target server. In order to map the folder with the french name to the respective folder, change the regional settings on the target server to match that of your source mailbox folder language (in this case, it is French).
  Steps to change the language and regional settings on Exchange server
- Step 1: Select Exchange migration
  In the EdbMails main window, select the option 'Live Exchange Migration (Hosted, hybrid, on-premise and more..)' and click 'Continue'.
- Step 2: Connect to Exchange server 2010 as Global Admin
  In the Connect to Exchange server (Source) window, select 'Connect using Global Admin User'. You can also connect to the mailboxes by loading a CSV file. See instructions to use the different Exchange server connection methods supported by EdbMails.
  With EdbMails, you can migrate mailboxes, public folders, and archive mailboxes from the source Exchange to the target server.
  Tip: EdbMails enables you to connect to Exchange with the Default connection where you specify the Exchange server name and Exchange version, or the Autodiscover Email option where you directly login with the user credentials.
- Step 3: Select the mailboxes and define the target connection
  Select the mailboxes and folders from Exchange 2010 that you want to migrate to Exchange 2019 server.
  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. If you have duplicate emails in your source server, you can remove them with the Exchange Duplicate remover tool before the migration.
  Click 'Migrate to Live Exchange' to setup the connection with the target server
  Tip: EdbMails provides the following additional options to help you customize the migration task.
  1. Additional Include and Exclude Filter Options
  2. Filter emails by Date: Migrate to Exchange 2019 by applying the Date filter
  3. Filter emails by Size: Exclude emails from migration larger than a specified size.
- Step 4: Connect to Exchange 2019 as Global Admin User
  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.
- Step 5: Match the source and target mailboxes
  The mapping activity in EdbMails can automatically match and map the mailboxes, folders between the two Exchange servers and saves time when you’re migrating a large number of mailboxes.
- Step 6: Start the migration to Exchange 2019
  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. You can also pause and resume the operation at your convenience. Login to your Exchange server to verify migrated items such as emails, calendars, contacts.
Method 2: Migrate 2010 to Exchange 2019 with an EDB file
If you have an EDB file from Exchange 2010, you can use EdbMails to import the mailboxes from EDB to Exchange. The application enables you to add an EDB file and repair it if it is corrupted. Finally you can select the mailboxes and migrate your mailbox data to Exchange 2019. The following steps describe the operation briefly.
- Step 1: Download EdbMails migration tool for EDB
  After you download and install the EDB to Exchange migration tool, select the option EDB Recovery and migration option from the main screen as shown.
- Step 2: Select the EDB file to import the data to Exchange
  If you have a corrupted EDB file from Exchange 2010 whose mailboxes you want to migrate, you can fully repair the file with EdbMails EDB repair tool. It can recover mailboxes, Public folders, contacts, calendars and all of your mailbox data.
- Step 3: Select the mailboxes and connect to Exchange 2019
  Next, select the required mailbox data and folders to migrate. EdbMails enables you to preview specific emails, tasks, notes, calendar items in the preview pane. Select 'Migrate to Live Exchange' and define the target connection to Exchange 2019.
- Step 4: Start the Exchange migration from 2010 to 2019
  Match the mailboxes, folders and verify the mapping operation. EdbMails can automatically perform the mapping for you to save time when you are migrating large mailboxes. Finally, start the Exchange migration and verify the migrated items with the log report.
Method 3: Mailbox migration from 2010 to 2019 with PST files
If you have Exchange 2010 mailboxes exported as PST, you can directly bulk migrate the PST files to Exchange 2019 with EdbMails. 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 migration technique as Exchange migration
  On the EdbMails migration selection popup, select the migration method as Exchange migration.
- Step 2: Select and add the Exchange 2010 mailbox PST files
  To add the PST files in bulk, close the Connect to Exchange (Source) connection window and click 'Migrate PST to Live Exchange' as shown. Continue with the operation after adding the PST files.
- Step 3: Connect to the target Exchange 2019 server as Global admin
  Next, select the Exchange connection option. You can also connect to a specific user account, load mailboxes with a CSV file or migrate to a Hosted Exchange server.
  With EdbMails, you can migrate mailboxes, public folders, and archive mailboxes.
- Step 4: Map mailboxes from the PST file and start the Exchange migration
  The mapping activity in EdbMails can automatically match and map the mailboxes and folders from the PST file to Exchange. After you complete the migration, verify the count of the migrated items, folders and mailboxes with the text based 'View Log' report.

III. Post-migration tasks

Step 1: Update the MX records to point to Exchange 2019 server
To receive messages on the Exchange server 2019, 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.
Step 2: Install the latest updates and configure features
Perform any necessary updates or upgrades to the new server, such as installing the latest service packs or cumulative updates. Configure any additional features or services that you want to use on the new server, such as archiving or eDiscovery.
Step 3: Create a new Outlook profile for users in the new domain
Exchange 2019 is compatible with Outlook 2013 and later. Uninstall any earlier versions and ensure that you have the latest client installed to prevent conflicts. Next, configure the Outlook profile for each user in your domain if Outlook has problems connecting to the new Exchange server.
Step 3: Decommission Exchange 2010 after the 2019 migration
Wait a few days and check to see if you are receiving emails correctly and that everything is working as expected.
- Remove any external connectors or send connectors that are pointing to the Exchange 2010 server.
- Remove any accepted domains or email address policies that are associated with the Exchange 2010 server.
- Remove any mail-enabled public folders that are hosted on the Exchange 2010 server.
- Remove any client access services from the Exchange 2010 server, such as Outlook Web Access (OWA), ActiveSync, and Outlook Anywhere.
- Remove the Exchange 2010 server from the organization.
- Remove the server object from Active Directory Domain Services (AD DS).
Finally decommission the source Exchange server. Follow the instructions on Microsoft's website to learn how to uninstall Exchange Server 2010.

IV. Exchange migration troubleshooting

See Exchange migration troubleshooting guide for possible solutions related to common migration errors.

Advantages of using EdbMails for Exchange 2010 migration

EdbMails simplifies complex Exchange server migration without requiring PowerShell scripts or technical knowledge of the operation. Based on your requirements, you can upgrade your server to the latest version or migrate mailboxes from Exchange 2010 to Office 365 tenant in a few clicks.

Best application for Office 365 and Exchange migration
You can perform 2010 to 2019 cross forest Exchange migration and easily transfer your data across different Active Directory forests.
Support for exporting Exchange mailboxes to PST
Facility for secure Exchange server backup of 2010 and 2019 mailboxes
Enables you to perform migration to a Hybrid Exchange and Office 365 environment.
Advanced include and exclude filter options for mailbox items and folders
Free 24x7 priority technical support and personalized migration assistance.

Frequently Asked Questions (FAQ)

How do I migrate Public folders from Exchange 2010 to 2019?
EdbMails enables you to migrate Exchange 2010 Public folders to 2016 and 2019 without requiring PowerShell scripts for the operation.
The following steps describe the 2010 Public folder migration to 2019
- Step 1: Download EdbMails and connect to Exchange 2010
- Step 2: Select Public folder migration in the connection window
- Step 3: Select the folders and click 'Migrate to Exchange'
- Step 4: Connect to the Exchange 2019 server as Global Admin
- Step 5: Map and migrate Exchange 2010 Public folders to 2019
Tip: You can also migrate Public folders to Shared mailbox with EdbMails.
What are the system requirements for the Exchange 2010 to 2019 migration?
You must meet the following prerequisites before you can start the migration
- Hardware: Exchange 2019 requires a 64-bit hardware.
- Active Directory: Exchange 2019 requires at least Windows Server 2012 R2 forest functional level.
- Exchange 2010: Exchange 2010 SP3 RU11 or later is required.
Can I migrate from Exchange 2010 to 2019 directly without an intermediate version?
Yes. With EdbMails, you can directly migrate 2010 to 2019 without having to migrate to intermediate versions first.
How to prepare my current Exchange 2010 environment for the migration?
- Install the latest service pack and rollup updates for Exchange 2010.
- Verify that all mailbox databases are mounted and in a clean shutdown state.
- Verify that all mailbox database copies are healthy and in sync.
- Check that all public folder databases are mounted and are mail enabled.
How to test the Exchange 2019 environment after the migration?
- Verify if all mailboxes and data have been successfully migrated.
- Verify and check if the Exchange services and features are functioning properly.
- Check the EAC on Exchange 2019 to confirm that all mailboxes and data from the Exchange 2010 server are present.
- Log in to a user mailbox and verify that all emails, contacts, calendar items, and other data are present and accessible.
- Ensure that you are receiving emails correctly and that your domains are set up properly.
- Test the various features of Exchange such as email, calendar, and contacts to ensure that they are working as expected.
- Use a client such as Outlook or a mobile device to test the connectivity to the Exchange 2019.
- Use tools such as Telnet or the Exchange Remote Connectivity Analyzer to test the performance and connectivity of the Exchange 2019 environment.
- If you have multiple Exchange servers or multiple domains, test the interoperation between the different servers and domains to ensure that they are functioning properly.

Free Download

Buy Now

Exchange 2010 migration to Exchange 2019

Steps to migrate Exchange 2010 to 2019 server

What’s new in Exchange server 2019?

I. Exchange 2010 to 2019 migration prerequisites

II. Migrate Microsoft Exchange 2010 to 2019

Method 1: Direct Exchange 2010 to Exchange 2019 migration

Method 2: Migrate 2010 to Exchange 2019 with an EDB file

Method 3: Mailbox migration from 2010 to 2019 with PST files

III. Post-migration tasks

IV. Exchange migration troubleshooting

Advantages of using EdbMails for Exchange 2010 migration

The following steps describe the 2010 Public folder migration to 2019