IMAP to Microsoft 365 Migration: Handling Large Mailboxes Over 50GB

The Large Mailbox Challenge

IMAP migration to Microsoft 365 is straightforward for mailboxes under 10GB. Microsoft's built-in IMAP migration tool handles the process with minimal configuration. But enterprise environments rarely have small mailboxes. Executives, legal teams, compliance officers, and long-tenure employees routinely accumulate 50GB, 75GB, or even 100GB+ mailboxes that break standard migration approaches.

The core problem is threefold. First, Microsoft 365 throttles IMAP migration bandwidth to protect service performance, causing large mailbox migrations to take days or weeks per mailbox. Second, IMAP connections time out after extended periods, requiring restarts that may duplicate or miss messages. Third, Exchange Online primary mailboxes default to 50GB (E3) or 100GB (E5), so oversized source mailboxes need archiving strategies before migration.

At EPC Group, we have migrated organizations with thousands of large mailboxes from legacy IMAP systems including Zimbra, hMailServer, Dovecot, MDaemon, and hosted providers to Microsoft 365. Our methodology addresses every challenge that arises when mailbox sizes exceed standard limits.

Pre-Migration Assessment: Know Your Source

A thorough pre-migration assessment prevents costly surprises during execution. For large mailbox migrations, the assessment must cover:

Mailbox Inventory and Sizing

• Per-mailbox size analysis: Catalog every mailbox by total size, message count, and largest individual message. IMAP migration has a 35MB per-message limit in Microsoft 365. Messages exceeding this limit are skipped and must be handled separately.
• Folder structure analysis: Deep folder hierarchies (10+ levels) and special characters in folder names cause IMAP migration failures. Identify and remediate problematic folder structures before migration begins.
• Attachment analysis: Large attachments (10MB+) are the primary driver of mailbox bloat. Identify whether attachments should migrate to OneDrive/SharePoint instead of Exchange Online to reduce mailbox size.
• Date distribution: Analyze email age distribution to determine the optimal split between primary mailbox and archive. Typically, the most recent 2 years belong in the primary mailbox and older email goes to the archive.

Source Server Evaluation

• IMAP capability: Verify IMAP4 support, TLS/SSL configuration, maximum concurrent connections, and any provider-specific limitations (Gmail limits connections to 10 per account).
• Bandwidth capacity: Source server bandwidth limits migration throughput. For hosted email, check provider SLA for migration bandwidth allowances. Some providers throttle IMAP connections during migration.
• Authentication: Document authentication methods. Some IMAP servers require app-specific passwords (Gmail), OAuth tokens, or have IP-based access restrictions that must be configured for Microsoft's migration endpoints.

Exchange Online Storage Architecture for Large Mailboxes

Before migrating 50GB+ mailboxes, configure Exchange Online storage to accommodate the data. The architecture decision depends on licensing and compliance requirements.

Enabling Auto-Expanding Archiving

For organizations migrating large mailboxes, enable auto-expanding archiving at the tenant level before migration begins. This ensures archive mailboxes grow automatically as historical email is imported. The PowerShell command is straightforward:

Once enabled, auto-expanding archiving applies to all new and existing archive mailboxes. The feature is irreversible at the tenant level, which is appropriate for organizations committed to Microsoft 365 as their primary email platform.

Batch Migration with PowerShell: The Enterprise Approach

The Exchange admin center IMAP migration wizard works for small batches, but enterprise migrations with 50GB+ mailboxes require PowerShell for control, error handling, and parallel execution.

Migration Endpoint Configuration

Create an IMAP migration endpoint that defines the connection to your source server. This endpoint specifies the server address, port, encryption method, and authentication type. For large migrations, configure the maximum concurrent migrations and incremental sync interval.

CSV-Based Batch Files

Organize migrations into batches of 50-100 mailboxes, grouped by department or mailbox size. Each batch references a CSV file mapping source IMAP credentials to target Microsoft 365 mailboxes. For large mailbox batches, EPC Group creates separate batches for mailboxes over 50GB to apply different monitoring and error-handling procedures.

Incremental Synchronization Strategy

The key to zero-downtime large mailbox migration is incremental sync. The process follows three phases:

