Program's components

CodeTwo Exchange Migration consists of the following components: Administration Panel and Data Provider Service. To provide you with maximum safety, there are no CodeTwo agents on the intermediary, third-party servers.

Administration Panel

As the name suggests, the Administration Panel is a command and control center of the software in the form of graphical user interface. However, it also runs a process that is responsible for migrating from IMAP sources and picking up data extracted by the Data Provider Service and sending it to the target server.

EWS Managed API libraries are used by the CodeTwo Exchange Migration Administration Panel to call EWS methods on the target Exchange Server, to access target mailboxes. Windows PowerShell is also used by CodeTwo Exchange Migration to connect to the target server. This is to check if the configured target server's admin account has application impersonation rights granted (if not, the software will do that on its own).

In order for CodeTwo Exchange Migration to perform migration jobs, you need to leave the Administration Panel open. 

The Administration Panel consists of two tabs: Dashboard and JOBS.

Dashboard

The Dashboard provides access to most of the configuration and monitoring options. There is no rocket science behind it, so let us keep its description short. To find out about specific features of the Dashboard and its usage, see this article.

JOBS

The JOBS tab provides access to jobs configuration and control, as well as reporting features.

Jobs are simply sets of migration configurations. If the source Exchange Server mailboxes are accessed via EWS or IMAP, the number of source Exchange Server connections is unlimited. When using the legacy MAPI protocol, you can only create one source connection. As for connections to target Exchange Server, it is possible to create multiple target connections in the program.

The program allows you to create multiple jobs. Several jobs can share a common source and/or target connection or each job may have an individual source/target connection configured.

Multiple jobs may come in handy, for example, when the old source server is about to become decommissioned, and the users are to be split and moved to two (or more) different environments. In this scenario, multiple jobs can be configured for different sets of mailboxes to be migrated to different target servers.

Another possible use could be a more complex scenario involving staged migration. For example, you want to migrate a few test mailboxes first. If that works, you will migrate newest emails and all contacts from all mailboxes first, then migrate the rest items from all mailboxes but in a certain order (e.g. mailboxes grouped by a company department). At the very end, you would like to rescan all the mailboxes on the old source server to make sure you did not miss a thing, etc. For all of those separate jobs can be configured instead of reconfiguring the existing migration settings.

CodeTwo Exchange Migration Data Provider Service

This is a Windows service responsible for accessing source Exchange Server mailboxes via the legacy MAPI protocol, extracting and preparing items for migration. The service is installed only when you configure a MAPI source connection.

Data Provider Service runs under the account the administrator configures in the program's source server connection. This account is used by the service to create a MAPI profile, which in turn is used to access source mailboxes. Using MAPI to access source mailboxes demands the software to be actually installed in the migration source domain. Meeting the software's specific user and service account requirements is necessary for MAPI to work.