Migrate Outlook.com to iCloud Mail (2026 Guide)

Moving from Outlook.com to iCloud Mail is mostly a consumer-side migration — people consolidating their mail into the Apple ecosystem after years of Hotmail-then-Outlook-then-whatever-Microsoft-calls-it-now. The mechanics are clean (both sides speak IMAP), but the auth flow has gotten complicated on both ends: Outlook requires app passwords when 2FA is on, iCloud requires app-specific passwords always, and Apple's password generation flow has moved twice in the last three years. This guide walks the path with the current auth specifics and the gotchas that aren't obvious until you hit them.

What you're moving#

Outlook.com mailboxes are typically smaller than corporate Exchange mailboxes (usually under 15 GB) but carry years of accumulated mail from the Hotmail-to-Live-to-Outlook era. The data layout is:

In the IMAP path: Inbox, Sent Items, Drafts, Deleted Items, Junk Email, Archive, and any user-created folders. Standard IMAP metadata (read/unread, flagged, replied) all carries across.

Outside the IMAP path: Categories (Microsoft's color-coded tag system applied to messages), Quick Steps (saved actions), automatic-reply rules, Inbox rules (Outlook.com server-side filters), Contacts (stored in People app, not in mailbox), Calendar, Tasks, and any Skype integration.

The mail itself migrates cleanly. The Outlook.com-specific overlays don't — plan for them separately if they matter.

Preparing iCloud Mail#

Verify iCloud Mail is active#

Not every Apple ID has iCloud Mail enabled by default. Check at icloud.com/mail — if you see a mailbox UI, it's active. If you see a setup prompt, follow it to create your @icloud.com address (or use an existing @me.com or @mac.com address if you have one).

Note your iCloud email address. This is the destination. You may have:

• name@icloud.com (modern accounts)
• name@me.com (mid-era Apple accounts)
• name@mac.com (early Apple accounts)

All three work as iCloud Mail addresses and aliases — they all point to the same mailbox.

Plan iCloud storage#

Your destination iCloud account needs storage for the entire migrated mailbox plus future mail. Add up:

• Current iCloud usage (Settings → iCloud → Manage Storage).
• Outlook.com mailbox size to be migrated.
• 20% buffer for future growth.

Upgrade to an iCloud+ tier with enough total capacity. Common tiers:

• 50 GB ($1/mo)
• 200 GB ($3/mo)
• 2 TB ($10/mo)
• 6 TB ($30/mo)
• 12 TB ($60/mo)

(Pricing varies by region; check apple.com for current rates.)

Generate the iCloud app-specific password#

At appleid.apple.com:

1. Sign in to your Apple ID.
2. Go to Sign-In and Security.
3. Click App-Specific Passwords → Generate Password.
4. Label it "Migration" (helpful for revoking later).
5. Copy the generated password — Apple shows it once.

This is the password your migration tool will use to authenticate to iCloud IMAP. Your regular Apple ID password will NOT work because 2FA is enabled (and Apple enforces 2FA on all accounts).

For broader context on app passwords across providers, our app password glossary entry covers the mechanics.

Preparing Outlook.com#

Confirm IMAP is enabled#

Outlook.com supports IMAP by default. If you want to verify or have had issues with it before, check at outlook.live.com → Settings → Mail → Sync email → POP and IMAP. IMAP should show as enabled.

Generate an Outlook app password (if 2FA is on)#

At account.live.com:

1. Sign in.
2. Go to Security.
3. Advanced Security Options.
4. App Passwords → Create a new app password.
5. Copy the generated password.

If 2FA is off (it shouldn't be in 2026), the regular Microsoft account password works for IMAP. Verify the auth flow with the password you plan to use before starting bulk migration.

IMAP connection details#

For Outlook.com:

• Host: outlook.office365.com
• Port: 993
• Security: SSL/TLS
• Username: full email address (e.g., user@outlook.com)
• Password: app password (or regular password if 2FA disabled)

Document folders and categories#

Before migration, log into Outlook.com and note:

• Folder structure (sidebar).
• Categories in use (View → Show Filter → Categories).
• Rules (Settings → Mail → Rules).
• Aliases (Settings → Account → Manage your aliases).

The folder structure migrates. Categories don't — note them so you can recreate as folders on iCloud if important.

Migration tool selection#

iCloud doesn't have a built-in migration importer, so you have one practical path: a desktop IMAP tool.

Desktop IMAP tool#

Mailbox Taxi or a similar tool authenticates to both Outlook (via app password) and iCloud (via app-specific password) and runs IMAP-to-IMAP migration. Desktop-first, with concurrency control and per-message logging.

This is the only realistic option for Outlook-to-iCloud because:

• Microsoft doesn't offer Outlook-to-iCloud migration tooling (they offer Outlook-to-other-Microsoft).
• Apple doesn't offer migration import (iCloud has no equivalent of Fastmail's Import or Gmail's DMS).
• Doing it manually with Outlook (the desktop app) configured for both accounts works for small mailboxes but is slow and error-prone for anything over 1 GB.

For broader context on email migration approaches across destinations, the complete email migration guide covers the landscape.

Step-by-step#

1. Pilot with one folder

   Before running the full migration, test with a single small folder. Pick a folder with 100–500 messages — large enough to be representative, small enough to migrate in minutes.

   Run the migration. Validate:

   • Folder appears on iCloud Mail.
   • Message count matches.
   • Sender/recipient/date headers are intact.
   • Attachments are present and openable.

   If anything's wrong here, fix it before you commit to the full migration.

2. Run the bulk migration

   Configure your tool with:

   • Source: outlook.office365.com:993 SSL, username = Outlook address, password = Outlook app password.
   • Destination: imap.mail.me.com:993 SSL, username = Apple ID, password = iCloud app-specific password.

   Cap concurrency at 3 threads. Outlook.com throttles aggressively above 4 simultaneous IMAP connections per account; iCloud throttles destination writes above similar limits.

   Expected throughput: roughly 1–2 GB per hour for a 5 GB mailbox. A 15 GB mailbox typically takes 8–12 hours overnight.

   Common errors during this stage:

   • Too many simultaneous connections on Outlook side — drop concurrency.
   • OAuth2 token expired if you used OAuth instead of app password — refresh.
   • Message too large for destination — iCloud's inbound size limit (~20 MB) is lower than Outlook's. Oversized messages will skip.
   • STARTTLS handshake failed — usually a transient network blip; retry.
3. Set up forwarding from Outlook to iCloud

   While bulk is running, set up forwarding so new mail also lands at iCloud.

   In Outlook.com → Settings → Mail → Forwarding → Enable forwarding → enter your iCloud address. Check "Keep a copy of forwarded messages" if you want to keep them on Outlook too (recommended during transition).

   After this is enabled, any new mail arriving at Outlook is also delivered to iCloud. This is your safety net during the migration window.

4. Update senders or domain ownership

   Outlook.com to iCloud migrations usually don't involve a domain change — both are consumer providers with their own domains (outlook.com, hotmail.com vs icloud.com). If you're moving away from Outlook entirely, notify senders to use your new iCloud address. There's no MX change because you don't own outlook.com.

   If you DO own a custom domain currently using Outlook (via Microsoft 365 personal Outlook custom domain), then this is a different migration entirely — see the Outlook to Gmail guide for domain-based Outlook migrations which work similarly.

5. Run the delta sync

   24–48 hours after bulk completes, run a delta against the Outlook source. With forwarding configured, the delta should be small — most new mail arrived at iCloud via forwarder.

   UID-based dedup means previously migrated messages don't duplicate.

6. Set up iCloud as your primary client

   On Mac: Mail app → Mail → Add Account → iCloud → sign in. Mail will sync with iCloud Mail.

   On iPhone: Settings → Mail → Accounts → Add Account → iCloud (it's usually already there if you're signed into iCloud on the device, just enable Mail).

   On Windows: iCloud for Windows handles mail through Outlook if you want; otherwise use any IMAP client with imap.mail.me.com and the app-specific password.

   On the web: icloud.com/mail.

7. Update Reply-To and verify outbound

   Send a test message from iCloud to an external account. Verify it arrives with the correct From address. If outbound goes through correctly, you can start telling senders to use your iCloud address as primary.

   In Outlook.com, optionally set up a vacation auto-reply directing senders to your new iCloud address: Outlook → Settings → Mail → Automatic replies → Send automatic replies.

8. Decide what to do with Outlook

   Two paths:

   • Keep Outlook.com active as a forwarding-only account. New senders use your old address; mail forwards to iCloud. This is the recommended path if you can't realistically notify every sender.
   • Close the Outlook account. Risky — anyone with the old address will bounce. Only do this if you're confident nothing important is incoming.

   If you keep Outlook open, leave forwarding enabled indefinitely. Microsoft won't close inactive accounts for several years.

Common failure modes#

AUTHENTICATIONFAILED on iCloud#

Almost always the regular Apple ID password instead of an app-specific password. Generate an app-specific password at appleid.apple.com and use that. Apple stopped accepting regular passwords for third-party IMAP years ago.

AUTHENTICATIONFAILED on Outlook.com#

Either an outdated app password (Microsoft sometimes invalidates old ones during security events) or the wrong username format. Use the full email address; don't use just the prefix.

Message too large for destination#

iCloud's inbound size limit is roughly 20 MB. Outlook.com allows up to 150 MB attachments. Messages over 20 MB will be rejected by iCloud. Log them; decide per-message what to do (extract attachments and email separately, or save to iCloud Drive).

Folder names not appearing#

Outlook's Junk Email folder is sometimes named "Junk Email" literally, sometimes hidden. iCloud's equivalent is "Junk". Most tools handle the mapping; verify in pilot.

Categories lost#

Expected. Outlook's categories don't survive IMAP migration. Document them, recreate critical ones as folders on iCloud if needed.

Sent items in two places#

Outlook.com's IMAP exposes both "Sent Items" and "Sent" in some configurations. Most tools handle the dedup; verify pilot result.

Folder UTF-7 conversion errors#

If you have folders with non-ASCII characters (Chinese, Arabic, accented characters), your tool needs to handle modified UTF-7 encoding correctly. Modern tools do; verify on pilot.

Comparing alternatives#

For the reverse direction — iCloud to Outlook — the iCloud to Outlook walkthrough covers the same auth specifics in reverse.

For moves between cloud providers without the Apple ecosystem dependency, Outlook to Gmail and Gmail to iCloud provide adjacent paths.

Validation#

Per-mailbox:

• Folder structure matches between Outlook and iCloud.
• Message counts per folder within 1%.
• Sent items present.
• Inbox shows recent mail correctly.
• Test message from external account arrives at iCloud.
• Mail app on Mac/iPhone shows new account correctly.

Account-level:

• iCloud has enough storage for current + future mail.
• Outlook forwarding set up and working.
• App-specific passwords stored securely.
• Reply-To set correctly on iCloud outbound.

When validation passes, the migration is done. Keep Outlook.com active as a forwarder indefinitely unless you're certain you've notified all senders.