IMAP and POP3 Migration FAQs

EdbMails IMAP migration transfers supported email data from an IMAP-enabled mailbox to another supported destination. You connect the source, prepare the target, choose the required mailboxes or folders and review mailbox mappings before starting. Use the destination-specific workflow for IMAP to IMAP, Microsoft 365, Exchange Server or PST export.

EdbMails supports standards-compliant IMAP environments and common providers such as Gmail, Yahoo Mail, Zoho Mail, Zimbra, cPanel, Rackspace and self-hosted IMAP servers. Compatibility depends on accessible IMAP services, supported authentication and provider limits. Check the supported platforms and test your exact source before migrating production data.

Standard IMAP migration covers supported messages, attachments, mail folders, folder hierarchy and common email properties available from the source and accepted by the destination. The scope is email-focused. Check a representative mailbox, including Sent items and custom folders, before assuming every provider-specific property will be retained.

These are not standard IMAP email workloads. Use a separate provider-specific or application-specific workflow for contacts, calendars, tasks and rules. If your project includes these items, identify their source and destination before starting; successful email migration alone does not confirm that the complete user account has been transferred.

Collect the source host name, port, TLS/SSL requirement, mailbox address and provider-supported authentication method. IMAP over TLS commonly uses port 993, but use your provider published settings. Also prepare destination mailbox access and enough capacity. Follow the EdbMails IMAP connection guide and test one account first.

Use the method supported by both the provider and the selected EdbMails connection workflow. Depending on the account, this may be provider sign-in, OAuth, a password or an app password. Microsoft 365 destination authentication is a separate setup. Do not assume the source account password or an app password works for every provider.

Check the supported EdbMails connection route and your Google account policy. Google recommends Sign in with Google where available. App passwords require eligible 2-Step Verification settings and may be restricted. Personal Gmail accounts no longer provide an Enable or Disable IMAP switch; Workspace access may still depend on administrator policy. Use the connection guidance.

Authentication must follow the provider supported method for that account and workflow. Some configurations permit OAuth or an app password; an ordinary password may fail when MFA is enabled. Check administrator policy and the current connection instructions. Do not disable MFA or tenant security controls as a general prerequisite for IMAP migration.

Select the IMAP to IMAP workflow, connect the source account and load its folders. Connect the destination, select the required email data, review filters and map the source mailbox to the intended target. Run a pilot, start migration and review the report. Follow the IMAP to IMAP steps.

Prepare the Microsoft 365 destination mailboxes and required access, then connect the IMAP source in EdbMails. Configure the supported Microsoft 365 authentication, load the mailboxes, select folders and map each source to its target. Run a pilot before the full migration and final incremental pass. See the IMAP to Microsoft 365 guide.

Yes. Use the EdbMails IMAP to Exchange workflow with a supported destination Exchange environment. Prepare target mailbox access, connectivity and capacity before mapping the source accounts. This workflow transfers supported IMAP email data; it does not rebuild Exchange Server or migrate non-mail workloads through IMAP. See the IMAP to Exchange steps.

Yes. EdbMails provides a bulk account workflow using its sample CSV. Enter the required account and connection details in the supplied format, validate a small batch and then load the full list. Protect CSV files containing credentials and restrict their access. Review the loaded mailboxes and mappings rather than assuming a successful import means every account can connect.

Review the source mailbox and its intended destination on the mapping screen before starting. Check complete email addresses, especially where domains or usernames differ. Confirm that each target exists and is accessible with the selected connection. Start with a small pilot so mapping errors are detected before data is copied to multiple user mailboxes.

Yes. Select the required folders and use supported include or exclude filters to limit the migration. Date, subject, sender and other criteria are documented in the IMAP migration settings. Check whether filters combine with AND or OR and record all exclusions, so intentionally omitted email is not mistaken for missing data.

EdbMails is designed to preserve supported messages, attachments, folder hierarchy and common email properties. Results depend on what the source exposes and the target accepts. Provider-specific labels and special folders can behave differently. Test representative messages and attachments and inspect the destination folders before approving the complete migration.

