Import an app from AppSheet
Moving off AppSheet? Emberblocks reads the app's Application Documentation export and rebuilds the app on a new Ember database — then tells you, item by item, what came across as-is, what changed and what it could not bring.
Before you start
- You need to be an owner or admin of the workspace.
- The import creates a new app with its own database; it never touches an existing app. Normal plan limits apply.
- The export contains no data rows, so the new app starts empty. Bring rows in afterwards with the CSV import on each table, or connect the original database as a data source.
How it works
- 1
Export the documentation
In the AppSheet editor open Manage → Author → App Documentation, then save the page as HTML (Ctrl+S, “Webpage, HTML only”). The file is typically 10–30 MB. - 2
Upload it
On the workspace home choose Import from AppSheetand drop the file. Your browser reads it and sends only the app's structure — tables, columns, expressions, views, rules, actions — never the file itself. - 3
Review
Pick the tables to import (AppSheet's internal bot tables are left out), confirm the users table and, for the few views whose table the export does not name, choose one. The coverage report on the right updates from your choices and can be downloaded as Markdown. - 4
Create
The app opens in the builder with an Import report strip under the top bar. Every item that did not import links to the field, view or action it concerns.
What comes across
| Setting | Options | What it does |
|---|---|---|
| Tables & columns | — | Every column type has an Emberblocks equivalent, including Time, Duration, EnumList-of-Ref (multi-reference), Signature, Image and File. Key columns are kept as hidden, read-only text. |
| Expressions | — | App formulas, initial values, Show_If / Required_If / Valid_If and slice filters are translated when they use functions Emberblocks has. Anything else is dropped and reported with the original expression. |
| Slices | — | Become filtered tables. A slice that filters on the signed-in user is proposed as a role row filter — never applied automatically. |
| Views | — | Table, deck, card, gallery, calendar and detail views, dashboards as multi-block pages, plus navigation order and icons. |
| Actions | — | Set value, add row, open URL, email, phone, SMS, navigation and grouped actions, placed by prominence. |
| Format rules | — | Become style rules on columns and actions. |
| Users & roles | — | The users table becomes the app's user source; one app role per value of its Role column, with table permissions from each table's update mode. |
| Bots | — | Not in the export. Each bot becomes a disabled placeholder workflow named after it, so you know what to rebuild. |
Wide tables
A table with more than 60 columns raises the new database's column limit to fit it (up to 150). Columns beyond 150 are skipped and listed in the report.
What is not imported
- Rows, files, bots and app settings — the export does not contain them.
Editable_IfandReset_Ifconditions,CONTEXT(), actions that run other actions on related rows, and expressions built on functions Emberblocks does not have (the report names each one).