Migrate Office 365 to Yahoo Mail Without Losing Folders

You're moving mail off Office 365 into a Yahoo Mail account. The reasons vary: a contract ending, a Microsoft 365 license going away, consolidating into the personal address you've had since 2003. Either way, the path is IMAP-to-IMAP, but the throttling profile, app-password requirements, and folder naming conventions are different enough on each side that a naive drag-and-drop in Outlook will leave you with duplicates, missing messages, or both. This guide walks through the move with the specific quirks called out.

Who this is for#

Two audiences end up doing this migration regularly.

The first is people losing access to a Microsoft 365 plan, either because they're retiring, a side business is closing, or an employer is decommissioning their account at the end of a contract. They want a copy of their mail history in an account that's free, durable, and doesn't tie them to a subscription.

The second is family-account consolidators. Someone has been forwarding mail from Yahoo to Office 365 for years because Outlook was their work client, and now wants to flip the script: Yahoo as the canonical mailbox, Office 365 as the archive being decommissioned.

Both groups face the same problem. Office 365 expects business-grade tooling on the way out. Yahoo expects you to pretend you're a 2010 IMAP client. Bridging that gap is what this guide is about.

What carries over and what doesn't#

Get the expectations right upfront.

Messages, headers, attachments, dates, and read/unread state move cleanly. So does folder hierarchy, including nested folders, as long as you map the reserved names correctly.

Flagged messages mostly survive because IMAP exposes \Flagged on both sides. Yahoo renders it as a star.

Outlook color categories do not survive. Yahoo has no equivalent. You'll lose the color metadata. If you depend on categories for filing, export a list of which messages had which categories from Outlook before migrating, in case you need to reconstruct any of it manually.

Calendar items, contacts, tasks, and notes do not move. This is a mail-only migration. Export calendar data to ICS and contacts to vCard separately, then import them into Yahoo's calendar and contacts through the web interface.

Office 365 retention tags and labels are Microsoft-specific properties. They don't survive the IMAP copy. If you have legally-required retention, plan for that with an archiving tool, not a migration tool.

Setup, in order#

There's a specific sequence that avoids backtracking. Do these steps in order.

Confirm IMAP is enabled on Office 365#

New Microsoft 365 tenants ship with IMAP disabled. Sign into the Microsoft 365 admin center as an admin, find the user under Active users, click into their mailbox, and check Manage email apps. IMAP must be on. If it's not, enable it and wait 15 minutes for the change to propagate before testing.

Generate a Microsoft app password if MFA is on#

If the mailbox has multi-factor auth enabled and the tenant uses Security Defaults, basic auth IMAP requires an app password. Go to mysignins.microsoft.com/security-info, click Add method → App password, give it a label, and copy the password. Save it to your password manager. You can read more about why these are necessary in our app passwords reference.

Generate a Yahoo app password#

Yahoo refuses regular passwords for third-party IMAP clients. Sign into your Yahoo account, go to Account Info → Account Security → Generate app password, name it "Migration", and copy the 16-character password Yahoo shows. You only see this once.

Note Yahoo's IMAP settings#

Yahoo's IMAP server is imap.mail.yahoo.com on port 993 with SSL. Username is your full Yahoo email address. SMTP is smtp.mail.yahoo.com on 465 with SSL or 587 with STARTTLS.

Verify Yahoo's mailbox is empty (or you know what's in it)#

Yahoo's 1 TB free quota means storage isn't usually the worry, but if the destination already has a mailbox of mail in it, the migration will merge into existing folders. If you want a clean overlay, archive or delete the existing Yahoo mail first. Otherwise plan for the merge.

Pick the right tool#

You have three paths.

Outlook drag-and-drop. Add both accounts to desktop Outlook (Yahoo via IMAP), then drag folders between them. This works for very small mailboxes but loses fidelity on anything over a few GB. Outlook's drag operations are not transactional, so a dropped connection halfway through a folder leaves you with partial copies and no clean resume.

Exchange admin center IMAP migration. This pulls into Office 365, not out of it. Wrong direction.

Desktop migration tool. Runs on your workstation, connects to both sides over IMAP, tracks per-message state, retries on transient failures, and avoids creating duplicates if you restart. Mailbox Taxi falls in this category. We'll use it for the rest of the guide.

For broader source-side context, see the Office 365 migration guide.

Step-by-step#

1. Verify Office 365 IMAP credentials work

   Before involving the migration tool, confirm the source credentials work. Open Thunderbird or any IMAP client and add the Office 365 account with host outlook.office365.com, port 993, SSL, the full email as username, and either the regular password (if MFA is off) or the app password from setup. List the folders. If they load, credentials are good. If you get AUTHENTICATIONFAILED, fix that before doing anything else.

2. Verify Yahoo IMAP credentials work

   Same test for the destination. Add the Yahoo account in Thunderbird with imap.mail.yahoo.com:993 SSL, full Yahoo address as username, and the 16-character app password from setup. Confirm folders list and you can manually append a test message. If Yahoo rejects the password, you used the regular Yahoo password instead of the app password.

