Frequently Asked Questions - CodeTwo Exchange Migration
Take a look at the list of Frequently Asked Questions for 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’ and public mailboxes - off your back. A pre-configuration wizard guides you through the setup and the Automatch feature pairs source and target mailboxes. After these steps you click Start and the program performs a direct migration of the mailboxes you selected (without deleting items on the source server side).
Our biggest advantages over competition and tools provided by Microsoft are:
- direct migrations from Exchange 2003, 2007 to Exchange 2010, 2013 (no stages required);
- radically simplified migrations to new domains or forests;
- easy public folder migrations;
- Extended control over IMAP migrations;
- intuitive user interface (no PowerShell skills required);
- competitive price.
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 it 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.
Later on, when 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 actually work?
The program performs Exchange-to-Exchange migrations by accessing your source server mailboxes to read their contents and copy items to the target server mailboxes. To achieve this, mailboxes on the target server side need to already exist and be active, and the user operating the program needs to have domain admin privileges on both the source and the target server.
During IMAP migrations, CodeTwo Exchange Migration reads data from email folders in source email accounts using the IMAP protocol, and then copies the email folders and their contents to mailboxes on the target server.
For more details on Exchange-to-Exchange and IMAP-to-Exchange migrations see the user manual.
Are migrations from Google Apps, 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) via the IMAP protocol. Compared to IMAP migration tools provided by Microsoft, CodeTwo Exchange Migration lets you control far more aspects of the process. For further details see this page.
Are migrations from hosted Exchange supported?
Yes, they are.
To migrate from hosted (e.g Rackspace) or other access-limited Exchange Server, the program uses IMAP protocol. Before migration, make sure that IMAP4 is enabled on the source server so that CodeTwo Exchange Migration can replicate email folders and their contents to the target server.
For further details see this page.
What are the limitations when migrating via IMAP?
The two limitations are that you can only migrate email folders and that you have to provide credentials for all user accounts that you want to migrate. For further details see this page.
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.
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 all technical documentation for CodeTwo Exchange Migration available online for users. Use the below links to get to the User’s Manual and Knowledge Base:
How is CodeTwo Exchange Migration licensed?
The application is licensed per migrated mailbox.
Suppose you purchased a 50 mailbox license and used our product to completely migrate 25 mailboxes and started migrating 10 mailboxes. In this situation you would have 15 seats left over and could use these seats to migrate any 15 mailboxes (private or public) from the 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.
How much does CodeTwo Exchange Migration cost?
The price of the program depends on the number of mailboxes you want to migrate. For a breakdown of license package prices go to this page.
CodeTwo Exchange Migration is highly scalable and can easily support organizations with 100,000+ mailboxes. If you are looking for a package for more than 1000 mailboxes, send us a quotation request via this form.
Where do I install the program?
You can install CodeTwo Exchange Migration anywhere in your source server domain – even on a workstation.
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, but it is very hard to say how long the whole process will take in your case.
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: 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 2003 to 2013 possible?
Exchange Server 2013 does not support coexistence with Exchange Server 2003. This is Microsoft’s limitation (see this TechNet article for more). Therefore, only cross-forest migrations from Exchange 2003 to Exchange 2013 are possible.
Using only the tools provided by Microsoft, to go from Exchange 2003 to Exchange 2013, you would have to perform a staged migration. With CodeTwo Exchange Migration this is not necessary, as the program can move mailboxes directly between the 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. On this userguide page you will find links to information about preparing for all available migration scenarios.
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 one looks at users' names and display names. The program also allows you to match mailboxes manually.
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.
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, 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.
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.
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 the new 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 migration, you would 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, or 2007 and 2016 is not possible. Therefore, in this case a direct migration is only possible in a cross-domain 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 no.286 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 the User’s Manual and Knowledge Base:
How to upgrade to version 2.0?
In order to upgrade CodeTwo Exchange Migration to version 2.0, you need to:
- Download a new version of the program from this website.
- If you have already started the migration process with version 1.0, stop it and close the program.
- Launch the installer and install the update on top of the existing version. The older version will be automatically detected and upgraded. All licensing info and settings will be kept. Your migration setting will be automatically converted into a migration job*.
- Open the program and resume the migration process using the Rescan button. As the program’s cache from the older version is kept during the upgrade, no duplicates in the target environment will be created.
All users who have a licensed version of CodeTwo Exchange Migration are free to perform the upgrade to version 2.0 at no additional cost.
* Migration job is a new feature added to the program that will help you better organize your migration process. Now you can group particular mailboxes into separate jobs and migrate them in batches. After upgrading to version 2.0, all mailboxes listed in the program will be automatically added to a newly created job with current settings preserved.
For more details on upgrading CodeTwo Exchange Migration please go to this website.