Live Exchange migration FAQs

EdbMails Exchange server Migration takes the most critical part of a server migration or Exchange upgrade - moving of user’s mailboxes as well as public folders - off your back. EdbMails automatically performs a direct migration of the mailboxes you selected on the source and mapped to the target server. (without modifying any items on the source server).

• Direct Exchange server migrations from any Exchange Server to Exchange 2010, 2013, 2016 or 2019 and to Office 365 organizations.
• Allows migrations to new domains or forests.
• Supports public folder migrations.
• Intuitive GUI (no PowerShell cmdlets are required).

EdbMails connects to the source and destination Exchange servers, displays the available mailboxes, and lets you select and map them before migration. It supports automatic and manual mailbox mapping and migrates the selected mailbox data directly to the destination. When connecting to Exchange Server using the Global Admin option, the administrator must manually configure the required impersonation rights.

Yes. EdbMails Exchange server migration supports migration to your Office 365 tenants. You can effortlessly migrate mailboxes from Exchange Server (Version 2019, 2016, 2013, 2010 and 2007) to Office 365.

Yes, EdbMails supports Hosted Exchange Server migration. Whether you're using services like Rackspace, GoDaddy, or others, EdbMails can easily migrate your mailboxes, public folders, and other data to your target Exchange server or Office 365.

EdbMails provides a graphical interface to migrate Exchange mailboxes, Public Folders, and supported mailbox data without writing migration scripts. It supports automatic mailbox mapping, incremental migration, and detailed migration logs. The application preserves supported folder structures and item properties, while allowing administrators to review migration results and verify the data in the destination Exchange Server.

Yes. EdbMails supports migrating Exchange Public Folder contents, subfolders, and supported permissions to the destination Exchange Server. Before migration, prepare the destination Public Folder environment and configure the necessary permissions. EdbMails helps preserve the supported Public Folder hierarchy, but administrators should verify folder access and permissions after migration.

• For Exchange Server 2013 / 2016 / 2019
• For Exchange Server 2010

Yes. EdbMails supports migration between eligible source and destination Exchange mailboxes within the same domain when the mailbox configuration allows it. If separate source and destination mailboxes are required, they must have distinct identities, and you can map them manually in EdbMails. Check the Exchange version and Active Directory coexistence requirements before starting the migration.

For Instance: If the source and target servers have a user mailbox with the name such as alex.joe@domain.com then you have to create a different mailbox for the same user in the target server (say, alex.j@domain.com).

NOTE: All the Microsoft’s coexistence limitations for various exchange server versions still apply and only cross-domain direct migrations are possible in all such cases.

No, EdbMails does not store your entire mailbox data on your local computer. It only keeps certain metadata details in an encrypted format, ensuring the security and privacy of your information. The actual mailbox data is migrated directly between the source and target servers, without being stored locally.

Yes. EdbMails supports migrating Exchange mailbox data containing Unicode characters and non-English languages. It preserves supported folder names, email content, and special characters during migration. If default mailbox folders use different languages on the source and destination, review the folder mapping to ensure that items are migrated to the correct folders.

EdbMails does not specify a fixed mailbox size or migration speed limit for Exchange Server migration. However, actual migration depends on source and destination mailbox quotas, message size limits, network performance, and Exchange throttling policies. Administrators should verify these limits before migrating large mailboxes.

The duration of the migration process can vary depending on several factors, such as internet speed, network hardware, system configuration, and any throttling policies on the source or target servers. While it’s difficult to give an exact time, EdbMails is optimized for high performance and is designed to complete migrations as quickly and efficiently as possible.

If you need help during the process, our 24x7 Technical Support Team is available via Email, Live Chat.

Yes, you can migrate mailboxes from Exchange 2003 using EdbMails. Since Microsoft does not support direct migration from Exchange 2003 to newer versions, the recommended approach is to export the mailboxes to an offline EDB file and use EdbMails to migrate the data directly from the EDB file to the latest Exchange versions (2013, 2016, 2019).

Yes. EdbMails supports Microsoft 365 connections with Multi-Factor Authentication using Modern Authentication (OAuth 2.0). Administrators can authenticate through the supported Microsoft sign-in process without using legacy app passwords. Ensure that the account has the necessary permissions and that authentication is permitted by the organization's security policies.

  Refer to the EdbMails Microsoft 365 Modern Authentication Guide.

Public Folder migration within the same Active Directory forest depends on the Exchange versions, coexistence configuration, and destination Public Folder environment. EdbMails can migrate supported Public Folder data when valid source and destination configurations are available. Check Microsoft's Public Folder coexistence requirements before attempting migration within the same forest.

