"We already deleted the account of an employee who left last month, but now we can't find the quotation template they created"—in offboarding consultations, we hear stories like this remarkably often. People treat departing employees' accounts just like clearing out a physical desk, deleting them abruptly on their last day of work. The feeling is understandable: license fees are an expense, and having an ex-employee's mailbox lingering feels untidy. However, in Google Workspace, this "immediate deletion" is a classic trap that leads to severe downstream accidents.
An offboarded user's account holds far more than their personal emails and calendars; it holds critical corporate assets that must not be lost, including ownership of shared business files, correspondence history with clients, and automation configurations. Yet when you delete the account, all of these disappear along with the individual's personal assets. The real problem is that you only discover what is gone after it has already been erased. In this article, we outline the proper sequence and key considerations for closing accounts upon employee departures.
Start with "Suspension" Rather than Immediate "Deletion"
The very first action to take during offboarding is not deletion, but suspension. Suspending an account instantly blocks logins without altering or damaging any underlying data. While the employee is locked out of their email and Google Drive from that moment on, all data remains intact from the administrator's perspective. It is the safest initial step, preventing unauthorized access by former staff while securing the time needed to wrap up loose ends.
Conversely, deleting an account from the beginning is irreversible. Files in Google Drive, emails, and calendar entries belonging to an offboarded employee whose ownership was not transferred will, as a rule, be permanently lost. If someone realizes after deletion that data was needed, recovery is limited to a 20-day grace period following deletion. Once those 20 days pass, whatever that person owned is truly unrecoverable.
Therefore, the fundamental sequence must be: Suspend → Transfer necessary data → Reclaim license → Delete (after a retention period). What you do on an employee's final day is merely suspend the account, not delete it. Getting this single sequence right prevents the vast majority of accidents.
Transferring Data Held as "Personal Property" to the Company
Once an account is suspended, the next step is transferring data that belongs to the company from the departing employee's account to someone else. It is crucial to understand that in Google Workspace, most data is associated as "the personal property of that individual," meaning it is left stranded once the user departs.
Transfer targets broadly fall into the following three categories.
| Target | Consequence | Example Destination |
|---|---|---|
| Files in My Drive | Sharing breaks and files vanish once the owner is removed | Transfer ownership to successor or supervisor |
| Gmail / Contacts | History of communications with clients is cut off | Delegate access to successor or configure forwarding |
| Calendar events | Meeting context lost due to missing organizer | Transfer ownership of recurring meetings |
The Google Workspace Admin Console provides migration tools to transfer a departed employee's Drive files and contacts to another user in bulk. For Gmail, anticipating that inquiries may continue for some time after departure, configuring account delegation or email forwarding for a set period prevents missing client emails due to "address not found" errors.
Here, it is worth stepping back to consider that having company files residing in an individual's My Drive is itself the underlying issue. Because files in My Drive have an individual owner, offboarding transfers must be performed every time someone leaves, turning missed transfers directly into data loss risks. To eliminate this fundamentally, business files should reside in Shared Drives (owned by teams) from the very start. Files stored in Shared Drives remain unaffected by individual departures. When read alongside our article on visualizing confidential files via AI classification in Drive, you will see that offboarding procedures and day-to-day data hygiene are closely interconnected.
Note That Licenses "Do Not Stop When Suspended"
Once data is transferred, revoke the license. A common misconception here is that suspending an account stops billing: suspending an account does not stop billing for its assigned license. Suspension merely blocks logins, leaving the seat (license) occupied. As more employees leave, paying continuously for unused paid accounts quietly adds up to substantial waste.
In practice, licenses are removed starting with departures whose data transfers are complete. Deleting the entire account naturally frees the license, but due to retention needs discussed later, you can also opt to keep the account suspended while only removing the license. Because preserving a suspended account requires no license, this serves as a pragmatic compromise when you hesitate to delete immediately but want to halt billing.
Decide When to Delete in Coordination with Legal
When to perform the final deletion is a topic that should not be decided by IT alone. Depending on the industry, there may be an obligation or operational necessity to retain departure emails and files as an audit trail for a certain period. Situations genuinely arise during disputes where the only evidence to verify what was said resides in a former employee's inbox.
This is where Google Vault proves effective. With Vault, even after an ex-employee's account is suspended or deleted, data can be preserved under retention policies or legal holds, allowing later search and export. Vault is a higher-tier plan feature and may not be available across every company, but the proper approach is to establish how many years departure data must be retained as a corporate policy, using Vault as the mechanism to technically enforce it.
At a company of roughly a dozen people that we supported, offboarding relied entirely on individual memory, resulting in inconsistent deletion records across past employees. By consolidating the standard sequence of Suspend → Transfer → Retain for 90 days → Delete into a one-page procedure while migrating files to shared drives in parallel, subsequent offboarding could be completed simply by running down the checklist. This transformed a person-dependent chore into an operational process yielding consistent results regardless of who executed it. Rather than the initial rollout itself, turning offboarding into a structured system is where custom development delivers real value. For overall criteria on adopting Google Workspace, our article discussing which plan to choose is also a helpful reference.
What to Do Before Departures Happen
The most effective offboarding approach is not panicking after a departure occurs, but creating an environment beforehand where data does not need manual transferring. Move operational files into shared drives, and summarize the departure checklist onto a single page starting with suspension. With just these two measures, the next departure will not turn into an incident.
Start by checking whether your company's operational files are predominantly stored in My Drive or shared drives. If that organization is lacking, designing file storage locations is well worth tackling even before drafting an offboarding checklist.
Source: Options to preserve former employee data (Google Workspace Help) / How to Offboard Employees in Google Workspace (Damson Cloud)
