Google Tables Shutting Down December 2025

Google has confirmed that Tables, the spreadsheet-database hybrid that came out of its Area 120 incubator, will be retired and no longer supported after December 16, 2025.

Launched in 2020 to streamline project tracking with automation and relational data, Tables moved from beta to a Google Cloud product in 2021 and survived multiple internal reorganizations that shuttered many Area 120 projects.

Why this matters

For organizations that used Tables for project management, CRM-like trackers, recruiting pipelines or IT operations, the shutdown means they must choose how to preserve data, automations and permissions without interrupting business processes.

Google’s message to admins is pragmatic: export to Google Sheets for simple table-based needs, or use a new migration tool to import into AppSheet when you need to keep column types, relationships and automation intact.

Sheets or AppSheet — which to pick

Think of Google Sheets as the quick shoe-box: great for flat exports, ad-hoc reporting and teams that can rebuild minor automations with formulas and notifications. AppSheet is the architect’s toolkit — it preserves data models, relationships and automations so you can rebuild apps and workflows without rethinking the schema.

If your Tables setup uses linked records, custom column types, role-based permissions or multi-step automations, AppSheet’s migration tool will likely keep more of your work intact and reduce rework.

Immediate actions for admins

Google’s timeline gives teams time, but not forever. Start with a rapid audit: identify active Tables, owners, downstream dependencies, critical automations and compliance-sensitive data. Then choose the migration path that minimizes operational risk.

• Export an inventory of Tables and map owners and usage.
• Decide per-table whether Sheets (simple) or AppSheet (app/workflow parity) is required.
• Test the migration tool with a noncritical table and validate column types, relationships and automations.
• Update documentation, access controls and integrations before cutover.

Broader context

Tables’ retirement is part of a longer arc: Area 120 was scaled back in 2022 and largely wound down in 2023 as Google refocused on AI. Several Area 120 projects were absorbed into core products, but Tables — after a stint inside Workspace under Google Cloud — has now reached its end-of-life.

For teams, the shutdown is a reminder to avoid lock-in with experimental platforms and to maintain clear export paths, backups and automation runbooks.

How to reduce migration risk

Treat migration like a small product release: define success metrics, stage the migration, communicate timelines to stakeholders, and keep a rollback plan. Validate that reporting, notifications and access controls work the same after migration.

Organizations that need help mapping complex Tables setups into AppSheet apps or recreating automations in Sheets should approach this as a data and workflow engineering problem, not simply a file export.

QuarkyByte’s approach is to quickly inventory assets, model the destination schema, and create migration playbooks that preserve relationships, automations and access controls — keeping teams productive through the transition. Start planning now to avoid last-minute disruption before the December 2025 deadline.