How to Migrate Yahoo Mail to Gmail

Yahoo-to-Gmail migrations look easy until you discover three things: legacy Yahoo accounts can be enormous (30 to 60GB is normal for a 20-year-old mailbox), Yahoo's IMAP server throttles aggressive parallel connections, and the destination matters more than you think. A consumer Gmail account, a Google Workspace tenant, and Gmail's own "Check mail from other accounts" all have different procedures. This guide walks you through each path, with the operational specifics for a clean Yahoo-to-Gmail move that does not stall halfway through.

Why Yahoo as a source is its own thing#

Yahoo Mail accounts have been around since 1997. The active ones have a lot of history. It is not unusual to inherit a Yahoo mailbox that is 40GB, contains 250,000 messages, and has folders the user has not opened in twelve years. Three things follow from that.

First, sizing matters. A 40GB source mailbox needs a destination that can take it. Consumer Gmail gives 15GB shared across Drive and Photos; Workspace tenants get more per user. Either upgrade Google One on the destination or accept that some messages will not fit.

Second, throughput matters. At a safe two-to-four-thread concurrency, a 40GB mailbox takes one to two days end-to-end. Plan the cutover window accordingly. Pushing more threads to speed it up does not work — Yahoo will refuse the connections.

Third, the source has app-password requirements that catch people off guard. Yahoo no longer accepts the normal account password for IMAP. You have to enable two-step verification on the Yahoo account, then generate an app password at account.yahoo.com. The string looks like abcdefghijklmnop and Yahoo shows it once.

Prerequisites and pre-flight checks#

Setup work is light on the Yahoo side but matters on the Gmail destination side, especially if you are migrating to Workspace.

On the Yahoo side#

• Two-step verification enabled at account.yahoo.com → Account Security. App passwords do not exist without it.
• A generated app password labelled for the migration. Copy the 16-character string immediately — it cannot be viewed again.
• A mailbox size estimate. The Yahoo web interface does not show total size cleanly; the easiest way is to add the account to a desktop client and let it index briefly.
• Forwarding rules and filters documented. They will not migrate over IMAP. If they matter, recreate them on the Gmail side after.

On the Gmail destination side#

• A provisioned destination mailbox. For consumer Gmail, the account must exist and IMAP must be on. For Workspace, the user must exist in the tenant.
• IMAP enabled at gmail.com → Settings → See all settings → Forwarding and POP/IMAP.
• Sufficient storage. Yahoo legacy mailboxes can be huge. For 40GB+ sources, the destination Gmail account needs Google One storage or a Workspace plan that covers it.
• Either OAuth set up through your migration tool (preferred) or an app password generated at myaccount.google.com → Security → App passwords. 2-Step Verification must be on.

For background on what an app password is and why both providers require one, see the app password glossary entry. For the IMAP terminology that surfaces in the migration logs, the IMAP protocol glossary is the quick reference.

The migration procedure#

Three real paths exist. Pick one based on scale and destination.

• Gmail's built-in import ("Check mail from other accounts" or "Import mail and contacts") for a single consumer Gmail destination, small to medium mailbox. Easiest to start, weakest control.
• Google Workspace Data Migration Service for tenant-wide moves into Workspace. Runs server-to-server, scales across many users.
• Desktop IMAP migration tool for everything else, especially large mailboxes or migrations with mapping requirements.

The procedure below covers the IMAP path because it is the most general; the path-specific notes are called out where they differ.

1. Confirm the destination Gmail or Workspace mailbox

   Sign in to the destination Gmail or Workspace mailbox through the web interface. Confirm IMAP is on at Settings → See all settings → Forwarding and POP/IMAP. If using Workspace, confirm the user exists in the admin console and the right licence is assigned. If using consumer Gmail and you expect over 15GB, upgrade Google One first.

2. Enable two-step verification on Yahoo

   Go to account.yahoo.com → Account Security. Turn on two-step verification. Yahoo will verify via SMS or call. Save the backup codes. The Generate app password option appears only after 2SV is on.

3. Generate a Yahoo app password

   Still in Account Security, click Generate app password. Label it Mailbox Taxi migration or similar. Yahoo shows the 16-character string once in a modal in the form abcdefghijklmnop. Save it to your password manager immediately. The label is just for your reference — Yahoo does not enforce it.

