Vault export contents

After you use Google Vault to search for the data you want, you can export a copy of that data and download it for further analysis. An export contains the following information:

A comprehensive copy of the data that matched your search criteria
The metadata you need to link the exported data to individual users in your organization
The corroborating information required to prove that the exported data matches the data stored on Google’s servers

Gmail exports

Expand section | Collapse all & go to top

Export contents

How Chat messages are organized in an export file

To provide context for Chat messages, your search results, preview, and export files include messages sent in the same conversation or thread as the matching messages. Chat messages are organized in an export file as follows:

Messages are grouped by conversation, thread, or Chat space.
If your export includes messages from several conversations, the conversations are in reverse chronological order based on the most recent matching message. For example, if the last matching message in one conversation was sent at 1 PM, and the last matching message in another conversation was sent at 8 PM, messages from the conversation with the 8 PM message are listed first in the export file, then the messages from the conversation with the 1 PM message.
Within each conversation or Chat space, messages are in chronological order.
Note: If you review your export in an email client, messages are in chronological order and aren’t grouped by conversation.

Reducing duplicate messages

When many messages in the same conversation or thread match your search, there can be overlap in the messages provided for context. To avoid exporting duplicate messages, Vault evaluates the overlap and groups messages accordingly.

For example, a conversation has 2 messages that match the search query, one sent at 9 AM on Monday and the other sent at 3 PM on Monday. The matching messages have the following context windows:

9 AM message: 9 PM Sunday to 9 PM Monday
3 PM message: 3 AM Monday to 3 AM Tuesday

The context windows overlap between 3 AM and 9 PM Monday. When the messages are exported, only one series of messages is returned for the conversation and it includes all messages sent between 9 PM Sunday and 3 AM Tuesday.

If another message in the conversation matches but was sent more than 24 hours after the previous matching message, then a second message grouping is created and returned in the export. Continuing the previous example, if another matching message was sent at 11 AM Thursday, its context window is from 11 PM Wednesday to 11 PM Thursday. This window doesn’t overlap with the previous window, which ended at 3 AM Tuesday, so the messages in this window are returned in a second group.

Information	File name	Description
Message contents	export_name-N.zip	PST or mbox files with the contents and details of the exported messages. Learn about options for reviewing PST and mbox files. The message files are named export_name-account-randomstring.mbox or export_name-account-randomstring.pst, where account is the full email address of the custodian (the account that sent or received the message). If the messages for an account exceed 1 GB for PST files or 10 GB for mbox files, they're exported in zip files. The files within are appended with a 6-character randomized string. The zip files are numbered sequentially. For example, if there are more than 10 GB of mbox files in the export, my-export could contain the following files for user1@example.com: my-export-1.zip my-export-user1@example.com-PrDhfQ.mbox my-export-user1@example.com-qN96Ew.mbox my-export-2.zip my-export-user1@example.com-f_5gjg.mbox If you're exporting PST files, the extension of the additional files is .pst. To decrypt client-side encrypted messages in mbox files, use the decrypter utility (beta). To view client-side encrypted emails in the PST format, import each users’ p7m file into Microsoft Outlook.
Message metadata	export_name-metadata.csv export_name-metadata.xml	export_name-metadata.csv–A CSV file that contains message metadata as it exists on Google servers. Open this file in a spreadsheet editor, and use it to connect message metadata with the message contents from the mbox file. export_name-metadata.xml–An XML file that contains message metadata as it exists on Google servers. Open this file in a spreadsheet editor, and use it to connect message metadata with the message contents from the mbox file. In addition to the fields that are available in both the CSV and XML, Gmail Classification labels are only included in the XML file. Learn more about the metadata file.
Accounts and message count	export_name-result-counts.csv	A CSV file that lists the accounts of message owners included in the export, the number of messages owned by each account, and how many messages were successfully exported or had errors. Learn more about the count file.
Drive links	export_name-drive-links.csv	A CSV file that lists the Drive file hyperlinks extracted from the Gmail message content. This file is only included if you enable the Export linked Drive files option and there is at least one Drive hyperlink in the exported messages. For each hyperlink, you get the: RFC822 message ID of the email containing the link Unique message ID of the email containing the link Hyperlink to the Drive file Document ID of the Drive file If the same email ID appears more than once, multiple Drive links were found in the same message body. The CSV file includes the hyperlinks regardless of whether you have permission to export them. You can look up the document ID in the Drive export files or error metadata to see if the export of a hyperlink was successful.
Error report	export_name-errors.xml	An XML file that lists errors retrieving messages. It's always part of the export, even when no errors occurred. Learn more about the error report.
Messages that didn't convert to PST	export_name-conversion_errors-N.zip	When you export in PST format, this file contains any messages that weren't converted to PST. Each message is a separate EML file named with the value of the `Message-ID:` header for each message. You get many zip files when there are more than 10 GB of messages.
File checksums	File checksums	A file that lists the message digest 5 (MD5) hash values for all files in the export.

