Supported platforms and system requirements
The tables below show the program's requirements, necessary for its proper operation, and the list of supported platforms.
|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). If you intend to migrate data from Exchange 2010 without SP1, or use the MAPI protocol to connect to your source environment, these additional requirements apply.
In the case of migration from Office 365, a hosted Exchange server or an IMAP server, the software can be installed on any machine that can connect to both the source and the target environment.
|Supported operating systems||
All 32-bit and 64-bit systems starting from Windows 8 / Windows Server 2008 R2 SP1 up to Windows 11 / Windows Server 2022(*) are supported.
(*) If you are using Windows Server 2016, make sure your operating system includes the latest updates. Learn more
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 4 GB of RAM. Be aware, aside from that and the internet connection speed, migration may also be affected by the performance of your LAN hardware such as modem, router, switch and Ethernet card. Learn more
|Size on disk after installation||
Similar to the size of the installation file (see the Download page for details). Installation of additional components (such as .NET) might be required - these components usually require less than 100 MB of available disk space.
The program doesn't store the data being migrated at any intermediate location on your local disk.
|Internet connection||The program's licensing service requires an internet connection to retrieve information on the number of available and used licenses. For that reason, when migrating between two Exchange servers, make sure you can enable access to the Internet on your source machine.|
|Required accounts and permissions||
The software user must be a local administrator.
Connection to source Exchange via EWS
An admin account used to connect to a source server via EWS:
To be able to connect to your source server via EWS, make sure that you are running at least Exchange 2010 SP1.
Connection to source Office 365 (via EWS and Graph API)
You need to register CodeTwo Exchange Migration in your source Azure Active Directory tenant to establish a connection between the program and Office 365. The program needs to be granted the following application permissions in Azure AD:
The registration can be done:
Either way, in both cases the account which credentials you provide in the program needs to be assigned an Office 365 license that includes the Exchange Online plan.
Connection to source Exchange via MAPI
An admin account used to connect to a source server via MAPI:
Migration of public folders requires full access permissions, see details.
Connection to source hosted Exchange server via EWS
An admin account used to connect to a source hosted Exchange server via EWS:
IMAP migration requires users' account credentials. Learn more
Depending on the environment, the installation of the components listed below may be required:
If so, the software will display an appropriate message.
In addition, CodeTwo Exchange Migration requires a modern web browser, such as:
|TARGET server environment requirements|
You can migrate your data to any Microsoft Exchange Server listed below:
The version of the target Exchange server can be newer, the same or older than the version you are currently using.
Looking for migration to Office 365?
|Admin account rights||
An admin account used to connect a target server:
(*) Please note that the Public Folders role is only required if you plan to migrate public folders. Moreover, the Mail Recipient Creation and Mail Recipients roles are required to create new users and mailboxes. Therefore, it's not required to assign them 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 EWS and MAPI; only mailboxes can be migrated from hosted Exchange servers (EWS connection); only emails can be migrated from other servers (accessed via IMAP).|
|Multi-factor authentication (MFA) is fully supported for source Office 365 connections.|
|Notes and warnings||If you plan to access the source mailboxes via MAPI, you first need to uninstall Outlook 2019 and 2016 or 64-bit versions of Outlook 2013 and 2010 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.|
|If you're using both local and network-wide security systems like firewalls, proxies or other protection software, make sure to unlock access to the CodeTwo licensing service at the following URL:
https://licensing2.codetwo.com/publicAdditionally, to be able to receive the CodeTwo SSL certificate, you also need to unlock access to the following GoDaddy endpoints:
ocsp.godaddy.com crl.godaddy.comover ports 80 (HTTP) and 443 (HTTPS).
|The program migrates mailboxes' and public folders' contents only. The properties, permissions, AD accounts, AD groups membership, GAL, etc. of mailboxes or public folders 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. If you need more information on how to retain permissions to public folders after the migration, check out this article.|
|Migration of public folders is possible only if target public folders already exist (see how to create them). Migration of public folders from hosted Exchange servers is not supported.|
|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 the All Active Directory users filter does not list disabled users from the source server to which shared mailboxes are assigned. You need to either pick them manually using the Active Directory users filter or enable those users' accounts in AD. Migration to shared mailboxes is supported.|
|Migration of archive mailboxes (or In-Place Archives) is supported, but you need to enable them manually on your target server before the migration (see how to do this). To migrate archive mailboxes larger than 100 GB, you may need to increase storage quota of your target archive mailboxes as shown in this article.|
|Migration of Microsoft 365 group mailboxes is currently not supported.|
|Migration of IMAP flags is currently not supported.|
|Hidden system folders in Exchange mailboxes such as Recoverable Items or Sync Issues are not supported.|
|Microsoft 365 from GoDaddy (Office 365 from GoDaddy) is supported as a source your migration. You need to have global admin rights to your Microsoft 365 tenant at GoDaddy.|
|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, as specified above) 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).|
Since public folders cannot reside in both Exchange on-premises and Office 365 at the same time, migrating them within a hybrid environment requires special preparations, as described in this article.
You will also not be able to migrate public folders with the HoldForMigration parameter set. The Hold for migration switch blocks any client or user from accessing a public folder mailbox.
|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.