Education & nonprofits

Backing up Google Workspace for Education: what Google keeps, what it deletes, and what the district is responsible for

Google keeps a deleted Workspace for Education account for 20 days, then it is gone, Vault data included. Here is what that means for student churn, Classroom and departing teachers, and which parts are the district's job.

Google runs the infrastructure behind Workspace for Education extremely well. It does not keep your district's data forever, and it does not decide what happens to it when people leave. That second part is the district's job.

Most K-12 districts now run email, documents and teaching on Workspace for Education. Every school year, thousands of accounts are created and retired on a fixed calendar. Every retirement is a moment where data can quietly disappear, and Google's own documentation is clear about how short the safety net is.

This article walks through what Google keeps, what it deletes and when, and which parts of the problem sit with the district. It covers the deleted-account window, the June student churn, Classroom, files left behind by departing teachers, and why Google Vault does not replace a backup.

What Google keeps, and for how long

When an admin deletes an account, Google holds it for 20 days. Inside that window a super admin can restore the user, along with their Gmail, the Drive files that weren't transferred, and their primary calendar. After 20 days the data is gone, and Google's own help article states that it cannot be restored.

There are two smaller catches. A restore needs a free licence of the same type the user had, so a district that has already reassigned seats may have to free one up first. And the 20 days run from the moment of deletion, not from the moment someone notices a problem.

For files and mail deleted inside a live account, the window is similar. Once an item is emptied from the user's trash, admins can restore it from the Admin console for roughly 25 days, by user and date range, not file by file.

Situation

Window

Who can recover

File in a user's Drive trash

Until the trash is emptied

The user

File or mail emptied from trash

About 25 days

Admin, by date range

Deleted user account

20 days

Super admin

After those windows

None

Nobody, including Google support

Those windows are designed for undoing mistakes noticed quickly. They are not designed for a parent complaint in October about work that vanished in July, or for an auditor asking for a former teacher's records two years later.

The June churn: student accounts on a timer

No other sector retires accounts the way schools do. Every summer a whole graduating class leaves, students transfer out, and many districts delete those accounts on a fixed date a few weeks later. The deletions are usually automated from the student information system, in bulk.

There is real pressure to delete. Since July 2022, Workspace for Education comes with a baseline of 100 TB of pooled storage shared by the whole institution, so alumni accounts compete for space with current students and staff.

Google gives students a way out, not the district. The Transfer your content tool, which admins can enable, lets a student copy their Gmail and Drive to a personal Google account. That copy belongs to the student. It does nothing for a district that later needs a graduate's submitted work, a disciplinary email thread, or a file the student owned that a teacher's lesson still links to.

Since 2025 there is a better option than deletion. Education editions now include free Archived User licences: an archived account cannot sign in, but its data is kept under the district's Vault retention rules and can still be searched and exported (Google's guide). Archiving is the right default for leavers. It is still not a backup, for the reasons in the Vault section below.

The practical risk is the bulk job. A sync rule that deletes instead of suspends, or that matches the wrong organizational unit, can remove hundreds of accounts in one run. Google's own advice is to configure Directory Sync to suspend rather than delete. If nobody notices within 20 days, there is nothing left to restore.

Classroom: two kinds of data in two places

Google Classroom looks like one app, but its data lives in two places, and they behave differently when something is deleted.

  • Files live in Google Drive. Each class has a Drive folder owned by the class's primary teacher, and work students turn in is owned by that teacher too. These are ordinary Drive files.

  • Class structure lives inside Classroom itself: the stream, posts and comments, assignments, due dates and grades.

The file half is tied to one person's account. If a teacher's account is deleted before their classes are transferred, Google says the classes can no longer be transferred to anyone else. Students still see them, but with limited functionality, and unless the teacher's Drive was transferred during deletion, the class folder goes with it. Restoring the teacher within 20 days is the only documented way back.

The structure half has no undo at all. Deleting a class is permanent: there is no trash for the class itself. The Drive files survive, but the stream and the grade records attached to the class do not. Archiving is reversible and should be the default at the end of the year.

For a district, that leads to two habits. Transfer class ownership before any teacher account is suspended or deleted, and back up the teachers' Drive, which is where every class folder and every turned-in assignment actually sits. For grades, keep the gradebook of record in the SIS, not only in Classroom.