Message parameters in the metadata file

The metadata CSV and XML files list the following information for each message. The value is blank if the information isn't available or doesn't apply to a message.

Column	Description	Note
`Rfc822MessageId`	A message ID that is the same for the receiver's and sender's messages. Use this value to correlate metadata with the message in an mbox export.	CSV file only
`GmailMessageId`	A unique message ID. Use this value to manage specific messages with the Gmail API.	CSV file only
`DocId`	A unique message ID. Use this value to manage specific messages with the Gmail API.	XML file only
`Account`	The account that has the message in its inbox. For example, user1@example.com received a message sent to groupA@example.com because user1 is a member of groupA. If a search returns the message because it's in user1's inbox, then the value of `To` is groupA@example.com and the value of `Account` is user1@example.com.
`From`	The sender account.
`To`	The recipient account. Multiple recipients are comma-separated and the list is in double quotes.	Gmail only
`CC`	Accounts in the cc: field.	Gmail only
`BCC`	Accounts in the bcc: field.	Gmail only
`Subject`	The message subject.	Gmail only
`Labels`	Labels applied to the message by Gmail or the user.	Gmail only
`DateSent`	The message send date in UTC (yyyy-MM-dd'T'HH:mm:ssZZZZ).	Gmail only
`DateReceived`	The message received date (yyyy-MM-dd'T'HH:mm:ssZZZZ).	Gmail only
`LabelName`	For Gmail items, the name of the classification Gmail labels and fields, if any. The labels included in the export are from the item's current version. The `LabelName` is available in the XML metadata file only.

Information in the count file

Column	Description
`Email`	The email address of the sender or recipient.
`AccountStatus`	If messages for the email account were successfully exported. Value can be the following: `Success`–Vault retrieved all messages for export. `PartialAccountError`–Vault was unable to retrieve all the messages for export. `AccountError`–Vault was unable to retrieve any messages for export.
`SuccessCount`	The number of messages successfully exported.
`MessageErrorCount`	The number of messages that aren't included in the export. These messages are identified in the error CSV file.

Google Chat & Groups exports

Expand section | Collapse all & go to top

Export contents

Information	File name	Description
Message contents	export_name-N.zip	Zip files of PST or mbox files. These files contain the contents and details of the exported messages. For Chat messages, these details include when the sender edited or deleted a message. The file names end with an increment to distinguish the files. Learn about options for reviewing PST and mbox files. You get multiple zip files in the following scenarios: The export includes messages from more than one account. The file size exceeds 1 GB for PST files or 10 GB for mbox. To decrypt client-side encrypted messages in mbox files, use the decrypter utility (beta). To view client-side encrypted emails in the PST format, import each user's p7m file into Microsoft Outlook.
Google Groups membership information	export_name-group-membership.csv	A CSV file that lists the following information for each group member: Member's email addresses Email address of the group When the user became a member of the group Member's role–`MEMBER` for a group member, `MANAGER` for a group manager, or `OWNER` for a group owner Type of account–`USER` for an individual user account or `GROUP` for a group email address
Message metadata	export_name-metadata.xml export_name-metadata.csv	export_name-metadata.xml–An XML file that contains Groups or Chat message metadata as it exists on Google servers. Learn more export_name-metadata.csv–A CSV file that contains Gmail metadata as it exists on Google servers. Learn more Note: PST file contents can’t be correlated with the XML file metadata.
Accounts and message count	export_name-results-count.csv	A CSV file that lists the accounts of message owners included in the export and the number of messages owned by each account.
Error reports	error.csv export_name–failed-group-membership-lookups.csv (Groups exports)	Error reports are included only if the export encounters errors. error.csv—Lists errors retrieving messages. Learn more export_name-failed-group-membership-lookups.csv—Lists group email addresses that were searched but not all members were returned
File checksums	File checksums	Lists the message digest 5 (MD5) hash values for all files in the export.

