Migrate

Migrate Outlook to Yahoo Mail: IMAP Move Guide for 2026

Move mail from Outlook.com or Microsoft 365 to Yahoo Mail using IMAP. App passwords, folder mapping, throttling limits, and a clean step-by-step path.

DO

Dan Okafor

MSP Practice Lead

· 11 min read
Envelopes stacked on a desk representing email migration

You opened Outlook.com one morning and decided you wanted out. Maybe the redesign annoyed you, maybe Microsoft 365 lapsed and you don't want to renew, maybe you just like Yahoo Mail's interface better. Whatever the reason, you now have years of mail sitting in folders in Outlook and you need it copied — intact, in the right folders, with attachments — into a Yahoo Mail account. This guide walks the IMAP path that actually works in 2026, including the auth quirks that trip up almost every first attempt.

Outlook
Yahoo Mail

Skip the manual setup — let Mailbox Taxi handle it

One desktop app, every IMAP provider, zero data leaving your machine.

Understand what "Outlook" means in your case

The word "Outlook" covers four different things, and the migration path changes depending on which one you have:

  • Outlook.com / Hotmail / Live — Microsoft's free consumer mail. IMAP is enabled by default and uses your normal Microsoft account password (no app password needed if you don't have 2FA, app password required if you do).
  • Microsoft 365 Personal or Family — Same Outlook.com infrastructure underneath, just with a custom domain or extra storage. Treat it like Outlook.com.
  • Microsoft 365 Business / Exchange Online — A tenant-managed mailbox. IMAP works but the admin may have disabled it tenant-wide. You may need to ask them to flip IMAP back on for your account.
  • Outlook the desktop client — Just a program. Your actual mail lives in one of the above. The migration source is the underlying mailbox, not Outlook the app.

For the rest of this guide, assume you're going from an Outlook.com or Microsoft 365 mailbox to a free Yahoo Mail account. The same approach works for Yahoo Mail Plus, just with a higher storage ceiling on the destination side.

What you need before you touch anything

Stop and gather these now. Pausing the migration halfway to hunt for an app password is the most common reason runs fail.

  • Outlook account email and password. If you have 2FA on, generate an Outlook app password at account.microsoft.com under Security → Advanced security options.
  • Yahoo Mail account, already created and verified. If you just made it, send yourself one test message from another address and reply to it. Yahoo sometimes shadow-bans new accounts that immediately start receiving thousands of inbound IMAP writes.
  • Yahoo app password. Sign in to Yahoo, go to Account Info → Account Security → Generate app password. Name it something like "Mailbox Taxi migration" so you can revoke it later. You'll get a 16-character string with no spaces. Copy it now; you cannot view it again.
  • A current folder inventory from Outlook. Right-click your mailbox in the Outlook web client and look at the folder list. Note any custom folders, nested subfolders, and the size of each. This becomes your verification checklist.
  • Roughly 90 minutes of uninterrupted runtime per 10 GB of mail. Yahoo is slower than Gmail or iCloud on inbound IMAP appends. Plan accordingly.

Yahoo app passwords are one-shot

Yahoo only shows the generated app password once. If you close the dialog without copying it, you have to generate a fresh one and revoke the old. Paste it into a password manager or a temporary text file the moment it appears.

Server settings you'll need

Both providers use standard IMAP/SMTP endpoints. Get these wrong and you'll spend an hour chasing phantom authentication errors.

Outlook.com / Microsoft 365 IMAP (source, read):

  • Server: outlook.office365.com
  • Port: 993
  • Encryption: SSL/TLS
  • Username: your full email address
  • Password: your account password (or app password if 2FA is on)

Yahoo Mail IMAP (destination, write):

  • Server: imap.mail.yahoo.com
  • Port: 993
  • Encryption: SSL/TLS
  • Username: your full Yahoo address (example@yahoo.com)
  • Password: the 16-character app password you just generated

