Migrate Yahoo Mail to Google Workspace: 2026 IMAP Guide

Yahoo to Google Workspace is one of the most common small-business migrations of 2026, mostly because small businesses outgrew personal Yahoo accounts and want their domain mail in a real admin-managed tenant. The migration itself is operationally straightforward — Yahoo speaks standard IMAP, Workspace's Data Migration Service supports Yahoo natively, and the folder model maps cleanly. The complications are throughput (Yahoo throttles harder than any other major provider) and the fact that you're often migrating accounts that have been used personally for 15+ years with eccentric folder hygiene. This guide is the operational plan that gets you to a clean cutover.

When this migration makes sense#

Yahoo to Workspace is the right move when:

• Your business outgrew personal Yahoo accounts and you want admin-managed mail with custom domain.
• You want shared mailboxes, group accounts, calendar resources, and other Workspace features that Yahoo Mail Plus doesn't offer.
• You need compliance, audit logs, eDiscovery, or Vault retention — none of which Yahoo provides.
• You're consolidating multiple personal Yahoo accounts into a single Workspace tenant for a small team.

It's also a reasonable path for a single individual who's been on Yahoo for years and wants to switch ecosystems entirely. For that case, Yahoo to Gmail consumer migration is the simpler walkthrough.

Pre-flight on the Workspace destination#

Get the destination tenant clean first.

• Create the Workspace organisation. Sign up at workspace.google.com, choose Business Starter, Standard, or Plus based on storage and feature needs. Business Standard (2 TB pooled) is the most common choice.
• Verify your destination domain. Add it during Workspace setup and complete the TXT verification. Don't change MX yet.
• Provision destination users. For each Yahoo user being migrated, create a Workspace user with the destination email address. If you're moving from personal Yahoo (alice.smith@yahoo.com) to a business domain (alice@company.com), document the mapping in a CSV before you start.
• Set per-user licensing. Each Workspace user needs a license. Workspace storage is pooled, so a 30 GB Yahoo mailbox doesn't fail on per-user quota — it consumes from the org pool.
• Configure aliases. If Yahoo users have multiple addresses (Yahoo allows up to 500 disposable addresses), decide which translate to Workspace aliases on the destination user and which die at cutover.
• Disable spam quarantine for migration source IPs. Apps → Gmail → Routing → Content compliance → bypass spam for messages from migration tool IPs. Otherwise 5–10% of historical mail will be misrouted to quarantine.

Pre-flight on the Yahoo source#

Yahoo source prep is per-user, not tenant-wide. There is no Yahoo admin console for businesses (Yahoo Small Business shut down in 2022).

1. Each user signs in to Yahoo and generates an app password. account.yahoo.com → Account Security → Generate app password. Name it "Workspace migration". Copy the 16-character string immediately; Yahoo only shows it once.
2. Confirm IMAP works. From a throwaway IMAP client, add the Yahoo account with the app password and watch it sync at least one folder. If this fails, the migration tool will fail too.
3. Document custom folders. Yahoo's folder structure varies wildly across users. Right-click in Yahoo Mail web and screenshot the folder list, or use IMAP to enumerate. This becomes your verification checklist.
4. Check for unusually large folders. Yahoo has no published per-folder limit, but mailboxes with single folders >5 GB run noticeably slower. Consider splitting large folders pre-migration.

Server settings#

Yahoo Mail IMAP (source):

• Server: imap.mail.yahoo.com
• Port: 993
• Encryption: SSL/TLS
• Username: full Yahoo address
• Password: 16-character app password

Google Workspace IMAP (destination):

• Server: imap.gmail.com
• Port: 993
• Encryption: SSL/TLS
• Username: full destination Workspace address
• Password: account password, OAuth, or app password

Folder mapping#

Yahoo's folder model and Gmail's label model translate cleanly in this direction (since Gmail labels accept any folder structure).

Yahoo source	Workspace destination	Notes
Inbox	Inbox	Clean direct map
Sent	Sent	Sent flag preserved
Draft	Drafts	Migrated but usually stale
Trash	Trash	30-day auto-purge
Bulk Mail	Spam	Workspace re-classifies on its own filter
Custom folders	Labels with same name	Each Yahoo folder becomes a Gmail label
Nested folders	Nested labels	Forward-slash delimiter both sides
Starred	Starred	Yahoo stars → Gmail stars
Archive (Yahoo custom)	Label "Archive" or merge with All Mail	Decide pre-migration
Yahoo Calendar	Google Calendar	Separate workstream — ICS export/import
Yahoo Contacts	Google Contacts	Separate workstream — vCard export/import

Running the migration via DMS#

1. Open Google Workspace Data Migration Service

   Apps → Data Migration → Set up data migration → Choose Mail. Source server: imap.mail.yahoo.com, port 993, encryption SSL/TLS. Source authentication: username/password with each user's app password.

