How to Export Apple Mail to MBOX (and Re-import It)

Knowing how to export Apple Mail to MBOX is the difference between a clean switch and a week of lost mail. The command is one menu item — Mailbox > Export Mailbox — and it writes a standard .mbox package to the folder you choose. What the package contains, and what quietly does not survive the round trip into a different client, is where most guides stop being useful.

This post covers the export step on macOS Sonoma and Sequoia (tested August 2026), what the archive actually holds, how nested mailboxes behave, and how to roll back if the new destination turns out to be wrong. It is deliberately Apple-specific: the general "how to move email" post ignores that Apple Mail writes one package per mailbox rather than one archive per account, and that read state and flags survive re-import inconsistently across clients.

What actually moves, and what does not#

An Apple Mail .mbox export is a folder on disk — a macOS package — that contains a single `mbox` file plus a small `Info.plist` and, on newer macOS versions, an `Attachments` subfolder. The `mbox` file itself is standard: each message is a full RFC 5322 message, attachments included as MIME parts, separated by lines beginning with `From `. Any client that reads mbox — Thunderbird, mutt, Mimestream's importer, most Linux mail tools — can open it.

The messages themselves move cleanly. Every header, body, inline image, and attachment is written into the mbox as part of the message envelope. The parts that move poorly are the metadata that live outside the message body: Apple Mail's read/unread flag, the flagged (colored) state, the To-Do link, and the mailbox-level rules that filtered mail into that folder in the first place. Rules are Apple-Mail-specific and are not part of the mbox format. If you re-import into Apple Mail on a new Mac, read state and flags usually survive because Apple wrote them; import into Thunderbird and read state often resets to unread.

Nested mailboxes are the second gotcha. If you select a parent mailbox that contains subfolders and choose Export Mailbox, Apple Mail exports the parent as one .mbox package and each child as its own separate .mbox package inside the destination folder. You get a tree of packages that mirrors your sidebar, not one combined archive. This is usually what you want, but it means "export the whole account" is not one file — it is a folder of files.

Pre-migration checklist#

Run these before you start, in this order. Skipping any of them is the difference between a two-hour job and a two-day one.

• Confirm your account type. IMAP, Exchange, and iCloud accounts hold the messages on the server — the export is a local backup you probably do not strictly need. On My Mac and POP3 accounts hold the only copy locally, and the export is your only safety net.
• Free up disk space equal to at least 1.5x the size of the mailbox. Apple Mail writes the full export to a new location without touching the source, so both copies exist during the write.
• Quit any other Mail client or sync helper that touches the same mailbox — Mimestream, Airmail, a plugin that indexes mail. A second process reading the store during export can leave the archive with truncated messages.
• Decide the destination folder before you start. Exporting to Desktop for a large mailbox then trying to move it to an external drive doubles the write time. Attach the drive first, export directly to it.
• Test on a small mailbox first. Pick a folder with a few hundred messages, export it, open the resulting .mbox in the target client, and confirm read state, attachments, and dates look right. Only then run the export on your archive.
• Note the macOS version and Mail version. A rollback later is easier if you know exactly what wrote the archive. As of August 2026 the current path is Sequoia 15 / Mail 17; Sonoma writes an identical mbox format.

How to export Apple Mail to MBOX, step by step#

The steps below are the current path on macOS Sonoma and Sequoia. The menu labels have not changed since macOS Ventura.

1. 1

   Select the mailbox in the sidebar

   Click a single mailbox — Inbox, Sent, an On My Mac folder, an IMAP subfolder. To export several mailboxes at once, hold Command and click each one; Apple Mail will write one .mbox package per selected mailbox into a common destination folder.

2. 2

   Choose Mailbox > Export Mailbox from the menu bar

   A standard Save dialog opens. There is no format picker — the command always writes .mbox. If Export Mailbox is greyed out, you have selected a smart mailbox or a search folder rather than a real mailbox. Click a regular folder and the option activates.

3. 3

   Choose a destination folder outside the Mail data directory

   Save to an empty folder on Desktop, Documents, or an external drive. Do not save inside ~/Library/Mail — Apple Mail will treat the export as a live mailbox and try to index it. A dedicated folder named after the date (2026-08-15-mail-export/) makes the archive easier to find later.

