Google Workspace Email and Data Retention When an Employee Leaves

By Patronum

October 26, 2026

Read Time: 7 mins

Google Workspace Email and Data Retention When an Employee Leaves image

The leaver timeline: suspend, hand over, preserve, delete
What happens to each type of data when you delete a user?
Can Google Vault keep a deleted user’s data?
Archived user vs suspended user: which keeps the email?
An example leaver retention checklist
How Patronum handles a leaver’s email and data
Putting it together
FAQ
Sources

To keep a former employee’s email in Google Workspace, make one decision first: keep the account on an Archived User license, or export the mail to an archive you control and verify it before anything is deleted. Deleting the user deletes their Gmail and any Drive files you didn’t transfer, and Vault retention rules and holds stop protecting that data the moment you delete. Patronum’s offboarding policies handle the handover: they transfer files, calendars and contacts, route the old address to a Google Group, and archive the leaver’s email and Vault data to your own Google Cloud Storage bucket.

Where new mail goes is a separate question. Routing the address to a group keeps customers’ emails from bouncing, but it doesn’t preserve a single message already in the mailbox.

The leaver timeline: suspend, hand over, preserve, delete

Keep these four stages apart. Squashing them into one click is how data gets lost.

Day 0: suspend. The user can’t sign in, but “Email, documents, calendars, and other data aren’t deleted.” New email and calendar invitations are blocked (Google Workspace Admin Help). There’s no time limit, but suspended accounts “are still charged” like active ones.
Handover (you set the length). Transfer files, calendar and contacts, and decide where new mail to the address should go. Check for a litigation hold first: “You can’t transfer data or delete a user who is on litigation hold.”
Preserve existing data. Either move the account to an Archived User license and keep it, or export the mailbox to your own archive and confirm the export is complete.
Delete, only if you exported. “You can restore a deleted account for up to 20 days.” That window is for mistakes, not storage: untransferred Drive files “are saved for 20 days but are only accessible if you restore the user” (Google Workspace Admin Help). An account you’re keeping as the archive is never deleted while its retention period runs.

The leaver timeline in Google Workspace: suspend, hand over, preserve, then delete only after a verified export

For the security steps (passwords, 2-Step Verification, devices, connected apps), see our Google Workspace offboarding guide.

What happens to each type of data when you delete a user?

During deletion, super admins can transfer “the user’s Drive and Docs files, primary Calendar data, and Data Studio data” (Google Workspace Admin Help). Everything else follows the table below.

Data	What deletion does	How to preserve existing data
Gmail	Messages and attachments are deleted.	Keep the account on an Archived User license, export from Vault, or migrate the mail to another account. Separately, route the address so new mail doesn’t bounce; routing keeps nothing already in the mailbox.
Drive (files the user owns)	Deleted unless transferred. Kept 20 days, reachable only by restoring the user.	Transfer ownership before deleting, ideally to a shared drive.
Shared drive files	Unaffected. The organization already owns them.	Nothing to do.
Calendar	Primary calendar is deleted unless transferred.	Transfer it during deletion.
Contacts	Not among the transfer options on Google’s deletion page.	Export before deleting, or hand over with a tool.
Chat	Not among the transfer options on Google’s deletion page.	Export from Vault, which supports Chat exports.
Groups they created	Kept, “even if they were the only member.”	Nothing to do.
Vault-retained or held data	Deleted with the account. Rules and holds “no longer apply.”	Archived User license with Vault coverage, or a Vault export stored outside Workspace.

Can Google Vault keep a deleted user’s data?

No. Google Vault retention rules and holds only protect data while the account exists. Google’s Vault help is blunt: “Do not delete the account. If you delete a user, you also delete that user’s Google Workspace data, including data held or retained by Vault” (Google Vault Help). Restoring within 20 days doesn’t bring that protection back.

Google gives two ways to keep held data: switch the user to an Archived User license, or “export the data from Vault and keep it outside Google Workspace.” A hold belongs to a legal matter, not to IT. Release one only with written authorization from whoever owns that matter, usually legal counsel or your compliance lead. Once a hold is released, the change takes 24 to 48 hours to take effect before deletion is possible (Google Vault Help).

If you export, download promptly: Vault export files “are available for 15 days after you start the export” (Google Vault Help).

Archived user vs suspended user: which keeps the email?

Both keep it. Vault “preserves data for suspended accounts,” but Google recommends an Archived User license “instead of, or shortly after, suspending their account” (same Vault page), since a suspended user costs a full license. Archived User licenses are available on Business Starter, Business Standard and Business Plus, plus Enterprise and Education editions (Google Workspace Admin Help).

