Wind-downs and transitions
Google Workspace at shutdown: export everything before deleting the account
By SourceX Editorial · Updated
Short answer
To export Google Workspace before closing a business, work in order: place Vault holds and pause retention rules, run the admin data export or Vault exports, transfer Drive ownership from departing users, verify the copies, and cancel the subscription last. Deleting a user or the subscription can take held data with it, so never delete first.
Key takeaways
- A Vault hold protects data while accounts exist; it is not an archive and should not be relied on after deletion.
- Suspending users keeps their data in place, while deleting them removes their mail and any files not transferred first.
- Gmail typically exports as MBOX, Calendar as ICS and Contacts as vCard, while native Docs convert to Office or PDF formats.
- Keep the domain registered after cancellation, because other services use it for sign-in and password resets.
What happens to Workspace data when you cancel?#
Google Workspace data is deleted after a business cancels its subscription or deletes its users, and once deletion completes it generally cannot be recovered. Google allows only a limited window after cancellation, and the details change, so check Google's current admin documentation rather than relying on a remembered grace period.
The safe sequence avoids every irreversible step until copies exist and have been checked. The order applies whether the company is small or has kept many former employees' mailboxes alive since past layoffs.
- Place Vault holds where your edition includes Vault, and pause retention rules that purge data.
- Export the organization's data with the admin export tool or with Vault exports.
- Transfer Drive and other data from departing users to a retained account.
- Verify the exports by opening samples and comparing counts.
- Cancel the subscription last, and keep the domain registered.
Step 1: Vault holds and retention rules#
Google Vault holds preserve mail, Drive files and chat messages for as long as the hold applies, even if users delete them, which makes them the first protection in a shutdown. Vault is included in some Workspace editions and not others, so confirm your edition in the admin console before planning around it.
Check existing retention rules too. A rule set years ago to purge mail or chat after a period keeps running during a wind-down. Pause or narrow it, and record the change and who approved it.
Treat a hold as protection while accounts exist, not as an archive. Deleting a user or cancelling the subscription can remove held data along with the account, so export anything under hold before any deletion, and confirm the behavior in Google's current Vault documentation.
Step 2: run the export and know what each service produces#
The organization-wide export in the admin console copies users' data across core services into Google Cloud Storage, from which an admin downloads the archives. Eligibility and included services vary by edition and account history, so read Google's documentation before relying on it. Where the tool is unavailable, Vault exports by user and service, or user-level exports the admin permits, are the alternatives.
Vault exports suit records that may need to prove authenticity later, because they come with metadata about senders, recipients and dates in a form built for legal review. The admin export suits broad preservation. Many companies use both: Vault for mail and chat, the admin export for everything else.
In many exports, Gmail labels travel as a header inside each message rather than as folders. Check that the mail client or review tool you plan to use reads that header before concluding that project labels were lost, since labels are often the only link between a thread and its project.
| Service | Typical export format | Context that can get lost |
|---|---|---|
| Gmail | MBOX files | Label structure in some mail clients, delegated access |
| Google Drive | Native files converted to Office or PDF formats | Ownership, sharing settings, comments in PDF copies |
| Google Calendar | ICS files | Room resources and attachments linked from Drive |
| Google Chat | Structured message files | Space membership and thread layout |
| Contacts | vCard files | Shared directory entries |
| Google Groups | Conversation archives | Group membership and settings |
| Meet recordings | Video files stored in Drive | Which meeting each recording belongs to, unless clearly named |
Step 3: transfer Drive ownership before deleting users#
Drive ownership transfer moves files owned by departing users to a retained account so the files survive when the users are removed. Files in a user's My Drive belong to that user, while files in shared drives belong to the organization. Deleting a user without transferring their files can remove documents colleagues still open from shared folders.
Check sign-in dependencies before suspending anyone. Many companies use Google accounts to sign in to Slack, Jira, the CRM or the accounting system, so suspending a user can lock those tools before their own exports run. List every service that relies on Sign in with Google and switch its admin to a retained account first.
- Suspend departing users first; suspension blocks sign-in but keeps their data in place.
- Use the admin console's data transfer option to move Drive files to a retained admin account, with a folder per former user.
- Where shared drives are available, put folders several people still use into one, so they stop depending on a single person's account.
- Transfer calendar and group ownership where other people still rely on them.
- Log each transfer with the user, date, destination and the person who ran it.
Step 4: verify, then cancel last#
Verification proves the exports open and are complete before anything irreversible happens. Open a sample of MBOX files in a mail client, search for messages you know exist, open converted Docs and Sheets, and compare counts of users, messages and files with what the admin console reports.
When verification passes, close the other services that sign in with Google accounts or move them to a retained address, then cancel the Workspace subscription. Keep the domain registered and its DNS records documented. Other vendors send password resets and ownership confirmations to addresses at that domain, and a lapsed domain can be registered by someone else.
Illustrative: a civil engineering firm closes its Workspace#
Illustrative: a fictional civil engineering firm that peaked at more than 50 employees closes after its principals retire. Project correspondence lives in Gmail, labeled by project number; drawings and calculations live in Drive; and a separate Deltek system holds project accounting.
The office manager places Vault holds on all users and pauses a chat retention rule. Exports run through Vault for mail and through the admin export for the rest. Two retired principals' Drive files are transferred to a retained admin before their accounts are deleted, and the firm's domain stays registered.
The archive now links RFIs, submittals and approval emails to their projects. Because many emails carry client information and drawings under client contracts, any later licensing review starts from internal design discussions and excludes client deliverables.
How SourceX approaches Workspace archives#
SourceX treats email as the hardest Workspace archive to clear, because a single thread can mix internal decisions, customer confidential details and personal information. In the Rights and Preparation steps of the SourceX five-step transaction, mail is scoped conservatively, often to internal threads on defined topics, and Drive content is reviewed by folder and owner.
The SourceX Evidence Packet records the export method and date as part of provenance. The fit check needs only metadata, such as the Workspace edition, the services in use and the date ranges they cover, so it can run before any account is touched.
Frequently asked questions
Can we use Google Takeout instead of the admin export?
Takeout works per user and only when the admin allows it for the organization. That can suit a small team, but it relies on each account still being active and produces separate archives that someone must collect and check. For a company-wide shutdown, an admin-run export or Vault export is easier to control and document.
Does a Vault hold protect data after a user is deleted?
Do not rely on it. Holds prevent users from purging data while accounts exist, but deleting a user or cancelling the subscription can remove data under hold. Export held data first, and confirm the current behavior in Google's Vault documentation before any account is removed.
What happens to files shared with outside collaborators?
Outside collaborators lose access when your files are deleted or their owners' accounts go. Files that outside people own and shared with you are not in your export. Warn key customers and partners who rely on shared folders, and give them time to make their own copies where contracts require it.
Should we keep one Workspace account active after closing?
Some companies keep a single account or a few suspended users for a period so records stay searchable and the domain keeps receiving vendor notices. Whether that is worthwhile depends on how often the records will be needed. A verified offline export with a clear index often serves the same purpose at lower cost.
Can Workspace email and Drive files be licensed later?
Parts can, after review. Internal threads and documents about how work was done can sometimes be licensed after personal and confidential details are stripped out, but email often contains customers' and vendors' confidential information. Rights and privacy obligations are assessed for each archive with counsel before anything is offered.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.