4. Audit the Yahoo source

   Add the Yahoo account to a desktop client temporarily so you can see the folder list and rough size. Note:

   • Total mailbox size in GB.
   • The folder tree. Yahoo uses real IMAP folders, so this is what you actually have.
   • Sent and Draft folders' contents (they migrate separately from regular folders).
   • Bulk Mail (Yahoo's spam folder) — usually skipped.
   • Any forwarding rules and filters, which will need to be recreated on the Gmail side after.
5. Pick your migration path

   Three options:

   • Gmail's built-in import: At gmail.com → Settings → See all settings → Accounts and Import → Import mail and contacts. Enter the Yahoo address and app password. Gmail will pull messages in the background. Adequate for under 5GB.
   • Workspace Data Migration Service: At admin.google.com → Data Migration. Set up an IMAP source pointing at imap.mail.yahoo.com, add users with their app passwords, start the migration. Best for tenant-wide moves.
   • Desktop IMAP tool: Add Yahoo as source (imap.mail.yahoo.com:993 SSL) and Gmail as destination (imap.gmail.com:993 SSL). Configure mappings. Run.
6. Configure folder-to-label mapping

   Set explicit mappings for Yahoo's special folders:

   • Yahoo Sent → Gmail [Gmail]/Sent Mail
   • Yahoo Draft (singular) → Gmail [Gmail]/Drafts
   • Yahoo Bulk Mail → skip (or → [Gmail]/Spam if you really want it)
   • Yahoo Trash → skip

   For every other Yahoo folder, decide whether to preserve nesting (Gmail will create nested labels with slash separators) or flatten. Gmail handles nesting fine, so preserving is usually right.

7. Pilot one mailbox

   Run one mailbox or one folder end-to-end. Open the result in Gmail's web interface. Verify:

   • Sent label has the expected message count, with the correct From addresses.
   • Drafts label has drafts (and not just empty placeholders).
   • Attachments open.
   • Unicode subjects render correctly.
   • Dates match the original Yahoo dates, not the migration date.
   • Nested folders translated to slash-separated labels cleanly.

   A clean pilot saves a full-batch rerun.

8. Run the full migration

   Start the full run with 2 to 4 IMAP threads per mailbox. Yahoo will throttle anything above that. Monitor the log for:

   • AUTHENTICATIONFAILED — usually means the Yahoo app password was revoked.
   • Too many simultaneous connections — drop concurrency.
   • Message too large for destination — Gmail's 25MB inline limit being hit. Log these for manual handling.
   • OAuth2 token expired on the Gmail side — re-authenticate and resume.

   Expect rough throughput of one to two GB per hour per mailbox at safe concurrency.

9. Verify and cut users over

   Compare per-folder message counts. Allow small variance on Drafts (Gmail and Yahoo handle draft auto-saves differently). Once verification looks clean, update the user's mail client to point at imap.gmail.com (port 993, SSL) and smtp.gmail.com (port 465 or 587). Tell the user when to switch. If you set up forwarding from Yahoo to Gmail during overlap, leave it running for two weeks so any senders who still have the Yahoo address do not lose mail.

Gotchas specific to Yahoo-to-Gmail#

The pair-specific issues that come up often enough to plan for.

Throttling is real and the symptoms are vague. Yahoo will accept a fifth IMAP connection, take a few commands on it, then start dropping responses. The migration log shows hangs and timeouts rather than a clean error. Drop concurrency to 2 if you see slow progress.

Legacy Yahoo accounts have weird Sent folders. Old Yahoo accounts sometimes have Sent, Sent-old, Sent Items, and Sent Messages all from various client reconfigurations. Inspect the folder list and consolidate before mapping.

Yahoo's Drafts folder is Draft, singular. Many tools default to mapping Drafts (plural) which does not exist on Yahoo. The Yahoo drafts then look empty. Map Draft explicitly.

Gmail's import wizard misses messages. Gmail's built-in import is convenient for under 5GB but it is known to skip messages silently when it hits errors. For anything important, use a desktop IMAP tool with proper logging.

Yahoo Mail Plus accounts behave the same as free. Yahoo Mail Plus removes ads and gives more storage, but the IMAP behaviour is identical. Throttling limits are the same. Do not assume Plus lets you push more threads.

Forwarding loops are easy to create. If you set up Yahoo-to-Gmail forwarding during the overlap window and Gmail also forwards to Yahoo (because of an old rule), you get a loop. Audit forwarding rules on both sides before enabling either direction.

Errors you will see#

The pattern-matching list for the most common log lines.

• AUTHENTICATIONFAILED from Yahoo. App password revoked or two-step verification disabled. Regenerate.
• AUTHENTICATIONFAILED from Gmail. App password revoked, or OAuth scopes wrong. Re-authorise.
• Too many simultaneous connections from imap.mail.yahoo.com. Drop concurrency to 2.
• Message too large for destination — Gmail's 25MB inline ceiling. Log and handle by manual upload to Google Drive.
• STARTTLS handshake failed. Port or TLS mode misconfiguration. Use 993 with SSL on both sides.
• OAuth2 token expired. The token refresh failed mid-run. Re-authenticate and resume.
• Folder UTF-7 conversion error on Yahoo folders with non-ASCII names. Rename the folder on the Yahoo side, then retry the affected folder.

If you are migrating in the reverse direction, see migrate Gmail to Yahoo. If the destination is Microsoft 365 instead of Gmail, see migrate Yahoo to Office 365. For another classic-provider source, see migrate AOL to Gmail.

Communicating the cutover#

For Yahoo-to-Gmail migrations the cutover is usually simpler than a business move because the source domain is consumer (no MX change), but user communication still matters.

A reasonable cadence for a multi-user move: one week out, send a setup guide with Gmail IMAP and SMTP settings and screenshots for the most common mail clients. Three days out, a reminder. The day of cutover, a 30-minute heads-up. The day after, a wrap-up with a contact for any issues. If the migration is just for one user (a relative moving off Yahoo), a phone call works better than email.

Schedule cutover for a Friday evening or Saturday morning. Migrations take a long time on the Yahoo side, so the run itself probably started a day or two earlier. The cutover is just the client reconfiguration and the forwarding turn-on. Plan a 14-day Yahoo-to-Gmail forwarding overlap so anyone with the old address keeps reaching the user.

For broader strategy around DNS, scheduling, and rollback in larger migrations, see the complete email migration guide. It is written for the multi-mailbox case but the planning approach is the same.