Delete a Google Workspace user, and their data has twenty days left
Someone leaves. In the same week, whoever holds the admin login deletes their account, because the licence costs money and the person is gone. Three weeks later a colleague goes looking for the supplier folder that used to be in that person's Drive, or the calendar the team booked rooms through. The account is gone, and so is the button that would have brought it back.
Google Workspace is the example here, on a business that owns its domain, because Google writes the consequences down in one place. Everything quoted comes from pages I read on 12 September 2026, and help pages change without notice.
The restore button lasts twenty days
Google keeps a deleted Workspace user for 20 days, and the restore button disappears with the data on day 21. The page that sets the window is blunt about it:
"You can restore a user account (including administrator accounts) up to 20 days after deleting it. After 20 days, the data is gone and you can't restore it."
Google, Restore a recently deleted user
Inside the window there is a second condition: you cannot restore a user if "You don't have an available user license for the service or edition that was previously assigned to the user". A licence you reassigned on the day you deleted the account is a licence you now need a second copy of.
Missing the window by a week is easy: a user deleted in the first days of the month, a request for a few of their files at the end of it, and the answer is that the data went with the account. Microsoft gives 30 days for a deleted Microsoft 365 user.
What goes with the account, and what stays
The delete page states the rule: "Any data that's not transferred is deleted." The list under "What is deleted" has eleven items, and the first four are the ones a small business runs on:
- Gmail messages and attachments
- Drive files the user owns—These files are saved for 20 days but are only accessible if you restore the user.
- Google Sites pages created by the user
- The user's primary calendar—Also retained for 20 days.
Google, Delete or remove a user from your organization, "What is deleted"
On Drive, the files are kept for twenty days and are "only accessible if you restore the user", licence and all.
The "What's not deleted" list has four items. Files in shared drives, because "Your organization owns these files, not users". Files other people own that happened to sit in the leaver's folders. Groups the user created. And, for now, "Shared calendars the user owns". A business that works in shared drives loses far less than one that works in personal Drives, and that choice was made long before anyone left.
The calendar note that says early 2026
Google's page on deleting a user carries a note that says "early 2026": once it takes effect, a deleted owner's secondary calendars, group calendars and all their events go with the account, and no transfer is possible afterwards. The note, under the list of things to ask the leaver to hand over:
"Note: Starting in early 2026, when a calendar owner is deleted, their secondary calendars—including group calendars—and all of their calendar events are also deleted. You also won't be able to make any additional transfers once a calendar owner is deleted. To prevent losing this data, we recommend transferring calendars before you delete users."
Google, Delete or remove a user from your organization
No exact date is given, and on 12 September 2026 the page's "What's not deleted" list still reads as though the change is pending, so I am quoting the note as it stands. The consequence is the same on any date. The bookings calendar, the one with every recurring client slot in it, lives in whoever created it. Delete that person and the calendar goes with them, events included. Google's calendar page adds that "If a user is suspended (not deleted), their events remain in Calendar".
Google lists the usual reason to delete under "when not to"
Google's own page tells admins not to delete a user to save a licence fee: the option it names is an Archived User licence, which keeps the data and frees the active seat. Whether deleting saves anything depends on the billing plan. The page, under "When not to delete a user":
"Save the cost of a license. To keep the user's data and reduce costs, assign an Archived User license to their account, instead."
Google, Delete or remove a user from your organization, "When not to delete a user"
On the Flexible plan "your monthly rate is prorated accordingly". On the Annual/Fixed-Term plan, "Deleting an account doesn't reduce the number of licenses you have and doesn't affect your billing". On an annual plan, deleting a leaver in month three leaves the bill where it was and starts the twenty-day clock anyway.
Suspended accounts cost the same: on the suspend page, they "are still charged at the same rate as active accounts on both the Annual billing plan and the Flexible plan". With an Archived User licence the data stays (Google's page says it "safely maintains" it) and the active licence "becomes available to reassign to another user within 24 hours". The page names no price, so I will not either.
The integrations that signed in as that person
A deleted user, Google's "Delete or remove a user" page says, "can't access any of your organization's Google Workspace services, or other services associated with their account". The automations authorised under that login are outside its scope, and I could not find a Google page that covers them. The nearest thing to an answer is on Zapier's page about removing a member from a team account:
"Shared account connections will continue working:
- As long as the user's app account exists.
- Until they expire per the app's expiration schedule."
Zapier, Remove members from your Team or Enterprise account, updated 27 August 2026
You can hand the leaver's Zaps to a colleague. They will still sign in to Google as the leaver, until that Google account no longer "exists", and that is the day the admin deletes it. The workflow that filed every invoice into Drive, or wrote every form response into a sheet, stops with no error at your end. Why automations fail silently is about exactly this shape.
The situation, in one line, is the one every integrator eventually hears from a client: we had to let someone go, and now our automations are all broken. The fix is the one argued at length in whose accounts your automation runs on: connections built on a shared address on the client's domain from the start.
Which automations in your business are signed in as a person, and which as the business, goes into the audit's map with an owner against each.
Where this leaves you
Three questions to answer before the next person leaves.
What did this person own? Files in their own Drive, calendars they created, and every automation connection that shows their name. A register of what is automated with an owner column answers this in a minute.
Delete, suspend or archive? Suspend keeps everything and keeps billing. Archive keeps everything and frees the licence. Delete frees the licence on one plan, keeps billing on the other, and starts the clock.
Who transfers the calendars, and when? Before deletion, because afterwards no transfer is possible, in Google's words. None of the three needs software. It is a licence choice and a transfer done in the right order, and the only thing worth writing down is who does it. That list, what each person's account holds and which automations stop the day it is deleted, is part of the process audit, drawn up before you need it. $299, three business days, and a written map you keep whether or not you hire us.
Nothing here is legal advice.