Follow the steps below to fix the 'Categories' and 'Color Code' display.

1. Right click on the mail / calendar item and from the 'Categories' menu, click the 'All Categories...' as shown below.

2. As shown below, in the 'Color Categories' window, create the categories with the appropriate color code.

This error can occur when Exchange cannot identify a mailbox associated with the specified email address. Verify that the mailbox exists, the SMTP address is correct, and the account has the required permissions. For Office 365, confirm that the destination mailbox is provisioned and has an appropriate license. Also check mailbox mapping, directory synchronization, and address-book visibility where applicable. After correcting the configuration, reconnect through EdbMails and retry the migration.

A TLS version mismatch can prevent EdbMails from establishing a secure connection to Exchange Server. Verify that the migration computer and Exchange Server support compatible TLS versions, preferably TLS 1.2 or later where supported. Check the Windows and Exchange security settings, certificates, and enabled protocols. If changes are required, apply them according to your server's supported configuration before reconnecting through EdbMails.

First, check the message size limits configured on the source and destination Exchange servers. Also verify network stability, Exchange throttling settings, and connection timeouts. If the problem is caused by a timeout, an Exchange administrator can review the applicable server settings. After resolving the restriction, retry the migration in EdbMails.

EdbMails can perform the migration from workstations (not just servers). However, to automatically create mailboxes during migration, you must install the EdbMails application on the target Exchange server and perform the migration from there.

Please follow the below steps to EdbMails create mailboxes on target Exchange server during migration

• Step 1: While mapping the Source and Target server mailboxes, select 'Automatically create mailboxes on my target server and map source mailboxes accordingly' option

  

• Step 2: Click on ‘Export Source Mailbox details to CSV File’

  

• Step 3: Use One of the methods to export the Mailbox details.
  • You can export mailbox details automatically by clicking ‘Export Mailbox Details to .CSV’ or manually using PowerShell commands.
  • The exported CSV file contains user information needed for mailbox creation on the target server.
  • You can edit the CSV to update UPN, passwords, or remove unnecessary entries.
  • Once prepared, proceed with the migration using this file.

    

• Step 4: Click ‘Create Mailboxes on the Target Server’ and upload the newly created .CSV file and proceed with the next process.

  

You can run EdbMails demo / trial version for a quick test / review using 2 easy steps:

Step 1: Download and install the EdbMails application
Step 2: Click the "Start Your Free Trial" button as shown in the below screenshot

Yes, EdbMails Exchange Migration offers a free trial version that allows you to explore and test all the features before purchasing. You can preview all the mail items and even perform limited migrations to evaluate the software’s capabilities. This helps ensure that the tool meets your requirements before making a commitment.

If you encounter any issues during the Exchange Server migration, we recommend checking the FAQs section first, which addresses many common queries and troubleshooting steps.

For further assistance, you can reach out to our 24x7 Technical Support Team via Email, Live Chat, or Phone. Our experts are available to help you resolve any technical problems and ensure a smooth migration experience.

The free trial version allows you to explore all features of EdbMails Exchange Migration. You can preview all mailbox items and perform limited data migration (30 items per folder), which helps you evaluate the tool before purchasing the full license.

No, you can access the EdbMails free trial without providing any payment information. Simply download and install the application to start evaluating the features.

EdbMails does not require a separate license key. After purchasing a license, your account is automatically upgraded according to the license type. Simply download and install the EdbMails software, then log in using your registered email address and password to start using the software immediately.

EdbMails counts only the source mailboxes that are actually being migrated. For example, if you migrate the following mailboxes:

• User1@source.onmicrosoft.com
• User2@source.onmicrosoft.com
• User3@source.onmicrosoft.com

Even if these mailboxes are migrated multiple times to different destination mailboxes or domains, EdbMails will only count 3 mailboxes towards your license.

You can easily view the number of mailboxes already in use. Click here to know more.

EdbMails is licensed per mailbox for Exchange Server migration.

For example, if you purchase a license for 100 mailboxes and initially migrate only 50, you can use the remaining 50 licenses at any time in the future to migrate additional mailboxes from the source server. The unused licenses remain valid until all are consumed.

The EdbMails Live Exchange migration license is based on the number of mailboxes you wish to migrate. For example, if you need to migrate 200 mailboxes to a different domain, you would need a 200-mailbox license. This license allows you to migrate the same mailboxes repeatedly for a lifetime, without needing additional licenses.

Yes, the license includes the migration of Contacts, Calendar items, Public Folders, and Archive Mailboxes as part of the Exchange migration process.

