What happens to Google Workspace data when you delete a user?

What is deleted, what stays and what can be moved#

Google Workspace user deletion removes data tied to the person's account and leaves data that belongs to shared spaces. The admin console offers to transfer some of the user's data during deletion; anything not transferred goes with the account.

The practical question for each row is ownership. Google Workspace ties most content to the account that created or owns it, so a person who kept quotes, customer spreadsheets and project folders in My Drive rather than a shared drive takes them along at deletion unless someone moves them first.

The Vault row surprises many admins. Google's Vault documentation warns that deleting an account removes that user's data even if it is under a hold, so a hold protects data only while the account exists. Check the current Vault help pages before you design offboarding around holds.

The deletion timeline, stage by stage#

A deleted Google Workspace user moves through four stages, before deletion, at deletion, the restore window and purge, and each stage closes options. Google's admin help documents how long a deleted user can be restored; check it before you count on that window, because once it passes the data is purged and Google support generally cannot bring it back.

The alias step is useful in offboarding. Once the account is gone, adding the former address as an alias on a manager's or a shared account keeps customer and supplier email arriving without keeping the old account alive.

• 1Before deletion: the account can be suspended, archived, exported or transferred with nothing lost.
• 2At deletion: the admin console offers transfers, and anything not transferred is scheduled for removal with the account.
• 3Restore window: an admin can restore the user and the data that went with the account, for a limited period.
• 4After the window: the account and its remaining data are purged, and the address can be reused or added as an alias to another user.

Pre-delete checklist#

A Google Workspace pre-delete checklist prevents the most painful loss in offboarding: mail and files someone needs after the account is gone. Run it for every departure, not only senior ones, because frontline staff such as dispatchers, coordinators and account managers often hold the customer threads.

Two items are easy to miss because they look like tools rather than records. Google Forms that collect service requests or quote inquiries are Drive files owned by whoever built them, and Apps Script automations or Looker Studio reports can stop working when their owner disappears. Move both to a role-based owner before the account goes.

• 1Confirm with HR, legal and the person's manager that no hold, dispute or audit requires the account to be kept.
• 2Transfer My Drive files to a named owner, ideally a role-based account rather than another individual.
• 3Export Gmail if the mail must be kept outside Google, and record where the export is stored.
• 4Check Vault: if retention rules or holds apply to the person, suspend or archive instead of deleting.
• 5Move ownership of Google Groups, Sites and calendar resources the person managed.
• 6Review third-party apps that used the person's account for sign-in or integrations, such as a CRM email sync.
• 7Write down the deletion date, who approved it and what was transferred or exported.

Suspend, archive or delete?#

Of suspending, archiving and deleting a Google Workspace user, only deletion removes data, so it should come last, once you are sure nothing in the account is still needed. Suspension blocks sign-in and keeps everything in place. An archived user license, where your edition offers one, keeps the data reachable for admins and Vault without an active user.

A sensible default is to suspend at departure, transfer and review during a set offboarding period, then either archive or delete with a documented reason. Writing that rule into your retention schedule takes the decision away from whoever happens to be clearing licenses that month.

Illustrative: a software company deletes accounts too fast after a layoff#

Illustrative: a fictional maker of fleet maintenance software for trucking companies reduces headcount. To cut costs, an admin deletes the departing support and engineering accounts the same afternoon, accepting the default prompts without transferring anything.

A week later the head of support asks for a former support lead's escalation tracker, a Google Sheet in that person's My Drive, and the threads with two large customers behind it. Because the restore window is still open, IT restores the deleted users, transfers their My Drive files to a role-based support account and moves the accounts to archived user licenses.

One account deleted at an earlier departure is past the window. Its files in the engineering shared drive survive, but its mail and My Drive files are gone, including a spreadsheet that mapped customer bugs to releases. The company rewrites its offboarding runbook: suspend at departure, review within a set period, and delete only with a recorded approval.

Why departed users' Drive files and mail matter later#

A departed user's Drive files and mail often hold the working records behind the systems of record: the tracker someone kept in a spreadsheet, the customer threads behind a credit, the notes on how a recurring fault was fixed. The CRM, help desk or field service platform keeps the outcome, but rarely the reasoning, and none of it can be rebuilt once the account is purged.

Kept records help with disputes, audits and handovers, and, after rights review and privacy preparation, they can be considered for licensing to AI developers. A SourceX fit check needs only metadata, such as how many retained accounts exist, which roles they belonged to and the years they cover. A package that proceeds follows the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, with the company approving each step.