4. 4

   Wait for the export to finish before doing anything in Mail

   Mail does not show a progress bar for exports. The dock icon stays quiet. Watch the destination folder in Finder — the .mbox package grows as messages are written. For a small mailbox this is seconds; for a 30 GB Gmail archive it can take an hour on an internal SSD and considerably longer to an external USB drive.

5. 5

   Verify the export by opening it in a second client

   In Thunderbird, install the ImportExportTools NG add-on and use Tools > ImportExportTools NG > Import mbox file. In Mimestream, drag the .mbox onto an account. Confirm the message count matches, open three messages at random, and check that attachments open. The export is not real until it opens somewhere other than Apple Mail.

6. 6

   For a whole account, repeat per top-level mailbox

   Apple Mail does not offer "export account." To capture everything, Command-click Inbox, Sent, Drafts, Trash, and each label or subfolder, then run Export Mailbox once. The result is a folder of .mbox packages that together represent the account. Keep the folder together — the tree is what preserves your original layout.

What breaks in the round trip#

The mbox format was designed in the 1970s for storing messages on a Unix filesystem. It carries the message and nothing else. Everything Apple Mail layered on top — flags, read state, To-Dos, rules, smart mailbox definitions — either travels as an extension the next client ignores, or does not travel at all. The table below is what we saw on Sonoma and Sequoia (August 2026) exporting to and re-importing from four common destinations.

Two of these are worth calling out. The flag-to-nothing loss into Thunderbird and Mimestream surprises people who used color flags as a triage system in Apple Mail — the state is written into the mbox as a proprietary Apple header that other clients skip. If flags mattered, plan to re-flag in the new client using search rather than expecting them to travel. The rules loss is the second: exporting the mailbox does not export the rule that filed mail into it. Screenshot or copy your rules out of Mail > Settings > Rules before you switch clients.

Rollback plan if the new client is wrong#

The most common reason to reverse a migration is not a bug — it is that the destination client turns out to be missing something you used every day. Apple Mail is unusually easy to roll back to because the source data was not modified during the export. The rollback is not "undo the export." It is "put Apple Mail back in charge of the account and let the server reconcile."

For an IMAP, Exchange, or iCloud account, the rollback is simple: re-add the account in Apple Mail (Settings > Accounts > +), wait for the initial download, and delete the .mbox archive when everything looks right on the server. Server-side mail was never touched. If you also imported the archive into another client and then created mail there, you will need to sync those new messages back — usually by leaving both clients pointed at the same IMAP account for a few hours and letting them converge.

For an On My Mac mailbox, the rollback is different because there is no server. Use Apple Mail's Mailbox > Import Mailboxes, select "Files in mbox format," and point at the .mbox package you exported. Mail rebuilds the local mailbox from your archive. Read state usually survives this round trip because both ends are Apple Mail. If you imported the archive into another client, edited messages there, and then need to reverse, treat the current state in the other client as the source of truth and re-export from there.

Doing it without downtime#

The reason people export mailboxes to mbox is usually one of three: switching Macs, changing mail providers, or moving off Apple Mail to another client. The export step is the same either way, but only the first case genuinely benefits from an mbox archive — the other two are usually better served by pointing the new client at the same server-side accounts and letting IMAP do the copying, with the export kept as a safety copy rather than the migration path itself.

If your reason is the third — you are moving off Apple Mail because triage, drafting, and follow-ups are eating the day — we build AI Emaily, an AI-native email client that connects Gmail, Outlook, iCloud, and IMAP through server-side sync. We do not import .mbox files. If your goal is to load a decades-old archive into a client and search it locally, Thunderbird or Mimestream is the honest first stop and we are not the right tool. What we do is take over the live inbox once you have connected the account: unified across providers, AI triage that keeps the important mail visible, drafts written from a Personal Context brain you set. There is a 7-day free trial on Pro if you want to see whether that changes the equation before you commit to the switch — see aiemaily.com/pricing.