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 for Exchange Server Migration works by accessing all the mailboxes in your source server and migrates all the data to the destination server. EdbMails automatically maps the mailboxes between source and the target server. It automatically sets impersonation rights to the target Office 365 server.

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. If your organization is running Hosted Exchange services on Rackspace, Godaddy etc., and are in the need of migration then EdbMails can easily accomplish seamless migration.

EdbMails is a user-friendly and most reliable migration application compared to any competitors. EdbMails application is being used by users from more than 150 countries. EdbMails ensures no server downtime during migration, by keeping high performance under every scenario. Your migration data is 1:1 copy of the source, by retaining original folder structure intact.

EdbMails does complete migration and we ensures 100% data is migrated. In addition, it migrates Mailbox, Public folders and Folders permission as well. EdbMails migrations are safe and secured as it follows Microsoft recommended flow for migration.

For Instance:

Yes. EdbMails Live Exchange migration tool can migrate all your Public folder contents and its permissions to target server. All you have to do is create Public folder and assign users to this Public Folder on target Exchange Server, EdbMails will replicate the source server Public folder structure exactly as it is, on the target server.

For Exchange Server 2013 / 2016 / 2019

For Exchange Server 2010

Yes. You can migrate mailboxes within the same domain using EdbMails if the the UPN (user principal name) of the source and target mailboxes are different.

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 keeps certain metadata details (not the entire mailbox details) on your computer in encrypted format.

Yes. EdbMails provides extensive support for Non-English Unicode languages. This means that you can migrate your data between source and target servers irrespective of the language. It also ensures that all special characters are migrated to the target servers without anything being left out.

EdbMails for Exchange server migration doesn’t impose any restrictions on the size of the mailboxes / items that can be migrated or the speed of migration. Nevertheless, the target exchange server may have its own mailbox size restrictions and throttling policies that limit connection speed which EdbMails cannot override on its own.

It is not easy to predict the duration of migration process as it will vary significantly depending on a number of factors involved. Important thing is that EdbMails is a high-performance oriented migration tool which is designed to improve the migration speed. However, few factors such as the Internet speed, router capabilities, configuration of the computers involved, connection speed throttling in the source and target servers etc., can affect speed of migration.

For any queries, you can always contact our 24x7 Technical Support Team by Email, Live chat or on Phone.

Yes. As Microsoft doesn't support the direct migration of Exchange 2003, you need to take an EDB file from Exchange 2013 and migrate directly from offline EDB to latest Exchange versions.

Yes. EdbMails Exchange Server migration tool is compatible with Office 365 Multi Factor Authentication. You can migrate from your MFA enabled Office 365 account using the Microsoft app-password instead of normal password.

No. It is not possible as Exchange Server does not allow creation of more than one Public folder in the same Active Directory 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.

Resolution:

• Verify if you have entered the correct email address associated with the mailbox for login.

• Login to your Outlook Web Application (OWA).
• Compose a new email and type or paste the correct email address in the To field.
• Additionally check if the email address is present in the address book or maps to a user.

For Office 365 users, check if you have assigned a license to the admin account. After assigning a license from the admin center, you need to wait for sometime and then try entering the email address of the user and performing the migration.

If a new Office 365 account is created, then the specific user needs to login to their account or Outlook Web Application to activate their email address. The SMTP error must be resolved after activating the mailbox.

For Exchange server 2013
If you are using Exchange server 2013, install this cumulative update from Microsoft to resolve this error.

Other scenarios

In some cases, if a user is hidden from the address book, the email address of that user cannot be resolved. Additionally, if the address book has not been synchronized with the recently created users or mailboxes, you will receive the above error. Try unhiding the user from the address book or keeping your address book entries up to date with any new or removed users.

The TLS version may cause this issue. Ensure that you have enabled TLS 1.2 or higher version on your client (migration computer) as well as on On-premises server.

To verify and enable TLS version on your computer, follow the below steps:

• 1.  Download and install the tool using the below link
  https://www.nartac.com/Products/IISCrypto/Download
