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 Office 365 Data Provider Service - responsible for accessing source Exchange mailboxes via MAPI
  • CodeTwo Office 365 Migration Administration Panel - for managing and performing migrations
SOURCE server environment requirements
Where to install 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, 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- 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.
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.
Migration source
  • Office 365 (*)
  • Exchange Server 2016
  • Exchange Server 2013
  • Exchange Server 2010 SP2
  • Exchange Server 2007 SP3
  • Exchange Server 2003
  • Windows Small Business Server (2008 and later)
  • all other mail servers, e.g. Gmail (access via IMAP)

(*) Source Office 365 requirements:

  • Office 365 Plans with Exchange Online.
Required accounts and permissions

General

The software user must be a local administrator.

Connection to source Exchange via MAPI

An admin account used to connect to a source server via MAPI:

  • must have a valid, working, non-hidden mailbox in the source environment,
  • must be a member of an appropriate AD group, depending on the source Exchange Server version:
    • Organization Management (Exchange 2013, 2010)
    • Exchange Organization Administrators (Exchange 2007)
    • Domain Admins (Exchange 2003).

Important

Migration of public folders requires full access permissions, see details.

Connection to source Exchange via EWS

An admin account used to connect to a source server via EWS:

  • must have a valid, working, non-hidden mailbox in the source environment,
  • must have a UPN address configured,
  • must have 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 Office 365 (via EWS)

Source Office 365 account credentials are required. Such an account:

  • must have a UPN address configured,
  • must have the following roles assigned:
    • ApplicationImpersonation
    • View-Only Recipients
    • View-Only Configuration

      Info

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

  • must be mailbox-enabled.

Learn more about the management roles.

IMAP migration requires users' account credentials. Learn more

Additional components

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
  • Office 365 Plans with Exchange Online

Looking for migration to Exchange Server 2016?

Admin account rights

To connect and migrate, target Office 365 account credentials are required. Such an account:

  • must have a UPN address configured,
  • must have the following roles assigned:
    • ApplicationImpersonation
    • View-Only Recipients
    • View-Only Configuration
    • Public Folders (*)
    • User management administrator/Global administrator (*)

      Info

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

  • must be mailbox-enabled.

(*) 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.

Learn more about the management roles.

See also: Notes and warnings in the table below.

Other
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 other 64-bit versions of Outlook (2010, 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 propertiesBe advised, some of 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).
Multi-factor authentication (MFA) is currently not supported. Be sure to disable MFA for the used admin account when creating a connection to the source/target Office 365 server. Read more about managing multi-factor authentication for Office 365 users.
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.
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. 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).

See also

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

Was this information useful?