3. Add both accounts in Mailbox Taxi

   Open the desktop app. Add Office 365 as the source IMAP server using the credentials confirmed in step 1. Add Yahoo as the destination IMAP server using the credentials confirmed in step 2. The tool will enumerate folders on both sides and show you a side-by-side list.

4. Configure folder mapping

   Yahoo's reserved folders are Inbox, Sent, Drafts, Spam, Trash, Archive. Office 365's reserved folders are Inbox, Sent Items, Drafts, Junk Email, Deleted Items, Archive. Map Sent Items to Sent, Deleted Items to Trash, and Junk Email to Spam, or exclude Junk Email entirely (recommended unless you have specific reason to keep spam history). Custom folders map one-to-one with their hierarchy preserved.

5. Run a small test batch

   Pick one folder with 100 to 500 messages, ideally with a mix of plain text, HTML, and attachments. Migrate just that folder. Open the result in Yahoo Mail (mail.yahoo.com) and verify message dates match, attachments open, HTML renders, and read/unread state is correct. If anything looks off, fix the configuration before running the full job.

6. Run the full migration overnight

   Start the full job in the evening with concurrency set to 2 or 3 connections. Yahoo throttles aggressively past 4 connections from a single IP. Mailbox Taxi will back off automatically on Too many simultaneous connections, but starting conservative avoids the early retry storms. Expect 6 to 12 hours per 10 GB.

7. Verify counts and spot-check

   When the job finishes, compare folder message counts between source and destination. Small differences (a few messages per folder) usually mean the tool deduplicated genuine duplicates from the source. Larger differences need a delta run. Open ten random messages across different folders and verify they look right.

Yahoo's throttle behavior#

A few specifics save you from chasing phantom problems.

Yahoo limits concurrent IMAP connections to around 4 to 5 from a single IP. Past that you'll get connection drops and Too many simultaneous connections. Three is the sweet spot for steady throughput.

Per-message append rate caps at roughly 2 messages per second per connection. With 3 connections that's about 6 messages per second, or 20,000 messages per hour. Mailboxes with many small messages will hit the message-count ceiling, not the byte ceiling.

Yahoo's per-message size limit is around 25 MB. Messages larger than that will fail to append with Message too large for destination. Office 365's default is 150 MB, so any messages over 25 MB on the source won't make it across cleanly. You'll get a list of failed messages at the end of the run.

Connection idle timeout is about 30 minutes. Long pauses between commands on a connection trigger a disconnect. A reasonable migration tool keeps connections active with periodic NOOPs.

After the migration#

The technical move is half the work. The cutover is the other half.

Set up forwarding from Office 365 to Yahoo. In Outlook on the web, go to Settings → Mail → Forwarding and forward to your Yahoo address. Keep a copy in the source mailbox for the first 30 days so you have an audit trail.

Reconfigure your mail clients. Remove the Office 365 account from Outlook, Apple Mail, your phone. Add the Yahoo account. The phone in particular usually requires the app password again because IMAP from a mobile client counts as a third-party app.

Update recovery emails and 2FA fallbacks. If your Office 365 address was the recovery email for any important services, switch them to Yahoo before the source mailbox goes dark.

Hold the Office 365 license for 30 days. Even after a clean migration, keep the source mailbox available for a month. Senders replying to old threads, old service notifications, and forgotten subscriptions surface during this window. Forwarding handles most of it. The licensed mailbox is your safety net for anything forwarding misses.

If you're considering Gmail as an alternative destination, the Office 365 to Gmail walkthrough covers a slightly different rhythm with much higher quotas. For the reverse direction, the Yahoo to Office 365 guide walks through bringing Yahoo mail into Microsoft 365. If you're choosing between iCloud and Yahoo as a personal landing pad, the iCloud destination guide has a similar shape.

Common errors#

AUTHENTICATIONFAILED from Office 365: IMAP is disabled at the mailbox level, or basic auth is blocked and you need an app password.

AUTHENTICATIONFAILED from Yahoo: you're using your regular Yahoo password instead of the app password. Regenerate one.

Too many simultaneous connections from Yahoo: reduce concurrency to 2 or 3.

Message too large for destination from Yahoo: the message is over Yahoo's per-message size limit. Save the attachment separately and either drop the message or re-import it with a note.

Folder UTF-7 conversion error: Office 365 has a folder name with characters Yahoo's IMAP doesn't accept in IMAP-modified UTF-7. Rename the source folder to plain ASCII before re-running.

Yahoo also occasionally returns generic BAD responses without explanation. In our experience these are transient: wait a minute, retry, and they clear. Persistent BAD responses on a specific message usually mean the message is malformed (bad MIME headers, illegal characters in From line). Skip those, finish the job, and handle them by hand.