When to Use IMAP Migration
IMAP migration is the right approach when your source email system is not Microsoft Exchange. If you are migrating from Gmail, Zimbra, Dovecot, hMailServer, Rackspace, or any other IMAP-compatible mail server, this is your primary migration path to Microsoft 365.
However, IMAP migration is not always the best approach even when available. Consider alternatives when:
- You need to migrate contacts and calendars — IMAP only transfers email messages
- You are migrating from on-premises Exchange — use cutover, staged, or hybrid migration instead
- You are migrating from Google Workspace and need Drive/Sites/Forms — use Microsoft's Google Workspace migration tool
- You have more than 50,000 mailboxes — consider third-party tools for better management and reporting
Prerequisites and Planning
Source System Requirements
- IMAP4 must be enabled on the source mail server
- IMAP access must be available over port 993 (IMAP/SSL) or port 143 (IMAP/TLS)
- Administrative credentials or individual user credentials for each mailbox
- If source system uses two-factor authentication, app-specific passwords may be required
- Firewall rules must allow outbound connections from Microsoft's migration service IP ranges
Microsoft 365 Requirements
- Active Microsoft 365 subscription with Exchange Online licenses for all users
- Mailboxes created in Exchange Online (manually, via CSV bulk import, or via directory sync)
- Global administrator or Exchange administrator role
- Custom domain verified and added to the Microsoft 365 tenant
Network Bandwidth Planning
IMAP migration throughput depends on your network connection to Microsoft's datacenters and the source server's capacity. Typical transfer rates:
| Connection Speed | Approx. Transfer Rate | Time per 5 GB Mailbox |
|---|---|---|
| 100 Mbps | 1-2 GB/hour | 3-5 hours |
| 1 Gbps | 3-5 GB/hour | 1-2 hours |
| 10 Gbps | 5-10 GB/hour | 30-60 min |
Note: Microsoft applies throttling to migration connections. Actual throughput is often limited by throttling rather than bandwidth, especially for concurrent batch migrations.
Step-by-Step Migration Process
Step 1: Create User Accounts in Microsoft 365
Before starting the IMAP migration, all target mailboxes must exist in Exchange Online. Create user accounts through the Microsoft 365 admin center, PowerShell bulk import, or Azure AD Connect synchronization. Each user must have an Exchange Online license assigned. Use a CSV file for bulk account creation with columns for username, first name, last name, display name, and license assignment.
Step 2: Prepare the Migration CSV File
Create a CSV file mapping source mailbox credentials to target mailboxes. The required columns are:
user1@company.com,user1@sourcemail.com,sourcePassword1
user2@company.com,user2@sourcemail.com,sourcePassword2
For Gmail migrations, use the user's full Gmail address as the UserName and an app-specific password (generated in Google Account settings) as the Password if 2FA is enabled.
Step 3: Create the Migration Endpoint
In the Exchange admin center, navigate to Migration and create a new IMAP migration endpoint. Specify the source IMAP server FQDN or IP address, the port (993 for SSL, 143 for TLS), and the security type (SSL or TLS). Test the connection to verify connectivity before proceeding.
Step 4: Create and Start Migration Batches
Create a new migration batch using your CSV file. Configure the batch settings including which folders to include (default is Inbox plus all subfolders), whether to exclude specific folders (Junk Email, Deleted Items), and the start date filter (to migrate only messages after a specific date). Start the batch and monitor progress through the migration dashboard.
Step 5: Incremental Synchronization
After the initial migration completes, the batch enters an incremental sync state where new messages received in source mailboxes are automatically synchronized to Exchange Online every 24 hours. This allows users to continue using their source email while the migration is in progress. Keep incremental sync running until you are ready to cut over DNS.
Step 6: DNS Cutover
When ready to complete the migration, update your domain's MX record to point to Exchange Online. The MX record should point to your tenant's Exchange Online endpoint (format: company-com.mail.protection.outlook.com). Also update SPF, DKIM, and DMARC records for email authentication. Allow 24-72 hours for DNS propagation.
Step 7: Post-Migration Validation
After DNS cutover, validate that mail flow is working correctly by sending test messages. Verify that all migrated messages are accessible in user mailboxes. Check folder structure integrity. Confirm that any mail flow rules or transport rules are functioning. Once validated, delete the migration batches and decommission the source mail system.
Enterprise Considerations for 1,000+ Mailboxes
Batch Strategy
For large-scale IMAP migrations, organize batches by department or geographic location rather than alphabetically. This allows you to validate migration success with each business unit before moving to the next. Plan for 5-10 concurrent batches of 50-100 mailboxes each. Schedule the largest mailboxes (power users with 10+ GB) in separate batches to prevent them from blocking other migrations.
Handling Contacts and Calendars Separately
Since IMAP migration only transfers email, you need a separate strategy for contacts and calendars. Options include manual export/import using PST or CSV files, third-party tools like BitTitan MigrationWiz that handle contacts and calendars, or for Google Workspace migrations, Microsoft's native Google Workspace migration tool which handles contacts and calendars alongside email.
Communication and Change Management
Develop a communication plan that notifies users 2 weeks before their batch is scheduled. Provide instructions for accessing their new Exchange Online mailbox via Outlook or OWA. Set expectations about what will and will not be migrated (email only — contacts and calendars require separate action). Provide a helpdesk escalation path for migration-related issues.
Comparison: IMAP vs. Cutover vs. Staged vs. Hybrid Migration
| Feature | IMAP | Cutover | Staged | Hybrid |
|---|---|---|---|---|
| Source | Any IMAP | Exchange 2003+ | Exchange 2003/2007 | Exchange 2010+ |
| Migrates Contacts | No | Yes | Yes | Yes |
| Migrates Calendar | No | Yes | Yes | Yes |
| Max Mailboxes | Unlimited | 2,000 | Unlimited | Unlimited |
| Coexistence | Limited | No | Yes | Full |
| Best For | Non-Exchange | Small orgs | Legacy Exchange | Enterprise |
Frequently Asked Questions
What are the limitations of IMAP migration to Office 365?
IMAP migration has several important limitations. It only migrates email messages — contacts, calendar items, tasks, and notes are not transferred and must be handled separately. The maximum message size is 35 MB. Shared mailboxes, distribution lists, and mail-enabled public folders are not supported. IMAP migration does not preserve read/unread status or message flags. Folder permissions and delegation settings are not migrated. For organizations needing to preserve these elements, a hybrid Exchange migration or third-party tool like BitTitan MigrationWiz or Quest On Demand Migration is recommended.
How many mailboxes can you migrate via IMAP to Office 365 at once?
Microsoft recommends migrating IMAP mailboxes in batches of 50-100 for optimal performance and troubleshooting granularity. The Exchange admin center supports creating multiple migration batches that can run concurrently, but each batch should contain no more than 2,000 mailboxes. For enterprise migrations of 1,000+ mailboxes, plan for 5-10 concurrent batches running over several days. Network bandwidth is typically the limiting factor — each mailbox transfers at approximately 1-2 GB per hour depending on message count and size distribution.
What email providers support IMAP migration to Office 365?
Any email system that supports IMAP4 can be migrated to Office 365, including Gmail and Google Workspace, Yahoo Mail, AOL, Zimbra, Dovecot, Courier, hMailServer, MDaemon, Kerio Connect, Rackspace Email, GoDaddy Email, and most Linux-based mail servers. The source system must have IMAP enabled and accessible over port 993 (SSL) or port 143 (TLS). Some providers like Gmail require enabling IMAP access and may need app-specific passwords if two-factor authentication is enabled.
How to troubleshoot failed IMAP migrations to Office 365?
Common IMAP migration failures and their solutions: authentication errors typically indicate incorrect credentials or IMAP not enabled on the source — verify credentials and enable IMAP access. Connection timeouts suggest firewall issues or incorrect port settings — verify ports 993/143 are open. Item-level failures often result from oversized messages (exceeding 35 MB) or corrupt items — identify and skip these using the migration report. Throttling errors occur when too many concurrent connections are made — reduce batch size. The migration report in Exchange admin center provides per-mailbox error details that should be your first diagnostic step.
What is the difference between IMAP migration and cutover migration?
IMAP migration connects to source mailboxes via the IMAP protocol and copies only email messages to Exchange Online. It works with any IMAP-compatible mail server but does not migrate contacts, calendars, or mailbox settings. Cutover migration is specifically for on-premises Exchange environments (2003 and later) and migrates all mailbox data including email, contacts, calendars, tasks, and notes. Cutover migration also automatically creates mail-enabled users in Azure AD. Cutover migration is limited to 2,000 mailboxes and is best suited for small organizations. For large Exchange environments, hybrid or staged migration is recommended instead.
Planning an Email Migration to Office 365?
EPC Group has migrated hundreds of thousands of mailboxes from IMAP, Exchange, Gmail, and other platforms to Microsoft 365. Get expert guidance on migration strategy, tool selection, and execution planning.
Schedule a Migration AssessmentErrin O'Connor
CEO & Chief AI Architect at EPC Group | 29 years Microsoft consulting