Migrate Office 365 to iCloud Mail: A Practical Guide

You're leaving a paid Microsoft 365 plan and want your mail to live in iCloud alongside the rest of your Apple account. The hard part isn't choice of tool, it's that iCloud Mail behaves like a consumer service while Office 365 was built for business. IMAP works on both sides, but iCloud's quota math, app-password requirement, and rate limits will catch you if you treat this like a standard tenant-to-tenant move. This guide walks through the move with realistic timing and the specific places things break.

Why people make this move#

The Office 365 to iCloud direction usually shows up in three scenarios. The first is a personal one: someone is winding down a freelance business or sole-proprietor LLC and wants their mail history in a place that doesn't require an ongoing subscription to a productivity suite. iCloud+ at 200 GB costs less than the cheapest Microsoft 365 plan and includes the rest of the Apple ecosystem.

The second is family handoff. A retired parent had a Microsoft 365 Family or Business Basic license through their old employer and the license is ending. They already use an iPhone and iPad, so iCloud is the obvious landing pad.

The third is consolidation. A user has years of Office 365 mail from a company that's shutting down and wants to fold it into the iCloud Mail address they use for everything else.

None of these are pure "business to business" migrations. The tooling assumptions are different, and that matters when you start picking software.

What you'll lose, what you'll keep#

Be honest about this before you start.

You keep messages, message headers, attachments, folder structure, and read/unread state. With a desktop IMAP migration tool, you also keep flagged/starred status because IMAP exposes the \Flagged keyword on both sides.

You lose Office 365 calendar items, contacts, Teams chat history, OneDrive files, and SharePoint sites. Mail migration is mail only. If you need calendar and contacts, export them to ICS and vCard separately and import them into iCloud through the iCloud web interface or System Settings on macOS.

You may lose category colors and some custom Outlook-only flags. iCloud doesn't expose Outlook's color category system through IMAP. The flag becomes a generic starred state.

You will lose some metadata fidelity on retention-tagged items if you had Office 365 retention policies attached. The message moves, but the retention tag is a Microsoft-specific property that doesn't survive the IMAP copy.

Before you connect anything#

There are five pieces of setup to handle before opening any migration tool. Do them in order.

Verify IMAP is on for the source mailbox#

Office 365 disables IMAP for new tenants by default. Sign into the Microsoft 365 admin center, open the mailbox under Users → Active users → Mail → Manage email apps, and confirm IMAP is checked. If it's a personal Microsoft account rather than a business tenant, IMAP is on by default at outlook.office365.com:993.

Decide on basic auth vs. modern auth#

If your tenant has Security Defaults turned on, basic auth IMAP is blocked. You'll need either an app password (if you have MFA enabled) or to use a tool that supports OAuth2 against Microsoft. Most desktop migration tools, including Mailbox Taxi, handle this through app passwords or OAuth2 device-code flow.

Buy enough iCloud storage#

This is the single most common cause of stalled migrations. iCloud's free tier is 5 GB shared across Mail, Drive, Photos, and device backups. A 20 GB mailbox does not fit. Go to Settings → [your name] → iCloud → Manage Account Storage → Change Storage Plan on an iPhone or Mac and pick a plan that comfortably exceeds your source mailbox size with at least 30 percent headroom.

Generate an iCloud app-specific password#

iCloud refuses your normal Apple ID password for third-party IMAP clients. Go to appleid.apple.com, sign in, then under Sign-In and Security → App-Specific Passwords, click the plus icon, label it "Mailbox Taxi" or similar, and copy the 19-character password Apple shows you. You only see it once.

For more on what these are and why every modern provider uses them, see our piece on app-specific passwords.

Note iCloud's IMAP host#

iCloud Mail's IMAP server is imap.mail.me.com on port 993 with SSL. The username is the full @icloud.com (or @me.com, @mac.com) address. SMTP is smtp.mail.me.com on 587 with STARTTLS. You won't need SMTP for the migration itself, but you'll need it when reconnecting clients afterward.

Choosing a migration approach#

You have three realistic options.

Drag and drop in a desktop mail client. Add both accounts to Apple Mail or Thunderbird, then drag folders between them. This works for mailboxes under 2 GB but falls over on anything larger. Apple Mail in particular handles partial failures badly: a dropped connection mid-folder leaves duplicates, and there's no clean way to resume from where it failed.

Microsoft's IMAP migration in the Exchange admin center. This is designed to pull mail into Office 365, not push it out. Wrong direction for your use case.

A dedicated desktop migration tool. Runs on your workstation, connects via IMAP to both sides, tracks per-message state, handles retries, and avoids duplicates on resume. This is what Mailbox Taxi does and what we'll use for the rest of this guide. If you're picking a tool, the key features to look for are duplicate detection, folder mapping, throttle awareness, and resumability after network interruptions.

For broader context on what's involved, our Office 365 migration guide covers the source side in more detail.

Step-by-step migration#

1. Confirm IMAP and authentication on Office 365

   Sign into the Microsoft 365 admin center as a global admin or user admin. Under the user's properties, verify IMAP is enabled. If the account uses MFA, generate a Microsoft app password from mysignins.microsoft.com/security-info. Save it somewhere temporary like a password manager note. Test the IMAP credentials with a simple client like Thunderbird before involving the migration tool, so you've isolated any auth problems early.

