Migrate AOL Mail to Office 365: IMAP Cutover Guide

Office 365 has become the default landing pad for personal mailboxes that have outgrown AOL. The reasons are practical rather than glamorous: a Business Basic licence costs less per year than half a streaming subscription, the storage allowance is roomy, and the same mailbox works in Outlook on the desktop, in the browser, and on mobile without any per-app contortions. The hard part is getting twenty years of AOL out cleanly. AOL's IMAP server has rough edges that punish naive migration scripts, and Exchange Online's IMAP receive side has its own folder quirks, especially around the Recoverable Items quota and Junk Email. This guide walks through the migration as a single mailbox cutover. The same shape works for half-a-dozen mailboxes in a small office, with one extra round of planning for licence assignment and tenant DNS. If you have run this play before for a Yahoo migration, most of the AOL-side steps will feel familiar.

What needs to be in place#

Office 365 will not let you sign in to a mailbox that does not have a licence. That sounds obvious, but the most common failure on day one is the migration tool authenticating to a brand-new tenant account whose Exchange Online licence has not actually attached yet. Microsoft 365 admin centre sometimes shows the licence as applied while the back end is still provisioning. Wait until you can sign in to Outlook on the web at outlook.office.com and see an empty inbox before you start.

You also need:

• The full AOL address and a current AOL app password.
• An Office 365 user account with Exchange Online Plan 1 or higher, or a bundled SKU that includes it.
• Either the user's password or an app-style credential for the destination. If your tenant enforces modern authentication only, the migration tool needs to support OAuth on the Office 365 side.
• A workstation that will stay awake for the duration. Plan on 90 to 180 minutes per 10 GB, slower if AOL throttles.

If your tenant has Conditional Access policies blocking IMAP or basic auth, your admin needs to allow the migration account's source IP, or use a tool that supports OAuth-based IMAP against Exchange Online. The Microsoft side has been moving away from basic IMAP for years and many tenants now block it outright.

Connection settings#

• AOL IMAP host: imap.aol.com
• AOL IMAP port: 993 with SSL/TLS
• AOL credential: full address plus app password
• Office 365 IMAP host: outlook.office365.com
• Office 365 IMAP port: 993 with SSL/TLS
• Office 365 credential: user principal name plus password or OAuth token

Some migration tools talk to Exchange Online via the EWS or Graph API rather than IMAP. Either works for an inbound migration, but IMAP is the simplest path for a single mailbox and is what this guide assumes.

Steps#

1. Audit the AOL mailbox

   Open AOL Mail in a browser and walk the folder tree. Note approximate size and message counts for each major folder. Empty Spam unless you actively need it for forensic reasons. Empty Trash. If you have any AOL Mail filters, screenshot them so you can recreate the important ones as Outlook rules later. Make a note of whether the AOL account has any forwarding already configured; if it does, you may need to disable it before the migration so messages do not arrive in two places at once.

   If the mailbox is genuinely huge (over 50 GB), consider archiving the oldest folders to a local PST first and migrating only the recent traffic. AOL gets visibly slower on very large mailboxes and a 50 GB single-stream pull can take more than a day.

2. Generate an AOL app password

   AOL does not allow IMAP login with the regular account password any more. Go to login.aol.com/account/security, enable two-step verification if it is off, and use the App Password option to generate a fresh credential. Label it Migration so you can revoke it cleanly afterwards. Copy the 16-character string and use it as the IMAP password in the migration tool.

   Treat the app password like a credential

   The app password lets anyone with it log in to your AOL mailbox over IMAP, bypassing two-step verification. Do not paste it into a shared chat. Revoke it the moment the migration is verified.

3. Provision the Office 365 mailbox

   In the Microsoft 365 admin centre, create the user if it does not already exist and assign a licence that includes Exchange Online. Wait until you can sign in to Outlook on the web before continuing. While you are in the admin centre, check whether IMAP is enabled on the user's mailbox under Mail > Manage email apps. Some tenants disable IMAP by default.

   If the mailbox will host a custom domain like @yourdomain.com, complete the domain verification and MX changes after the migration finishes, not before. Doing it the other way around will route fresh AOL mail into a half-empty Office 365 mailbox while you are still trying to copy the history across.

4. Run a small dry run

   Pick a folder of 50 to 200 messages. The Sent folder is usually a good candidate because it covers a wide date range without being huge. Configure the migration tool to copy only that folder. Run it. Then open Outlook on the web for the Office 365 account and verify:

   • The folder appears in the Office 365 tree with the same name.
   • Original sent dates are preserved.
   • Read and unread states match the source.
   • Attachments open correctly.
   • Non-ASCII characters in subjects render correctly.

   If any of these fail, fix the configuration before you commit to the multi-hour full run. Most issues at this stage come from tools that default to UTC date handling or that strip MIME parts they do not recognise.