EdbMails documents 10 concurrent mailboxes by default and a configurable maximum of 20. Choose a level suited to the migration computer, network and provider connection limits. Increasing concurrency does not override throttling or guarantee a faster result. Test a small batch and review errors and throughput before increasing the workload.

There is no fixed duration. Time depends on item count, message size, bandwidth, server responsiveness, throttling, filters and concurrency. Run a representative pilot to estimate the migration window. Include time for validation, retries and the final pass; the first bulk transfer is not the whole cutover process.

Yes. Supported workflows can process eligible new or changed email in follow-up runs without repeating the complete initial transfer. Keep the project configuration consistent and review each report. Do not treat incremental migration as continuous two-way synchronization or a guarantee of duplicate-free results after changing mappings, filters or destination configuration.

Yes. EdbMails provides pause and resume controls. After resuming or recovering from an interruption, inspect the job status and report for failed or skipped items. Restore the required network and authentication access before retrying. Keep the migration computer and application available for the transfer instead of assuming a closed application continues the job.

Plan an initial transfer while the source service remains available, then coordinate the final pass and client switch with users. New mail can continue arriving during the project, so the first pass may not contain the final mailbox state. Agree when users should use the destination and verify mail delivery after the change.

Treat mail routing and client configuration as separate administrator tasks. Copying email into the destination does not establish that new messages will arrive there. After validation, coordinate any required DNS changes, confirm delivery and run the final migration pass for mail still received at the source. Keep source access until the cutover checks are complete.

Check the host name, port, TLS setting, username format and authentication method. Confirm that provider policy permits access and that the migration computer can reach the server. Check connection limits and whether an app password or consent has expired. Use the connection checklist and record the exact error before contacting support.

Confirm the data exists on the source server and was visible to the connection. Review folder selections, filters, mappings, trial restrictions and failed or skipped items in the report. Gmail labels and special folder behaviour can affect comparisons. Local-only Outlook or Thunderbird data is outside a server IMAP transfer and needs a separate workflow.

Read the report for the affected items and check target mailbox quota, message-size limits, source access, throttling and any size exclusion settings. Resolve the reported cause before retrying the affected scope. A successful mailbox status should not replace checking item-level exceptions. Contact EdbMails support with the relevant error details if needed.

Review migration reports and investigate failed or skipped items. Compare the selected source folders with the destination, allowing for intended exclusions and provider label behaviour. Open representative old and recent messages, inspect attachments and dates, and check Sent items and custom folders. After cutover, verify incoming and outgoing mail and retain the report.

EdbMails runs in your environment and does not use EdbMails servers as a staging location for mailbox content. Use TLS connections supported by the endpoints and the documented authentication method. Protect migration computers, credentials, CSV files and reports. See the EdbMails security page for current details; avoid treating a migration feature as a blanket compliance guarantee.

EdbMails is a Windows application. Check the current IMAP system requirements for the selected destination rather than assuming every operation has the same dependencies. The IMAP to PST workflow specifically requires the documented Outlook components and profile preparation. Verify the requirements for server migration separately before installing it for a project.

IMAP exposes server email folders and their messages, while POP3 is mainly an Inbox retrieval protocol. Choose the connection matching the provider and data available. Neither server connection can retrieve messages that exist only in local client folders. Confirm the POP3 workflow and its supported destination with EdbMails if the source has no IMAP access.

Yes. Use the IMAP to PST export workflow, select the required mailboxes and folders, choose the output location and start the export. Prepare the documented Outlook components and profile first. Review the export report and verify representative messages in the resulting PST. See the IMAP to PST guide.

Download and install EdbMails, then choose Start Your Free Trial. The documented IMAP trial migrates up to 30 items from each folder. Test representative folders, attachments, authentication and target mapping before purchasing. A trial can prove the workflow, but its item limit means it is not a full mailbox completeness test.

No separate licence key is required for the account based activation described on this page. After purchase, sign in with the EdbMails account used for the order to access its purchased mailbox entitlement. Check the current pricing and licence terms for the required scope before starting a larger project.

Open the General or License Usage area for the IMAP project in EdbMails. Review the purchased entitlement and the mailboxes already counted as used; search for a specific address where the build provides that option. Confirm licence scope with support if the planned source or destination differs from the original project.