Migrate Yahoo Mail to Outlook: IMAP Move with App Passwords

Yahoo Mail to Outlook is a server-to-server IMAP migration, which sounds simple until you run into Yahoo's two specific gotchas. The first is that Yahoo refuses regular passwords for IMAP — third-party tools must use app passwords or the connection fails with AUTHENTICATIONFAILED. The second is that Yahoo throttles aggressively, both on concurrent connections and on sustained APPEND traffic, in ways that surprise people moving from Gmail or Microsoft 365 where the limits are more forgiving. Plan around both and the migration runs cleanly. Ignore them and you spend the day on retry loops.

Two destinations called "Outlook"#

Same naming problem as everywhere else. "Outlook" can mean Outlook.com (the free consumer service) or Microsoft 365 (the paid business service with Exchange Online). The IMAP host differs, the auth model differs slightly, and the throughput limits differ.

This guide covers both because the source-side work — getting Yahoo Mail ready to be read by an IMAP client — is the same regardless of which Outlook you are heading to. Where the destination matters, the guide calls out the difference.

Outlook.com:

• IMAP host: imap-mail.outlook.com, port 993, SSL
• Auth: OAuth2 or app password when MFA is on
• Mailbox quota: 15 GB free, more with Microsoft 365 personal subscription

Microsoft 365:

• IMAP host: outlook.office365.com, port 993, SSL
• Auth: OAuth2 with IMAP.AccessAsUser.All scope
• Mailbox quota: 50 GB or 100 GB depending on plan

If you are unsure which destination applies, sign in at outlook.com. Consumer interface means Outlook.com. Corporate "Outlook on the web" means Microsoft 365. For the M365 case, also read migrate Yahoo to Office 365 which covers the conditional access and tenant-side details specific to corporate moves.

Yahoo source setup#

The source side is where most Yahoo migrations stall, almost always because of authentication.

Generate the app password#

Yahoo turned off password-based IMAP login years ago for third-party clients. Real password authentication returns AUTHENTICATIONFAILED no matter how correct the password is.

To get an app password:

1. Sign in to mail.yahoo.com
2. Click the account icon, then Account info
3. Open Account security
4. Confirm two-step verification is on. App passwords require 2-step verification to be enabled — Yahoo will not show the option without it.
5. Click Generate app password
6. Name it something memorable. "Outlook Migration" is fine.
7. Yahoo displays a 16-character password without spaces. Copy it now. You cannot see it again.

That string is the password the migration tool uses with the user's Yahoo email address. The user's actual Yahoo password is never used during migration.

The app password walkthrough has more detail on Yahoo's specific edge cases — recovery options, regional differences, and the rare cases where 2-step won't enable.

Confirm IMAP settings#

Yahoo's IMAP endpoints:

• IMAP: imap.mail.yahoo.com, port 993, SSL required
• SMTP (if needed): smtp.mail.yahoo.com, port 465 or 587

Test the connection from your migration host:

openssl s_client -connect imap.mail.yahoo.com:993 -crlf -quiet
A1 LOGIN user@yahoo.com <app-password>

You should see OK LOGIN completed. If not, the app password is wrong or 2-step is off.

Inventory the source mailbox#

In Yahoo Mail, the storage indicator at the bottom shows total mailbox size. Note it. Free Yahoo accounts have 1 TB of storage so the mailbox can be very large in absolute terms.

Note the folder structure. Yahoo's standard folders are Inbox, Sent, Drafts, Spam (Bulk Mail), Trash, plus user-created folders. Yahoo also has a feature called "Recent" that is a saved view, not a folder — it does not need migrating.

Set up Yahoo forwarding (paid only)#

If the user has Yahoo Mail Plus (the paid subscription), enable server-side forwarding so mail received during the migration window also lands in the destination. Free Yahoo accounts cannot forward server-side. For free accounts, plan a cleanup pass at the end of the migration to capture any mail that arrived during the move.

Outlook destination setup#

Setting up the destination depends on which Outlook you are heading to.

For Outlook.com#

Enable IMAP on the target account. In Outlook.com settings, search for IMAP and confirm it is on. Generate an app password if MFA is on and your tool doesn't support OAuth2 — at account.microsoft.com under Security > Advanced security options.

For Microsoft 365#

Confirm IMAP is enabled on the mailbox in the Exchange admin centre under Recipients > Mailboxes > the user > Manage email apps. Register an Azure AD application with the IMAP.AccessAsUser.All delegated permission for OAuth2 authentication. Check conditional access policies for anything that might block the migration tool's traffic.

Confirm mailbox quota#

A Yahoo mailbox can be much larger than the Outlook destination quota. A 100 GB Yahoo mailbox migrating to a 15 GB Outlook.com mailbox will fail somewhere around the 15 GB mark. Plan the destination quota first: upgrade Microsoft 365 plan or trim source content if needed.

