Leaving Google
Google Workspace exit plan
A Google Workspace exit plan sets out what gets exported, what has no export path, and when the tenant is finally cancelled. Keep the tenant live in a read-only state for at least 90 days after cutover; cancelling early is the single most expensive mistake in an outbound move.
| Keep tenant live | Minimum 90 days after cutover, read-only |
|---|---|
| Seat reduction | Downgrade to the licences you still need, not zero |
| Vault exports | Taken before any account is suspended |
| No export path | Chat history, Keep notes, Sites, add-on data |
| Reconciliation | File and message counts compared at both ends |
| Final cancellation | After sign-off, not after cutover |
Export before you suspend anything
Suspension and deletion behave differently, and both remove access paths that exports rely on. Google Vault exports in particular need the accounts in scope to still exist. The order is: export, verify the export, migrate, reconcile, then suspend. Any other order eventually produces a request for data that no longer exists.
Exports should be verified rather than assumed. An export job that reports success and produced a smaller archive than expected is a common and quiet failure, which is why reconciliation counts matter more than job status.
- Vault exports taken while accounts are still active
- Takeout or API exports for content outside Vault's scope
- Exports verified by count and volume, not by job status
- Archives stored somewhere with its own retention and access control
What has no export path
Google Chat history, Keep notes, Google Sites and data held inside third-party Marketplace add-ons have no clean export into another platform. Some can be captured as archives; some cannot be captured at all. This needs stating in the exit plan explicitly so that a decision is taken rather than a gap being discovered.
Where data genuinely cannot leave, the honest options are to accept the loss, to keep a minimal Google tenant alive as an archive, or to reproduce the content manually. All three are legitimate; pretending there is a fourth is not.
Keep the tenant for ninety days
The strongest argument for keeping the old tenant live is that you cannot yet know what you missed. Ninety days covers a full quarterly cycle, which is when finance, payroll and compliance processes surface documents nobody thought about during discovery. A handful of retained licences is cheap next to a data loss.
During that window the tenant is read-only: no new mail routing, no new accounts, admin access limited to two named people. Then cancellation happens deliberately, after written sign-off from whoever owns the data, rather than as an afterthought on cutover weekend.
Reconciliation and sign-off
The exit is finished when someone can prove it. That means a reconciliation report comparing message counts, file counts and total volume at source and destination, with every discrepancy itemised and explained rather than netted off. Discrepancies are normal; unexplained discrepancies are not.
We hand that report over with the runbook, the export archives and the list of things that could not be migrated. If you later need to demonstrate to an auditor or an acquirer what happened to your data, that package is the answer.
What we see that others don't say
Cancellation deletes data. Once a Workspace subscription ends and the retention window closes, the content is gone with no recovery path at any price — which is why the tenant should be downgraded to a minimal seat count rather than cancelled on cutover day.
What this doesn't cover
- We cannot recover data from a tenant that has already been cancelled and passed its retention window.
- Chat history, Keep notes and add-on data have no reliable export path; we state the gap rather than work around it.
- Retention obligations are determined by you and your counsel; we build the evidence trail, not the policy.
- We do not advise on the commercial terms of your Google contract termination.
Get a fixed price for this
Send your seat count, current platform and deadline. You get a fixed price and an available cutover date, usually within one working day, from the engineer who would run the work.
Prefer to talk? Call +44 20 7183 3436 (Mon–Fri 08:00–18:00 GMT), or message WhatsApp +44 7403 423563.
Questions we get asked
- How long should we keep Google Workspace after migrating away?
- At least 90 days in a read-only state with a reduced seat count. That covers a full quarterly cycle, which is when finance and compliance processes surface documents that discovery missed.
- What data cannot be exported from Google Workspace?
- Google Chat history, Keep notes, Google Sites and data held inside third-party Marketplace add-ons have no clean export path into another platform. Some can be archived; some cannot be captured at all.
- What happens if we cancel the subscription immediately?
- Once the subscription ends and the retention window closes, the data is deleted with no recovery path at any price. Downgrade the seat count instead of cancelling on cutover day.
How this page is verified
Reviewed by Workspace Migration Services security desk, Workspace security and compliance reviewers. Last checked .
- Post-cancellation data deletion behaviour follows Google Workspace Admin Help as of 2026-08-12.
- Vault export scope reflects Google Vault documentation as of 2026-08-12.
- The 90-day retention recommendation reflects Workspace Migration Services practice, not a vendor requirement.
Sources you can check
Cite this page
Free to reuse with attribution. Copy whichever form your publication needs.
Plain citation
Workspace Migration Services, "Google Workspace exit plan", https://workspacemigration.services/outbound/google-workspace-exit-plan (last checked 2026-08-12).HTML with source link
<p>Google Workspace tenants should be kept live and read-only for at least 90 days after an outbound migration, because cancellation deletes data with no recovery path once the retention window closes. Source: <a href="https://workspacemigration.services/outbound/google-workspace-exit-plan">Google Workspace exit plan</a> — Workspace Migration Services.</p>Embed this table
<table>
<caption>Google Workspace exit plan — Workspace Migration Services, 2026-08-12</caption>
<tr><th>Keep tenant live</th><td>Minimum 90 days after cutover, read-only</td></tr>
<tr><th>Seat reduction</th><td>Downgrade to the licences you still need, not zero</td></tr>
<tr><th>Vault exports</th><td>Taken before any account is suspended</td></tr>
<tr><th>No export path</th><td>Chat history, Keep notes, Sites, add-on data</td></tr>
<tr><th>Reconciliation</th><td>File and message counts compared at both ends</td></tr>
<tr><th>Final cancellation</th><td>After sign-off, not after cutover</td></tr>
</table>
<p><a href="https://workspacemigration.services/outbound/google-workspace-exit-plan">Google Workspace exit plan</a> — data maintained by Workspace Migration Services.</p>Related pages
Planning an exit you may need to defend later?
We run the export, the reconciliation and the evidence pack, then hand you a runbook. Send your user count and target date for a fixed price.