An Archived User license doesn’t automatically mean Vault coverage, though. Google says you can protect an archived user’s data with retention rules and holds “If the user has a Google Vault license or a license from an Archived User subscription that contains Vault” (Google Workspace Admin Help). Business Plus, Enterprise Standard and Enterprise Plus include Vault; Business Standard and Business Starter aren’t on Google’s list of editions that do (Google Vault Help). On those plans, an archived account still keeps its data in Workspace, but it isn’t under Vault retention rules or holds unless you’ve bought Vault add-on licenses.

We compare the three account states in suspend, archive or delete a Google Workspace user and cover the license in our Archived User license guide.

An example leaver retention checklist

Copy this into your leavers policy. It sets who owns each item and what prompts a review; it doesn’t tell you how long to keep anything. Retention periods depend on your country, sector, contracts and open disputes, so agree them with your legal or compliance lead and write them into the policy, not this table.

Data	Action at exit	Where it’s kept	Owner	Review trigger
Gmail	Archive the account or export the mailbox; route the address to a team group for new mail	Archived User license, Vault export or own archive	IT admin, with records owner	Policy period ends and no hold applies
Drive (owned files)	Transfer to a shared drive	Shared drive	Team lead who owns the drive	The drive’s own content review
Calendar	Transfer to the manager	Manager’s account	Receiving manager	Annual records review, or the manager leaves
Contacts	Export or hand over to the manager	Manager’s account or export file	Receiving manager	Annual records review, or the manager leaves
Chat	Preserve if relevant to a matter	Vault, or Vault export	IT admin, with legal	Policy period ends and no hold applies
Data under legal hold	Keep the account archived; don’t delete	Archived User license with Vault coverage	Owner of the legal matter	Written release from the matter owner
The account itself	Suspend on day 0, then archive or (after a verified export) delete	Admin console	IT admin	Handover checklist signed off

How Patronum handles a leaver’s email and data

In Patronum, you build an offboarding policy scoped to an organizational unit, a Google Group or all users, with conditions such as Suspended or End Date. Moving a leaver into an offboarding OU is the typical trigger; Emergency Offboard runs it against one user on demand. You configure:

Files: transfer Drive files to a shared drive (folder structure rebuilt, file IDs kept) or to an executor such as {{manager}}.
Calendar and contacts: transfer calendars, and remove the leaver from everyone’s My Contacts.
Email routing (new mail): Rename User, then Assign Google Group, so the old address delivers to a team group. The group must already exist; Patronum won’t create it (Patronum Help Center).
Licenses: remove them, or assign an Archived User or Cloud Identity Free license.
Archive (existing mail): “Archive User Email” sends the leaver’s email to your own Google Cloud Storage bucket in Mbox (RFC 4155) format. Patronum Archive can also move Google Vault data there, “including deleted emails held under a retention or hold policy.” You set retention per bucket, search by former employee, date or keyword, and restore a mailbox or single items to Gmail (Patronum).

Archive covers email and Vault data, not Drive files; those go through the Files transfer. The Backup section’s Vault export, which writes the user’s Vault email as MBOX to a named shared drive, is a separate mechanism.

Before you rely on it, confirm the routing group exists, the bucket is connected (Settings > Integrations), and the execution log shows success. Run the policy on a test account before a real departure.

Putting it together

Say a 40-person company on Business Standard has a sales manager leaving on Friday. IT suspends the account that afternoon. Business Standard doesn’t include Vault, so they confirm whether this user has a separate eligible Vault entitlement before relying on Vault retention rules or holds.

Next week, Drive files move to the sales shared drive, the calendar goes to the manager, and the address delivers to a sales group, so new customer emails land somewhere. That handles new mail only. For the existing mailbox, they pick one route:

Keep it in Workspace. Move the account to a Business Standard Archived User license and keep it archived for the period in their policy. The data stays in Workspace; without a Vault entitlement it isn’t covered by Vault rules or holds. The account isn’t deleted.
Keep it outside Workspace. Export the mailbox to the company’s own archive, check the export is complete and opens, and get sign-off from whoever owns records. Only then delete the account, with the 20-day window as a safety net for mistakes.

For the security side of the same departure, work through our Google Workspace offboarding guide.

FAQ

Can I give the leaver’s email address to someone else?
Yes. The address is removed 20 days after deletion, but “you can reassign the address to another managed user before that 20-day period ends” (Google Workspace Admin Help).

Does deleting a user cut my bill?
Not on an Annual/Fixed-Term plan, where deleting “doesn’t reduce the number of licenses you have.” On the Flexible Plan, charges are prorated (same page).