Ready to migrate?
Admin Guide

IMAP to Microsoft 365 Migration Guide

This guide explains how to migrate your IMAP server mailboxes to Google Workspace, Microsoft 365, or Exchange using the Cloudiway migration platform.

10 min read Updated: 2025-12-18 IMAP to Microsoft 365

Overview

This article explains how to migrate your IMAP server to Google Workspace, Microsoft 365, or Exchange with the Cloudiway migration tools.

Key Challenge: One of the biggest challenges for IMAP migrations is being able to create an IMAP administrator account with permissions to read all mailboxes. Cloudiway offers multiple solutions for this.

Looking for our IMAP Migration Solution?

Discover all features, pricing, and use cases for IMAP to Microsoft 365 migration.

View Solution Page

Migration Modes

Cloudiway supports two approaches for IMAP migration:

Administrator Account Mode

Use a dedicated admin account with permissions to access all mailboxes. This requires no user passwords and enables batch migration without individual involvement.

Self-Service Migration Mode

When admin accounts are not available. Users receive an email with a migration link and enter their own IMAP credentials. Migration processes on Cloudiway servers - users can close their browser.

Step 1: Create IMAP Connector

Create an IMAP connector in the Cloudiway platform to connect to your IMAP server:

1

Create New Connector

Go to Connectors > New and select IMAP as the connector type. Select Mail as the product to migrate.

2

Configure Connector Settings

Configure your IMAP server connection with the following parameters:

IMAP Connector Configuration
IMAP connector configuration in Cloudiway platform

Server Settings

Parameter Description
Server Name* The hostname or IP address of your IMAP server (e.g., mail.company.com)
Port* The IMAP port: 993 (SSL - recommended) or 143 (standard)
Domain Names The email domains hosted on your IMAP server (e.g., company.com)

Administrator Account

Parameter Description
Administrator Account* The IMAP administrator email address with access to all mailboxes (leave blank for magic password mode)
Administrator Password The password for the administrator account (or the magic password for all users)
Authentication Mode Select None for admin-based authentication, or Self Service for user-based authentication
3

Complete Setup

Click NEXT to review your configuration, then click NEXT again to save your connector.

Magic Password Mode: For servers like Postfix that don't support admin accounts, leave the Administrator Account field blank. The Administrator Password will be used as the authentication credential for all users.
Self-Service Mode: For IMAP servers where you don't have admin access (like Cyrus), select Self Service authentication. Users will be prompted to enter their own credentials during migration.

Step 2: Create Target Connector

Create a target connector for your destination platform. You can migrate IMAP to Microsoft 365, Google Workspace, or Exchange On-Premises.

Option A: Microsoft 365 Target

Microsoft 365 target connector configuration
Microsoft 365 target connector configuration
1

Create New Connector

Go to Connectors > New, select Microsoft 365 as connector type.

2

Configure Authentication

Choose Automatic mode and enter your Microsoft 365 Global Administrator credentials, then click GRANT ADMIN CONSENT.

3

Complete Setup

Review settings and complete the connector creation.

Documentation: For detailed instructions, refer to our Microsoft 365 Connector Configuration guide.

Option B: Google Workspace Target

Google Workspace target connector configuration
Google Workspace target connector configuration
1

Create New Connector

Go to Connectors > New, select Google Workspace as connector type.

2

Configure Service Account

Choose Automatic mode and sign in with your Google Workspace Super Admin account to authorize access.

3

Enable Domain-Wide Delegation

Follow the prompts to enable domain-wide delegation for the Cloudiway service account in your Google Admin Console.

4

Complete Setup

Review settings and complete the connector creation.

Documentation: For detailed instructions, refer to our Google Workspace Connector Configuration guide.

Option C: Exchange On-Premises Target

You can also migrate IMAP to an on-premises Exchange server using EWS (Exchange Web Services).

1

Create New Connector

Go to Connectors > New, select Exchange On Premises as connector type.

2

Enter EWS URL

Enter your Exchange Web Services endpoint URL: https://your-exchange-server/EWS/Exchange.asmx

3

Select Authentication Mode

Choose your authentication method:

  • Impersonation: Migration account impersonates each user (requires ApplicationImpersonation role)
  • Delegation: Migration account has Full Access rights to each mailbox
  • Self Service: Each user provides their own credentials
4

Complete Setup

Enter the migration account credentials and complete the connector creation.

Documentation: For detailed instructions, refer to our Exchange Configuration guide.

Step 3: Configure Global Settings

Navigate to Mails > Global Settings to configure your migration options:

Mail migration global settings
Mail migration global settings configuration

Migration Scope

