The team behind Tables has created a new, first-party experience to power automated apps and workflows directly inside AppSheet, Google’s no-code platform. This new experience was generally launched in June of 2023 as AppSheet databases. Users who want to try AppSheet databases can learn more about getting started with AppSheet here.
This migration tool will migrate data from Tables into AppSheet while preserving relationships, data type columns and formatting. Alternatively, users can export their data into Google Sheets and convert it to a Table in Sheets for similar functionality.
The migration tool consists of 3 main steps: exporting the workspace into a Google Sheet, importing the data into an AppSheet database, and locking the Tables Beta workspace to prevent future edits. Note that the Sheet that is exported from this migration tool consists of additional metadata needed to preserve column types, relationships, and views. It is different from the one generated by the export to CSV option. Any edits to data or table structure should be done inside Tables, not the exported Google Sheet.
Migration Tool FAQ
What types of data can be migrated from Tables to AppSheet via this tool?
For a full list of supported column types and what they will look like in AppSheet, see here. Comments are now exported into a text column, upon importing into AppSheet databases they will remain as a text column. Files that are uploaded into Tables will not be migrated.
I'm stuck on the "Data export in progress" step of the migration tool, or my data is not exporting. What should I do?
First, ensure that Tables has access to core services data in order to export data into Google Sheet. This setting is controlled by your Google Workspace administrator.
If a column has missing configuration details (Ex. a dropdown column is missing selection options) or if the column is not supported in AppSheet databases, this may cause issues during the data export. Convert the column to a text column and try again. If export through the migration continues to fail, export the data into Sheets and then import it into AppSheet.
What does it mean when a workspace is locked?
Workspaces can be locked by the workspace editors in the migration tool, or any time from the workspace menu. When a workspace is locked, the workspace and all tables in it will become readonly - their details and data can no longer be updated. We recommend locking exported workspaces to maintain data consistency, as it will indicate that future edits must be made in the new data location.
If a workspace is locked and you want to export it again, or you need to make an edit to the data, the workspace owner can unlock the workspace from the workspace menu until the read only date.
Can I redirect my exported workspace to the new data location in AppSheet database?
Yes, if you lock a workspace from the workspace menu (not through the migration tool), it will give you the option to specify a link to an AppSheet database. The locked workspace will then show a link to redirect users to the new data location.
Will ACLs from Tables beta be preserved or translated to AppSheet?
No, workspace ACLs will not be automatically migrated to AppSheet. The process owner will have to re-share the AppSheet database with the team. Unfortunately, Google groups are not directly supported for sharing at the moment. By default when an app or database is created, it is not shared with anyone except the creator.
Will the migration process preserve the formatting and styling of my data?
Yes, the migration tool should preserve relationships, most column types and formatting (ie. colours) as well as views.
Is there a way to preview the migration tool before fully migrating?
Workspaces can be exported multiple times, so you can try out migrating your data as many times as you need before fully making the switch. If you have locked your workspace but need to retry the migration, you can unlock the workspace from the workspace menu to access the migration tool again.
Can I migrate data from multiple workspaces at once?
Yes, accessing the migration tool from the Home page will allow you to select multiple workspaces that you own at the same time.
Can I migrate data from multiple Workspaces into a single AppSheet database?
No, this is not currently supported. If you would like tables to end up in the same AppSheet database, it is recommended to move those tables into the same workspace before starting the migration process. In AppSheet, data can be copied from one database to another using automation and data actions.
If I modify my exported workspace in Sheets or AppSheet database, will those edits be reflected in the original Tables Beta workspace?
No, any edits to exported versions of the workspace will not be reflected back in the original Tables workspace. We recommend locking the Tables workspace once it is exported so that all future edits will be done in the new data location.
I’m missing data after importing into AppSheet databases, what can I do?
If a column has partially columns with some missing data: retry the export and import
If a column is present but it is entirely blank: retry the export and import
If a column is entirely missing from the table: check that it is not one of the unsupported column types and if there is a work around here.
If a column has a different data type: check that it is not one of the unsupported column types and if there is a work around here.
If there are rows missing from the table: Retry the export and import into AppSheet. Check that your AppSheet plan allows for the appropriate number of rows in an AppSheet database.
There’s an error when I import the Sheet to AppSheet, what can I do?
Your tables may fail to import if there is a blank table with no columns. Delete the blank table inside Tables and then export your data through the migration tool again.
General AppSheet FAQ
Do I need an app or a database? I don’t see any bots inside AppSheet databases.
The primary distinction between a workflow setup in Area 120 Tables Beta and AppSheet is in the components used to create the workflow. In Tables, both the Bot and Form are created in the same interface as the table.
In AppSheet, Bots are built and managed in the app editor, which is separate from the table. If you prefer users to use a similar interface for editing data as you did in Tables, you can continue to use AppSheet databases. Forms are a type of view for Apps, more about forms can be found here.
What is AppSheet?
AppSheet is a no-code platform that enables users to create mobile and desktop applications to help digitize their processes. These applications include powerful automations that can perform actions on connected data. Users can connect their existing data or manage it in our native data source: AppSheet databases.
AppSheet databases offer a data modeling and interaction experience that is familiar to Area120 Tables Beta users. Many of the use cases that Tables supports are also supported across AppSheet. However, there are some Tables features and behaviors that are not currently replicated within AppSheet. This document provides an overview of the differences between Area120 Tables Beta and AppSheet databases.
Does AppSheet databases have an API?
AppSheet databases do not have a direct Rest API, however, there is a Rest API to access a table within an AppSheet app. This means if an AppSheet database is connected to an app, the AppSheet API can read and write data to that table. Learn more here.
I’m unable to choose a file from my Drive to import or I get a 403 error upon import, what should I do?
This may happen when AppSheet is unable to connect with your Google Drive account. Try logging out of AppSheet and logging back in to reestablish the connection.