Webinar · Oct 29 Still paying for Archived User (AU) licences? See how to preserve former-employee data, delete old accounts safely, and reclaim licences — while staying 100% compliant.
Save my seat →
Start For Free

Google Workspace Archived User Licenses: Cost, Alternatives, and How to Stop Paying for Them

IT Ops Automation, Zenphi Use Cases By Industry Or Role

Archived User licenses· Employee offboarding· Google Workspace cost

Archived User licenses keep a former employee's data searchable in Google Vault, and they keep billing every month for as long as the account exists. We compare the five things you can do with a departed employee's account, including a license-recycling approach that keeps data in Vault without adding a new Archived User license.

By Daniel Kovach Updated September 2026
Quick answer

Yes, you pay for archived users in Google Workspace. Each archived account needs an Archived User license, and because most organizations retain former-employee data for years, these licenses accumulate. The alternatives are to suspend (billed at the full rate), delete (Vault data is lost), export and then delete (data leaves Vault), or recycle the account for a replacement hire, where Vault retention rules keep the former employee's data and no Archived User license is needed.

What's in this guide
The basics

What an Archived User license does

When you archive a user in the Google Admin console, Google replaces their active Workspace license with an Archived User (AU) license. According to Google, the archived user can't sign in to any Workspace service, disappears from the Global Address List, and stops receiving new email and calendar invitations. Their data stays in place and remains available to Vault for retention, search, and export. The active license they held becomes available to reassign within 24 hours.

Archived User licenses are supported on Business Starter, Business Standard, Business Plus, Enterprise, and Education editions. On the Flexible Plan, you receive an AU license automatically for each user you archive and are charged for it on your next bill. Data belonging to archived users also counts toward your organization's pooled storage. Rates vary by edition and by how you buy Workspace, so check the Billing section of your Admin console or ask your reseller for the figure that applies to you.

The cost problem

Why Archived User costs keep growing

A full license is tied to someone who works for you. An Archived User license is tied to someone who used to, and it stays on the bill until the retention period ends and someone actively deletes the account. That means the number of archived accounts tracks your cumulative departures over the retention window, and it doesn't shrink on its own.

1,050

archived accounts for a 1,000-person company with 15% annual turnover and a seven-year retention requirement, if every departing employee is archived. Illustrative arithmetic: 150 departures a year × 7 years. Your turnover and retention periods will differ.

In that example, the organization pays for more archived accounts than it has employees before the oldest accounts become eligible for deletion. The per-license price is lower than a full seat, and the volume grows every year for companies with steady turnover and long retention obligations.

Compare your options

Five options for a former employee's Google Workspace account

Every departure ends in one of five outcomes. The right one depends on whether you must retain the data, whether it needs to stay searchable in Vault, and whether someone is joining to take over the role.

Option What happens to the data Searchable in Vault Ongoing license cost Fits when
Suspend Stays in the account. Collaborators keep access to shared files. Yes Full license rate The situation is temporary: leave, an investigation, or a pending decision.
Archive Stays in the account. The user can't sign in. Yes One Archived User license per account Data must stay in Vault for a long period and nobody will reuse the account.
Delete Removed. Recoverable for 20 days, then gone unless transferred first. No None No retention obligation applies and needed files have been transferred.
Export, then delete Kept in an export location such as a Google Cloud Storage bucket. No Storage costs only Data must be kept, but day-to-day Vault search isn't required.
Recycle for a new hire Purged from the mailbox and Drive, and kept in Vault by retention rules. For data under retention rules None beyond the seat the new hire needs anyway A replacement is starting and retention rules already cover the former employee's data.
Suspend

Suspension blocks sign-in without touching data, and it can be reversed at any time. Google bills suspended accounts at the same rate as active ones on both Annual and Flexible plans, so suspension suits short holding periods while a decision is pending.

Archive

Archiving is Google's recommended way to keep a former employee's data available to Vault. It costs less than a full seat, and the cost continues for every month the account remains archived.

Delete

Deletion ends the cost and the data. Google's Vault FAQ confirms that once a user is deleted, their data can't be searched or exported from Vault, retention rules and holds stop applying, and data can be expunged right away. Use Google's transfer tool first for any Drive files or calendars that colleagues still need.

Export, then delete

Running a Google Vault export to a Cloud Storage bucket before deleting the account removes the license cost while keeping a copy for compliance. The trade-off is that the data is no longer searchable in Vault, so any future eDiscovery request means working with the export files directly.

Recycle the account for a new hire

When a replacement joins, the former employee's account can be cleared, renamed, and handed to the new person. Vault retention rules keep the purged data available for search, and because the account is never deleted, no Archived User license is added. This option has the most prerequisites of the five, and we cover them in detail below.

