Google Vault MBOX Export to Excel, 4 Ways Compared
Try it now: extract email data to Excel, CSV, or JSON
Connect a Gmail or IMAP mailbox to parse new mail automatically, or paste an email below to test the converter now.
Create a free account to download. No credit card required.
A Google Vault Gmail export already includes a spreadsheet: the file ending in metadata.csv lists every message with its account, sender, recipients, subject, labels and sent and received dates. What it does not include is anything from the message body. If you need the amounts, order numbers, names or dates written inside the emails, you have to convert the mbox files themselves, and that is where the four routes below differ.
This comparison is for the Google Workspace admin, paralegal, HR lead or controller who has just run a Vault export for one matter, one departing employee or one vendor dispute, and now has a zip of mbox files and a request for "the spreadsheet" by the end of the week.
Need the values inside the emails, not just the headers?
Upload the mbox from your Vault export to the MBOX to CSV converter, name the fields you want from the body, and download CSV, Excel or JSON with one row per message.
What is in a Google Vault Gmail export
When you export Gmail from Vault you choose PST or mbox for the message files. Google's documentation lists the rest of the package, and it matters because two of those files are already spreadsheets.
| File in the export | What it holds | Opens in Excel |
|---|---|---|
| export_name-account-randomstring.mbox (or .pst) | The messages themselves, bodies and attachments included, one file per account | No |
| export_name-metadata.csv | One line per message: Rfc822MessageId, GmailMessageId, Account, From, To, CC, BCC, Subject, Labels, DateSent, DateReceived | Yes |
| export_name-metadata.xml | The same metadata plus the FileName that ties each record to its message in the mbox | Only with an XML import |
| export_name-result-counts.csv | Per account: status, messages exported, messages that errored | Yes |
| export_name-errors.xml and checksums | Messages that failed, and MD5 hashes to prove the files were not altered | Not needed |
File names and fields as described in Google's Vault export contents documentation. If an account's messages exceed 10 GB of mbox (1 GB for PST), Vault splits them across zip files.
Can you open a Google Vault export in Excel?
Partly. The metadata.csv and result-counts.csv files open in Excel directly, and for many requests the metadata file is the whole answer: a message log with who wrote to whom, when, and under which subject. The mbox files do not open in Excel. An mbox is one long text file with every message stacked end to end, so Excel either refuses it or pours raw headers and encoded MIME parts into cells. To get body content into columns you have to convert the mbox.
Pick mbox rather than PST when you set up the export if a spreadsheet is the goal. Mbox is plain text that most converters and scripts read, while PST is a binary Outlook container that needs Outlook or a specialist tool to open.
Four ways to get a Vault export into Excel, compared
| Route | Body content in columns | Size it handles | Skill needed | Best for |
|---|---|---|---|---|
| Open metadata.csv | No, headers only | Any export | None | A message log of dates, parties and subjects |
| Thunderbird with ImportExportTools NG | Body text as one column, no field extraction | Large, limited by your machine | Moderate | Reading the mail and a one-off CSV dump |
| Litigation support or review platform | Full text search, tagging, redaction | Very large matters | Vendor onboarding | Formal review and production to opposing counsel |
| MailParse MBOX converter | Yes, each named field is its own column, table lines become rows | Up to 200 messages and 50 MB per run | Low, in the browser | Pulling amounts, IDs and names out of a targeted export |
Capabilities of third-party tools vary by version. No pricing is implied.
Route 1, the metadata CSV you already have
Unzip the export, open export_name-metadata.csv, and filter. Every message is a line with its sender, recipients, subject, labels and both timestamps, and the Account column tells you whose mailbox it came from. For a correspondence log, a count of messages between two parties, or a date range check, stop here. It costs nothing and it is the record Vault itself produced, which counts for something when someone later asks how the list was made.
Route 2, Thunderbird and an add-on
Google suggests Thunderbird for reviewing mbox files. Install it, add ImportExportTools NG, import the mbox, and use the add-on's spreadsheet export on the imported folder. You get the headers again plus the message text in a column. It is a fine way to read the mail. It will not split a body into fields, so if the question is "what did this vendor bill us each month", someone still copies every amount by hand. Remember that Gmail labels do not become folders; everything lands in one.
Route 3, a review platform
If the export is heading to opposing counsel, needs privilege tagging, or runs to many gigabytes across dozens of custodians, load it into a litigation support platform. That is what those tools exist for, and a spreadsheet is the wrong container for a formal production. Google names these systems in its own review guidance for exactly this reason.
Route 4, convert the mbox with the fields you name
The gap the first three leave is the business content inside each message. Invoice totals from a supplier, order numbers from a customer thread, quoted prices, policy numbers, a start date in an offer letter. The MBOX to CSV converter splits the Vault mbox into messages and writes one row per email with the standard headers plus a column for every field you name. When a message carries an HTML table of charges or products, each line becomes its own row, so totals can be summed straight away. Download CSV for Excel, an .xlsx workbook, or JSON if the data is going into a system.
How do I convert a Google Vault MBOX file to CSV?
- Keep the export narrow. Scope the Vault search to the accounts, date range and terms the request actually covers. A tight export converts faster and keeps unrelated personal mail out of your spreadsheet.
- Choose mbox as the Gmail format and download the zip once the export finishes.
- Unzip and find the account's mbox. Each file is named after the export, the account and a random string.
- Upload it to the converter and name the fields you need from the body. One run covers up to 200 messages from an mbox of up to 50 MB on the Plus and Pro plans.
- Download CSV or Excel, then line it up against metadata.csv using the Rfc822MessageId or the date and subject if you need Vault's own identifiers beside the extracted values.
If the archive is bigger than one run, split the export in Vault by date range or by account and convert each piece, or use a desktop converter built for multi-gigabyte archives. For mail that is still arriving in a live mailbox, connecting it over IMAP is simpler than exporting at all; see extracting data from Gmail.
Which route fits your request
Match the tool to the question you were asked. "Who emailed whom and when" is metadata.csv. "Let me read what was said" is Thunderbird. "Review, tag and produce" is a review platform. "Give me the numbers in these emails as a table" is a field converter, and that last one is the request that usually arrives from finance, operations or a manager rebuilding a departed employee's customer history.
Privacy requests are their own case. When a Vault export is part of answering a data subject access request, the harder problem is usually finding every system that holds that person's data in the first place, which is the job of dedicated DSAR software; the mailbox export is only one source among many. For compliance teams weighing tools for recurring email records, the email to Excel converter comparison for compliance teams goes deeper on audit trails and retention.
Common problems with Vault mbox files
Everything appears in one folder. Labels are not converted into mailbox folders. Use the Labels column in metadata.csv to filter instead.
Several zip files for one account. Vault splits large accounts. Each part holds complete messages, so convert each mbox separately and stack the results.
Times look shifted. Header dates carry the sender's time zone offset, while you may be comparing against a report in Eastern or Pacific time. Normalize before you sort across senders.
Threads repeat themselves. Long reply chains quote earlier messages in every reply. The converter writes the new text and the quoted reply as separate columns, which keeps a thread from repeating across every row.
Frequently asked questions
Can Google Vault export to CSV?
Vault exports message metadata as a CSV file, export_name-metadata.csv, with sender, recipients, subject, labels and dates for every message. The message content itself exports only as mbox or PST. To get body content into CSV you convert the mbox with a converter or a script.
Does a Google Vault export include attachments?
Yes. Attachments stay inside each message in the mbox or PST file. When you convert the mbox to a spreadsheet, the attachment file names are listed in a column for each message; saving the attachment files themselves to a folder needs an email client or a desktop MBOX tool.
Should I export Vault mail as PST or mbox?
Choose mbox if the goal is a spreadsheet or a script, because it is plain text that most converters read. Choose PST if the reviewer works in Outlook or the receiving review platform asks for it. Vault also splits PST into zip files at a lower size, 1 GB, than mbox at 10 GB.
Who can run a Google Vault export?
A Workspace user with Vault privileges to search and export for the relevant matter, usually an administrator or someone the admin delegates in the Vault roles settings. Vault is included in some Google Workspace editions and not others, so check your edition before planning around it.