Setting Description
Migrate Emails Enable to migrate email messages from IMAP mailboxes
Migrate Trash Enable to migrate items from the Trash/Deleted Items folder

Advanced Settings

Setting Description
Date Filter Optionally filter items by date range to migrate only recent data
Convert Email Address Rewrites email addresses found in headers from old domain to new domain
Tip: Use the Date Filter option to run a pilot migration with only recent emails before migrating the full mailbox history.

Step 4: Run Migration

Now you can populate the user list and run the migration.

Populate User List

Navigate to Mails > User List to add users for migration. There are three ways to populate the user list:

Discovery (Get List)

Automatically discover all users from the IMAP server (if supported).

Import User List

Upload a CSV file with the list of users to migrate.

Create Manual Entry

Manually add individual users one by one.

Option 1: Discovery (Get List)

Under MIGRATION, click on the Get List option:

Get List menu option
Migration > Get List option

Specify the following parameters:

1

Source Pool

Select the IMAP source connector you created earlier.

2

Target Pool

Select the Microsoft 365 or Google Workspace target connector.

3

Matching Rule

Choose how source emails should be mapped to target emails:

  • Mail Exact Match: source email = target email
  • Keep Email Prefix Same as Source: only the domain changes
  • FirstName.LastName: (e.g., [email protected])
4

Target Domain

Specify the target domain for the migrated users.

Note: The Get List feature for IMAP may not be available on all servers. If your IMAP server doesn't support user discovery, use the Import or Manual Entry options instead.

Option 2: Import User List

Click on MANAGE > Import to upload a CSV file containing the users to migrate.

Import users dialog
Import users from CSV file
1

CSV File

Click on BROWSE to select your CSV file. You can click Download sample csv to get a template file.

2

Source Connectors Pool

Select the IMAP source connector.

3

Target Connectors Pool

Select the target connector (Microsoft 365 or Google Workspace).

CSV Format: For more details on the syntax of the CSV file, read our guide: How to Fill the Users/Groups CSV File

Option 3: Create Manual Entry

Click on MANAGE > Create to manually add individual users. Enter the source IMAP email address and the target email address for each user.

Run Audit (Recommended)

Before migrating, run an Audit task to assess mailbox sizes and identify potential issues:

1

Select Users

Select the users you want to audit using the checkboxes.

2

Start Audit

Click MIGRATION > Audit to start the audit process.

3

Review Results

Check the audit results to see mailbox sizes, item counts, and any errors.

Execute Migration

Once you have reviewed the audit results, you can start the migration:

1

Select Users or Batches

Select the users you want to migrate. You can migrate all users at once or create batches for phased migration.

2

Start Migration

Click MIGRATION > Start to begin the migration process.

3

Monitor Progress

Monitor the migration progress in the dashboard. You can see the status of each user and any errors that occur.

4

Delta Migration (Optional)

Run a delta migration to sync any new items created since the initial migration. Click MIGRATION > Start again to perform incremental sync.

Delta Migration: Cloudiway tracks which items have been migrated. Running the migration again will only migrate new or modified items since the last run.

Special Cases

Postfix IMAP Server

Postfix IMAP servers cannot create admin accounts with universal mailbox access.

Solution: Set identical "magic passwords" for all accounts. Leave the administrator field blank and the administrator password will be used as the authentication credential for all users.

Cyrus IMAP Server

Cyrus IMAP servers do not support admin accounts with full permissions to all mailboxes.

Solution: Use the self-service migration scenario. Each user will enter their own credentials.

Folder Binding Considerations

Cloudiway synchronizes folders between source and target mailboxes before migrating mails. Note that:

  • In IMAP or Google, a user can flag a folder to hide it from IMAP
  • If a folder is hidden, it and its content will be ignored since Cloudiway cannot access it through IMAP

Frequently Asked Questions

What IMAP servers does Cloudiway support?

Cloudiway supports any IMAP-compliant server including Postfix, Cyrus, Dovecot, hMailServer, and hosted email providers that offer IMAP access.

Can I migrate IMAP without an admin account?

Yes, Cloudiway supports self-service migration where each user provides their own credentials. Users receive an email with a migration link and can start their own migration.

What ports does IMAP migration use?

IMAP uses port 143 for standard connections and port 993 for IMAP over SSL/TLS. We recommend using SSL for secure migrations.

How does magic password authentication work?

Leave the administrator username blank in the connector configuration. The administrator password will then be used as the authentication credential for all users. This is useful for Postfix servers.

Why are some folders not migrated?

In IMAP, users can flag folders to hide them from IMAP access. Hidden folders and their contents are ignored during migration since Cloudiway cannot access them.

Ready to Start Your Migration?

Get a free migration quote in minutes — entirely self-service.