Skip to main content
Prism MigrationPrism Migration
Cloud Migration

How to Import Google Takeout ZIP into New Gmail Account (Direct Cloud Restore)

D
David Vance Author

Senior Cloud Infrastructure Architect

8 min read · Published August 16, 2026
Executive Summary & Key Takeaway

Downloaded your Google Takeout archive but don't find a restore button in Gmail? Learn how to stream Takeout MBOX emails directly into any new Gmail account.

On This Page (8 sections) ▾
✦Tip

⚡ Quick Direct Answer: Importing Google Takeout into a New Gmail Account

Google Takeout exports your email history as an .mbox archive (e.g., All mail Including Spam and Trash.mbox), but Gmail provides no web UI upload button.

  1. Automated Cloud API Restore: Use Prism MBOX Converter Tool to authenticate via Google OAuth 2.0 PKCE, parse the MBOX file, and stream messages into your new Gmail account using the users.messages.import API to preserve original message dates and X-Gmail-Labels.
  2. Contacts & Calendars: Import All Contacts.vcf at contacts.google.com and [User].ics at calendar.google.com natively.
  3. Manual IMAP Relay (Small Mailboxes): For small archives (<2,000 items), import MBOX into Mozilla Thunderbird and copy messages to Gmail via IMAP, subject to daily bandwidth throttles.

Users transitioning between domains, moving off university accounts, or consolidating personal mailboxes frequently download their email history through Google Takeout before the source account is deactivated.

However, opening the new @gmail.com or Google Workspace inbox and navigating to Settings > See all settings > Accounts and Import reveals no native import mechanism for Takeout archives.

CODE / SCRIPTCode / Script
┌───────────────────────────────────────────────┐
│  THE GOOGLE TAKEOUT IMPORT DILEMMA            │
├───────────────────────────────────────────────┤
│  Google Takeout = Official EXPORT Service     │
│  Google Workspace = NO Native IMPORT Button   │
└───────────────────────────────────────────────┘

Google designed Takeout primarily as an outbound data portability pipeline to comply with data privacy regulations (such as GDPR Article 20). The standard webmail interface does not provide an inbound browser uploader for gigabyte-scale ZIP or MBOX files.

This guide explains how to restore Google Takeout data into a fresh Gmail or Google Workspace account while preserving original folder labels, attachments, and historical email timestamps.


Anatomy of a Google Takeout Archive

When Google completes your Takeout request, you receive one or more .zip or .tgz files structured into discrete folders:

CODE / SCRIPTCode / Script
Takeout/
├── Archive_Browser.html
├── Mail/
│   └── All mail Including Spam and Trash.mbox
├── Contacts/
│   └── All Contacts.vcf
└── Calendar/
    └── [Username].ics

1. Contacts and Calendars: Quick Native Restore

While email lacks a web upload button, Contacts and Calendars can be uploaded natively through Google's web portals:

  • Contacts: Navigate to contacts.google.com, click Import, and select your All Contacts.vcf file. Contact details, notes, and addresses restore directly into your address book.
  • Calendar: Go to calendar.google.com, click the gear icon > Settings > Import & Export, and upload [Username].ics into your primary calendar.

2. Multi-Part ZIP Archives (Takeout 50GB Splits)

If your mailbox exceeded your chosen ZIP split threshold (default 2GB or 50GB), Google generates sequential archives: takeout-20260901T000000Z-001.zip, takeout-20260901T000000Z-002.zip.

Extract all ZIP files into a single destination folder so that partial MBOX files consolidate into the primary Mail/All mail Including Spam and Trash.mbox payload.


The Technical Problem: Why You Can't Just "Upload" MBOX to Gmail

Unzipping a Takeout export yields a monolithic text file named All mail Including Spam and Trash.mbox.

Buried inside that raw text structure are custom metadata headers:

CODE / SCRIPTHTTP
X-Gmail-Labels: Inbox,Important,Work/ProjectAlpha,Starred

Getting those messages back into a live Gmail environment requires:

  1. Authenticating against the destination Gmail mailbox via Google OAuth 2.0 PKCE.
  2. Parsing the local MBOX archive into discrete MIME payload streams.
  3. Calling the users.messages.import REST API endpoint.
  4. Recreating matching user labels and assigning them to each message.
  5. Filtering duplicate Message-ID headers to prevent mailbox bloat.

Critical API Distinction: users.messages.import vs users.messages.insert

Basic DIY scripts often call the standard Gmail insert API.

When you use insert, Google ignores the email's original Date: header and assigns the current ingestion timestamp to every single message. If you import 40,000 emails, every message will display the current time, disrupting your chronological inbox sorting.

The correct method calls users.messages.import with internalDateSource=dateHeader. This instructs Google's backend to parse the original RFC 2822 date string and index the message in its authentic historical timeline.


Using a dedicated desktop ingestion utility like the Prism MBOX Converter Tool simplifies this migration:

CODE / SCRIPTCode / Script
┌───────────────────────────┐      ┌──────────────────────────────┐      ┌───────────────────────────┐
│   Google Takeout MBOX     │ ───> │  Prism Direct Cloud Streamer │ ───> │  Destination Gmail Account│
│  (Local NVMe / SSD Disk)  │      │  (OAuth 2.0 PKCE / TLS 1.3)  │      │ (Restored Labels & Stars) │
└───────────────────────────┘      └──────────────────────────────┘      └───────────────────────────┘
  1. Launch the application and select your downloaded Takeout .zip archive or extracted .mbox file.
  2. Click Authenticate with Google to trigger a browser-based OAuth 2.0 PKCE authentication flow.
  3. Log into the target account and grant permissions—the tool communicates through scoped OAuth tokens without accessing your master password.
  4. Select the specific labels you want to migrate (Inbox, Sent, custom labels) and optionally exclude Spam and Trash.
  5. Click Migrate to stream messages over TLS directly to the Google REST API.
