CodeTwo Exchange Migration
- Seamless migration to Exchange
2010, 2013, 2016 and 2019 - Used by 10k+ organizations from 170+ countries
- Ultra-secure (no 3rd party involved) »
Videos
Watch the video below to find out how the program works and how to effectively use it to perform migrations between various Exchange Server environments.
Screenshots
Take a look at the screenshots below. They show the user interface and main functionalities of the program.
This is the main window of CodeTwo Exchange Migration. From here, you can e.g. quickly navigate to all migration jobs, check the status of the migration process, or configure source and target connections by using server connection wizards.
You can connect to source Exchange via Exchange Web Services (EWS) or Messaging Application Program Interface (MAPI). The MAPI protocol is used to connect to legacy Exchange servers, such as Exchange 2010 without SP1.
While connecting to a target server, another connection wizard launches to guide you through the connection process.
In cross-forest Exchange migrations, the program connects to a target server using EWS. In this scenario, you need configure the EWS URL of the target server.
When connecting to on-premises Exchange, the program asks you to provide the UPN of an admin account that will be used to access your mailboxes. If this account lacks any permissions, the program will assign them automatically.
The program doesn’t store or use any credentials to connect to Office 365 (Microsoft 365). Instead, to establish the connection, CodeTwo Exchange Migration registers itself automatically in the Entra ID (Azure AD) of your source Office 365 tenant.
You will be asked to provide your Office 365 (Microsoft 365) global admin credentials on a dedicated Microsoft sign-in page and accept all permissions needed by the program to access your tenant and perform the migration.
Manual registration is also possible. In this case, you simply need to provide the ID of your tenant and other information regarding the registration process.
To connect to a source IMAP server, provide its address (or select it from the drop-down menu) and complete the remaining steps of the connection wizard.
The server connection wizard goes through a checklist to verify your connection and check whether the migration will run smoothly. It also suggests possible configuration changes or improvements.
The program lets you migrate to Exchange 2019 or 2016 from any version of Exchange Server (starting from Exchange 2010), Small Business Server 2011, Office 365 (Microsoft 365), and from servers supporting IMAP (e.g. Google Workspace, Zimbra or Zarafa).
This is a migration job configuration wizard which will help you create a new migration task. The first steps require to select mailboxes for migration.
The Mailbox types step is available when migrating data from Exchange server (on-premises or online) and allows you to select the types of mailboxes you want to migrate: primary, archive or both.
You have different options to choose from when adding mailboxes to your migration job. You can add e.g. all users, specific AD accounts, groups, OUs or use the Email address filter.
Once you have selected source mailboxes for migration, you can use the Automatch option to let CodeTwo Exchange Migration match them with mailboxes in your target organization.
You can use a predefined matching pattern or create your own custom algorithm based on some of the Active Directory attributes.
After the Automatch process completes, the Match mailboxes window displays a short summary with information about actions that will be performed once the migration starts. You can modify these actions before saving the settings.
You can generate a detailed report on the mailbox matching process to see, for example, which mailboxes could not be automatically matched.
The program lets you match source and target mailboxes manually if you decide not to use the Automatch option, if mailboxes could not be matched automatically, or if you wish to, e.g., migrate source primary mailboxes to target archive mailboxes (or vice versa).
You can also create primary mailboxes on your target server directly in the program. This is what the default settings of the Create target users/mailboxes wizard look like. You can modify these settings according to your needs.
The built-in scheduler lets you schedule when the migration is supposed to be automatically triggered during the week. It can also run automatic delta migrations.
The job creation wizard lets you filter migrated data as well. In the Time filter step, you can, for example, choose to move items from the last couple weeks or months only.
You don’t have to migrate folders like Junk Email or Deleted Items. By using the Folder filter option, you can easily exclude these and other unnecessary mailbox folders from the migration job.
In the Advanced settings step of the wizard, the administrator can decide e.g. how many mailboxes can be migrated at the same time.
Once you complete the migration job wizard, you can begin the migration right away or wait for the scheduler to start the process automatically.
If you want, you can enable email reports to receive information regarding the migration progress directly to your inbox. The program's built-in migration reports can be tailored to your needs.
If you want, you can create and view reports directly in the program. For example, the in-depth mailbox migration report shows the migration status for the selected mailbox only.
It is also possible to monitor the overall migration process by generating reports that contain information on all your migration jobs.
If you want to get more information about the migration process performed within a single job, you can generate the job migration report.
