IMAP to Office 365 Migration Tool

Migrate email from IMAP-enabled servers to Microsoft 365 (Office 365) with a planned, verifiable workflow. EdbMails supports migrations from common IMAP environments such as Gmail, Zimbra, Zoho Mail, IceWarp, Yandex, cPanel, GoDaddy, Rackspace, Amazon WorkMail, and other standards-compliant IMAP servers. The target Microsoft 365 environment can provide Exchange Online email together with services such as Teams, SharePoint, OneDrive, and the Microsoft 365 productivity apps.

EdbMails IMAP Migration Tool provides a guided workflow for IMAP to Office 365 migration, including single-user and bulk mailbox loading, source and target mailbox mapping, filtering, incremental migration, concurrent mailbox processing, and migration reporting. The application runs in your environment and transfers supported email data between the configured source and Microsoft 365 target. During the copy phase, users can generally continue using the source mailbox; final cutover activities such as DNS, MX, and Outlook profile changes should still be planned and verified.

1. IMAP to Office 365 Migration Plan

   Before migrating IMAP mailboxes to Microsoft 365, define the migration scope, target design, cutover method, and validation plan. Use the following checklist before starting a production batch.

   1. Inventory the source mailboxes, mailbox sizes, active users, IMAP host names, ports, authentication requirements, and any provider-specific connection limits.
   2. Confirm what must be migrated. Standard IMAP covers email, folders, attachments, and supported message properties; contacts, calendars, and tasks require a separate workflow.
   3. Remove or exclude data that does not need to be migrated, such as obsolete mail folders or unwanted messages, where appropriate for the project.
   4. Prepare the Microsoft 365 tenant, create or provision the required target mailboxes, assign licenses where required, and configure any shared, archive, or public-folder targets included in the project.
   5. Decide whether to perform a single cutover or a staged migration with an initial pass followed by one or more incremental passes.
   6. Estimate bandwidth and migration-computer capacity and account for source connection limits, Microsoft 365 throttling, mailbox sizes, and message-size limits.
   7. Define the source-to-target mailbox mapping and identify any folder-mapping exceptions before the bulk run.
   8. Run a pilot migration with representative mailboxes and verify the target folder structure, attachments, message properties, and migration report.
   9. Communicate the migration schedule and any expected sign-in, DNS, MX, or Outlook profile changes to users and stakeholders.
   10. After the final migration pass, verify mail flow and target mailbox data before completing the cutover or decommissioning the old environment.

2. IMAP to Office 365 Migration Prerequisites

   On the source IMAP server:

   1. Confirm that IMAP access is enabled and collect the correct IMAP server host name, port, TLS/SSL requirement, email address, and authentication method for each source mailbox.
   2. For bulk migration, download the sample CSV file from EdbMails and enter the required source mailbox details. Validate a small test set before loading a large production CSV.
   3. For Gmail or Google Workspace sources, use the authentication method supported by your account and the current EdbMails workflow. If the workflow uses a Google app password, create one only where the Google account policy permits it.

       See Gmail app-password guidance.

   4. Check whether the source provider limits IMAP connections per user, per IP address, or per server. These limits can affect the useful level of concurrent migration.

    See Microsoft's guidance on finding an IMAP server host name.

   On the Microsoft 365 target:

   1. Prepare the target Microsoft 365 tenant and verify the custom domain if the organization will continue using it after migration.
   2. Create or provision the required Microsoft 365 mailboxes and assign the appropriate licenses. EdbMails can assist with target mailbox creation in supported workflows; review the generated mailbox list before migration.
      • Add users and assign licenses in Microsoft 365
      • Assign Microsoft 365 licenses to user accounts
   3. If the destination includes shared mailboxes, archive mailboxes, or public folders, create and configure those targets and assign the permissions required for the selected EdbMails workflow.
      • Create and configure Microsoft 365 public folders
      • Create Microsoft 365 shared mailboxes
   4. Use the current EdbMails Microsoft 365 modern-authentication method. For automatic registration, follow the automatic app-registration guide. For environments that require a customer-managed app, follow the manual app-registration guide.
   5. Review network capacity, Microsoft 365 throttling behavior, and target message-size limits before starting the production batch. Do not assume every item accepted by the source will automatically be accepted by the target.
   6. Run a pilot mailbox or small batch and verify the result before increasing concurrency for the full migration.