No, a separate license is not required. The EdbMails migration license includes support for migrating Contacts, Calendars, Tasks, Emails, Public Folders, and Archive Mailboxes as part of your mailbox license.

Yes. You can reuse the license for the same mailbox for a lifetime. This means you can migrate the same mailbox any number of times to any destination server or domain without needing to purchase additional licenses.

Yes, you can easily purchase additional licenses for more mailboxes at any time after your initial purchase.

Navigate to the 'General' tab from the left pane of the Exchange Server Migration window, then click the 'License Usage' tab as shown in the screenshot below:

You'll find a list of mailboxes already utilized for migration along with the count of total purchased and used mailbox licenses.

Furthermore, you can use the search bar to locate a specific mailbox and check if it has been used for migration.

EdbMails can migrate emails, journals, tasks, calendars, contacts, notes, public folders, archive mailboxes, and mailbox permissions from the source server to the target Live Exchange server.

You can install the EdbMails Exchange Migration tool on any computer (server or client machine) that has network access to both the source and destination Exchange servers.

For Instance: Your source Inbox folder is named 'Boîte de réception', which is in French language. If you migrate this folder directly to the destination server then by default it will not get mapped to the 'Inbox' folder on the target server. In order to map this to the respective folder, there are two methods

Method 1: Change the regional settings on Office 365 target server to that of your source mailbox folder language (in this case, it is French).

For Office 365:

Click here to know the steps to change the language and regional settings

For Exchange Server:

Click here to know the steps to change the language and regional settings

Method 2: Manually select and map specific target folders during the migration process. For instance, you can choose to select the 'Inbox' folder on your target server and migrate the corresponding 'Inbox' folder from the source to it.

Click here for the steps to manually select and map the specific target mailbox folder

EdbMails supports migrating encrypted emails available in the source Exchange mailbox, subject to the encryption method and destination compatibility. However, accessing encrypted content after migration may require the original certificates, encryption keys, or appropriate permissions. Administrators should verify encrypted email accessibility in the destination mailbox after migration.

Yes. EdbMails Exchange migration tool automatically maps source mailboxes to required target mailboxes.

No, EdbMails does not alter any data on the source server. It only reads the data from the source server and migrates it to the target server without making any changes to the original data.

In some cases especially in cross forest migrations all the target server mailboxes may not get listed. For this, you have to generate a .csv file containing all the mailboxes in the server and import it to the application. Execute the below Exchange Management Shell (EMS) commands to generate the CSV file.

Command: Copy & Paste it on EMS & change CSV file path

Get-Mailbox -ResultSize Unlimited | Select-Object PrimarySmtpAddress, DisplayName | export-csv "C:\Mailbox_Names.csv"

Result

Yes, to verify the already migrated data, EdbMails stores certain metadata (not the entire mailbox content) on your computer in an encrypted format. These metadata details are used during the incremental migration check. Therefore, after migrating a mailbox from a specific computer, it's essential to use the same computer for subsequent migrations to avoid duplicates. However, other mailboxes not migrated from this computer can be migrated from any other computer in parallel.

Yes, EdbMails allows you to manually map source mailbox folders to specific target mailbox folders during the migration process. This feature ensures that your data is migrated to the correct folder in the target mailbox.

 Steps to perform Live Exchange Migration

Yes, EdbMails allows migration of archived mailboxes along with regular mailboxes, ensuring no data is missed during the migration.

Yes, you can select multiple mailboxes from the source server and migrate them simultaneously to the target server.

Click here to know the steps to recreate Outlook profiles after migration

Yes, you can continue using the source mailboxes after migration. EdbMails does not alter the contents of the source mailboxes in any way. This ensures that the source mailboxes remain fully functional even after the migration process is complete.

EdbMails supports incremental migration to process eligible new or modified mailbox items after the initial migration. Run the migration again using the same source and destination configuration and retain the existing migration metadata. EdbMails uses this information to identify previously migrated items and reduce duplicate migration. You can also use date filters when required.

  Refer to the EdbMails Incremental Migration Guide.

You can verify by logging into the target mailboxes, checking folder structures, email counts, calendars, contacts, and comparing them with the source mailbox.

No. It is recommended to wait until you fully verify the migrated data, mail flow, and Outlook connectivity before decommissioning the old server.

First, review the EdbMails migration log and verify that the missing items are present in the source mailbox. Check the mailbox mapping, selected folders, filters, and destination mailbox limits. After correcting any issues, rerun the migration for the affected mailbox or folders. EdbMails incremental migration can help process eligible items without unnecessarily migrating previously processed data again.