2. Build the user mapping CSV

   Two columns: source_email,destination_email. Most entries map Yahoo addresses to Workspace addresses (alice@yahoo.com,alice@company.com). For each row, you'll need that user's Yahoo app password — collect via a secure form, not email.

3. Test with a pilot of one user

   Add a single user to the DMS migration. Watch the status. Pilot timing tells you what a full wave looks like. Validate destination mailbox: labels appear with expected names, counts match, attachments open, sent flag preserves.

4. Build production waves of 10–20 users

   Yahoo's per-account throttling is the bottleneck, but DMS does multiple users in parallel. Cap waves at 10–20 users to stay inside Yahoo's tenant-level connection limits (Yahoo enforces these at the IP level — too many simultaneous connections from one source IP triggers temporary blocks).

5. Monitor errors and re-run gaps

   Common errors: AUTHENTICATIONFAILED (Yahoo app password mismatched — regenerate), Too many simultaneous connections (Yahoo IP-level throttling — reduce wave concurrency), Message too large for destination (rare; Gmail accepts 50 MB inbound, Yahoo caps outbound at 25 MB), Quota exceeded (Workspace pooled storage hit). Re-run failed users individually.

6. Reconcile counts

   For each migrated user, compare Yahoo folder counts (via IMAP from a throwaway client) with Gmail label counts (Gmail API messages.list per label). Discrepancies above 1% need investigation. Re-run affected users with incremental DMS.

7. Cutover MX records

   Update DNS to point MX at Workspace SMTP (aspmx.l.google.com and four backup MX records). Schedule for a low-traffic window. Run one more DMS delta 24 hours post-cutover.

Errors you'll see in production#

• AUTHENTICATIONFAILED Invalid credentials on Yahoo — almost always means the user used their normal Yahoo password instead of the app password, or the app password was regenerated and the old one stored.
• Too many simultaneous connections on Yahoo — IP-level throttling. Reduce wave concurrency to 5–10 users.
• OAuth2 token expired on Workspace — refresh failed; re-auth migration admin.
• Quota exceeded — Workspace pooled storage limit. Upgrade tier or skip large folders.
• Message too large for destination — rare; check whether source has any unusual messages over 25 MB.
• Folder UTF-7 conversion error — non-ASCII folder names. Rename or accept mangled label names.
• STARTTLS handshake failed on Yahoo — your tool used port 143 with STARTTLS. Use port 993 SSL/TLS directly.

What doesn't move#

• Yahoo Calendar. Limited ICS export; events migrate but invitee responses and recurring exceptions are unreliable.
• Yahoo Contacts. vCard export → Google Contacts import. Yahoo's CSV export sometimes loses phone number formatting; vCard is better.
• Yahoo Notes. No Workspace equivalent. Export manually, save as text or import into Google Keep.
• Yahoo filters. Gmail's filter syntax is different. Rebuild top 10 manually.
• Yahoo disposable addresses. Yahoo's 500 disposable addresses per account don't translate. Decide which become real Workspace aliases pre-migration.
• Yahoo Briefcase / Photos / Messenger. All defunct or separate services with no migration path.

When DMS isn't the right tool#

DMS handles most cases. Look at alternatives when:

1. You have 1–3 users only. Setting up DMS for a single user is overkill; a desktop IMAP tool finishes in 1–2 hours.
2. You don't want to share app passwords. DMS needs each user's Yahoo app password centrally. A desktop tool lets each user run their own migration locally.
3. You want fine-grained control over folder order, scheduling, or attachment handling. DMS is one-size-fits-all; a desktop tool gives you all the knobs.
4. You're consolidating multiple Yahoo accounts into one Workspace user. DMS doesn't merge; it migrates 1:1. Desktop tools can merge with label prefixes.

For broader context, see the Google Workspace migration guide for tenant prep and licensing. The single-user personal path is covered in Yahoo to Gmail. For the inverse direction, Yahoo to Microsoft 365 is the closest sibling guide for an alternate destination. The Yahoo app password reference is essential reading before starting. And for IMAP migration patterns regardless of source, IMAP to Gmail covers the general flow.

After cutover#

• Days 1–3. Final DMS delta runs. Monitor Workspace inbound mail. Watch for users still typing the old Yahoo address.
• Days 4–10. Rebuild filters, signatures, mailbox delegation. Workspace filters take ~15 minutes per user to recreate from Yahoo filter exports.
• Days 11–20. Decommission Yahoo accounts. For business users, deactivate at account.yahoo.com → Terminate. Keep one Yahoo account active as forwarder for 60 days.
• Days 21–30. Final reconciliation report. Archive DMS logs.
• Day 60+. Close remaining Yahoo accounts. Update vendor records, password-recovery emails, and account-recovery email on critical services.

The single most-forgotten step: account recovery emails. Most users have set Yahoo as the recovery address on bank accounts, social media, and government services. After Yahoo closes, they're locked out of password recovery. Audit and update before deactivating Yahoo, not after.