Running the migration#

1. Test both endpoints

   From the migration host, connect to imap.mail.yahoo.com:993 with the app password and to the destination IMAP server with its credentials. Confirm both authenticate before going further.

2. Map Yahoo folders to Outlook folders

   Inbox to Inbox, Sent to Sent Items, Drafts to Drafts, Trash to Deleted Items, Bulk Mail to Junk Email. User-created folders map straight across. If a Yahoo folder contains the slash character (rare but possible), check that your tool escapes it correctly during the IMAP CREATE on the destination.

3. Cap parallelism

   Two to three concurrent IMAP connections on the Yahoo side. Yahoo throttles aggressively above that. The Outlook destination can usually accept more, but the source is the bottleneck here.

4. Pilot one folder

   Migrate a mid-sized folder first. Verify in Outlook that messages appear, dates are right, attachments open, read/unread flags are preserved, and threading works.

5. Run the full migration

   Plan around 50–80 MB per minute against Yahoo's throttle. Run overnight for mailboxes over a few GB. Resume after rate-limit recovery if interrupted.

6. Pick up calendar and contacts separately

   In Yahoo Mail, go to Contacts and click More > Export to download as CSV. For Calendar, find the calendar settings and export as ICS. Import both into the Outlook destination separately.

7. Reconfigure clients

   Update Outlook desktop, Outlook for Mac, and mobile devices to the new account. Confirm the user can read and send before final cutover.

8. Forward and decommission

   For paid Yahoo accounts, set forwarding to the new Outlook address. For free accounts, run a final incremental pass after cutover to capture any mail that landed in Yahoo during the window. Keep the Yahoo account active for 30–60 days as a safety net.

Throughput and limits#

Yahoo is one of the tighter IMAP sources. Plan around:

• 2–3 concurrent IMAP connections per account
• 50–80 MB per minute realistic throughput
• Roughly 25 MB per-message attachment limit (Yahoo's send limit; receive is higher but pulling messages over IMAP rarely hits issues)
• Aggressive APPEND rate limiting on the source side — Yahoo can stall a fast connection within minutes

If you hit a Yahoo throttle, you typically see one of:

• Connection stalls without error for 5–15 minutes
• BAD command rejected on otherwise-valid commands
• Slow response to FETCH with a noticeable lag growing per command
• Outright connection drop with no error message

Stop, wait 30 minutes, lower parallelism to 1 connection, resume. Pushing harder extends the throttle.

Errors worth recognising#

AUTHENTICATIONFAILED against Yahoo — almost always means the app password is wrong or 2-step is off. Regenerate the app password.

AUTHENTICATIONFAILED against Outlook — MFA on, real password used. Generate an app password or switch to OAuth2.

Too many simultaneous connections against Yahoo — drop to 1–2 connections.

Message too large for destination — Outlook.com rejects messages over 150 MB. Skip these or migrate manually.

Folder UTF-7 conversion error — non-ASCII folder name encoding mismatch. Rename source folder to ASCII.

OAuth2 token expired against Outlook — tool should refresh automatically.

Verification#

A done Yahoo-to-Outlook migration looks like:

• Per-folder count comparison between Yahoo Mail and Outlook. Counts should match within a small margin.
• Spot-check ten messages per major folder: date, sender, body, attachments, threading.
• Search in Outlook for known senders to confirm reachability through search.
• Calendar and contacts imported separately and visible in Outlook.
• Forwarding (paid Yahoo) or final incremental pass (free Yahoo) ensures recent mail landed in the destination.
• The user can sign in, read, send, and use Outlook desktop or mobile with the new account.

Keep the Yahoo account active with forwarding (paid) or with periodic check-ins (free) for at least 30 days. Missing-message reports surface weeks after cutover.

What about Yahoo aliases?#

Yahoo lets free accounts create up to 500 disposable aliases. Mail to those aliases lands in the main mailbox. The migration copies the mail correctly. What does not migrate is the alias configuration itself — the user loses their disposable addresses and the auto-routing rules associated with them.

If aliases are important, document them before cutover. Outlook.com supports email aliases too (up to about ten per account), so the user may want to recreate the most-used aliases on the new account.

Related routes#

If the destination is Gmail or Google Workspace, see migrate Yahoo to Gmail. The label-versus-folder model is the main difference.

If the destination is specifically Microsoft 365 corporate rather than Outlook.com consumer, see migrate Yahoo to Office 365 for the tenant-side considerations.

If the direction is the opposite and you are moving Gmail content into Yahoo, migrate Gmail to Yahoo covers the same general server-to-server pattern with Yahoo as destination.

The app password walkthrough has Yahoo-specific edge cases. The complete email migration guide covers higher-level planning that applies to any source-destination pair.