Message parameters in the metadata file

The metadata file contains the following information:

Metadata for Groups messages

#From—Email account of the sender
#To—Email accounts of all recipients
#CC—Email accounts of all Cc'd recipients
#BCC—Email accounts of all Bcc'd recipients
#Subject—Message subject
#DateSent—Timestamp for when the message was sent
#DateReceived—Timestamp for when the message was received

Metadata for Chat messages

#DateFirstMessageSent—Timestamp for when the first message in a conversation was sent
#DateLastMessageSent—Timestamp for when the last message in a conversation was sent
#DateFirstMessageReceived—Timestamp for when the first message in a conversation was received
#DateLastMessageReceived—Timestamp for when the last message in a conversation was received
RoomID–Space, group chat, or DM identifier that the message belongs to
Participants–Email addresses of all users who participated in the conversation
Labels—Labels applied by Chat, such as ^INBOX, ^TRASH, and ^DELETED. Also shows any labels applied to the message by the user.
RoomName–The value depends on the type of message:
- For Chat spaces, the name of the space
- For group conversations created after early December 2020, Group chat
- For group conversations created before early December 2020 and DMs, a comma-separated list of accounts that participated
ConversationType–The message type:
- For a group chat created after early December 2020 or a space, the value is Room
- For a group chat created before December 2020, the value is Group Direct Message
- For a DM, the value is 1:1 Direct Message

Metadata for all messages (Groups and Chat)

FileName—Message identifier. Use this value to correlate metadata with the corresponding message in an email client or a text editor.
FileSize—Size of the message in bytes
Hash—MD5 hash of the message

Query parameters for the entire export

UserQuery—Query submitted by the Vault user that retrieved the messages included in this export
TimeZone—Time zone used for date-based searches
Custodians—Email addresses of the users whose accounts were searched. If you search for content rather than individual user accounts, no custodians are listed here.

Message parameters in the Google Groups metadata file (CSV)

Google Drive exports

Expand section | Collapse all & go to top

Export contents

Information	File name	Description
Files	export_name_N.zip	Contains all the files and sites found by your search. Vault exports up to 10 GB of data in a single compressed file. If you export more than 10 GB of data, Vault creates multiple files. Exported files are named with the original name of the file followed by an underscore ("_") and the Drive file ID. Exported Google files are converted as follows: Google Docs to DOCX Google Sheets to XLSX Google Forms to ZIP (HTML and CSV) Google Slides to PPTX Google Drawings to PDF Google Sites to PDF. Each page in a site is saved as a separate PDF file that's named using the site-name_page-name_site-ID_page-ID.pdf format. Google Vids to MP4 Note: When you export client-side encrypted files, the files remain encrypted, and the filenames end with `.gcse`. To decrypt the files, use Google client-side decrypter. When you decrypt a Google Docs, Sheets, or Slides file, the file name ends with `.gdoc`. The decrypter can’t convert these files to DOCX, XLSX, or PPTX yet.
File metadata	export_name-metadata.xml	Contains metadata, including: Document IDs (Note: These IDs are not the Drive file IDs. They correspond to values in the CSV file.) User email addresses Created and modified dates for each file Document types and titles Learn more
Accounts and doc IDs	export_name-custodian-docid.csv	Lists user accounts with their associated document IDs. Use this information to determine which users have access to the exported files. This file is not included if you're exporting Gmail data and you enable the Export linked Drive files option. For details, go to Start an export.
Error reports	error.csv export_name-incomplete-accounts.csv	Error reports are included only if the export encounters errors. error.csv—Lists errors retrieving files and the file metadata. Learn more export_name-incomplete-accounts.csv—Lists accounts that were searched but not all matching files were exported
File checksums	File checksums	The file lists the message digest 5 (MD5) hash values for all files in the export.

