Google has confirmed that Tables will stop working after December 16, 2025. The company told customers to move their data to Google Sheets or AppSheet. The notice arrived by email and on the Tables website. Users should act now to protect data and workflows.
Tables launched in 2020 from Area 120. The tool combined spreadsheet-style views with database features and built-in automation. It appealed to teams that needed flexible project tracking. Google moved Tables into Google Cloud in 2021 and promised it would grow into a full product.
Why the shutdown is happening
Area 120 changed direction in recent years. Google closed many experimental projects and shifted focus to core and AI work. Some Area 120 ideas moved into other Google products. Tables lasted longer than many experiments. Now Google has set a firm end date.
What Google recommends
Google gave two migration paths. For simple needs, export to Google Sheets. Sheets can hold records and basic formulas. It can also support conditional notifications and scripts for some workflows. For teams that need app-like features, move to AppSheet. AppSheet is a no-code platform that keeps column types, relationships, and many automations. Google built a migration tool to preserve more structure when moving to AppSheet.
Start the migration now
Begin by cataloguing the Tables workspaces that matter. Back up all data locally. Export a copy to Sheets to keep an immediate archive. Use the AppSheet migration tool on a test workspace to see how automations and permissions transfer. Check automations and integrations carefully after migration. Allow time to retrain team members on the new system.
What to expect in AppSheet
AppSheet preserves table relationships and many column settings. It supports automations approvals, and fine-grained access controls. AppSheet also integrates with Google Workspace and Cloud services. For teams that run approval forms or field operations, AppSheet will be the closest replacement.
Small teams and simple cases
If a team used Tables only for basic tracking, a Google Sheets workbook may be enough. Sheets can scale and can be enhanced with macros and Apps Script. That route will be faster for simple projects. It is a good choice when you do not need app logic or role-based access.
Integrations and third-party tools
Do not forget external integrations. Any tool that is connected to Tables must be reconfigured to point to Sheets or AppSheet. Dashboards and reporting will need validation. If a third party used an API to read Tables, make sure that the connection is rebuilt.
Timing and risk
The shutdown date is not far away. Teams with heavy use should begin migration now. Test the migrated workflows and make sure reporting and permissions hold up. Google will publish support documents and an FAQ. Follow the official guidance and keep a local backup of all records.
What this means for users
The end of the Tables is a reminder of the life cycle of cloud tools. Teams must plan for product changes and vendor shifts. AppSheet offers an orderly path for teams that need automation and app-level controls. Google Sheets will work for many straightforward uses. Either way, the move will take time and planning.
How to manage the change
Assign a project owner to lead the migration. Make a checklist of key tables, automations, and integrations. Run a pilot migration. Communicate with your team about timing and training. Keep a conservative timeline to allow for fixes and user feedback.
Google closing Tables will reshape how some teams work. The change is manageable if it is planned early. Export data today and begin testing the migration tool so workflows remain intact.