If your Outlook tenant is Microsoft 365 Business and basic auth has been disabled, you'll need OAuth2 against outlook.office365.com instead of password auth. Mailbox Taxi handles this natively; older Perl-based tools generally don't.

Folder mapping: where most migrations get ugly

Outlook and Yahoo don't agree on what to call special folders. Decide your mapping before the migration runs, not during.

Outlook folderYahoo equivalentNotes
InboxInboxDirect map, no issues
Sent ItemsSentYahoo uses singular "Sent"
DraftsDraftYahoo uses singular "Draft"
Deleted ItemsTrashYahoo's trash auto-purges after 30 days
Junk EmailBulk MailSpam filtering rules differ; expect re-classification
ArchiveArchive (custom)Yahoo has no native Archive; create a folder
Outbox(skip)Local-only queue, never has real mail in it

Custom folders copy across as-is. Nested subfolders work fine in both directions. The one place to be careful is folder names with slashes — Yahoo treats / as a hierarchy delimiter, so a folder named 2024/Q1 in Outlook becomes a parent 2024 with a child Q1 in Yahoo. If that breaks your filing system, rename slashes to dashes before migrating.

Step-by-step migration

  1. Enable IMAP and prepare both accounts

    In Outlook.com web, go to Settings → Mail → Sync email and confirm "Let devices and apps use POP" is on (this also enables IMAP). In Yahoo, confirm you can log in with the app password by adding the account to a throwaway client like Thunderbird and watching it sync. If Thunderbird won't connect, the migration tool won't either, and you've saved yourself two hours of debugging.

  2. Run a 50-message test migration

    Pick a single small folder — a sent-items archive from 2018, a project folder you no longer touch. Copy just that folder to Yahoo first. Confirm: folder appears in Yahoo, message count matches, attachments open correctly, dates are preserved. If any of these fail on 50 messages, they will fail on 50,000. Fix the auth or folder-naming problem before continuing.

  3. Map folders explicitly

    In your migration tool, override the default mapping for the special folders listed in the table above. Don't trust auto-detection — Outlook localises folder names in non-English accounts (a German Outlook calls Sent Items "Gesendete Elemente") and most tools fail silently on that.

  4. Run the full migration single-threaded

    Yahoo's IMAP server starts throwing Too many simultaneous connections errors above 5 concurrent connections per account, and LIMIT errors above roughly 500 messages appended per minute. Set your tool to one connection, 250-message batches, and let it run. A 20 GB mailbox typically takes 18–28 hours.

  5. Verify counts and re-run gaps

    When the run completes, compare folder-by-folder message counts between Outlook and Yahoo. Discrepancies of 1–3 messages per folder are usually drafts or items being edited mid-migration; anything larger is a real gap. Re-run the affected folders only.

  6. Set up forwarding and cutover

    Once counts reconcile, set Outlook to forward incoming mail to Yahoo (Settings → Mail → Forwarding). Keep Outlook live for at least 60 days while you redirect senders, password-reset accounts, and update your email address everywhere it appears. Don't close the Outlook account on day one.

Run during off-peak hours

Yahoo's IMAP servers are noticeably faster between roughly 02:00 and 09:00 UTC. Starting a large migration at midnight local time on a weekday is the slowest possible window. If you can schedule overnight US-time or early morning EU-time, you'll see 30–50% better throughput.

Throttling and the errors you'll actually see

Real-world errors you should expect, and what they mean:

  • AUTHENTICATIONFAILED Invalid credentials on Yahoo — almost always means you used your normal Yahoo password instead of the app password. Regenerate the app password and retry.
  • OAuth2 token expired on Outlook — your Microsoft tenant token has a 1-hour lifetime. Any decent migration tool refreshes automatically; if yours doesn't, you'll need to re-authenticate mid-run.
  • Too many simultaneous connections on Yahoo — you exceeded 5 concurrent IMAP sessions. Drop to 1–2 and the error stops within a minute.
  • Message too large for destination — Yahoo has a 25 MB per-message limit. Large Outlook messages with embedded attachments will fail. Either extract attachments to cloud storage and replace with links, or accept the loss and log the failed message IDs.
  • Folder UTF-7 conversion error — Outlook stores folder names in modified UTF-7. A small number of non-ASCII folder names (accented characters, CJK) confuse some tools. Rename the source folder to plain ASCII before migrating.