File parameters in the metadata file

The metadata file included with your export captures the following metadata:

Included with each file

Column	Description
`DocID`	A unique identifier for the file. For sites exports, the value is the page ID.
`#Author`	The email address of the person who owns the file in Drive. For a shared drive file, it shows the shared drive name.
`Collaborators`	The accounts and groups that have direct permission to edit the file or add comments. Also includes users with indirect access to the file if you chose this option during export.
`Viewers`	The accounts and groups that have direct permission to view the file. Also includes users with indirect access to the file if you chose this option during export.
`#DateCreated`	The date a Google file was created in Drive. For non-Google files, usually the date the file was uploaded to Drive. Learn more about timestamps for uploaded files.
`#DateModified`	The date the file was last modified. Learn more about timestamps for uploaded files.
`#Title`	The filename as assigned by the user. Because some operating systems can't expand zip files with extremely long filenames, Vault truncates the filename at 128 characters during export. The value shown by the `#Title` tag isn't truncated.
`DocumentType`	The file type for Google files. Possible values are: `DOCUMENT`—A document created in Google Docs `SPREADSHEET`—A spreadsheet created in Google Sheets `PRESENTATION`—A presentation created in Google Slides `FORM`—A form created in Google Forms `DRAWING`—A drawing created in Google Drawings `SITES_PAGE`—A page from a site created in new Google Sites `VID`—A video created in Google Vids
`Duration`	For Google Vids, the duration of the video recording in milliseconds.
`Others`	The accounts from your query that have indirect access to the file if you opted to exclude access level information during export. May also include users for whom Vault couldn't determine permission levels at the time of export.
`SitesTitle`	For sites, the name of the page.
`PublishedURL`	For sites, the web address of the published page. Value is empty for unpublished sites.
`DocParentID`	For sites, a unique identifier for the site the page is part of.
`SharedDriveID`	The identifier of the shared drive that contains the file (if applicable).
`LabelName`	For Drive items, the name of the Drive labels and fields, if any. The labels included in the export are from the item's current version.
`SourceHash`	A unique hash value for each version of a file. Can be used to deduplicate file exports and verify the exported file is an exact copy of the source file. Supported by Google Docs, Sheets, and Slides files only.
`FileName`	The file name. Use this value to correlate the metadata with the file in the export ZIP file.
`FileSize`	The size of the file in bytes.
`Hash`	The MD5 hash of the file.
`ClientSideEncrypted`	Indicates that the file was encrypted with Google Workspace client-side encryption. Files that aren't client-side encrypted don't include the `ClientSideEncrypted` tag.
`Reviews`	A section that lists metadata for file approvals. Not included when no approvals were requested on the file. For each approval request, a `Review` section contains the following information: `ApprovalId`—A unique identifier for the review `CreatedAt`—The time when approval was requested `ModifiedAt`—The last time the approval status changed `Approvers`—A comma-separated list of the approvers’ emails `ApprovalStatus`—The status of the approval. Possible values are: `IN_PROGRESS`—An approval was requested `APPROVED`—All approvers approved the file `DECLINED`—An approver declined the request to approve the file `CANCELLED`—An approver rejected the file
`ContentVersionDate`	If a version date was included in the export query, the date when a specific version of a Drive document was saved.
`SlideRecording`	Metadata about recordings (if exported item is a Slides presentation with associated recordings). For details, go to Use slides recording in Google Slides.

Query parameters for the entire export

Column	Description
`UserQuery`	The query submitted by the Vault user that retrieved the files included in this export.
`TimeZone`	The time zone used for date-based searches.
`Custodians`	The email addresses of the users whose accounts were searched. If you searched for content rather than individual user accounts, there are no custodians listed here.

