Migrate AOL Mail to Google Workspace: 2026 IMAP Guide

AOL Mail in 2026 mostly exists as a decades-deep archive. People who signed up in 1996 still have those accounts, still receive mail there from old contacts, and now want it all moved to a real business mail platform with a custom domain. AOL itself runs on Yahoo's backend (the two services merged operationally after Verizon's acquisition and subsequent sale to Apollo), which means the migration mechanics are nearly identical to a Yahoo migration. What makes AOL different is the archive — 25+ years of mail with all the encoding quirks, format weirdness, and folder hierarchy strangeness that early consumer email collected. This guide walks the IMAP path that handles AOL's quirks and gets you to a clean Workspace destination.

Why this migration is more common than it sounds#

You'd think AOL accounts would have died out by now. They haven't. The typical scenarios:

• Long-time AOL users moving to a business. Someone with name@aol.com since 1998 starts a business, gets a domain, wants their personal email history in the business Workspace.
• Estate and household consolidation. Inherited accounts, family members consolidating multiple AOL accounts into one shared Workspace.
• Small businesses that never modernised. Sole proprietors who used AOL for years are forced into Workspace by clients or contracts requiring a custom domain.
• Archive preservation. People who want to keep AOL mail searchable and accessible long after AOL itself eventually shuts down.

The last point matters. AOL Mail is not actively being killed, but it's also not getting much investment. Migrating to Workspace is partly insurance against future service decay.

When this migration makes sense#

AOL to Workspace is the right move when:

• You want a custom domain mail experience with proper admin controls.
• You're consolidating personal AOL mail into a business identity.
• You need compliance, audit logs, or eDiscovery — none of which AOL provides.
• You want to preserve a decades-deep archive in a platform that's actively maintained.

For a personal one-way move with no business need, AOL to Gmail consumer migration is the simpler path.

Pre-flight on the Workspace destination#

Set up the destination cleanly first.

• Create the Workspace organisation at workspace.google.com. Business Standard (2 TB pooled storage) is the most common tier for migrations of personal AOL archives, since those mailboxes are usually 5–30 GB.
• Verify your destination domain. Add it during Workspace setup, complete TXT verification. Don't change MX yet.
• Provision destination users. Map each AOL address to a Workspace user. If consolidating an AOL personal address (name@aol.com) to a business address (name@company.com), document the mapping pre-migration.
• Set licenses. Pool licenses across the org. Workspace storage is pooled, so heavy AOL archives consume from the org pool rather than per-user quotas.
• Configure aliases. AOL allows multiple usernames per account (a legacy from screen names). Decide which become real Workspace aliases.
• Disable spam quarantine for migration source IPs. Apps → Gmail → Routing → Content compliance. Old mail from the 1990s/2000s often trips modern spam classifiers because formatting differs from today's norms.

Pre-flight on the AOL source#

AOL prep is per-user. There is no AOL admin console for businesses.

1. Each user signs in to AOL Mail and generates an app password. account.aol.com → Account Security → Generate app password. Name it "Workspace migration". Copy the 16-character app password immediately; AOL only shows it once.
2. Confirm IMAP works. Add the AOL account to a throwaway IMAP client like Thunderbird. Watch it sync. If this fails, the migration tool will fail too.
3. Inventory folders. AOL Mail's folder structure varies wildly. Personal accounts often have nested folders going back years (2003/Q2, Family/Mom/Birthday). Screenshot the folder tree as your verification checklist.
4. Check for unusually old messages. Messages from before 2005 sometimes have encoding issues that confuse modern IMAP tools. Find your oldest folder and inspect a few messages — make sure they render correctly in AOL Mail before migrating.

Server settings#

AOL Mail IMAP (source):

• Server: imap.aol.com
• Port: 993
• Encryption: SSL/TLS
• Username: full AOL address (yourname@aol.com)
• Password: 16-character app password

Google Workspace IMAP (destination):

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

AOL also accepts imap.aim.com (legacy AIM domain) and imap.netscape.com (legacy Netscape mail) for accounts originally created on those services. They all route to the same backend.

Folder mapping with archive considerations#

AOL's folder model translates cleanly to Gmail labels.

AOL source	Workspace destination	Notes
Inbox	Inbox	Direct map
Sent	Sent	Sent flag preserved
Drafts	Drafts	Migrated but rarely useful
Trash	Trash	30-day auto-purge
Spam	Spam	Workspace re-classifies
Old Mail	Label "Old Mail"	AOL auto-archives messages 30+ days old here; keep the label
Saved Mail	Label "Saved Mail"	User-archived; keep the label
Custom folders	Labels with same name	Each folder becomes a label
Nested folders	Nested labels	Forward-slash delimiter both sides
Flagged	Starred	AOL flags → Gmail stars

The "Old Mail" folder is AOL-specific. AOL automatically moves messages out of Inbox into Old Mail after 30 days unless the user has touched them. For an archive migration, Old Mail often contains the bulk of historical content — don't accidentally skip it.

Step-by-step migration#

1. Set up Google Workspace Data Migration Service

   Apps → Data Migration → Set up data migration → Choose Mail. Source server: imap.aol.com, port 993, encryption SSL/TLS. Authentication: username/password with app password. AOL isn't in the DMS preset list — choose "Other IMAP server" and enter manually.