The recycling option

Recycling a Google Workspace account for a new hire

This approach relies on how Vault retention works. Google's documentation states that users can delete messages and items in Google services, and any data covered by a retention rule or hold remains available in Vault. Deleted messages retained by Vault also don't count against the user's storage. If your retention rules already cover the former employee's data, clearing their mailbox and Drive removes it from the account without removing it from Vault. The account itself, and the license attached to it, can then move to the person replacing them.

Vault is a prerequisite.

Recycling only works on an edition that includes Google Vault, such as Business Plus or Enterprise, with retention rules configured for the organizational unit the account belongs to. Without an active retention rule, clearing the mailbox and Drive deletes the data permanently once Gmail's 30-day preservation period and Drive's trash cycle pass.

The sequence

  1. Confirm retention coverage

    Check that Vault retention rules cover the account's organizational unit for every service you need to retain, for at least your required retention period. Vault covers Gmail, Drive, Chat, Calendar, Groups, Meet, Sites, Voice, and the Gemini app. Services outside that list, such as Contacts and Keep, aren't retained, so export anything from them that you need to keep.

  2. Record the handover

    Log the former employee's name, the reassignment date and time, and who approved it. Future Vault searches on the account can be bounded by that date to separate the two people's data.

  3. Secure the account

    Reset the password, sign the user out of all sessions, revoke app passwords and third-party app access, remove recovery details and 2-Step Verification devices, and remove the account from managed mobile devices. Clear any mail delegation, forwarding, and filters.

  4. Hand off what colleagues still need

    Transfer ownership of Drive files and calendars that others rely on to a manager or a shared drive before clearing anything. Deleting files the former employee owned removes collaborators' access to them, and removing events they organized can disrupt attendees.

  5. Clear the account's content

    Delete the remaining email, Drive files, calendar events, contacts, and Chat content. Items covered by retention rules stay available in Vault.

  6. Reset memberships and profile

    Remove the account from groups, shared drives, and admin roles the new hire shouldn't inherit. Update the organizational unit, title, department, manager, photo, and email signature.

  7. Rename the account and deal with the old address

    Change the primary email to the new hire's address. Google keeps the previous address as an alias that delivers to the same inbox, so remove it, or reroute it to a manager or group, before the new hire signs in.

  8. Hand the account to the new hire

    Issue fresh credentials, require 2-Step Verification enrollment on first sign-in, and assign the license tier the new role needs.

What to settle with legal and compliance first

Recycling changes who an account's Vault records belong to over time. Before adopting it as policy, agree on how you'll handle the following:

  • Vault searches, holds, and exports on the account will return data from both the former and the new employee. The handover date is how you tell them apart.
  • A hold placed on the account after reassignment also captures the new employee's data.
  • If retention rules for that organizational unit are shortened or removed later, the former employee's data can be purged.
  • Your privacy notices and employee policies should reflect that a reassigned account carries a prior owner's retained records.
  • Confirm with your Google account team or reseller that account reassignment fits your agreement.

When to archive instead

Recycling suits routine backfills where the retention requirement is general. Archive the account instead when the former employee is the subject of a legal hold, litigation, or an investigation; when your policies require each custodian's records to sit in a separate account; when nobody is replacing them; or when your edition doesn't include Vault.

Planning to recycle accounts at scale?

Walk us through your retention rules, your approval chain, and what should happen to each departing employee's account. We'll map the offboarding flow that fits your policy.

Book a call See offboarding automation
Clean up the backlog

Reducing the archived users you already pay for

Recycling helps with future departures. Most organizations also carry a backlog of archived accounts, and many are older than the retention period that justified archiving them. A periodic review can bring that number down:

  • List every archived account with its archive date. The Admin console shows archived status in user reports, which makes the list straightforward to pull.
  • Compare each account against your retention schedule. Flag accounts whose retention period has ended.
  • Check for holds and open matters. Any account connected to a legal hold or an active matter stays archived.
  • Delete accounts that are past retention and clear of holds. This ends the Archived User license for each one.
  • Export and delete where Vault search isn't needed. For accounts that must be kept but are unlikely to be searched, an export to Cloud Storage replaces the license with storage cost.

Going forward, the most effective control is to decide the outcome for each account at the moment someone leaves: archive, export, recycle, or delete. That decision works best as a step in your employee offboarding checklist with a named approver.

Former employees are one source of unused licenses. Active accounts that nobody signs in to are another. For that side of the problem, see our guide to Google Workspace license management and inactive-user audits.

Do the math

How to estimate your Archived User savings