Exporting access-level information for users with indirect access to files

Google Voice exports

Expand section | Collapse all & go to top

Export contents

Information	File name	Description
Voice data files	export_name-N.zip	A zip file is generated for each account and contains PST or mbox files of text conversations, call logs, voicemail MP3 audio files, and voicemail transcriptions.
File metadata	export_name-metadata.xml	An XML file is generated that contains metadata as it exists on Google servers.
File checksums	File checksums	A checksum file is generated with message digest 5 (MD5) hash values for all files included in the export.
Error report	error.csv	Error reports are included only if the export encounters errors. Learn more

Note: Unlike other services, Voice exports don’t include a count file.

Voice data parameters in the metadata file

Google Calendar exports

Export contents

Information	File name	Description
Files	export_name_N.zip	Internet Calendar Scheduling (ICS) or Personal Storage Table (PST) files with users' calendar events. One file is created for each user. For extremely large calendars, the export might be split into several files. When you export client-side encrypted files, the export contains separate files: Non-encrypted events are in .ics or .pst files. Encrypted events are in .ics.gcse files. To decrypt the files, use the Google client-side decrypter. Export an event If the event is in a series, you can export only the full series. For details, go to Search & export an event series. If the event contains a hyperlink to a Drive file, the link is included in the export but the file itself is not. Export a PST file If the PST file doesn’t support an email address format, the address is replaced with the placeholder `invalid_email@calendar.google.com`
File metadata	export_name-metadata.csv	An identifier for each event and the account to which it belongs
Accounts and event count	export_name-result-counts.csv	The file includes for each account: `AccountStatus`—Indicates whether the export for this user was successful. It displays `Success`, `PartialAccountError` if some events are missing for this user and `AccountError` if the export completely fails for the user. `SuccessCount`—Indicates how many events were exported. `CalendarEventErrorCount`—Indicates how many exported events had errors (but excludes events that failed to export).
Error reports	export_name-errors.xml	The file lists the errors that occurred when retrieving events. The file is always part of the export, even when no errors occur. For details, go to Error report contents for Calendar (later on this page).

Gemini app exports

Expand section | Collapse all & go to top

Export contents

Information	File name	Description
Conversation content	export_name.zip	A zipped file containing one XML file for each conversation owner. Each XML file contains the exported prompts and responses that match your search criteria. To provide context, Vault includes all prompts and responses from the same conversation sent 12 hours before and 12 hours after the matched prompt or response. Learn more about the Gemini app conversation content file.
Accounts and conversations count	export_name-result-counts.csv	A CSV file that lists the accounts of conversation owners included in the export and how many messages were successfully exported or had errors. Learn more about the Gemini app count file.
File checksums	File checksums	A checksum file is generated with message digest 5 (MD5) hash values for all files included in the export.
Error report	export_name-error.xml	An XML file that lists errors retrieving conversations. It's always part of the export, even when no errors occurred. Learn more.

Note: Unlike other services, Gemini app exports don’t include a metadata file.

Gemini app conversation content file

Column	Description
`Email`	The email address of the owner of the Gemini app conversation.
`ConversationId`	A unique ID that identifies each Gemini app conversation.
`ConversationTopic`	The topic name.
`ConversationTurn`	Contains information about a specific prompt-response pair, including User prompt Gemini app response Gemini model version Parent-request ID, if this is a child request
`Timestamp`	The timestamp for a specific prompt-response pair in UTC (yyyy-MM-dd'T'HH:mm:ssZZZZ).

Gemini app count file

Field	Description
`Email`	The email address of the owner of the Gemini app conversation.
`AccountStatus`	Indicates whether the conversations for the email account were successfully exported. The value can be one of the following: `Success`–Vault retrieved all conversations for export./li> `PartialAccountError`–Vault was unable to retrieve all the conversations for export. `AccountError`–Vault was unable to retrieve any conversations for export.
`SuccessCount`	Indicates how many Gemini app prompt-response pairs were exported for the account.