2. Upgrade iCloud+ and create an app-specific password

   On an Apple device signed into the destination iCloud account, upgrade storage to a plan with at least 30 percent more capacity than the Office 365 mailbox size. Then go to appleid.apple.com, sign in, navigate to App-Specific Passwords, and generate one labeled for this migration. Copy it to your password manager. Verify it works by connecting to imap.mail.me.com:993 from a test IMAP client and listing folders.

3. Add both accounts to your migration tool

   Open Mailbox Taxi on your desktop. Add the Office 365 account as the source: host outlook.office365.com, port 993, SSL, username is the full email, password is the app password from step 1. Add iCloud as the destination: host imap.mail.me.com, port 993, SSL, username is the full @icloud.com address, password is the app-specific password from step 2. The tool will list folders on both sides once authentication succeeds.

4. Map folders deliberately

   iCloud uses specific folder names: Inbox, Sent Messages, Drafts, Junk, Archive, Trash. Office 365 uses Inbox, Sent Items, Drafts, Junk Email, Archive, Deleted Items. Map Sent Items to Sent Messages, Deleted Items to Trash, and Junk Email to Junk. Leave custom folders as one-to-one. Exclude Junk Email from the migration unless you specifically need it, because it's mostly noise and counts against your iCloud quota.

5. Run a small test batch first

   Migrate one small folder, say a project folder with a few hundred messages, before committing to the full mailbox. Check in iCloud (via icloud.com/mail or Apple Mail) that messages arrive, attachments open, dates match, and read/unread state is preserved. If the test folder looks good, proceed with the full run.

6. Run the full migration overnight

   Start the full job in the evening. iCloud throttles aggressively, so a parallel connection count of 2 to 3 is realistic, not 10. Mailbox Taxi will back off automatically on Too many simultaneous connections errors, but starting with conservative concurrency avoids the early retry storms. Let it run overnight and check in the morning.

7. Verify counts and spot-check

   When the job finishes, compare folder message counts between Office 365 and iCloud. Small discrepancies (a few messages) are usually genuine duplicates the tool deduplicated. Larger gaps mean a folder was throttled and needs a delta run. Spot-check a dozen messages with attachments, embedded images, and HTML formatting to make sure rendering survived.

Throttle behavior to expect#

iCloud's IMAP throttling isn't documented publicly, but here's what you'll see in practice.

Connection limits sit around 4 to 6 simultaneous IMAP connections from a single IP. Push past that and you get Too many simultaneous connections and dropped sockets. Concurrent appends across folders behave better than concurrent appends to one folder, so a multi-folder migrator naturally spreads load.

Per-message append rate caps roughly around 2 to 3 messages per second per connection for messages under 1 MB. Larger messages slow proportionally. Expect throughput around 2 to 4 GB per hour on a good run.

Bursting works, then doesn't. iCloud lets you append 100 to 200 messages quickly, then starts inserting delays. The pattern is consistent enough that any reasonable migration tool will hit it and back off.

Failed appends on messages over 50 MB are common. iCloud's effective per-message limit sits below Office 365's 150 MB default. If you have a folder full of large attachments, expect a small number of failures you'll need to handle manually, usually by saving the attachments separately and uploading them to iCloud Drive.

After the migration#

Three things need attention once the data is across.

Reconfigure your mail clients. Remove the Office 365 account from Apple Mail, Outlook, and your phone. Add the iCloud account. If you'd been using the Office 365 address as your primary, set up forwarding from Office 365 to iCloud so mail sent to the old address still reaches you during the transition. Forwarding is configured in Outlook on the web under Settings → Mail → Forwarding.

Update your authentication recovery details. If the Office 365 account was the recovery email or 2FA fallback for anything important, change those settings to point at iCloud before you decommission the Microsoft account.

Keep Office 365 alive for at least 30 days. Even with a clean verification, keep the source account licensed for a month. Senders who reply to old threads, services using the address for account recovery, and occasional friends still using the old address will surface during this window. Forwarding handles most of it, but you'll want the source mailbox available in case you need to re-pull anything.

For the reverse direction (moving back to Microsoft), see iCloud to Office 365. And if you're considering Gmail instead, the Office 365 to Gmail walkthrough covers the same source side with a different destination.

Common errors and fixes#

AUTHENTICATIONFAILED on the Office 365 side almost always means basic auth is blocked and you need an app password or OAuth2. Less commonly, it means IMAP is disabled at the mailbox level.

AUTHENTICATIONFAILED on the iCloud side almost always means you used your Apple ID password instead of the app-specific one. Regenerate the app password and try again.

Too many simultaneous connections on iCloud means lower your concurrency. Three connections is usually the safe number.

Message too large for destination on iCloud means the message exceeds iCloud's per-message size limit. Either skip those messages or save the attachments separately.

Folder UTF-7 conversion error shows up when Office 365 has folder names with characters iCloud doesn't accept in IMAP-modified UTF-7 form. Rename the offending folder on the source side to plain ASCII before re-running.

If you hit a different issue, the Yahoo destination guide covers a similar consumer-style endpoint and has overlapping troubleshooting notes.