Supported platforms and system requirements
|The program consists of two main components installed together:
|SOURCE server environment requirements|
|Where to install||When migrating from Exchange Server, the 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, but only under certain conditions (learn more and check exceptions). In the case of migration from an IMAP source or from Office 365, the software can be installed on any machine with a connection to both the source and the target environment.|
|Supported operating systems||
All 32-bit and 64-bit systems starting from Windows 7 / Windows Server 2008 R2 up to Windows 10 / Windows Server 2016(*) are supported. Installing the software on older systems (Windows Vista / Windows Server 2008 / SBS 2008) is also supported, but not recommended.
(*) Make sure your operating system includes the latest updates. Learn more.
|Hardware||There are no specific hardware requirements for the software to run; however, migration bottlenecks may occur due to 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.|
|Required accounts and permissions||
The software user must be a local administrator.
An admin account used to connect to a source server via EWS:
Source Office 365 account credentials are required. Such an account:
An admin account used to connect to a source server via MAPI:
Migration of public folders requires full access permissions, see details.
IMAP migration requires users' account credentials. Learn more
Multi-factor authentication (MFA) is supported. Be sure to use the app password instead of your regular password each time the program asks you to provide the credentials of any MFA-enabled Office 365 user. Learn more.
Depending on the environment, the installation of the below-listed components might be required:
If so, the software will display an appropriate message.
|TARGET Office 365 requirements|
|Target Office 365||
Looking for migration to Exchange Server 2016?
|Admin account rights||
(*) Please note that the Public Folders role is only required if you plan to migrate public folders. Moreover, the User management administrator/Global administrator role is required to create new users and mailboxes. Therefore, it's not required to assign it to the admin account if you are migrating data to the mailboxes that already exist on the target server.
See also: Notes and warnings in the table below.
|Items supported for migration||The program supports migration of all standard Exchange Server/Office 365 mailbox items and Exchange public folder items via MAPI and EWS; only emails can be migrated from other servers (accessed via IMAP).|
|Notes and warnings||If you plan to access the source mailboxes via MAPI, you first need to uninstall Outlook 2016 or 64-bit versions of Outlook 2010 and 2013 from your machine.|
|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 any other MAPI-using programs while migration is in progress, to avoid conflicts. Disabling such programs is recommended.|
|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 properties. Be advised, some of the mentioned properties are recreated automatically by target server upon successful migration e.g. free/busy statuses.|
|Migration of Public Folders is possible only if target Public Folders were already created (see how to do this).|
|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 and resource mailboxes (such as conference rooms) is currently not supported. However, there is a workaround that allows you to migrate resource mailboxes as regular mailboxes and then convert them back to a room or equipment mailbox. Learn more in our Knowledge Base article.|
|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.|
|Migration of archive mailboxes (or In-Place Archive in Office 365) is currently not supported.|
|Migration of IMAP flags is currently not supported.|
|The program does not support creating target mailboxes when migrating to Office 365 Germany.|
|Hybrid setup support||Hybrid as a source: Migrating from a hybrid environment is possible. To migrate your on-premises mailboxes, you need to create a connection to on-premises Exchange Server. To migrate your Office 365 mailboxes, you need to create a connection to Office 365. To migrate a hybrid environment you can, for example, create two migration jobs: one connecting to source on-premises mailboxes, and another connecting to source Office 365 mailboxes.|
|Hybrid as a target: Migrating to a hybrid environment is supported if you use CodeTwo Exchange Migration to migrate to mailboxes located in on-premises Exchange (target server connection must use on-premises admin account that has adequate roles assigned) and CodeTwo Office 365 Migration to migrate to mailboxes located in Exchange Online (target server connection must use Office 365 admin account, also with appropriate roles assigned, as specified above).|
|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.