Error reports

When Vault is unable to export data from a service, Vault generates an error report. The report lists the items with export errors along with more details and metadata.

Vault reports two types of errors:

Transient errors—A backend server was unable to retrieve the email message or file. The item should be available for export when you search for it later.
Non-transient errors—Any error that's not explicitly labeled as transient is the result of an issue that cannot be corrected. Typically these errors occur when a message attachment or file was deleted, isn't supported for export, or can't be converted to the requested format.

To determine if the problem is transient or non-transient, open the CSV file with Google Sheets or another spreadsheet app and find the Error Description column. Note: Error descriptions aren't available for Voice exports.

Recover from transient errors

You can use message and file details to search for and export the data that wasn't exported due to transient errors:

If the error report includes messages with transient errors, use each message’s RFC 822 identifier to find those specific messages when you search again. The format of the search term is rfc822msgid:identifier.
If the error report includes Drive files with transient errors, use each file's title to find those specific files when you search again. The format of the search term is title:"title-of-file".

Error report contents

Expand section | Collapse all & go to top

Error report contents for Gmail

Summary section

The error report contains the following data for the entire export in a Summary section.

Field	Description
`AccountErrorsCount`	The number of accounts that Vault was unable to retrieve any messages for export.
`PartialAccountErrorsCount`	The number of accounts that Vault was unable to retrieve all messages for export.
`MessageErrorsCount`	The number of messages that Vault was unable to retrieve completely from Gmail. For these messages, Vault retrieves the metadata but not all the message content.
`Account`	The account that has the message in its inbox. For example, user1@example.com received a message sent to groupA@example.com because user1 is a member of groupA. If a search returns the message because it's in user1's inbox, then the value of `To` is groupA@example.com and the value of `Account` is user1@example.com.
`Count`	The number of errored messages associated with a specific account.
`PSTConversionErrorsCount`	The number of messages that weren’t converted to PST.
`MessageProcessingError`	The number of messages that Vault was unable to process because it couldn’t decode the message body. To recover these emails, contact support.

Lists of errors

After the Summary section, the export contains metadata for the accounts and messages that had errors. Values aren't reported if the data isn't available or applicable for a message.

Field	Description
`AccountErrors`	A list of the users whose messages couldn't be searched. Each entry includes values for `Account` and `Reason`.
`Reason`	For accounts that Vault was unable to retrieve any messages for export, the error returned by Gmail.
`PartialAccountErrors`	A list of users whose messages were only partially searched.
`MessageErrors`	The metadata for messages that couldn't be exported. Fields are the same as the metadata file.
`PSTConversionErrors`	For PST-formatted exports, a list of the `Account` and `Rfc822MessageId` values for messages that weren't converted for PST. These messages are available in their original EML format in the export_name-conversion-errors-N.zip file included in the export.
`MessageProcessingError`	A list of errors returned when the message body couldn’t be decoded by Vault. To recover these emails, contact support.

Field	Description
`Document ID`	A unique identifier for the file
`Document type`	The document type. Value is `mail`.
`File type`	The file type. Value is `mail`
`Attachments count`	The number of attachments to the message
`Attachment names`	The file names of the attachments
`Subject`	The message subject
`Size`	The message size
`From`	The sender's email account
`To`	The email accounts of all recipients
`Cc`	The email accounts of all Cc'd recipients
`Sent time`	The timestamp for when the message was sent
`Source account`	The account that was included in the search query
`Error description`	A description of the error
`RFC 822 Message-ID`	A unique identifier for a message that's added by mail servers Example: `rfc822msgid:AANLkTilQ5MWSp7-iE6SKepvOl-` `Spjupgr1NZTiLGu16Z@mail.solarmora.com`

Field	Description
`Document ID`	A unique identifier for the file
`Filename`	The document type. Value is `mail`.
`Conversation Type`	The type of message. Value is `mail`.
`space Name`	The name of the space
`Error description`	A description of the error

