Supported platforms and system requirements

The tables below show the list of supported platforms and program's requirements necessary for its proper operation:

Software components
The program consists of two main components installed together:
  • CodeTwo MAPI Service - responsible for accessing source Exchange mailboxes via MAPI
  • CodeTwo Exchange Migration Administration Panel - for managing and performing migration
SOURCE server environment requirements
OS installation When migrating from Exchange Server, program can be installed either directly on the server machine or on any workstation in the source server environment. Installing directly on the source Exchange Server machine is recommended when migrating via MAPI but only under certain conditions (read why and check exceptions). In the case of migration only from IMAP source the software can be installed anywhere.
All 32 and 64 bit systems starting from Windows 7 / Windows Server 2008 R2 up to Windows 10 / Windows Server 2012 R2 are supported. Installing the software on older systems (Windows Vista / Windows Server 2008 / SBS 2008) is not recommended, while installing on legacy systems (Windows XP / Windows Server 2003 / SBS 2003) is not possible at all - you need to use a separate workstation with a newer Windows version.
Hardware There are no specific hardware requirements for the software to run, however migration bottlenecks may occur due old or slow equipment. For the best software performance we recommend that you use at least a quad-core CPU and 4GB of RAM. Be aware, aside from that and Internet connection speed, migration may also be affected by the performance of your LAN hardware such as modem, router, switch and Ethernet card. Read more here.
Source Exchange Server
Installation, operation and service account rights

The software user:

  • must be a Local Administrator
  • must have a valid, working, non-hidden mailbox in the source environment

additionally, the user must be a member of the appropriate group depending on the source Exchange Server version:

  • Organization Management (Exchange 2010, 2013)
  • Exchange Organization Administrators (Exchange 2007)
  • Domain Admins (Exchange 2003)

Public Folders migration requires full access permissions, see details.

IMAP migration requires user's account credentials.

Additional components

Depending on the environment, the installation of the below listed components might be required:

  • One of the Windows Management Framework Core components
  • .NET 4.0 or higher (required on all systems, might be already installed)
  • MAPI Client and Collaboration Data Objects (MAPI CDO, required on any system except for ones equipped with x86 version of Outlook older than 2016) 


    MAPI CDO is required only for MAPI migrations.

    Additionally, if your machine is equipped with x86 version of Outlook older than 2016 the installation is still possible but strongly not recommended, as the MAPI CDO component could not be installed due to conflict with MAPI libraries provided by Outlook. Be advised that high percentage of your items might be considered a corrupted or the migration may turn out impossible because of authentication error.

If so, the software will display appropriate message.

TARGET server environment requirements
Target Exchange Server Only migration to the same (starting from Exchange 2010 SP2) or higher version of Exchange Server is supported. Other restrictions may apply depending on the migration scenario, see details.
  • Exchange Server 2016
  • Exchange Server 2013
  • Exchange Server 2010
  • Small Business Server 2011

Looking for migration to Office 365?

Service account rights

To connect and migrate, credentials to target Exchange Server are required. Such an account:

See our KB for Role Based Access Control (RBAC) compliance.

See also Notes and warnings below.

Items supported for migration The program supports migration of all standard Exchange Server mailbox items as well as Exchange Public Folders items via MAPI and emails only via IMAP.
Notes and warnings The program cannot be installed on a machine equipped Outlook 2016 or with the following 64-bit versions of Outlook: 2010, 2013, 2016.
The program may not work properly if installed alongside other applications that use MAPI libraries. Install CodeTwo software on another machine, do not share service account with, and preferably disable other MAPI-using programs while migration is in progress, to avoid conflicts.
The program migrates mailboxes' and Public Folders' contents only. Mailboxes' properties, permissions, AD accounts, AD groups membership, GAL, etc. are NOT migrated, however, you can set the program to create mailboxes automatically and migrate desired AD propertiesBe advised, some of mentioned properties are recreated automatically by target server upon successful migration e.g. free/busy
Migration of Public Folders is possible only if target Public Folders were already created (see how to do this)..
Migration of linked mailboxes and resource mailboxes (such as conference rooms) is currently not supported.
Migration of shared mailboxes is possible, however, be aware that All Users and other group filters do not list disabled users (to which shared mailboxes are assigned) so you need to either pick them manually using Active Directory User filter or enabled those users' accounts in the AD. Migration TO shared mailboxes works.
Hybrid setup support Hybrid as a source: Migrating from a hybrid environment is possible for accounts that have mailboxes in on-premises Exchange only. Source server connection must use account that has mailbox in on-premises Exchange too. Be aware, the newest on-prem Exchange Server you can migrate from is 2013.
Hybrid as a target: Migrating to a hybrid environment is supported providing you use CodeTwo Exchange Migration to migrate to mailboxes located in on-premises Exchange (target server connection must use on-premises admin account) and CodeTwo Office 365 Migration to migrate to mailboxes located in Exchange Online (target server connection must use Office 365 admin account).
ADFS is not yet supported. Single Sign On (SSO)-enabled accounts may be used for target server connection configuration but only when a UPN in a non-federated target domain address is used (e.g. *

See also

Installation process - this article describes step-by-step how to install the program.

Was this information useful?