IMAP Migration System Requirements and Supported Platforms
Before installing EdbMails for an IMAP migration or IMAP-to-PST backup project, verify the Windows environment, network access, target compatibility, authentication requirements, and local storage needed for the selected workflow. Product compatibility is different from Microsoft or provider lifecycle support, so use a currently supported operating system and mail platform where possible. For the commercial product overview and supported migration destinations, see the EdbMails IMAP Migration Tool.
The supported platforms and system requirements are listed in the below table.
- Install EdbMails on a Windows workstation or Windows Server system that can reach the source IMAP service and the selected destination.
- For IMAP to Microsoft 365, Exchange, or IMAP-to-IMAP migration, the computer must have network connectivity to both source and target during the operation.
- For IMAP to PST export, use a Windows environment that meets the current Outlook/PST requirements and has sufficient local storage for the output files.
- Physical systems, virtual machines, and cloud-hosted Windows environments can be used when they meet the application, network, and authentication requirements.
EdbMails may run on several Windows client and Windows Server releases. For a new production migration, use a Microsoft-supported and fully patched Windows release wherever possible.
- Windows 11
- Windows Server 2022 / 2025, where supported by the installed EdbMails build
- Legacy Windows releases may continue to work with specific EdbMails builds, but vendor support and security-update status must be reviewed before production use.
Lifecycle note: Standard Windows 10 support ended on October 14, 2025. Older releases such as Windows 7/8 and older Windows Server versions are also outside normal Microsoft support. Do not interpret legacy application compatibility as a recommendation to deploy an unsupported operating system.
Architecture: Use the Windows architecture supported by the EdbMails build and any required Outlook components. For PST workflows, keep Outlook and related components on compatible architecture.
- Baseline: Use at least a modern dual-core CPU and 4 GB RAM for a small test or light workload.
- Recommended for production: A quad-core CPU or better, 8 GB RAM or more, SSD storage, and stable network connectivity.
- Increase CPU, memory, storage, and bandwidth for larger mailbox batches or when using higher concurrency.
- Disk-space requirements include the application, logs, local metadata, and—when exporting to PST—the actual PST output and working space.
- The application installation footprint is separate from the disk space needed for logs, local migration metadata, and PST output.
- EdbMails does not stage complete mailbox data on its servers as part of the migration workflow. Minimal local metadata may be retained for migration tracking and incremental checks.
- Network or Internet access is required whenever the EdbMails computer must reach remote source or target services. A local on-premises source or target may use internal network connectivity instead.
- For PST export, provide enough free local storage for the expected PST files and additional working space.
IMAP to PST export requires the Outlook components specified by the current EdbMails build. Prefer a currently supported classic Outlook desktop environment for production PST work. Microsoft ended support for Office 2016 and Office 2019 on October 14, 2025, so older Outlook versions should not be treated as recommended simply because an application can still interact with them.
Verify the current EdbMails Outlook requirement before starting a large PST export, and keep Outlook and Windows fully patched.
Target Server Compatibility
- Microsoft 365: Exchange Online / Microsoft 365 plans that provide the required mailbox service, licensing, permissions, and authentication for the selected EdbMails workflow.
- IMAP servers: Standards-compliant IMAP services such as Gmail, Yahoo Mail, Zoho Mail, Zimbra, AOL, Yandex, IceWarp, cPanel, Dovecot, and other providers where IMAP access and a supported authentication method are available.
- Exchange Server: EdbMails can work with legacy Exchange targets listed by the product, but Microsoft support status varies by version. Exchange Server 2016 and 2019 reached end of support on October 14, 2025. For Exchange Server Subscription Edition, verify compatibility with the current EdbMails build before the production migration.
- Hosted Exchange: Compatibility depends on the provider's Exchange version, connectivity, permissions, and authentication method.
Important: A platform appearing in a legacy compatibility list does not mean the operating system or mail server is still supported by its vendor.
Security and Compliance
- EdbMails runs in your environment and does not use EdbMails servers as a staging location for mailbox content during the migration.
- Minimal local metadata may be stored for job tracking and incremental migration checks.
- Network connections use TLS where supported by the source and target service.
- Authentication depends on the selected provider and workflow. Microsoft 365 targets use the current EdbMails modern-authentication method; IMAP source authentication varies by provider.
For current security and compliance information, see the EdbMails security page.
