Program's components

The main component of CodeTwo Exchange Migration is the Administration Panel. To provide you with maximum safety, CodeTwo does not install any agents on intermediary or third-party servers.

The Administration Panel is the command and control center of the software and provides a graphical user interface.

EWS Managed API libraries are used by the CodeTwo Exchange Migration Administration Panel to call EWS methods on the source and target Exchange server, to access 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). The Microsoft Graph API is used to access source Office 365 (Exchange Online) mailboxes.

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. To learn more about the Dashboard and its features, see this article.

Jobs

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

Jobs are sets of migration configurations. The program allows you to create multiple jobs. You can also configure multiple source and target connections. Several jobs can share a common source and/or target connection, or each job can use its own source and target connections.

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

Important

Multiple jobs can be created and saved, but only one can be running at a given time.

Another possible use is a more complex scenario involving staged migration. For example, you might want to migrate a few test mailboxes first. If the test migration is successful, you can migrate the newest emails and all contacts from all mailboxes, and then migrate the remaining items in a specific order (e.g. by company department). Finally, you can rescan all mailboxes on the old source server to make sure no items were missed. You can configure separate jobs for each of these stages instead of reconfiguring an existing job.

Info

Jobs can be executed either automatically, using a built-in scheduler, or manually, if desired. The Administration Panel must be kept open for the Scheduler to work, though.