What departing teachers leave behind

Teachers build up years of curriculum, and much of it is used by colleagues who never think about who owns it. That ownership decides what survives when the teacher leaves.

Shared folders in someone's My Drive. The English department's "shared" curriculum folder is very often a folder in one teacher's My Drive, shared with the rest of the department. Sharing does not transfer ownership. When that teacher's account is deleted without a data transfer, the files disappear for everyone, even though colleagues used them daily.

Shared drives. Files in a shared drive belong to the organization, not to a person, so they survive any single account deletion. The weak point is management. When the only managers of a shared drive were teachers who have since left, nobody can add members or change access except an admin, and Google's own troubleshooting guide treats drives with no manager or no members as a problem to fix. Nothing is deleted, but nobody is looking after the drive either, which is exactly how content goes missing unnoticed.

Three habits cover most of this:

  1. Move department and grade-level material into shared drives, and make a role account or a department head a manager of each one.

  2. At offboarding, transfer the teacher's Drive and Classroom ownership before suspending, archiving or deleting the account.

  3. Back up the teacher's account before any of that happens, so a missed step can be fixed later.

We covered the general version of this in Off-boarding an employee without losing their data. In a school, the same steps simply happen to dozens of people on the same day in June.

Why Vault isn't a backup

Google Vault is a retention and eDiscovery tool. It answers the question "can we find and produce this record?", not "can we put this back the way it was?". Google says as much in its own Vault FAQ: exports are built for legal discovery, Vault cannot make differential backups, and it cannot deduplicate.

The gaps that matter for a district:

  • Deleting the user deletes the Vault data. When an account is deleted, its retention rules and holds stop applying and the data can be purged immediately. Google notes it cannot be recovered even if the account is restored within the 20 days.

  • There is no restore. Vault produces export files. Drive exports aren't separated by account and Google Docs, Sheets and Slides come out in other formats, so putting a teacher's folders back means rebuilding them by hand.

  • Retention rules delete, too. A Vault rule that keeps mail for three years also removes it after three years. A misconfigured rule is a deletion policy.

  • It lives inside the same tenant. A compromised super admin account, or one bad sync job, can delete users and with them everything Vault was holding. A backup should sit outside the tenant, under separate credentials.

Use Vault for what it is good at: legal holds, records requests and searches across the domain. Use a backup for getting data back.

What the district is responsible for

The split is simple. Google is responsible for keeping the service running and not losing data through its own failures. The district is responsible for everything that happens because of its own decisions: who is deleted and when, who owns which files, how long records are kept, and recovering from mistakes, sync errors and compromised accounts.

A short checklist for the next school year:

  • Configure SIS and Directory Sync to suspend or archive leavers, never delete them directly.

  • Use Archived User licences for staff and students who leave, and set Vault retention to match your records schedule.

  • Transfer Classroom ownership and Drive files before any teacher account changes state.

  • Move shared curriculum out of personal My Drives and into shared drives with an active manager.

  • Export Classroom grades to the SIS at the end of each term.

  • Back up every account, staff and students, before the June deletions run, and keep that backup outside Google.

How Duplicati fits

The managed Google Workspace backup in the Duplicati Console covers that last step without the district running any servers.

  • Per-user licence, storage included. Each seat adds 100 GB of backup storage on Duplicati storage, or you can point backups at your own destination.

  • Your credentials, your tenant. You create the access in your own Google Admin console and hand it to the Console. There is no shared vendor credential with access to every school's data.

  • Encrypted before it is stored, with the encryption key shown to you so you keep your own copy.

  • Incremental after the first run, so backing up thousands of student accounts every night stays practical.

  • The backup outlives the account. Deleting a student or teacher in Workspace does not delete their backup; your retention settings decide how long it is kept.

  • Restore where it is needed: back into the original account, or into another one, such as the teacher who takes over a class.

If your district or the MSP that supports it wants to try it before the next June churn, the Console has a 14-day free trial.

Get started for free

Pick your own backend and store encrypted backups of your files anywhere online or offline. For MacOS, Windows and Linux.

Pick your own backend and store encrypted backups of your files anywhere online or offline. For MacOS, Windows and Linux.

  • Example image