1. Initial sync (days 1-7): Full migration of all email from source to destination. For 50GB+ mailboxes, this takes 25-50 hours per mailbox. Run 50-100 mailboxes in parallel to maximize throughput.
2. Delta syncs (daily): Nightly incremental syncs capture new email received since the last sync. Delta syncs typically take minutes per mailbox as they only process new messages.
3. Final cutover sync: During the maintenance window, run a final delta sync, update MX records to point to Exchange Online, and verify all messages are present. Cutover window is typically 2-4 hours.

PST Import as an Alternative for Oversized Mailboxes

For mailboxes exceeding 75-100GB, PST import via Azure may be more efficient than IMAP migration for historical email. The process involves exporting old email to PST files, uploading them to Azure Blob Storage using AzCopy, and importing into Exchange Online archive mailboxes.

• Export phase: Export email older than 2 years from the source IMAP server to PST files. Use client-side tools (Outlook, Thunderbird) or server-side export utilities depending on the source platform.
• Upload phase: Use AzCopy to upload PST files to the Microsoft-provided Azure Blob Storage SAS URL. Upload speeds depend on your internet bandwidth but are not throttled by Microsoft. A 1Gbps connection can upload 50GB in approximately 7 minutes.
• Import phase: Create PST import jobs in the Microsoft Purview compliance portal. Map PST files to target mailboxes and specify whether to import to the primary mailbox or archive. Filter by date range to import only historical email to the archive.
• Validation: After import, verify message counts and folder structures match the source PSTs. Spot-check specific emails identified during pre-migration assessment.

Calendar, Contact, and Rule Migration

IMAP protocol transfers only email messages and folder hierarchy. Calendars, contacts, tasks, and mail rules require separate migration methods.

Post-Migration Validation Checklist

Validation is the most overlooked phase of email migration. EPC Group's post-migration validation process ensures no data is lost and all services function correctly.

• Message count reconciliation: Compare source and destination message counts per folder. Allow for a 1-2% variance due to system messages and duplicates, but investigate any folder with greater variance.
• Date range verification: Confirm the oldest and newest messages in each mailbox match expectations. IMAP migration occasionally misses messages from specific date ranges due to source server indexing issues.
• Attachment integrity: Spot-check attachments on 5-10 messages per mailbox, focusing on messages with large or unusual attachment types (ZIP, encrypted PDFs, embedded images).
• Folder structure: Verify folder hierarchy, special characters in folder names, and folder depths. IMAP migration maps source folders to Exchange Online folders, but naming conflicts can cause unexpected restructuring.
• Mail flow testing: Send test emails to and from each migrated mailbox. Verify internal routing, external delivery, and reply functionality. Test mobile device connectivity (ActiveSync, iOS Mail, Outlook Mobile).
• Client configuration: Validate Outlook desktop profile reconfiguration, Outlook on the web access, and mobile device setup. Provide user documentation for profile updates.
• Archive verification: For mailboxes using Exchange Online archiving, verify archive mailbox content, auto-expanding archive functionality, and retention policy application.

Common Pitfalls and How to Avoid Them

• Throttling underestimation: Microsoft 365 throttles IMAP migration aggressively. Plan for 1-2GB/hour per mailbox, not the theoretical maximum. Schedule migrations over weekends when throttling is typically lighter.
• DNS propagation delays: MX record changes take 0-48 hours to propagate. Set TTL to 300 seconds (5 minutes) at least 48 hours before cutover to minimize propagation time during the maintenance window.
• Shared mailbox conversion: IMAP sources often use shared/generic accounts that should become shared mailboxes in Exchange Online (no license required). Identify these during assessment to avoid unnecessary licensing costs.
• Legacy protocol dependencies: Some source systems use POP3, SMTP relay, or proprietary protocols for line-of-business application email. Inventory all non-user email flows and plan Exchange Online connector configuration before cutover.
• User communication: Large mailbox migrations take time. Keep users informed about migration progress, expected downtime, and post-migration steps. Provide a dedicated support channel during cutover.

Partner with EPC Group for Your Email Migration

EPC Group has managed IMAP to Microsoft 365 migrations for organizations ranging from 50 to 10,000+ mailboxes across every major IMAP platform. Our Microsoft 365 consulting team handles the entire migration lifecycle from assessment through post-migration support, ensuring zero data loss and minimal user disruption. With 25+ years of Microsoft migration experience, Errin O'Connor and the EPC Group team deliver enterprise-grade migrations that keep your business running.