Export Google Workspace Email to PST: Everything You Need to Know

Why Organizations Export G Suite to PST?

• Employee offboarding: preserving a departing employee’s mailbox in a portable, searchable format without keeping their Google Workspace license active.
• Legal holds and e-discovery: producing mail data in a format legal teams and review platforms are built to ingest.
• Compliance retention: meeting record-keeping requirements that specify a defined retention period independent of the live mailbox.
• Standalone backup: building an offline copy of mail data that doesn’t rely on continued Google Workspace access.
• A step inside a larger migration: moving off Google Workspace altogether, where PST serves as an intermediate or archival format rather than the final destination.

If the goal is a live, working mailbox rather than an archive, that’s a different project. See our guide on migrate Google Workspace to Microsoft 365 for the direct migration path instead of export-to-file.

What a Complete PST Export Should Include

A PST export that’s actually usable later needs more than just message bodies. At minimum, export Google Workspace email to PST should carry across:

• Every message across all folders and labels, not just the inbox.
• Attachments in their original form, not stripped out or converted.
• Headers, including sender, recipient, and original timestamps.
• No changes should be done in Read/unread status.
• Folder structure that maps sensibly from Gmail’s label system into Outlook’s folder hierarchy.

Contacts, Calendar, and Tasks are separate Google services with their own export paths; PST is a mail-only container. If those need to migrate too, they have to be handled as separate export or migration steps, not assumed to ride along inside the PST automatically.

Export Google Workspace (G Suite) Emails to PST via Google Takeout, Then Convert

For a small number of mailboxes, Google’s own tools can get partway there:

1. Sign in to the Google account and go to Google Takeout.
2. Deselect all, then select Mail only (add Contacts or Calendar separately if those are also needed).
3. Choose the label scope: all mail, or specific labels only.
4. Then, choose the archive format and maximum archive size; larger size settings mean fewer split files to reassemble later.
5. Create the export and wait for Google’s notification email; this can take anywhere from minutes to a couple of days depending on mailbox size.
6. Download every part of the archive before the download link expires.
7. Extract the ZIP files to get the MBOX file(s) inside.
8. Convert the MBOX output into PST using a conversion tool, since Outlook cannot open MBOX directly.

Why Export G Suite mailbox to PST Isn’t a One-Click Job?

• Google doesn’t export straight to PST: Takeout only outputs MBOX. To end up with PST, you either convert MBOX afterward or use a tool that pulls from Google Workspace and writes PST natively.
• Takeout also wasn’t built for IT-scale exports: It’s a per-user tool, so admins can’t run one export for an entire org — someone has to trigger it account by account.
• PST has a 50 GB per-file cap in Outlook 2010 through 365, so any export of large mailboxes needs a plan for splitting across multiple files, not just one big dump.
• Google adds its own limits on top: Takeout caps and splits archive size, and the Gmail API enforces per-user quotas. Both need to be factored into the export plan, especially for old, attachment-heavy mailboxes.
• Big exports also tend to get interrupted: dropped connections, API throttling. Whether the process can resume where it stopped or has to restart from scratch makes a real difference on large jobs.

Advanced Method: Export Google Workspace email to PST

Once the job involves multiple mailboxes, or requires an auditable, IT-managed export, a Cigati Google Workspace Backup Tool is generally the more practical route. The relevant capabilities to look for:

• Admin-level, bulk mailbox selection rather than one self-service export per user.
• Direct PST output, without routing through MBOX as an intermediate step.
• PST splitting once a mailbox’s exported data approaches the destination format’s size ceiling.
• Folder and label structure preserved, with metadata intact.
• Resume capability if the job is interrupted partway through.
• A completion report per mailbox, listing item counts and any items that failed to export.

Additional Features You Get When Export Google Workspace Emails to a PST file Free Up Server Space: Move migrated items to the Bin or permanently delete them after successful migration. Date Range Filter: Migrate or back up only the data within a specified date range. Skip Folder: Exclude selected folders from the backup or migration process. Duplicate Handling: Prevent duplicate items by skipping data that has already been migrated. Split Resultant File: It divides large output files into smaller, manageable sizes. Downtime: Minimize service interruption with a migration process designed to keep business operations running.

Simple Way to Export Google Workspace emails to Outlook PST

1. Install and run the Cigati Google Workspace Backup Tool on your system.
   
   


2. Choose Mailbox Migration from the center panel.
   
   


3. Select the login method and enter the login credentials.
   
   


4. Choose the account from which you want to migrate data >> Next.
   
   


5. Select PST as the Output destination from the file format dropdown.
   
   


6. You have to apply the filters for specific data migration and click on Start Migration.
   
   


7. View or monitor the migration process.
   
   

Authentication and Permissions

Exporting at the organization level, rather than one user exporting their own mailbox through Takeout, requires admin-level access on the Google Workspace side. Depending on the method, that typically means one of:

• OAuth 2.0 authentication as an authorized admin.
• Domain-Wide Delegation, which lets a service account act on behalf of any user in the domain without each user individually authorizing access.
• A service account with a JSON or P12 key, scoped to the specific Google APIs the export uses (Gmail API at minimum).
• An IMAP app password that pulls mail through IMAP rather than the Gmail API directly.

Whichever method is used, the account performing the export needs sufficient admin scope to read every target mailbox. A standard user account can only export its own mail, not other users’ mailboxes in bulk.

For organizations weighing whether PST export is even the right call versus a direct platform migration. It’s worth reviewing common causes of Google Workspace migration failure before committing to either path. The planning mistakes that derail a migration are largely the same ones that derail a bulk export.

Confirming the Export Actually Worked

Before deleting anything from the source Google Workspace account, verify:

• The PST opens in Outlook without a repair prompt or corruption warning.
• Message counts in the PST reasonably match the source mailbox (accounting for any date or label filters applied).
• Folder structure mirrors the original label structure in a sensible way.
• Attachments open correctly and aren’t truncated.
• Timestamps and read/unread status are carried over.
• If the mailbox was large enough to require multiple PST files, every split file is accounted for, and none were left behind mid-download.

Conclusion

Getting Google Workspace mail into PST comes down to matching the method to the task. Use Takeout plus conversion for a small number of individual mailboxes needing export. Choose a dedicated tool like Cigati Google Workspace Backup Tool for anything spanning the whole organization instead. Always account for the 50 GB PST limit and Google’s own export quotas. If the real goal includes moving Calendar, Drive, or Photos, plan differently. That’s a full migration project, not a simple way to export Google Workspace email to PST. Either way, verify the output carefully in Outlook before touching the source mailbox.

Related Post