ℹNote

Free Trial Evaluation: The demo version migrates up to 50 items per folder, allowing users to verify OAuth 2.0 authentication, label recreation, and timestamp accuracy before licensing.


The Thunderbird IMAP Upload Relay (Manual Workaround)

Small archives (under 2,000 messages) can be uploaded via an IMAP bridge configured in Mozilla Thunderbird:

  1. Log into the target Google account, navigate to Google Account Settings > Security > 2-Step Verification, and generate an App Password.
  2. In Mozilla Thunderbird, add the account using standard IMAP settings (imap.gmail.com, Port 993, SSL/TLS) paired with your app password.
  3. Install the community add-on ImportExportTools NG.
  4. Right-click Local Folders, select ImportExportTools NG > Import mbox file, and select your Google Takeout MBOX file.
  5. In the local view, select messages in batches of 100 to 200, right-click, and choose Copy To > Destination Gmail > Inbox.
✕Caution

IMAP Bandwidth & Quota Limitations:

  • Google enforces daily IMAP upload limits (typically 500 MB per day for Google Workspace accounts, with rolling throttling on personal consumer Gmail accounts). Exceeding these thresholds can trigger a temporary 24-hour account upload lock.
  • Messages copied manually over IMAP lose custom X-Gmail-Labels metadata and appear as standard unread messages in the destination folder.

Comparing Migration Methods: API Ingestion vs IMAP Relay

CapabilityDedicated API MigratorManual IMAP Relay
AuthenticationOfficial OAuth 2.0 PKCELegacy IMAP App Password
Date Timestamp IntegrityExact Historical RFC 2822 DatesOften overridden with import timestamp
Label Hierarchy PreservationExact Label Sync (X-Gmail-Labels)❌ Flat Dump (No Labels)
Upload SpeedREST API Rate & Quota BoundHeavily Throttled (~500 MB/day)
Duplicate PreventionAutomated Message-ID Filter❌ Manual Check Required
Attachment HandlingDirect MIME Stream⚠️ May Truncate on Timeouts
Daily Bandwidth CeilingREST API Quotas with Backoff500 MB / day (IMAP Policy Cap)

Resolving MBOX "From " Escaping Issues

Standard Unix MBOX files delimit individual emails using an unquoted From separator line followed by an arbitrary envelope sender and date:

CODE / SCRIPTCode / Script
From mailer-daemon@google.com Mon Aug 18 10:30:15 2026
MIME-Version: 1.0
Subject: Project Status

If an email body contains the word "From " at the beginning of a line (e.g., "From our conversation yesterday..."), MBOX formatters escape it by prepending a greater-than symbol: >From .

Incomplete migration scripts can misparse these escaped lines, splitting single long emails into truncated fragments. The Prism Takeout engine implements RFC 4155 byte-boundary verification to ensure multiline MIME messages remain whole and correctly formatted.


Frequently Asked Questions

Why does Gmail have an export service (Takeout) but no import option?

Google provides Google Takeout to comply with data portability mandates (such as GDPR Article 20). However, browser-based webmail uploaders are not designed to decompress and index multi-gigabyte ZIP and MBOX archives during an active browser session. Restoring mail requires API-level message ingestion.

Can I import Google Takeout into Google Workspace without giving my password?

Yes. Modern tools connect using Google OAuth 2.0 authentication. You log in through your standard browser window, granting scoped permissions to insert messages. Your master Google password is never exposed.

How are custom Gmail labels restored from the Takeout MBOX file?

The MBOX file encodes original folder names in X-Gmail-Labels headers. The Prism MBOX Converter Tool reads these header flags and calls the Google Labels API to recreate the exact tag structure in the new account.

What happens if the import is interrupted by a network drop?

The engine uses SQLite checkpoint logging to track each successfully migrated Message-ID. If a network interruption occurs, clicking Resume continues where it stopped without duplicating emails.

Can I filter out Spam and Trash from my Takeout MBOX before importing?

Yes. Google Takeout bundles everything into All mail Including Spam and Trash.mbox. The tool includes an automated filter option to exclude items tagged with \Spam or \Trash, saving cloud storage space.


Summary and Next Steps

Restoring your Google Takeout archive into a new Gmail or Google Workspace account can be performed cleanly by addressing the lack of a native browser uploader. For larger mailboxes, using an API-direct tool like the Prism MBOX Converter Tool preserves historical timestamps, attachments, and custom X-Gmail-Labels hierarchies.

Related Guides: Opening Takeout archives in Outlook instead? Follow How to Open Google Takeout MBOX in Outlook 2026. To extract Takeout ZIP files safely, see How to Open & Extract Google Takeout Files.

Recommended Automated Utility Windows 11 & 10 (64-bit) & macOS

MBOX Converter Tool (2026 Enterprise Edition)

Export, convert, migrate, and backup MBOX mailboxes from Thunderbird, Apple Mail, Google Takeout, and Eudora to multiple formats including Unicode PST, PDF, EML, Microsoft 365, and Gmail. Standalone 64-bit engine with zero Outlook dependency. Runs natively on Windows 11 and Apple Silicon (M1–M4) macOS.

Windows 11 & 10 (64-bit) & macOS 1, 2 & 3-Year License Options Free Trial (50 items/folder)