IMAP to Exchange Migration FAQs

Download and install EdbMails, then choose Start Your Free Trial. The IMAP trial lets you migrate up to 30 items from each folder, which is suitable for testing a representative mailbox before a production migration.

No separate license key is required. Sign in with the account used for the purchase and EdbMails activates the purchased mailbox entitlement associated with that account.

Use the complete IMAP to Exchange Migration Tool and step-by-step guide for planning, source connection, target Exchange preparation, mapping, migration, verification, and cutover.

EdbMails supports standards-compliant IMAP environments and many common providers such as Gmail, Yahoo Mail, Outlook.com, Zoho Mail, Zimbra, cPanel, Rackspace, GoDaddy, IceWarp, and self-hosted IMAP systems. Connection success depends on IMAP access, provider authentication, network reachability, and service-specific limits.

Collect the source IMAP host name, port, TLS/SSL requirement, email address, and provider-supported authentication method. For Gmail or Google Workspace, use the authentication method allowed by the account policy; app passwords are only available in certain 2-Step Verification configurations.

Yes. Use the EdbMails bulk mailbox workflow and sample CSV to prepare multiple source IMAP accounts. Validate a small test set before loading the full production list.

Standard IMAP is primarily for supported email messages, attachments, mail folders, folder hierarchy, and common message properties. Contacts, calendars, tasks, and rules are not standard IMAP mailbox data and require a separate workflow.

Microsoft ended support for Exchange Server 2016 and 2019 on October 14, 2025. Exchange Server Subscription Edition (SE) is Microsoft's current supported on-premises release. For an existing legacy Exchange target, confirm both its support posture and current EdbMails compatibility before migration.

Yes. EdbMails supports folder selection and supported include/exclude filters. Review the IMAP migration filter settings before the production run.

Yes. EdbMails processes 10 mailboxes concurrently by default and can be configured up to 20 where source limits, Exchange capacity, bandwidth, and the migration computer permit. More concurrency does not override provider or server limits.

Users can generally continue working in the source mailbox during the data copy phase, but the final cutover can still require DNS, MX, Autodiscover, Outlook, or account changes. Plan and communicate the cutover rather than treating every migration as literally zero-downtime.

Review the migration report, verify representative folders, messages, attachments, and item counts on the target Exchange server, test client access and mail flow, and resolve failed or skipped items before decommissioning the source environment.