Current annual AU spend = archived accounts × monthly AU rate × 12 Savings per recycled account = monthly AU rate × 12 × years of required retention

Use your contracted Archived User rate from your Admin console or reseller invoice. Each recycled account avoids one Archived User license for its full retention period, and each backlog account deleted after its retention period ends removes one from the current bill. Recycling only applies to roles you backfill, so count departures with a replacement separately from those without one.

Automation

Automating the decision and the steps

Each option above is a sequence of Admin console actions, and the recycling sequence has eight steps that need to happen in order. Teams handle this in a few ways: manually in the Admin console with a checklist, with scripts built on the Admin SDK and Vault APIs, or with a workflow automation platform that combines the steps with approvals and an audit trail.

Zenphi is a no-code workflow platform built for Google Workspace. An offboarding and data archiving flow in Zenphi can start from an HR system update or a form, look up the user's manager and current licenses, and route the account decision to HR, legal, or IT for approval. Once someone approves an outcome, the flow runs the matching steps, such as suspending the account, transferring Drive and calendar ownership, exporting Vault data to a Cloud Storage bucket, renaming the account and removing the old alias, or archiving. Each step is written to an audit log with the approver and timestamp.

Because recycling hands an account straight to a new hire, it works best when offboarding and onboarding run as one connected process. Our guide to Google Workspace user lifecycle management covers how to link the two.

You can get started with Zenphi and build the flow around your own retention rules, or ask questions in the Zenphi Users community.

Further reading

Related guides

License management Find inactive users and reclaim unused licenses Run recurring license audits, route decisions to managers, and act on the result. Checklist Employee offboarding checklist The steps IT needs to complete so departing employees lose access to company data. Offboarding automation Automate employee offboarding in Google Workspace Build an offboarding flow that covers access, data transfer, and account status.

Stop adding Archived User licenses by default

Bring your retention schedule and your offboarding process. We'll show how Zenphi can route each departing account to the right outcome and run the steps automatically.

Book a call with the Zenphi team Explore Google Admin automation
Frequently asked questions

Google Workspace archived users: FAQ

Do you pay for archived users in Google Workspace?

Yes. Each archived account requires an Archived User license, which costs less than a full Workspace license and is billed for as long as the account stays archived. On the Flexible Plan, Google adds an Archived User license automatically for each user you archive. The rate depends on your edition and how you buy Workspace. With Zenphi, a scheduled workflow can check archived accounts against your retention schedule and route each one for deletion, export, or continued archiving once its retention period ends.

What happens when you archive a user in Google Workspace?

The user can't sign in to any Workspace service, is removed from the Global Address List, and stops receiving new email and calendar invitations. Their data stays in the account and remains available to Google Vault. Their active license becomes available to reassign within 24 hours, and their data continues to count toward pooled storage. Zenphi can archive users as the final step of an automated offboarding flow, after Drive files and calendars have been transferred to the right owner.

Should I archive or delete a former employee's account?

Archive when you need the data to remain searchable in Google Vault. Delete when no retention obligation applies and any files colleagues need have been transferred. Deleting a user removes their data from Vault and ends any retention rules or holds on it, and the account can only be restored within 20 days. If you must keep the data but don't need Vault search, exporting it to Cloud Storage before deleting is a middle option. Zenphi can route this decision to HR, legal, or IT for approval and then run the chosen outcome, including a Google Vault export to Cloud Storage before deletion.

Does a suspended user still use a Google Workspace license?

Yes. Google bills suspended accounts at the same rate as active accounts on both Annual and Flexible plans. Suspension is useful as a temporary state while you decide what to do with an account. In Zenphi, an offboarding flow can suspend an account right away and then archive, export, or delete it once the outcome is approved, so accounts don't stay suspended on a full license.

Can I reuse a former employee's Google Workspace account for a new hire?

Yes, if your edition includes Google Vault and retention rules cover the former employee's data. You clear the account's content, rename it, remove the old address alias, and assign it to the new hire. Retained data stays searchable in Vault and no Archived User license is needed. Agree first with legal and compliance on how Vault searches and holds will separate the two people's data, and archive instead if the former employee is subject to a legal hold. The steps can be run manually or scripted, and Zenphi can automate the sequence with an approval step and an audit log of each action.

What happens to Google Vault data when you delete a user?

Vault can no longer search or export the user's data, retention rules and holds stop applying, and the data can be expunged right away. Google recommends an Archived User license for data you need to preserve. Recycling the account for a new hire or exporting the data before deletion are the alternatives when you want to avoid that license. Zenphi can export a user's Vault data to a Cloud Storage bucket before the account is deleted, as a step in an automated offboarding workflow.