3. Step-by-Step Guide for IMAP to Office 365 Migration

   • Step 1: Download and install EdbMails for IMAP to Office 365 migration

     • Download and install EdbMails on any Windows computer.
     • Follow the instructions that appear to complete the installation.

        See EdbMails system requirements for Office 365 migration

       

     • Open the EdbMails application on your computer.
     • Enter your registered email address and password, then click ‘Login’. If you have not created an account yet, choose ‘Start Your Free Trial’ to continue using the trial version.
        Note: The free trial lets you evaluate the IMAP migration workflow and migrate up to 30 items from each folder. To migrate all eligible items for licensed mailboxes, purchase the required IMAP migration license from the EdbMails pricing page.

        View current IMAP migration pricing.

       

     • Select the option ‘IMAP (Gmail, Outlook & more) Migration’

       

     • Select ‘IMAP to Office 365 Migration’.

       

     • You can either keep the default job name or select the ‘New Job’ button to assign a different name.

       

   • Step 2: Connect to the Source IMAP Server

     • To connect one user account, select ‘Single User / Account Migration’, choose the desired protocol like ‘Connect to IMAP Server’ or ‘Connect to POP3 Server’, and then click ‘Next’ to continue.

       

     • For a single-user login, select the appropriate IMAP host name from the list or enter the full IMAP server name manually. Enter the source email address and the authentication credential required by that provider. For Gmail or Google Workspace, use the authentication method supported by your account and EdbMails; use an app password only where the Google account policy allows it.
     • Click the ‘Login’ button.

       

     • Once the mailbox is loaded, click ‘Next’ to proceed.

       

     • For enabling the migration of multiple IMAP accounts simultaneously, select ‘Multiple (Bulk) Users/Accounts Migration’ and click ‘Next’.

       

     • Click ‘IMAP Migration CSV File’ to download the ‘Sample.CSV’ file.

       

     • Modify the CSV file with the required details such as email address, password, host name and port number in the CSV file and save the changes.

       

     • Close the CSV file, click the ‘Load Modified CSV File’ button, select the modified CSV file.
     • Verify the mailboxes, and click 'Next'.

       

        Refer to the EdbMails detailed steps on connecting to single and multiple users during IMAP migration.

   • Step 3: Select Source IMAP Server Mailboxes

     • Select the ‘Mailboxes’ or ‘Folders’ to migrate, then click ‘Next’.

         See tips to optimize IMAP migration to Exchange Online.

       

   • Step 4: Connect to the Target Office 365 Server

     • Click the ‘Add New Connection’ button to establish a new connection to the target Office 365. To use the previous connection, select it from the connection list and click the ‘Connect to Existing’ button to proceed.

       

     • Select the required connection options and click the ‘Next’ button.

       

     • Select the appropriate target connection method based on modern authentication.
     • Click the ‘Login’ button to continue.

       

     • Authenticate through the official Microsoft sign-in page. The target Microsoft 365 connection uses OAuth 2.0 modern authentication, so the Microsoft sign-in flow handles user authentication instead of placing a Microsoft 365 password directly into the migration job.

       

     • Select one of the methods to load the mailboxes. You can Select ‘Load Mailboxes Automatically’, Load Mailboxes using .CSV file or ‘Load Mailboxes from previous list’ and click ‘Next’.

       

   • Step 5: Map Source and Target mailboxes

     • Choose the required mailbox mapping option to map source mailboxes with their corresponding target mailboxes.

       

     • Where supported and selected, EdbMails can help create the required target Microsoft 365 mailboxes. Review the source-to-target mailbox and folder mappings before starting a bulk migration.

       

   • Step 6: Start IMAP to Office 365 migration operation

     • After mapping the mailboxes, click the ‘Start Migration’ button and initiate the migration process.

       

     • Click the ‘View Log’ button to review the migration report. Use the report to check mailbox and folder status, migrated item counts, errors, and warnings. Investigate failed or skipped items and run the required retry or incremental pass before final cutover.

       

4. IMAP to Office 365 Post-Migration Tasks

   • Step 1: Verify the final migration pass

     Review the migration report and verify representative folders, messages, attachments, and item counts in Microsoft 365. Resolve failed items and run any required retry or incremental pass before changing mail flow.

   • Step 2: Update DNS and MX records when ready for cutover

     After the target mailboxes are verified, update the Microsoft 365 DNS and MX records required for the domain. Allow for DNS propagation and monitor inbound and outbound mail flow after the change.

   • Step 3: Configure Outlook and user access

     Confirm that users can sign in to Microsoft 365 and access their new mailboxes. Recreate or reconfigure Outlook profiles only where required. Do not remove the old profile or source configuration until the migrated mailbox and mail flow have been verified. See Outlook profile configuration guidance.

   • Step 4: Monitor the source during the transition

     Keep the source environment available for the agreed validation period where practical. Confirm that no required new mail remains only on the source and that users know when the source environment will be retired.

5. Troubleshooting IMAP to Office 365 Migration

    For common connection, authentication, mapping, throttling, and item-level errors, refer to the migration troubleshooting guide. For IMAP-specific questions, see the IMAP migration FAQ. Review the migration report before rerunning a job so the retry is focused on the items that actually require attention.

---

Additional resources:

• EdbMails IMAP Migration Tool
• IMAP to Office 365 migration screenshots
• IMAP to Office 365 shared mailbox migration
• GoDaddy to Office 365 migration
• Zoho Mail to Office 365 migration
• Zimbra to Office 365 migration
• cPanel to Office 365 migration
• AWS WorkMail to Office 365 migration
• Rackspace to Office 365 migration