Supported platforms and system requirements

Learn more about CodeTwo Office 365 Migration Administration Panel

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.

In the case of migration from Office 365 or a hosted Exchange server, the software can be installed on any machine that can connect to both the source and the target environment.

All 32-bit and 64-bit systems starting from Windows 10 / 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 Internet connection speed, migration may also be affected by the performance of your LAN hardware such as modem, router, switch and Ethernet card.

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. 

• Microsoft 365 (Office 365) plans with Exchange Online (including F1 and Kiosk plans)
• Exchange Server Subscription Edition (SE)
• Exchange Server 2019
• Exchange Server 2016 CU2
• Exchange Server 2013 CU13
• hosted Exchange servers (Exchange 2013 and newer), e.g. Intermedia, Rackspace or GoDaddy

General

The software user must be a local administrator.

Connection to source on-premises Exchange

An admin account used to connect to a source server must have:

• a valid, working, non-hidden mailbox in the source environment,
• a UPN (User Principal Name) configured. The UPN must be the same as this admin’s primary SMTP email address (note that these two values are case-sensitive),
• the following roles assigned:
  • ApplicationImpersonation
  • View-Only Configuration

    Info

    If any of these roles are missing, the software will attempt to assign them automatically. Learn more about the management roles

Connection to source Microsoft 365

You need to register CodeTwo Office 365 Migration in your source Microsoft Entra ID tenant to establish a connection between the program and Microsoft 365 (Exchange Online). The program needs to be granted the following application permissions in Entra ID:

Microsoft Graph:

• User.Read.All
• Directory.Read.All
• MailboxSettings.ReadWrite
• MailboxFolder.Read.Al
• Mail.ReadBasic.All
• MailboxItem.Export.All
• MailboxItem.Read.All

The registration can be done:

• automatically by the program – an account with the Global Administrator or Privileged Role Administrator role is required to perform the registration;
• manually – you will be asked to provide an email address of any user from your Office 365 tenant, together with some of the application registration details from Entra ID.

In both cases, the account whose credentials you provide in the program:

• must be assigned an Office 365 license that includes the Exchange Online plan,
• must have a UPN (User Principal Name) configured. The UPN must be the same as this account’s primary SMTP email address (note that these two values are case-sensitive).

Learn more about OAuth 2.0 authentication process

Connection to source hosted Exchange server

An admin account used to connect to a source hosted Exchange server must have:

• a valid, working, non-hidden mailbox in the source environment,
• a UPN (User Principal Name) configured. The UPN must be the same as this admin’s primary SMTP email address (note that these two values are case-sensitive),
• the ApplicationImpersonation role assigned (only for the mailboxes to be migrated).

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

• Microsoft .NET Framework 4.7.2 or higher, required on all systems,
• Windows PowerShell 3.0, required on all systems.

If so, the software will display an appropriate message.

In addition, CodeTwo Office 365 Migration requires a popular modern web browser, such as:

• Microsoft Edge,
• Google Chrome,
• Mozilla Firefox.

Microsoft 365 plans with Exchange Online (including F1 and Kiosk plans)

Looking for migration to Exchange Server Subscription Edition?

You need to register CodeTwo Office 365 Migration in your target Microsoft Entra ID tenant to establish a connection between the program and Microsoft 365 and to perform the migration. The program needs to be granted the following application permissions in Entra ID:

Microsoft Graph:

• User.ReadWrite.All
• Directory.ReadWrite.All
• Device.ReadWrite.All
• MailboxSettings.ReadWrite
• MailboxItem.ImportExport.All
• Mail.ReadWrite
• MailboxFolder.ReadWrite.All
• Mail.Send* 

The registration can be done:

• automatically by the program – an account with the Global Administrator or Privileged Role Administrator role is required to perform the registration; 
• manually – you will be asked to provide an email address of any user from your Office 365 tenant, together with some of the application registration details from Entra ID.

In both cases, the account whose credentials you provide in the program:

• must be assigned a Microsoft 365 license that includes the Exchange Online plan,
• must have a UPN (User Principal Name) configured. The UPN must be the same as this admin’s primary SMTP email address (note that these two values are case-sensitive).

Learn more about OAuth 2.0 authentication process

If you intend to migrate public folders, this account needs to meet some additional requirements. Refer to the Notes and warnings section below to learn more.

The program supports migration of all standard Exchange Server / Exchange Online (Microsoft 365) mailbox items and public folder items.

Only mailboxes can be migrated from hosted Exchange servers.

The program migrates emails encrypted using Microsoft 365 Message Encryption (OME) and emails with sensitivity labels. Such emails remain encrypted and retain their properties after the migration. In cross-tenant migration scenarios, users from the target Microsoft 365 tenant will not have sufficient permissions to open emails encrypted by OME or, for example, emails marked as Confidential \ All Employees. This is the expected behavior – for security reasons, encrypted emails can only be read by intended recipients (original recipients). CodeTwo Microsoft 365 Migration does not decrypt such emails during the migration.

Multi-factor authentication (MFA) is supported for Microsoft 365 connections. However, passkeys are not supported.

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/public

ocsp.godaddy.com
crl.godaddy.com

over 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 were already created (see how to do this). In addition, the admin account used to establish a connection with the target Office 365 tenant needs to be assigned the Owner permission level to the root public folder on that tenant and to all subfolders to which the data will be migrated.

Migration of public folders from hosted Exchange servers or by using a CSV file is not supported.

If you are working with AD synchronization tools e.g. Microsoft Entra Connect (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 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 from source on-premises Exchange environments – you can migrate them to primary Office 365 (Exchange Online) mailboxes. Support for archive mailbox migration from and to Office 365 will be available soon.

Recurring appointments and recurring tasks are migrated as series (not as single occurrences).

Migration of Microsoft 365 group mailboxes 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, both as a source and target of your migration. You need to have global admin rights to your Microsoft 365 tenant at GoDaddy. To learn how to migrate mailboxes from GoDaddy to Microsoft 365, see this article.

The program fully supports Microsoft 365 GCC, but Microsoft 365 GCC High and Microsoft 365 DoD environments are not supported.

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 Microsoft 365 mailboxes, you need to create a connection to Microsoft 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 Microsoft 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 Microsoft 365 admin account, also with appropriate roles assigned, as specified above).

Since public folders cannot reside in both Exchange on-premises and Microsoft 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).