5. Run the full migration

   Start the full sync in the evening. AOL is happiest with one or two concurrent IMAP connections. The destination side, Exchange Online, will accept four or more easily, but the bottleneck is AOL. Let the tool pick its defaults unless you have a reason to override them.

   Plug in the machine. Disable sleep on lid close. Leave the network on. Most migration tools log progress as they go and survive a brief network blip, but a half-hour disconnect from the source side can force a full folder rescan when the connection comes back.

   Expect AOL to drop the session once or twice in the middle of large folders. The tool should reconnect automatically. You will see logs like BYE Connection closed followed by a fresh LOGIN.

6. Verify and cut over

   After completion, log in to Outlook on the web and run targeted searches:

   • A five-year-old PDF attachment.
   • A thread with accented characters in the subject.
   • A flagged or starred message — note that AOL flags map roughly to Outlook flags but not perfectly.
   • A draft, if AOL Drafts had anything you cared about.

   Compare folder counts. Numbers will be within a few percent if the source mailbox was quiet during the run.

   Set up AOL forwarding to the new Office 365 address under AOL Settings > More Settings > Mail Forwarding. If you are keeping the AOL address as a vanity identity, add it as an alias in Office 365 Admin > Users > the user > Manage email aliases. This needs the AOL domain verified in the tenant, which is more trouble than it is worth for personal use; most people simply forward.

Gotchas worth knowing#

Exchange Online has a Recoverable Items quota separate from the visible mailbox quota. If you migrate then immediately delete folders to tidy up, the deleted items still count toward the underlying storage for two weeks. On a large migration this can briefly tip the mailbox over its size limit and cause 552 5.2.2 Mailbox full rejections on inbound mail. Wait two weeks before doing a big cleanup, or have the admin purge Recoverable Items.

AOL's IMAP server does not advertise the CONDSTORE extension, so migration tools cannot rely on modification sequence numbers for incremental syncs. Each pass walks the folder and asks for UID lists. On very large folders this means the first pass is the long one and resumes are almost as expensive. Plan to do it in one go if you can.

Exchange Online also routes anything that looks even mildly suspicious into Junk Email during the initial population. Newsletters from a defunct mailing list, very old marketing emails, and threads with broken DKIM all land in Junk. After the run, walk the Junk Email folder and move false positives back to Inbox.

Errors you will probably see#

• AUTHENTICATIONFAILED against AOL — wrong app password or two-step not enabled.
• LOGIN failed: Basic authentication is disabled against Office 365 — the tenant has disabled basic IMAP. Switch to OAuth or have the admin temporarily enable IMAP for the migration mailbox.
• Too many simultaneous connections — AOL throttling. Drop concurrency to one stream.
• Message too large for destination — rare, since AOL caps outbound at well under the 150 MB Exchange limit, but log entries with this error are usually corrupted source messages.
• 552 5.2.2 Mailbox full — Exchange Online quota tripped, often because of Recoverable Items pressure rather than visible mailbox size.

Communication plan#

For a single personal mailbox, AOL forwarding plus a Send Mail As alias in Office 365 covers most needs. For a small office, write a one-paragraph email and send it from the new Office 365 mailbox a day before the cutover. Two sentences are enough: "On Saturday morning I am moving my mailbox from AOL to Microsoft 365. From Saturday onward please send to new@domain.com; the AOL address will forward for ninety days." Most contacts will update their address book on the next reply. For billing and 2FA recovery, update those manually because forwarders are not a long-term solution.

If you are looking at this as part of a wider corporate move, the full Office 365 migration guide covers tenant prep, DNS sequencing, and Conditional Access in more depth than makes sense here. For mixed environments where some users want a personal account instead, the parallel AOL to Gmail walkthrough and AOL to Outlook.com guide cover the same source side with different destinations. The general IMAP to Office 365 reference is useful when the source is something other than AOL.

When to walk away and try again later#

If AOL is throttling you so aggressively that the run is making no progress, stop and try at a different time. The throttles relax overnight in the source's home timezone (US East coast), and a run started at 22:00 Eastern often completes by morning when a run started at 14:00 stalls for hours. If Exchange Online is rejecting batches with quota messages, pause for an hour and resume. The throttles reset on a rolling window and most single-mailbox migrations finish inside the first window.