2. Build the user mapping CSV

   Columns: source_email,destination_email,password. Most rows map AOL addresses to Workspace addresses. For each row, you'll need that user's AOL app password — collect via a secure form.

3. Run a pilot of one user, one small folder

   Before full migration, do a small pilot of one user with just one small folder selected (a Sent folder from a recent year, ideally). Validate: folder appears in Workspace as expected label, message counts match, attachments open, dates preserve. Encoding issues from old AOL mail will show up here if anywhere.

4. Test encoding handling on the oldest folder

   Run a second pilot pointed at the oldest folder in the source (anything pre-2005). This is where AOL's legacy encoding most often breaks. If sender names show as =?UTF-8?B?... instead of decoded text, your migration tool isn't handling AOL's modified UTF-7 properly. Switch to a tool that handles it (Mailbox Taxi, GWMME with custom config) before continuing.

5. Run the full migration in small waves

   AOL/Yahoo backend throttles per account at roughly 5 concurrent IMAP connections. DMS handles waves of 10–20 users in parallel without hitting that, but each user's per-account throughput stays low. Plan 15–25 hours per 10 GB user mailbox.

6. Reconcile counts and re-run gaps

   Compare AOL folder counts (via IMAP from a throwaway client) with Gmail label counts. Discrepancies above 1% need investigation. Re-run affected users individually with DMS incremental.

7. Cutover MX records

   Update DNS to point MX at Workspace SMTP. AOL was the source of personal email for decades; many old contacts still send to the AOL address. Set up AOL → Workspace forwarding via AOL's Settings → Forwarding before MX cutover, and keep it active for 6–12 months as safety net.

Errors you'll see in production#

• AUTHENTICATIONFAILED Invalid credentials on AOL — almost always means the user used their normal AOL password instead of the app password.
• Too many simultaneous connections on AOL — IP-level throttling on the shared Yahoo/AOL backend. Reduce wave concurrency.
• Folder UTF-7 conversion error — common on old AOL folder names with accented characters or international encoding. Rename source folders to plain ASCII pre-migration.
• Message too large for destination — Workspace accepts 50 MB inbound; AOL caps outbound at 25 MB. Rare unless AOL admin raised the limit (they didn't, but check).
• OAuth2 token expired on Workspace destination — re-auth migration admin.
• Encoding garbage in sender names or subjects — old AOL mail often uses modified UTF-7 or Latin-1. Modern tools convert transparently in most cases; if you see =?ISO-8859-1?Q?... literals on the destination, switch tools.
• STARTTLS handshake failed on AOL — use port 993 SSL/TLS, not 143 STARTTLS.

What doesn't move#

• AOL Calendar. Service discontinued. If anything's left, it's in Yahoo Calendar (same backend) — export as ICS from there.
• AOL Address Book / Contacts. Export as CSV from AOL Mail web → import to Google Contacts.
• AOL Notes / AOL Today. Defunct services with no migration path.
• AOL Instant Messenger. Long discontinued. No mail-side artifacts to migrate.
• AOL Custom Stationery. AOL's HTML-formatted "stationery" sometimes embeds in old mail; modern Gmail renders the HTML but loses the editing context.
• AOL filters. Gmail's filter syntax differs. Document and rebuild the top 10 manually.

A few archive-specific considerations#

AOL archives have characteristics other migrations don't:

1. Attachments in old proprietary formats. AOL used to compress attachments into .aim or proprietary formats. Modern AOL converts them to standard MIME, but extreme legacy mail (1990s) may have attachments that don't open in Gmail. Plan to accept some losses.
2. Embedded images using old URLs. Mail from 2002 with embedded images often references AOL CDN URLs that no longer exist. Images appear broken in Gmail. Nothing to be done; the source content is permanently gone.
3. Sender display names in legacy encoding. Names like "François" or "Müller" may show as Fran=E7ois in old AOL mail. Modern tools convert; ancient ones don't.
4. Trash and Spam folders are usually empty. AOL purges aggressively. Don't expect to recover anything from these folders.

For broader context, see the Google Workspace migration guide for tenant prep and licensing. The simpler single-user personal path is in AOL to Gmail. For the inverse business destination, AOL to Microsoft 365 covers the M365 path. The AOL app password reference is essential reading. And for general IMAP migration patterns, IMAP to Gmail covers source-agnostic flow.

After cutover#

• Days 1–3. Final DMS delta runs. Monitor Workspace inbound mail for AOL-originated forwards.
• Days 4–10. Rebuild filters, signatures, contact lists in Workspace.
• Days 11–30. Set up AOL → Workspace forwarding for ongoing inbound mail. AOL is full of old contacts who still send to the AOL address; forwarding catches them for the next year+ while you redirect each manually.
• Day 60+. Decide whether to close AOL or keep it as a permanent forward. For a decades-old account with hundreds of unknown old contacts, keeping the forward indefinitely is usually safer.
• Critical: update account recovery emails. Most users have set their AOL address as the recovery email for bank accounts, government services, and other critical accounts. Audit and update before closing AOL, not after.

The single biggest gotcha with AOL migrations is post-cutover discovery of services that recovery-email to the old AOL address. Make a list of every account where the recovery email is name@aol.com and update each one to the new Workspace address. This is the most-forgotten step and the most painful to fix after the fact.