Google Tables, the lightweight work-tracking tool that tried to marry spreadsheets with simple databases and automations, is being put out to pasture. In an email to users this week, Google said Tables “will no longer be supported” after December 16, 2025, and it is urging customers to either export their data to Google Sheets or migrate it into AppSheet — Google’s no-code app platform — using a migration tool that preserves column types and relationships.

This isn’t just another product sunset. For the teams and small businesses that built day-to-day workflows in Tables — kanban boards for hiring, lightweight CRMs, ticket queues, field checklists — the announcement is a sharp reminder of a painful truth in the cloud era: tools that look indispensable can vanish when they stop being core to their parent company’s strategy.

Tables began life inside Area 120, Google’s internal incubator for employee-led projects, and launched publicly in 2020 as an easy way to track work with automation “bots” — recurring reminders, conditional notifications, and simple triggers that moved rows between queues. The project did well enough to be “promoted” out of Area 120: in 2021, Google moved Tables into the Google Cloud/Workspace family, signaling that it saw the product as having broader enterprise and productivity potential.

But Google’s in-house lab didn’t survive intact. Area 120 was pared back during a reorg and then wound down during wider company layoffs; some projects were folded into core products, others quietly faded. Tables survived that winnowing for a while by living inside Workspace, but surviving didn’t mean indefinite investment. The team behind Tables has been shifting its focus for years toward a unified “data experience” inside AppSheet — a move that makes the current shutdown less sudden than it feels.

What Google is offering Tables users (and what will be lost)

Google laid out two clear paths for users:

• Export to Google Sheets. If your Tables usage is simple — flat tables, occasional conditional notifications — a Sheets export keeps your raw data in the Google ecosystem. But Sheets lacks many of the relational or automation niceties that made Tables appealing to users who wanted lightweight app-like behavior inside a table.
• Migrate to AppSheet using Google’s migration tool. AppSheet databases are a first-party, native data layer inside AppSheet that was announced in mid-2023; Google says the migration route will preserve column types, relationships, and automation workflows where possible, and let teams manage permissions, integrations, and more sophisticated automations. For organizations that relied on Tables’ structured data and bots, AppSheet is the more natural destination.

The support documentation also notes that workspaces are already in read-only mode, and that bots, forms, and the API are disabled. That means teams can view and export, but they can’t continue normal operations in Tables while they plan a migration.

The human side: teams, templates and the cost of moving

For many small teams, Tables was attractive because it allowed non-technical people to build custom workflows without engineers. That convenience is precisely what makes a shutdown costly: templates, dozen-column schemas, views and automations — all of that needs translation into Sheets formulas or AppSheet app logic. Migrating will take someone on the team to map fields, test automations, and re-train staff.

Google’s migration tooling aims to reduce that friction, but tool-assisted moves are rarely frictionless. Expect surprises: calculated fields that rely on specific Table behaviors, integrations with third-party services, or internal scripts that can’t be mapped automatically will require manual engineering. For organizations that embedded Tables in critical workflows, the practical path is to triage: export everything, identify mission-critical workflows, and prioritize which should be rebuilt in AppSheet (or replaced by a competitor like Airtable, Notion, or a homegrown database).

Why Google is folding Tables into AppSheet (and what that signals)

Product rationales are usually a mix of strategy and math. Google’s public messaging suggests overlap between Tables and AppSheet’s native database experience — rather than maintain two parallel no-code data products, Google appears to be consolidating investment behind AppSheet as the primary no-code platform inside Workspace and Cloud. The company has been steadily evolving AppSheet’s native database features since mid-2023, and pushing users toward a single platform simplifies product roadmaps and support.

That decision also fits a broader pattern at big tech firms: experimental tools can be quickly incubated and, if they don’t scale to a certain adoption or strategic fit, the parent company folds their functionality into larger platforms — or retires them entirely.

A practical checklist for Tables users (what to do this week)

1. Export everything now. Download CSVs or use the Sheets export to capture raw data (don’t rely on live access).
2. Inventory automations and integrations. Document any bots, form inputs, API hooks and third-party integrations. These will be the hardest to recreate.
3. Decide: Sheets, AppSheet, or another tool. If you need relational data, granular permissions, or app-style UI, move to AppSheet. If your usage is tabular and formula-driven, Sheets may suffice.
4. Test critical workflows first. Rebuild and validate one core workflow in the target platform before moving everything.
5. Communicate with your team. Expect downtime or behavioral changes; set expectations and training time.

Final thoughts

Google Tables’ end is a bummer for the teams that had come to rely on its simple, no-code automations. But it’s also an instructive case study: choose tools that solve real problems, but assume any single-vendor product — even one from a giant like Google — can be reprioritized. Keep backups, maintain an inventory of automations, and where possible, avoid single points of vendor lock-in for mission-critical workflows.