Part 2: IMAP to Microsoft 365 Migration – Technical Guide (cPanel Example)

This guide is written for IT administrators and technical users who want to migrate email from an IMAP-based system to Microsoft 365 themselves. We use cPanel-hosted email as the reference platform, but the same process applies to most IMAP providers.

Scope reminder IMAP migrations move email only Contacts, calendars, tasks, rules, and permissions are not migrated and must be handled separately.

How IMAP Migration Works (At a High Level)

1. Prepare Microsoft 365

2. Verify Domain

3. Prepare IMAP Access

4. Run Migration Batch

5. Cut Over DNS

Important IMAP Migration Limits (Read This First)

Limitation	Microsoft IMAP Behavior
Calendar, contacts, tasks	Not migrated
Email rules & permissions	Not migrated
Maximum items per mailbox	500,000 items
Maximum message size	35 MB
Archive / MRM policies	May cause “missing items” reports

Critical warning Disable any Messaging Records Management (MRM) or archival policies before migration. These policies can make migrated data appear missing even when it is not.

Phase 1: Microsoft 365 Preparation

Create Tenant, Users, and Licenses

Create your Microsoft 365 tenant
Add users and assign Exchange Online licenses
Create shared mailboxes separately

Mailboxes must exist in Microsoft 365 before IMAP migration can start.

Phase 2: Domain Verification (No MX Change Yet)

Verify domain ownership using the TXT record provided by Microsoft.

Do not change MX records yet Changing MX early will route new mail to Microsoft 365 before migration completes.

Phase 3: Prepare cPanel IMAP Access

Mailbox Authentication Options

Option A: Use existing mailbox passwords (least disruptive)
Option B: Reset all mailboxes to a temporary password

cPanel IMAP Settings

IMAP server: mail.yourdomain.com
Port: 993
Encryption: SSL/TLS

Performance tip If possible, increase IMAP connection limits on the server or firewall to speed up migration.

Phase 4: Execute the IMAP Migration

Create Migration CSV

EmailAddress,UserName,Password
user@company.com,user@company.com,Password123

Create Migration Endpoint

In Exchange Admin Center:

Go to Migration → Migration endpoints
Create new IMAP endpoint
Enter cPanel IMAP server details
Test connection

Create and Run Migration Batch

Upload CSV
Name the batch clearly
Start migration

Mail continues to arrive at cPanel during synchronization.

Phase 5: DNS Cutover & Finalization

Verify all mailboxes show Synced or Completed
Update MX to Microsoft 365
Add SPF, DKIM, and DMARC records
Allow final sync
Complete migration batch

Best practice Keep cPanel mail active for 7–14 days as a fallback.

When IMAP Migration Is NOT the Right Tool

Large mailboxes with heavy archives
Complex shared permissions
Strict compliance environments
Need for calendar and contact preservation

In these cases, third-party tools or staged/hybrid migrations are often safer.

Final Thoughts

IMAP migration works well when its limitations are respected. Most failed migrations happen due to poor preparation, early DNS changes, or misunderstanding what IMAP can and cannot move.

Free Migration Assessment

Validate your plan, risks, and timeline before making irreversible changes.

Start Free Assessment

Free Intro Call

Want a second opinion before you proceed? Walk through your setup with an expert.

Book Intro Call