What does not move

Be honest with yourself about scope. IMAP is mail-only. None of these come across:

  • Calendar events. Export from Outlook as ICS, import to Yahoo Calendar.
  • Contacts. Export as CSV from Outlook People, import into Yahoo Contacts.
  • Rules and filters. Yahoo's filter syntax differs from Outlook's. Rebuild manually — usually 10–20 rules for a heavy user, an afternoon's work.
  • Categories and flags. Outlook's coloured categories don't have a Yahoo equivalent. Star/important flags partially survive as Yahoo stars, but coloured categories are dropped.
  • Aliases. If you sent mail from you+work@outlook.com, the alias itself doesn't migrate. You can add aliases in Yahoo Mail Plus.
  • Shared mailboxes. If your Outlook account had access to a shared mailbox, that's a separate account and a separate migration.

Why a desktop migration tool beats the alternatives

You have three real options:

  1. Yahoo's built-in import. Yahoo's "Check mail from other accounts" pulls messages via POP3, not IMAP. It collapses everything into the Inbox and skips folder structure entirely. Useless for anything beyond a couple of hundred messages.
  2. A cloud SaaS migration service. These work, but they require you to hand both passwords to a third party, hold mail in transit on their servers, and bill per gigabyte. For a 20 GB personal migration they're overkill.
  3. A desktop IMAP migration tool like Mailbox Taxi. Runs locally on your machine, both providers see direct IMAP connections from your IP, no mail ever leaves your network in transit. You pay once, run it as many times as you need, and you can pause/resume.

For a single personal mailbox the difference is mostly privacy and cost. For an MSP doing 30 mailboxes for a small business, the desktop approach saves real money.

If you're thinking longer term — keeping Outlook open for archive and moving day-to-day mail to Yahoo — see the reverse direction Yahoo to Outlook migration guide for the round-trip considerations. If you're hopping Outlook to Gmail instead, the Outlook to Gmail migration walkthrough covers Google-side rate limits in more depth. And if you're really moving to Apple's ecosystem rather than Yahoo, the Outlook to iCloud Mail guide is the right detour. The broader complete email migration guide covers cross-provider planning that applies regardless of source and destination.

Post-migration checklist

After the cutover, run through this in the first 48 hours:

  • Send a test message from an outside account to your old Outlook address and confirm it forwards to Yahoo.
  • Update your reply-from default in Yahoo to your Yahoo address (not the forwarded Outlook one).
  • Verify Yahoo's spam folder for the first week — legitimate mail from contacts who used to email Outlook sometimes gets initially mis-classified.
  • Reconfigure any DMARC-aware mailing lists that previously verified your Outlook domain.
  • Update your password recovery email on critical accounts (bank, government, work) to your Yahoo address. This is the single most-forgotten step.
  • After 60–90 days of confirming nothing breaks, decide whether to close Outlook or keep it as a permanent forward.

The Yahoo app password is your single most fragile dependency — if Yahoo invalidates it for any reason (you changed your account password, you ran the migration from an unusual IP, the app password aged out), the whole migration halts. Treat it like a real credential, store it in a password manager, and revoke it explicitly the moment your migration ends.

Try Mailbox Taxi

Migrate your mailbox the easy way

Join the waitlist for early access and lock in launch pricing.

Related reading

Try Mailbox Taxi

Migrate your mailbox the easy way

Join the waitlist for early access and lock in launch pricing.