IMAP and POP3 Migration FAQs

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

No separate license key is required. After purchase, sign in to EdbMails with the account used for the order and the application activates the purchased mailbox entitlement associated with that account.

Use the dedicated IMAP to Office 365 migration guide for planning, prerequisites, source connection, Microsoft 365 authentication, mailbox mapping, migration, and cutover verification.

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 availability, the provider's authentication method, network access, and any service-specific connection limits.

Collect the IMAP host name, port, TLS/SSL requirement, email address, and provider-supported authentication method. IMAP must be available for the mailbox, except where the provider manages it automatically. For Gmail personal accounts, Google no longer exposes a manual Enable/Disable IMAP switch; use the provider-supported sign-in method and current account policy.

See IMAP connection guidance.

Open the EdbMails application and use the General / License Usage area for the IMAP migration project. It shows purchased mailbox entitlement and the mailboxes already counted as used. Use the search option to check a specific mailbox where available in the current application build.

Yes. You can deselect folders from the mailbox tree and use the IMAP migration settings to exclude standard or custom folders and apply supported message filters. Review the selected exclusions before migration because default exclusions may not match every project.

Use the License Usage area in EdbMails to review mailboxes that have already been counted for the purchased migration license. The exact navigation can vary by application build, so use the current General/License Usage view rather than relying on Office 365-specific wording.

Review the migration or export report first. Check the source host name, port, TLS setting, authentication method, target permissions, mailbox mapping, provider throttling, message-size limits, and network connectivity. Retry only the mailboxes or items that require attention.

If the issue continues, contact EdbMails 24/7 technical support.

EdbMails runs in your environment rather than using EdbMails servers as a staging location for mailbox content. Network connections use TLS where supported. Authentication depends on the selected provider and workflow; Microsoft 365 target connections use the current EdbMails modern-authentication method, while source IMAP authentication varies by provider. See the EdbMails security page for current security and compliance information.

Standard IMAP migration is primarily for email messages, attachments, mail folders, folder hierarchy, and common message properties exposed by the source and accepted by the target. Contacts, calendars, tasks, rules, and other non-mail workloads require a separate provider-specific or application-specific workflow.

Yes. EdbMails processes 10 mailboxes concurrently by default and can be configured up to 20 where the source provider, target service, network, migration computer, and license scope can support it. More concurrency does not override provider throttling or connection limits.

Yes. After the initial pass, supported migration scenarios can process eligible new or changed email items in follow-up runs. This is useful for staged migrations before final cutover. Incremental migration is not a continuous two-way synchronization service.

No. Authentication varies by provider and account policy. Some services support OAuth or provider sign-in, while others may require a password or app password. For Google accounts, Google recommends Sign in with Google where available; app passwords are limited to certain 2-Step Verification configurations and may be restricted by administrators.

IMAP provides server access to email folders and messages, while POP3 is a simpler retrieval protocol that primarily exposes the Inbox. If mail exists only in local client folders and not on the server, a server-based IMAP or POP migration cannot retrieve that local-only content.

Yes. Use the IMAP to PST export and backup workflow to create PST copies of supported IMAP email data. Review the current Outlook and Windows requirements and verify the resulting PST after export.