Supported Platforms and System Requirements

Recommended for production: Use a currently supported Windows version with the latest applicable security updates and confirm that it is supported by the EdbMails release you are installing.

The existing EdbMails compatibility list includes 32-bit and 64-bit Windows environments such as Windows 7, Windows 8, Windows 10, Windows 11, and Windows Server releases from 2003 through 2022. Several of these operating systems are now legacy Microsoft platforms.

Legacy compatibility: If you plan to use an older Windows or Windows Server release, verify compatibility with the current EdbMails build and any required Microsoft framework/browser components before using it for a production migration.

No specialized hardware is required. However, CPU, memory, storage, and network capacity can affect migration performance, especially when processing large mailboxes or multiple mailboxes concurrently.

• CPU: A quad-core processor or better is recommended for stronger migration performance.
• Memory: 4 GB RAM or more is recommended; larger workloads may benefit from additional memory.
• Storage: Provide enough free local space for installation components, logs, configuration, and incremental-check metadata.
• Network: Use a stable, reliable connection. Internet quality, routing, switching, and endpoint connectivity can affect migration throughput.

Allow approximately 100 MB of local disk space for installation and supporting components where applicable, plus additional free space for logs, configuration, and metadata.

• EdbMails does not use the local disk as a staging location for mailbox data being migrated.
• Local storage is still used for application files, logs, configuration, and metadata required for incremental migration checks.
• If you export mailbox data to PST, provide enough disk space for the resulting PST files.

Depending on the Windows environment and EdbMails release, make sure the required supporting components are available.

• Microsoft .NET Framework 4.6.2 or later where required.
• Windows PowerShell 3.0 or the version required by the installed EdbMails release.
• A modern web browser such as Microsoft Edge, Google Chrome, or Mozilla Firefox for authentication and related web-based tasks.
• Microsoft Outlook is required only when the selected workflow exports mailbox data to PST through Outlook-dependent functionality; it is not required for direct Microsoft 365 or Exchange migration.

The application can notify you when required supporting components are missing.

• Internet connectivity is required for Microsoft 365 authentication, licensing checks, and Microsoft 365 mailbox migration.
• The EdbMails workstation must be able to connect to the selected source environment.
• The workstation must also be able to connect to the selected target environment.
• Use a stable connection for the duration of migration; throughput and latency can affect performance.

• Confirm that required Microsoft 365 and source/target hostnames resolve correctly through DNS.
• Allow the outbound HTTPS/TLS connectivity required by the source, target, and Microsoft 365 authentication endpoints.
• If the organization uses an authenticated proxy, confirm that the EdbMails workstation can use the required connection path.
• Check whether endpoint protection, web filtering, or firewall policy is blocking the application or its required connections.
• Test source and target connectivity before starting a large migration batch.

Use a mailbox-enabled Microsoft 365 account with the permissions required for the selected migration scenario. The current EdbMails connection workflow may use roles such as:

• View-Only Recipients
• View-Only Configuration

If required roles are missing, EdbMails may attempt to assign supported roles automatically, depending on the connection method and privileges available to the signed-in account.

Provide an appropriate target Microsoft 365 account and the permissions required for the destination workload. Do not assume that every migration requires the same administrator role set.

• Target mailboxes should be provisioned and licensed where the selected scenario requires licensed user mailboxes.
• Public-folder migrations require the additional access needed for the destination public-folder hierarchy.
• Shared mailbox and archive mailbox scenarios may require additional target preparation.

Microsoft 365 connections use modern authentication. Some environments may require manual EdbMails application registration in Microsoft Entra ID, and Microsoft 365 connections are compatible with multi-factor authentication (MFA).

 See how to manually register the EdbMails app in Microsoft Entra ID.

Required permissions vary by source, target, and workload. Validate the specific connection method before starting production migration.

EdbMails supports standard mailbox data and, where supported by the connected platform, public folders, archive mailboxes, and shared mailboxes. For hosted Exchange connections, supported workloads depend on the provider and connection method. IMAP migrations are limited to email data available through IMAP.

Mailbox migration does not automatically reproduce every directory or service configuration. Items such as Active Directory accounts, group memberships, GAL entries, mailbox properties, and certain permissions are not migrated by default. Where supported, EdbMails provides separate options for mailbox creation or selected directory properties.

EdbMails supports migration of emails protected with Microsoft 365 Message Encryption (OME) and emails that carry sensitivity labels without decrypting them. In cross-tenant scenarios, the destination user may not be able to open protected content if the original protection policy does not grant access in the target tenant.

Confirm that the required target public-folder structure and administrator permissions are prepared before migration. The destination administrator should have the access required to write to the target public folders.

 Review the public folder migration guide.

Shared mailbox migration is supported. If disabled directory accounts associated with shared mailboxes are hidden by the current user filter, select the required accounts manually or prepare the source directory as needed.

 Guide for shared mailbox migration.

Archive mailbox migration is supported. Ensure the target archive mailbox is enabled before migration. Large archive migrations may require additional Microsoft 365 archive capacity or provisioning time, so confirm the target archive configuration before starting.

 Guide for archive mailbox migration.

If the environment uses Microsoft Entra Connect or another directory-synchronization workflow, review how synchronized identities and attributes will be handled before migration.

 Review the directory synchronization guidance.