System requirements for Office 365 Migration

When migrating from Office 365, the program can be installed on any machine that can connect to both the source and target environments. While direct installation on the source Office 365 environment is possible, it is generally recommended only under specific conditions. The software ensures seamless migration from Office 365, hosted Exchange, or IMAP servers without the need for complex intermediary setups.

Please ensure you have the latest update of your Operating system.

• Supports both 32-bit and 64-bit machines.
• Windows 7
• Windows 8
• Windows 10
• Windows 11
• Windows Server 2003
• Windows Server 2008
• Windows Server 2008 R2
• Windows Server 2012
• Windows Server 2016
• Windows Server 2019
• Windows Server 2022

The software does not require specialized hardware to function. For optimal performance, a system with a quad-core processor and a minimum of 4 GB RAM is recommended. Migration speed may also be influenced by network conditions, including the performance of your modem, router, switch, Ethernet card, and overall internet connection.

Size of the installation file

• Installation of additional components (like .NET framework) requires 100 MB of available disk space
• The application doesn't store the data, which is being migrated to any temp location on your local disk.
• Meta-data for Incremental check. This will be of a very small size.
• EdbMails requires an Internet connection ONLY to authenticate your login credentials and the number of available and used mailbox licenses. In addition, you may require an Internet connection to migrate your Office 365 mailbox data.

Office 365 (Microsoft 365) plans that include Exchange Online, including F1 and Kiosk plans.

Connection to source Office 365

Source Office 365 account credentials are required.

• Must be mailbox-enabled

Must have the following roles assigned:

• View-Only Recipients
• View-Only Configuration

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

Important: Migration of public folders requires full access permissions

 See how to manually register the EdbMails app in Entra ID (Azure Active Directory).

Based on your environment, the following components may need to be installed:

• Microsoft .NET Framework 4.6.2 or higher (required on all systems)
• Windows PowerShell 3.0 (required on all systems)
• Microsoft Outlook, if exporting to PST

The software will notify you if any of these components are missing.

Additionally, EdbMails Office 365 Migration requires a modern web browser such as Microsoft Edge, Google Chrome, or Mozilla Firefox.

Migration to any version of Exchange Server starting from Exchange 2007 supported

• Office 365
• Exchange 2010
• Exchange 2013
• Exchange 2016
• Exchange 2019
• Windows Small Business Server (2008 and later)
• Hosted Exchange Server, e.g., Intermedia, Rackspace, or GoDaddy
• Other mail servers, including Google Workspace, IBM Notes, Zimbra, Zarafa, Kerio Connect, and any IMAP-accessible platforms.

Appropriate Office 365 account credentials should be provided for the connection.

Should be mailbox-enabled (An Office 365 license should be assigned)

The following roles should be assigned:

• View-Only Recipients
• View-Only Configuration
• User management administrator/Global administrator
• For the Public folder migration, the public folder needs to be assigned to the required user.

See how to manually register the EdbMails app in Entra ID (Azure Active Directory).

Hybrid Environment Migration

Source login:

• Exchange Server
• Office 365

Target Login:

• Office 365
• Exchange Server

The software allows migration of all standard mailbox and public folder items from Microsoft 365 to Exchange Server or other servers via EWS. For hosted Exchange servers (EWS connection), only mailboxes can be migrated, whereas for IMAP-accessible servers, migration is limited to emails.

• The software supports migration of emails secured with Microsoft 365 Message Encryption (OME) as well as emails marked with sensitivity labels. These emails retain their encryption and associated properties throughout the migration process.
• In cross-tenant migration scenarios, users in the destination Microsoft 365 tenant may not have permission to open OME-encrypted emails or emails labeled, for instance, as Confidential \ All Employees. This behavior is by design—encrypted emails are accessible only to the original intended recipients. EdbMails Microsoft 365 Migration does not decrypt these emails during migration, ensuring full security compliance.
• Microsoft 365 connections are fully compatible with multi-factor authentication (MFA).

• The software migrates mailbox, public folder, and archive mailbox data. However, certain elements such as mailbox properties, Active Directory accounts, group memberships, GAL entries, and permissions are not migrated by default. You can configure the program to automatically create mailboxes and migrate selected AD properties. Set the required permissions for the Admin user refer to this link
• Public folder migration is supported only if the target public folders already exist. Additionally, the administrator account used to connect to the destination Office 365 tenant must have Owner permissions on the root public folder and all subfolders where data will be migrated.
• If your environment uses Active Directory synchronization tools such as Microsoft Entra Connect (Azure AD Connect), Azure AD Sync, DirSync, or Forefront Identity Manager 2010 R2 (FIM), it is recommended to review the relevant Knowledge Base article before starting the migration.
• Shared mailbox migration is supported. Note that the "All Active Directory Users" filter does not automatically display disabled users who are assigned to shared mailboxes. To include these accounts, you must either select them manually using the Active Directory users filter or enable their accounts in AD. Migration to shared mailboxes proceeds smoothly once the appropriate users are selected.

  Guide for Shared mailbox migration

• Migration of archive mailboxes (In-Place Archives) is fully supported. Before starting, ensure that archive mailboxes are enabled on your target server. For archive mailboxes exceeding 100 GB, enable auto-expanding archiving to increase the storage capacity of the destination archive mailboxes.

  Guide for Archive mailbox migration

Important: As per Microsoft’s guidelines, it may take up to 30 days for Exchange Online to provision additional storage (an extra 100 GB) for archive mailboxes. Consequently, migrating archive mailboxes larger than 100 GB could take 30 days or longer, depending on the size of your source mailboxes.