Migrating from Gmail to Apple Mail: the mbox Export Method

Moving away from Gmail is harder than moving in. Gmail will happily IMAP-sync your messages into any new client, but if you want a clean, complete, permanent copy - not dependent on Google's servers staying up or your account remaining active - you need to export to mbox via Google Takeout and import that into your destination client. For Apple Mail users, the mbox-via-Takeout to Email Converter route is the cleanest path.

This guide walks through the full process: requesting the Takeout archive, what you actually get, how to handle the inevitable duplicates, and how Email Converter bridges the gap between Takeout's mbox and Apple Mail's .emlx format.

Step 1: request and download the Takeout archive

Go to takeout.google.com. Sign in with the Google account whose mail you want to export. Deselect everything, then re-select only "Mail". Click the dropdown for Mail to optionally filter to specific labels (otherwise everything including Spam and Trash is exported).

Choose the delivery method (download link, or push to Google Drive / Dropbox / OneDrive - easier for large mailboxes). Choose the file size threshold (max 50 GB per zip - splits into multiple files if larger). Choose the format (.zip for most users, .tgz if you're comfortable with command line).

Click "Create export". Google emails you when ready. For mailboxes under 10 GB this is typically 1-6 hours; large mailboxes can take 24-48 hours.

Download the resulting archive. Inside it you'll find a single large mbox file per account, named something like All mail Including Spam and Trash.mbox. This file is in standard Unix mbox format - every message concatenated, separated by "From " line headers. The good news: every email client knows how to read this format.

Step 2: import into Apple Mail via Email Converter

You have two options. The first is Apple Mail's built-in mbox import: File - Import Mailboxes - "Files in mbox format" - point at the Takeout file. This works but has known issues with large mboxes (over 5 GB the import can hang for hours, sometimes failing silently). It also doesn't preserve Gmail labels.

The cleaner option is to first run the mbox through Email Converter to split it into individual EML files organised by Gmail label, then import those into Apple Mail. The advantage: you get folder structure that matches your Gmail labels, the import is interruptible and resumable, and duplicates can be detected before they hit your Apple Mail database.

Email Converter workflow for Gmail mbox:

1. Open Email Converter, choose "From mbox" as source

2. Point at the Takeout file

3. Choose "Split by Gmail label" - uses the X-Gmail-Labels header to create one output folder per label

4. Choose "One EML per message" as output format

5. Optional: enable "Deduplicate by Message-ID" to drop duplicates within the export

6. Run the conversion - progress bar shows messages processed

7. Drag the resulting folders into Apple Mail's sidebar to import

This route handles 50 GB mailboxes reliably (the splitting step parallelises and is memory-efficient). It also gives you a clean intermediate state - the EML directory - that you can archive separately as a permanent record.

Quick comparison

Common pitfalls and how to avoid them

Across every domain this article touches, the same shape of mistake recurs. Practitioners new to the field overweight the most visible piece of the system — the screenshot, the paywall, the exam question, the headline price — and underweight the underlying constraint that actually determines outcomes.

The five most common failure modes:

1. Optimising for the demo, not the durability. A working demo in a controlled environment proves nothing about reliability under real conditions. In iOS development, an in-app purchase flow that works in the Xcode Simulator says nothing about how it behaves in App Store sandbox with network latency and Ask to Buy approvals. In an exam, a 100% score on an untimed quiz tells you nothing about whether you can do 49/50 in 45 minutes with no second guesses. Build for the hardest realistic case from the start.
2. Skipping the first-principles documentation. Every system has a canonical specification. App Review Guidelines for iOS, the official EU regulations for tax deductibility, the CITB question bank for CSCS, the OMIE market rules for Spanish electricity. Reading them takes a few hours but saves weeks of wrong-direction work. Secondary sources (blogs, tutorials, this article included) are useful as orientation but never authoritative.
3. Ignoring the rate limit. Every external system has rate limits — explicit (APNs silent push throttling, RevenueCat API quotas, exam retake fees) or implicit (App Review patience, customer attention spans, your own working memory). Plan around them. A workflow that requires more rate-limited operations than the system allows will fail in production, not on day one but during the first stress event.
4. Underweighting localisation and regional variation. What is true for Germany is not always true for Italy. What is true for English-speaking users is not always true for Japanese ones. What is true for the UK CSCS test is not always true for the Irish equivalent. Always check the local rule before applying a general one.
5. Treating the documentation as static. Apple updates App Review Guidelines. The Bundeslaender change Schonzeiten. OMIE adjusts market clearing algorithms. Set up a periodic review (quarterly is enough for most things) and re-read the canonical sources. Workflows that worked perfectly a year ago can be silently broken today.

None of these are dramatic. The dramatic mistakes (catastrophic bugs, audit findings, exam failures) are the visible tip of a longer-running iceberg of small misses. Catching the small misses is what separates routine outcomes from problematic ones.

Key takeaways

• Takeout request — Google export. Email when ready.
• Download mbox — Zip from Takeout. Up to 50 GB per file.
• Email Converter — Split + dedupe. By Gmail label.
• Apple Mail import — Drag folders. Indexes in background.

The pattern that runs through every section above: start with the constraint, not the wishlist. In an exam, the constraint is the question bank and the pass mark. In an electricity market, it is the auction clearing rule. In a tax workflow, it is the receipt-retention requirement. In a code architecture, it is the platform's design decision (StoreKit's transaction lifecycle, App Review's guideline, APNs's authentication model). Get the constraint right and the rest follows.