• 2.  Open IISCrypto.exe application.

  

• 3.  Under ‘Server Protocols’ and ‘Client Protocols’ select TLS 1.2. Refer the below screenshot.
  Note: By default TLS 1.2 is Grey selected. Click the TLS 1.2 and make it Black.

  

• 4.   Select the ‘Reboot’ option and click the ‘Apply’

Increase the connection timeout for data transfer. Follow the below steps.

• 1.   Start IIS manager (run - > inetmgr.exe)
• 2.   Select the Default Web Site
• 3.   Right click on the site and select Manage Website
• 4.   Select Advanced Settings -> expand Limits.
• 5.   Set 'Connection Time-out (seconds)' to greater than '120'.

Important Note: EdbMails can perform the migration by installing it on Workstations (not only server). However, if you want the mailboxes to be automatically created by EdbMails during migration then you must install the EdbMails application on your target Exchange server and perform the migration operation.

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, click the 'Create a New Mailbox in Target Server' option

  

• Step 2: Fill all the details and 'Continue'

  

• Step 3: Repeat the above steps for all the mailboxes that you wish to create automatically.

  Alternatively, you can use the below Exchange Management Shell (EMS) scripts and easily create the required mailboxes on target server

  • Step 1: Create a CSV file with the necessary columns for the mailbox attributes, such as DisplayName, FirstName, LastName, Alias, and UserPrincipalName. You can use a text editor or spreadsheet program to create the CSV file.

    Example of a CSV file that you could use to create mailboxes in Exchange Server:

    #DisplayName,FirstName,LastName,Alias,UserPrincipalName
    John Smith,John,Smith,johns,johns@contoso.com
    Jane Doe,Jane,Doe,janed,janed@contoso.com
    Bob Johnson,Bob,Johnson,bobj,bobj@contoso.com

    Each row in the CSV file represents a separate user, with the values for each column separated by a comma. You can customize the columns in your own CSV file to match the attributes you want to use when creating mailboxes in Exchange Server.

  • Step 2: Open the Exchange Management Shell (EMS) on the Exchange server.
  • Step 3: Use the Import-Csv cmdlet to import the CSV file into EMS. For example, if your CSV file is named "MailboxList.csv" and is located in the C:\Temp directory, you can run the following command:
    Command: Copy & Paste

    Import-Csv "C:\Temp\MailboxList.csv"

  • Step 4: Use the ForEach-Object cmdlet to loop through each row in the CSV file and create a mailbox for each user. You can use the New-Mailbox cmdlet to create the mailbox, and specify the mailbox attributes using the values in the CSV file. For example:
    Command: Copy & Paste

    Import-Csv "C:\Temp\MailboxList.csv" | ForEach-Object {
    New-Mailbox -Name $_.DisplayName -FirstName $_.FirstName -LastName $_.LastName -Alias $_.Alias -UserPrincipalName
    $_.UserPrincipalName -Database "Mailbox Database 01"
    }

    This command creates a mailbox for each user listed in the CSV file, using the specified mailbox attributes, and assigns the mailbox to the "Mailbox Database 01" database.

  • Step 5: Save the PowerShell script as a .ps1 file, for future use.

    That's it! By following these steps, you can create multiple mailboxes on an Exchange server using a CSV file.

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. 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

Demo / Free trial will migrate 30 items from each and every folder maintaining the exact source server folder hierarchy. You can Migrate 30 items from each and every folders from your Live Exchange server to other Live Exchange Server / Office 365.

This means that, if you’re using it to migrate e.g. a user’s mailbox, only 30 emails from each mail folder, 30 calendar items from each calendar, 30 contacts from every contacts folder, etc. will be migrated.

Later you can purchase the license for full version of Live Exchange Migration tool; you can resume the migration and move all remaining items incrementally.

For any queries / issues related to Exchange Server Migration, you can refer FAQs which answers most of the general questions / queries.

In addition, you can always contact our 24x7 Technical Support Team by Email, Live chat or on Phone.

