Frequently Asked Questions - CodeTwo Exchange Migration
Take a look at the list of frequently asked questions about CodeTwo Exchange Migration:
- Why do I need this product?
CodeTwo Exchange Migration takes the most grueling part of a server migration or upgrade – the move of users’ mailboxes and public folders – off your back. A configuration wizard guides you smoothly through the migration job setup and the Automatch feature pairs source and target mailboxes. After these steps, simply click Start and the program automatically performs a direct migration of the mailboxes you selected to the target environment (without deleting items on the source server side).
Our biggest advantages over the competition or tools provided by Microsoft are:
- direct migrations from any Exchange Server (including Small Business Servers) to Exchange 2019, 2016, 2013 or 2010 (no need for double-hop migrations or migrating data in batches);
- migrations from Office 365 organizations to on-premises environments;
- radically simplified migrations to new domains or forests;
- easy public folder migrations;
- different data filtering options (migrate only what you need);
- more control over IMAP migrations;
- intuitive user interface (no PowerShell skills required);
- competitive price.
See a full comparison of CodeTwo Exchange Migration vs Exchange native migration tools.
- Can I test CodeTwo Exchange Migration before buying it?
Yes, you can.
Unless activated with a paid license key, CodeTwo Exchange Migration is functional for 30 days, with the only limitation being that you can migrate a maximum of 10 items per folder. This means that if you’re using the program to migrate e.g. a user’s mailbox, only 10 emails from each mail folder, 10 calendar items from each calendar, 10 contacts from every contacts folder, etc., will be migrated.
Once you purchase the license and activate your copy of CodeTwo Exchange Migration, you can resume the migration and move all remaining items.
You can download the CodeTwo Exchange Migration installer here.
- How does CodeTwo Exchange Migration work?
The program performs Exchange-to-Exchange migrations by accessing your source server mailboxes via Exchange Web Services (EWS) or MAPI (used primarily for legacy versions of Exchange Server) in order to read their contents. Then, the selected data is copied to the target server mailboxes (this time only via EWS).
To connect to an on-premises Exchange server, the user operating the program needs to have certain management roles assigned. If any required role is missing, the program will help you assign them. To establish a connection with source Office 365 tenant, CodeTwo Exchange Migration is registered in that tenant’s Azure Active Directory. The registration can be performed automatically by the program (which is perfectly safe, as the program authenticates with your Office 365 tenant using OAuth 2.0 tokens), or you can decide to register the program by yourself (learn more).
During IMAP migrations, CodeTwo Exchange Migration reads data from email folders in source email accounts using the IMAP protocol, and then copies these folders and their contents to mailboxes on the target Exchange server.
It is necessary to have mailboxes prepared in the target environment prior to migration. If they are missing, you can automatically create them directly in the program. CodeTwo Exchange Migration can also automatically match source mailboxes with their target counterparts.
For more details on how the program works, see this article.
- Can I migrate from Office 365?
Yes, you can. CodeTwo Exchange Migration lets you migrate mailboxes and public folders from Office 365 to Exchange 2019, 2016, 2013 or 2010.
- Are migrations from G Suite, Zimbra and other non-Exchange platforms supported?
Yes, CodeTwo Exchange Migration supports migrations of emails from those and other servers, e.g. IBM Notes (formerly Lotus Notes), Zarafa or Kerio Connect via the IMAP protocol. Compared to IMAP migration tools provided by Microsoft, CodeTwo Exchange Migration gives you control over many more aspects of the process. For further details, see this page.
When migrating from IMAP servers, there are two limitations that you should be aware of:
- you can only migrate email folders (due to the IMAP protocol limitations),
- you have to provide credentials for all user accounts that you want to migrate.
- Are migrations from hosted Exchange environments supported?
Yes, they are.
To migrate from hosted (e.g. Rackspace) or other limited-access Exchange Server, the program uses the IMAP protocol to connect to the source server. Before the migration, make sure that IMAP4 is enabled on the source server, so that CodeTwo Exchange Migration can access source email folders and then replicate their contents in target mailboxes.
For further details see this page.
- Will the program migrate encrypted emails?
The program will migrate encrypted emails as regular emails, which will be then normally accessible on the target server. The email encryption configuration will not be migrated and it needs to be reconfigured after migration. All emails from the source server are copied “as such” to the destination server and look exactly as the original.
- Can the program migrate items between servers with different language versions?
Yes. CodeTwo Exchange Migration supports all languages, regardless of the language on the source and the target server. The software moves all special language characters so that all items can be migrated with no issues. Learn more in the user’s manual.
- Do I have to pay to get support?
No, technical support for this product is included in the license price. Our team can be reached via phone or email. When necessary, online sessions are performed to help resolve issues. You can find out more about our technical support program on this page.
Additionally, we have made technical documentation for CodeTwo Exchange Migration available online for all users:
- How is CodeTwo Exchange Migration licensed?
The application is licensed based on the number of source mailboxes you want to migrate. Each mailbox consumes 1 license once you start a migration job. To migrate public folders, you need to use up 25 licenses (this number is fixed; it does not matter how much data is contained in these folders).
For example, you purchased a 50-mailbox license and used our product to completely migrate 25 mailboxes and started migrating 10 more mailboxes. In this situation, you would have 15 seats left and could use them to migrate another 15 mailboxes from the source server.
Our licensing model also lets you use the remaining seats for a different migration project, e.g. migrate another source server.
For more on licensing, consult this article.
- Can I purchase additional licenses after my initial purchase?
Yes. You can do this by selecting the Additional licenses option in the first step of the online order form.
If you need to purchase additional licenses for your current 2.x or 1.x version of the program, we recommend purchasing a 3.x license key for as many additional mailboxes as you need. Upgrade your program to version 3.x (the upgrade is free of charge for version 2.x and version 1.x users) and migrate the remaining mailboxes.
- What type of data can be migrated using CodeTwo Exchange Migration?
To learn more on what type of data is supported for migration, see this section of the user's manual.
- Where do I install the program?
You can install CodeTwo Exchange Migration anywhere in your source server domain – even on a workstation. If you are migrating from Office 365, install the program on your target Exchange server.
- Are there any size or speed limits?
CodeTwo Exchange Migration does not impose any limits on mailbox or items size, or migration speed. It is, however, possible that your Exchange Server imposes its own limits, which our product will not be able to override. Refer to the articles linked below to find out how to check and modify native Exchange Server migration size and speed limits:
- How long does the migration process take?
Nowadays, an average migration speed is between 500 MB and 2 GB per hour. However, how long the entire migration process will take may depend on various factors.
The first thing to note is that our software does not affect the speed of the migration in any way. Environment-specific factors that can limit or increase this speed include the quality of your internet connection (in the case of a migration to a different network), your local router throttling, source and target server throttling, performance of the computers involved, etc.
- How is a direct migration from Exchange 2010 to 2019 possible?
Exchange Server 2019 does not support coexistence with Exchange Server 2010 (as well as with 2007 and 2003). This is Microsoft’s limitation (see this article for more). Therefore, only cross-forest migrations from Exchange 2003 to Exchange 2019 are possible.
Using only the tools provided by Microsoft, to go from Exchange 2010 to Exchange 2019, you would have to perform a double hop migration (i.e. update Exchange to 2013 or 2016, and then migrate to Exchange 2019). With CodeTwo Exchange Migration, this is not necessary, as the program can move mailboxes directly between any two Exchange Server editions. See this page to find out more.
- How do I prepare my environment for the migration?
The requirements vary depending on the server which will be acting as the source in your migration. In this user’s manual article you will find links to information about preparing for all available migration scenarios.
- Does the program support multi-factor authentication when migrating from Office 365?
Yes, it does. You can use your MFA enabled admin account when setting up a connection to the source Office 365 server.
- Can CodeTwo Exchange Migration auto-match source and target mailboxes?
Yes. CodeTwo Exchange Migration can match source and target mailboxes based on various predefined and custom attribute patterns. The default pattern will connect mailboxes based on users' names and display names. The program also allows you to match mailboxes manually. Learn more...
- How does the program create mailboxes on the target server?
If during the auto-matching process the program detects that any of the source mailboxes do not have their counterparts on the target server, it will propose creating these mailboxes based on a set of source mailbox data. You can modify this set using a range of mailbox properties. Learn more...
- Does CodeTwo Exchange Migration migrate public folders? How does this work?
Yes, CodeTwo Exchange Migration does migrate Exchange public folders. You just have to enable public folders on the target server (in the case of Exchange Server 2013/2016/2019, create a mailbox for them) and configure the program to include public folders in the migration. Our software will recreate the source server public folders tree on your target server and copy all items. In addition, the admin account used in the program to connect to the target Exchange server needs to be granted the Owner rights to all folders to which the data will be migrated (including the root public folder).
Additionally, bear in mind that migrating public folders reduces your CodeTwo Exchange Migration license by 25 users.
- Can I migrate public folders in the same Active Directory forest?
No, you cannot. Exchange Server does not let you create the second public folder infrastructure in the same AD forest. Because of that, CodeTwo Exchange Migration lets you migrate public folders in a cross-forest migration scenario only.
It is also not possible to migrate public folders in a hybrid environment because you cannot have public folders in both on-premises Exchange and Office 365 at the same time.
- Does the program migrate free/busy statuses?
Free/busy statuses are generated ad hoc by the Exchange Server Availability Service, based on the content of users' calendars.
CodeTwo Exchange Migration migrates users' mailboxes, including their calendars. This means that, provided you have created users' accounts in AD and did not limit free/busy permissions in any way, the Availability Service will automatically update the free/busy statuses.
- Does the program delete anything from the source server?
No, it doesn't. CodeTwo Exchange Migration accesses the source server data passively, which means that no data is deleted or modified on your source server.
- Can source mailboxes still be used after they have been migrated?
Yes, they can. The data on the source server is not modified in any way, so you can keep using the source mailboxes without any limitations. If you do so, and later on want to migrate the new items that have been created in the process, simply click the Rescan button and the program will update the mailboxes on the target server by copying these items.
- Help! Target server mailboxes addresses are not resolving and are not listed!
In some migration scenarios, such as a cross-domain migration, the target server email addresses may not resolve or be listed. In these cases, target mailboxes have to be selected manually by providing their addresses.
- Is it possible to migrate mailboxes within the same domain using your program?
Yes, provided that the User Principal Names (UPN) of the source and target mailboxes are not the same.
For example, it is not possible to migrate from server A to server B within the same domain, e.g. example.com, if both the source and target mailboxes are named email@example.com. In order to successfully carry out such a migration, you have to create a different mailbox for this user in the target location and name it differently, e.g. firstname.lastname@example.org.
Please note that other limitations still apply. Coexistence of Exchange 2003 and 2013/2016/2019, 2007 and 2016/2019 or 2010 and 2019 is not possible. Therefore, in this case a direct migration is only possible in a cross-forest scenario, which is fully supported by CodeTwo Exchange Migration.
- I am getting an error...
If you have encountered any problems with the application, follow the steps from Knowledge Base article about troubleshooting CodeTwo Exchange Migration.
If none of the suggestions from the article help, contact our Technical Support team.
We have also made all technical documentation for CodeTwo Exchange Migration available online for users. Use the below links to get to:
- How to upgrade to version 3.0?
In order to upgrade CodeTwo Exchange Migration to version 3.0, you need to follow the steps from this article.