The opposite failure mode — designing for an aesthetic ideal, then trying to retro-fit the constraint — is the most common cause of wasted work in every domain covered here. A beautiful paywall that hangs in sandbox is rejected at App Review. A polished freelancer expense report that lacks receipts is disallowed by the tax office. A study plan that ignores the actual question distribution leaves the candidate stuck below the pass mark.

The practical recommendation: read the official rules of whatever system you are operating in, extract the binding constraints, and treat them as inputs to the design — not afterthoughts. Every section of this article is the application of that principle to a specific domain.

FAQ

How long does Google Takeout take for Gmail?
For mailboxes under 10 GB, typically 1-6 hours. For larger mailboxes, 24-48 hours. Very large (100+ GB) can take days. The export is split into multiple zip files if it exceeds 50 GB.

Will I lose Gmail labels in the migration?
If you use Apple Mail's built-in mbox import, yes. If you route through Email Converter with 'Split by Gmail label' enabled, no - each label becomes a folder in Apple Mail.

How do I handle duplicates from re-exports?
Email Converter has a 'Deduplicate by Message-ID' option that drops duplicate messages based on the standard RFC Message-ID header. This is more reliable than date+subject matching.

Can I do this without uploading to a cloud service?
Yes. Google Takeout offers a direct download link option. The mbox file is processed locally by Email Converter; nothing leaves your Mac.

Further reading and references

The references below cover the official sources for the rules cited in this article. Where applicable, they include the canonical documentation, regulatory text, or vendor-provided guides. For each one, prefer the official source over secondary commentary — secondary sources go stale fast and frequently misquote the binding rule.

• Official documentation of the system in question (linked from each app or service's own help centre).
• Apple Developer Documentation for any iOS/macOS reference — the WWDC session videos and the corresponding Human Interface Guidelines pages are the authoritative source.
• For EU regulatory questions (taxation, data protection, energy market structure), consult the relevant national authority — most publish their guidance in English.
• For Spain and Italy energy market data, OMIE and GME both publish full historical price series in CSV format from their public websites — no API key required.
• For UK CSCS prep, the CITB publishes the official question bank book each year — buy a current copy if you want the authoritative source.

If you find a contradiction between this article and an official source, the official source wins. Article rules of thumb are summaries — they have edge cases, exceptions, and regional variations that the source documents specify exactly.