EdbMails does not require any separate KEY to use the application after purchasing the license. That is, your account will be automatically upgraded to the type of the license that you have purchased. You need to download and install the application and login using the EdbMails account credentials (E-mail Address and password) that you have created during license purchase.

EdbMails only counts source mailboxes that are actually considered for migration.

For Instance:
User1@source.onmicrosoft.com
User2@source.onmicrosoft.com
User3@source.onmicrosoft.com

If you migrate above 3 mailboxes to any destination mailboxes (with different domains) for any number of times (for lifetime), EdbMails only counts number of mailboxes used as 3.

You can directly view number of mailboxes that are already used. Click here to know more

EdbMails is licensed per mailbox for Exchange Server migration.

For Instance, if you have purchased license for 100 mailboxes and migrate only 50, you can migrate the remaining 50 more items from the source server whenever you choose to.

Live Exchange migration license works based on how many mailboxes you want to migrate. That is, if you want to migrate 200 Mailboxes to a different domain then you just need 200 Mailboxes license. And you can use this license to migrate same mailboxes repeatedly for lifetime.

Yes. It will support Contact, Calendar, Task, Mail, Public Folders / Archive mailbox migration.

No. The migration license will support Contact, Calendar, Task, Mail, Public Folders / Archive mailbox migration.

Yes. You can reuse the license for the same mailbox for lifetime. That is, migrate the same mailbox any number of time repeatedly to any destination server / domain without buying any additional licenses.

Yes, you can easily purchase additional licenses for more mailboxes after the initial purchase. Click here to upgrade the license with additional mailboxes.

In the Exchange Migration screen, Click on the button 'Get Details'

You will be displayed with the list of Mailboxes that are already used for migration.

EdbMails can migrate all emails, journals, tasks, calendar, contacts, notes, public folder, archive folder, permissions from the source server to target Live exchange server.

You can install EdbMails Exchange Migration tool on any computer (server or client) that can access both the source and destination 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

Yes. EdbMails supports migration of all emails on the source server whether it is encrypted or regular. All the source server mailboxes are migrated “as is” to the target server.

Yes. EdbMails Exchange migration tool automatically maps source mailboxes to required target mailboxes. It also allows you to select appropriate source and target mailboxes during Exchange Server migration. For this, select the mailbox from the list of mailboxes/folders that are selected for migration and choose the target mailbox from the right pane as shown in the below screen.

No. EdbMails does not alter the data in the source server in anyway. It will read source server data and migrate it to target server.

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

To verify the already migrated data, EdbMails keeps certain metadata details (not the entire mailbox details) on your computer in encrypted format. These metadata details are used for incremental check during migration. Hence, once you migrate a mailbox from a particular computer, during consecutive migration use the same computer to avoid duplicates. However, other Mailboxes that are not being migrated from this computer can be migrated from any other computer in parallel.

Click here to know more on Incremental Migration

Absolutely! With EdbMails, you have the flexibility to manually map the source mailbox folders to specific target mailbox folders during the migration process. This feature allows you to precisely define the mapping and ensure that your data is migrated to the desired locations (folder) in the target mailbox.

Steps:

• Step 1: In the mapping window as shown in the below screenshot, click ‘Select the Target Mailbox from existing list’ 

  

• Step 2: Select the target mailbox and click the ‘List Target Mailbox Folder’ button 

  

• Step 3: Select the target mailbox folder and click ‘OK’ to proceed

  

• Step 4: Click ‘Continue’ to proceed with the migration

  

Steps to perform Live Exchange Migration

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

Yes. EdbMails does not alter the contents of source mailboxes in anyway and this ensures that you can keep using the source mailboxes as you normally would even after migration process. With EdbMails incremental migration, only the new items that are created in the source server after first full migration can be migrated to target server again without having to repeat the full migration.

EdbMails supports incremental migration wherein, it will only migrate the new items that are created in the source server after the first full migration without creating any duplicate data on target server.

In addition, to avoid complete re-scanning of the source mailboxes, you can apply the filter and include items based on your last migration date. You can access the include / exclude option under the 'Settings' menu as shown below.