Supported platforms and system requirements
|The program consists of two main components installed together:
|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, 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 XP SP3 / Windows Server 2003 R2 SP2 up to Windows 10 / Windows Server 2012 R2 are supported, however, using 64 bit CPU is strongly recommended, see why.|
|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:
additionally, the user must be a member of the appropriate group depending on the source Exchange Server version:
IMAP migration requires user's account credentials.
Depending on the environment, the installation of the below listed components might be required:
If so, the software will display appropriate message.
|TARGET Office 365 requirements|
|Target Office 365||
Looking for migration to Exchange Server 2016?
|Service account rights||
To connect and migrate, credentials to target Exchange Online 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 with 64 bit versions of Microsoft Outlook.|
|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, AD accounts, AD groups membership, GAL, etc. are NOT migrated. Be advised, some of those are recreated automatically by target server upon successful migration e.g. free/busy.|
|Migration is possible only if target mailboxes were already created. The same applies to Public Folders (see how to do this).|
|You must not use an account that has multi-factor authentication enabled in Office 365, this is currently not supported.|
|If you are working with AD synchronization tools e.g. Azure Active Directory Connect, Azure Active Directory Synchronization Services (AAD Sync), Azure Active Directory Synchronization Tool (DirSync), Forefront Identity Manager 2010 R2 (FIM) please refer to this Knowledge Base article prior to migration.|
|Migration of linked mailboxes is possible only if software is installed in the environment that hosts the source Exchange Server. Be aware that All Users and other group filters do not list disabled users (to which linked 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 mailboxes that happen to be linked, works.|
|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. *.onmicrosoft.com).|
Installation process - this article describes step-by-step how to install the program.