# Can you archive a departed Google Workspace user instead of keeping an active seat?

> Test historical retrieval, Vault access and future-contact handling before replacing a departed user's active Workspace license with the archive route your account supports.

Updated 2026-10-21 · https://onelesstool.com/guides/google-workspace-leaver-archive-test

**Archiving can be suitable when colleagues need historical records, but only after you prove retrieval and arrange future contacts separately.** Keep the current paid arrangement if either requirement remains unresolved. A successful archive test does not establish that the current contract will cost less.

This concerns one departed user's account while the organization keeps [Google Workspace](/tools/google-workspace). Sources were checked on October 21, 2026; the proposed pilot is **UNEXECUTED**. No account was changed and no catalog price was freshly verified. The records owner must supply approved retention and access requirements: this is not legal retention advice. Forms, Apps Script, integrations and other live workflow transfers need separate tests.

## Choose the account state deliberately

| State | What it means for this decision |
| --- | --- |
| Administrator suspension | Blocks the user's access without deleting data, but also blocks new email and calendar invitations. Suspended accounts still incur active-account charges. [Google's suspension guidance](https://knowledge.workspace.google.com/admin/users/suspend-a-user-temporarily). |
| Archive | Retains data while blocking account sign-in and new email/calendar invitations. [Google's archive behavior](https://knowledge.workspace.google.com/admin/users/archive-former-employee-accounts). |
| Deletion | Removes the user's Workspace data, including data held or retained by Vault. It is outside this procedure. [Google's preserve-leaver warning](https://knowledge.workspace.google.com/admin/vault/preserve-data-for-users-who-leave-your-organization). |

Keeping a license during investigation must not mean leaving a former employee able to sign in. Have the administrator maintain the organization's offboarding controls independently of this cost review. Suspension alone is neither the archival decision nor a complete future-contact plan.

Write down the historical jobs: finding an old customer thread, opening its attachment, retrieving a Drive document and locating a calendar record. Specify who may perform each job, acceptable retrieval time and where approved exports belong. Separately decide whether future correspondents can be redirected to a successor or require uninterrupted delivery to an established address.

## Identify which archive route your account actually offers

**Separate Archived User subscription:** licenses match the Workspace edition, such as Business Plus with Business Plus – Archived User. Under that subscription's Flexible billing, archiving automatically adds licenses and charges; Annual billing can require additional purchased capacity. [Google's Archived User licensing](https://knowledge.workspace.google.com/admin/billing/add-archived-user-licenses).

**Flexible Plan without a separate Archived User subscription:** Google now documents an archive alternative within the user-removal flow. Confirm Flexible billing and the absence of an Archived User subscription in the actual account. [Google's separate-subscription exception](https://knowledge.workspace.google.com/admin/users/archive-former-employee-accounts).

Do not treat those as identical purchasing arrangements or infer that the second is free. Record the edition, direct-versus-reseller purchase, displayed archive option and dated billing confirmation. This article supplies no deletion click path. If the administrator cannot distinguish the archive confirmation from deletion, stop and obtain account-specific guidance.

## Prove that preservation includes usable retrieval

Vault coverage for an archived user depends on their Vault license or an Archived User license containing Vault. [Archived-user Vault conditions](https://knowledge.workspace.google.com/admin/users/archive-former-employee-accounts). An archive badge alone is insufficient evidence.

Google lists Vault with Business Plus and Enterprise Standard/Plus, among other editions; it does not list Business Starter or Standard as including Vault. For add-on compatibility, Google directs customers to Sales. Vault administrators also need Vault licenses. [Current Vault licensing requirements](https://knowledge.workspace.google.com/vault/getting-started/vault-overview).

Inspect both the archived subject's entitlement and each retrieval operator's access. Creating an export requires Manage Searches and Manage Exports; organizational-unit scope and access to the relevant matter also affect what an operator can retrieve. [Google's Vault privilege reference](https://knowledge.workspace.google.com/admin/vault/set-up-vault-privileges). Do not widen access merely to make the rehearsal pass.

Vault is not an independent backup: retention rules act on supported service data, and Google says retention does not begin until rules are configured. [Vault's retention boundaries](https://knowledge.workspace.google.com/vault/getting-started/vault-overview). Have the records owner confirm existing coverage and required history without changing policies for this test. If Vault is unavailable, mark that retrieval route unproven; a visible shared file does not demonstrate recoverable historical mail.

## Give future contacts an accountable destination

For the no-separate-subscription route, Google documents a delegate for file-access requests and future email, with a notification telling email senders whom to contact instead. [Google's delegate guidance](https://knowledge.workspace.google.com/admin/users/archive-former-employee-accounts). That statement does not promise automatic forwarding or a successor inbox containing every original message.

Name the future-contact owner and a backup person. Agree who checks requests during absence and how correspondents reach the backup. Test what the sender sees and what the delegate actually receives; do not infer one from the other. If uninterrupted receipt is essential, defer archiving until an administrator has separately established and tested that arrangement. Do not assume this delegate behavior applies to every licensing route.

## UNEXECUTED pilot: dummy records, retrieval and reversal

Use an approved dummy user with the intended edition, archive route and relevant policies. Keep the real leaver's records and account state unchanged during the rehearsal. Record the actual names of the administrator, records owner, contact owner and **backup retrieval owner**; a team name is insufficient. Approve any test-related charges before proceeding.

1. **Prepare fixtures.** Create clearly labeled dummy received and sent messages, an attachment, a Drive document and a calendar event. Record identifiers, expected contents and access boundaries. Include a restricted document to test that unrelated users remain excluded. Preserve the fixture manifest and baseline evidence.
2. **Establish the baseline.** The primary and backup retrieval owners independently find the fixtures through the intended authorized route. Record their licenses, roles, matter scope, search terms, export destination and results. A missing baseline item stops the test before archiving.
3. **Rehearse archiving only.** The administrator applies the confirmed archive route to the dummy and records its resulting state and license inventory. Confirm blocked dummy sign-in. Repeat retrieval and open the exported attachment and document; compare content and identifiers with the manifest. Record elapsed time and every missing or unreadable item.
4. **Exercise future contacts.** From approved internal and external test addresses, send harmless messages and a calendar invitation to the dummy. Capture sender outcomes and delegate notifications. If redirection is acceptable, have the test sender follow the notice and confirm actual successor receipt. Have the backup handle a dummy file-access request under the approved access rules. An unexplained bounce, missing request or contact dependent on the absent primary fails acceptance.
5. **Rehearse reversal.** Google says unarchiving restores the previous status, requires an available matching Workspace license and then manual license assignment. [Google's unarchiving conditions](https://knowledge.workspace.google.com/admin/users/archive-former-employee-accounts). On the dummy only, have the administrator verify that sequence, intended access state and fixture retrieval. Record timing and differences; returning to a previously suspended state is not a failed restoration merely because sign-in remains blocked.

Keep the evidence until the records owner accepts retrieval and the contact owner accepts the tested destination. If the dummy cannot reproduce a relevant entitlement or restriction, label that portion **unproven**. Defer the real archive when retrieval, backup coverage, contact handling or reversal fails; this checklist authorizes no live change.

## Reconcile the remaining bill and commitment

Archived data still consumes pooled storage, and existing add-on licenses remain assigned. [Google's storage and add-on behavior](https://knowledge.workspace.google.com/admin/users/archive-former-employee-accounts). Obtain the proposed storage entitlement and actual usage before assuming capacity is sufficient.

Google's Annual/Fixed-Term guidance says payments remain unchanged until renewal despite unnecessary licenses being removed. [Seat-reduction timing](https://knowledge.workspace.google.com/admin/billing/reduce-user-licenses). A reusable seat is therefore not an immediate invoice reduction.

Compare current and proposed organization charges over the same future term, currency and tax basis. Show purchased active seats, archived users, remaining commitment and renewal date explicitly. Include archive charges, required Vault access for subject and operators, retained storage/add-ons and any separate contact-handling cost once. Have the billing administrator or reseller confirm the effective date and first affected invoice, especially for the newer Flexible route.

Calculate **current committed charge minus confirmed remaining charge**; record one-time rehearsal effort separately. If the total cannot decrease yet, count no current saving. Keep or defer when the operational test fails, the contract is unclear or the remaining bill removes the benefit. Record the accepted decision in the [subscription audit](/audit), with the [cancellation checklist](/guides/cancel-software-safely) for billing follow-through.