Field	Description
`Document ID`	A unique identifier for the file
`Document type`	Indicates the file type for Google files. Possible values are `DOCUMENT`, `SPREADSHEET`, `PRESENTATION`, `FORM`, `DRAWING`, `SITES_PAGE`, and `VID`.
`File type`	The file format, such as PDF or XLSX
`Title`	The filename as assigned by the user
`Size`	The size of the file
`Creator`	The email address of the person who owns the file in Drive. For a shared drive file, it shows the shared drive name.
`Collaborators`	The accounts and groups that have direct permission to edit the file or add comments. Also includes users with indirect access to the file if you chose this option during export.
`Viewers`	The accounts and groups that have direct permission to view the file. Also includes users with indirect access to the file if you chose this option during export.
`Others`	The accounts from your query that have indirect access to the file if you opted to exclude access level information during export. May also include users for whom Vault couldn't determine permission levels at the time of export.
`Creation time`	The date a Google file was created in Drive. For non-Google files, this indicates when the file was uploaded to Drive.
`Last modified time`	The date the file was last modified
`Error description`	A description of the error
`Drive Document ID`	A unique identifier for a file in Drive

Vault export contents

On this page

Gmail exports

How Chat messages are organized in an export file

Reducing duplicate messages

Google Chat & Groups exports

Google Drive exports

Google Voice exports

Google Calendar exports

Gemini app exports

Error reports

Recover from transient errors

Error report contents

Summary section

Lists of errors

Summary section

Lists of errors

Summary section

Lists of errors

Was this helpful?

What is the issue with this selection?

Share additional info or suggestions

Column	Description
`Rfc822MessageId`	Message ID that is the same for the receiver's and sender's messages. Use this value to correlate metadata with the message in an mbox export.
`GmailMessageId`	Unique message ID. Use this value to manage specific messages with the Gmail API.
`Account`	The account that has the message in its inbox. For example, user1@example.com received a message sent to groupA@example.com because user1 is a member of groupA. If a search returns the message because it's in user1's inbox, then the value of `To` is groupA@example.com and the value of `Account` is user1@example.com.
`From`	Sender account
`To`	Recipient account. Multiple recipients are comma-separated and the list is in double quotes
`CC`	Accounts in the cc: field
`BCC`	Accounts in the bcc: field
`Subject`	Message subject
`Labels`	Labels applied to the message by groups
`DateSent`	The date the message was sent in UTC (yyyy-MM-dd'T'HH:mm:ssZZZZ).
`DateReceived`	The date the message was received in UTC (yyyy-MM-dd'T'HH:mm:ssZZZZ).

Field	Description
`Account`	The email address of the account that some data wasn’t exported for.
`Failed Conversation Count`	The number of conversations that weren’t exported. If the number is unknown, the value is `Unknown Failure Count`.

Field	Description
`AccountErrorsCount`	The number of accounts for which no event data could be exported
`PartialAccountErrorsCount`	The number of accounts for which some event data could not be exported
`CalendarEventErrorsCount`	The number of accounts for which some event data could not be exported
`Account`	The account that included the events
`Count`	The number of events that have errors for a particular account
`PSTConversionErrorsCount`	The number of events that weren’t converted to a PST file

Field	Description
`AccountErrors`	A list of users whose calendars weren't exported.
`PartialAccountErrorsCount`	A list of users whose events were partially exported.
`CalendarEventErrorsCount`	The metadata for events that weren't exported because: Version failure—Event version failed to be recorded. Format failure—Format for the event failed.
`PSTConversionErrorsCount`	For PST-formatted exports, a list of events that couldn't be converted to a PST file. These events are available in their original ICS format in the `export_name-conversion-errors-N`.zip file included in the export.

Field	Description
`AccountErrorsCount`	The number of accounts for which no Gemini app conversation data could be exported
`PartialAccountErrorsCount`	The number of accounts for which some but not all Gemini app conversation data could not be exported

Field	Description
`AccountErrors`	A list of users whose Gemini app conversations weren't exported. Each entry includes a value for `Account`.
`PartialAccountErrors`	A list of users whose events were partially exported. Each entry includes a value for `Account`.