Data in and out
Data in and out
Who can do this: Edit on the table to import rows. Read on the table to export its rows. Owner to repeat an import on a schedule, to export or import a whole space, to duplicate a space and to install modules. See the .
What it's for
You can bring data into a table from a file, a Google Sheet, a web address, a pasted block or another table. You can save the way you map the columns so the next import is one click. You can take rows out as CSV or XLSX. And you can move or copy a whole space: export it to a file, import that file into another space, or duplicate the space in one step.
Before you start
For a table import you need Edit on that table.
Uploaded files are stored by the installation. Google Sheets and web addresses are fetched by the server.
Needs your administrator: file uploads and file storage are installation settings. If an upload fails with a storage error, ask your administrator to check file storage. See .
Steps: import rows into a table
Open the table. In the toolbar, open the Data menu and choose Import data…. You do not see it on a table you cannot edit.
Upload. Pick one source tab:
Upload file: CSV, XLSX, JSON or XML, up to 100 MB. Drag a file in or click to choose.
Fetch URL: a web address, with optional Headers and Request body. The address is fetched by the server, so it must be reachable from where the app runs.
Google Sheets: paste the link and press Import sheet. Set the sheet's sharing to "Anyone with the link can view" first. Only the first tab is imported by default; you can switch tabs in the next step.
Paste: copy cells in Excel or Google Sheets and paste. Include the header row so columns match by name.
Table: copy rows from another table in the space. You can take All rows or only the rows of a saved view. The copy keeps links, tags and statuses and shows only columns you can see in that table.
Configure. Set Encoding, Separator, Sheet or Header row as needed. The preview shows the first 10 rows. The wizard detects the file format and the header row, and flags low confidence — please confirm when unsure.
Mapping. For each Source column, pick a Target field (or Do not import) and a parser (Text, Number, Date, Boolean). Tick Skip if empty to drop rows missing a value. Add new column creates a column on the spot.
Under Conflict handling choose a Strategy:
For the last two, pick Match by column.
Always insert (allow duplicates)
Skip if row with same key exists
Update if row with same key exists
Review. Check Source, Mapping and Existing rows, then start the import. A progress screen shows Imported rows and Skipped rows.
Careful: a number longer than 15 digits is rounded when stored in a number column (for example a long card or order number). The wizard warns: map such a column to a text column.
Save the mapping as a profile
On the Configure step, under Reusable profile, press Save as a new import profile and give it a name. Anyone who can edit the table can then pick it with Apply saved import profile. Updating a profile changes it for everyone who uses it, including automations that import with it; the dialog lists how many. A profile belongs to one table. From other tables copies a profile by matching column names and tells you which fields it could not match.
Repeat an import automatically
An owner sees Repeat automatically on the Review step. It saves the import as a schedule. Scheduled imports need Update or Skip, because Always add would duplicate every row each run. Manage them under Scheduled imports (Run now, Delete). A schedule that keeps failing is turned off automatically.
Undo an import
A table import writes one Bulk import entry in the change log, with no before-image, so it cannot be undone from the log. Copy a table first if the import is risky, or import into a scratch table. See . When you copy rows from another table, the progress screen can also offer Remove from source, which turns the copy into a move.
Steps: export a table
In the table, open the Data menu.
Choose Export to CSV or Export to XLSX. On a pivot view the items read Export view to CSV and Export view to XLSX; Export source rows to XLSX gives the underlying rows.
The file downloads. It holds the columns you can see, in the order shown, and the rows that match the current filters and sort.
The Data menu is shown to everyone who can open the table; export needs only read access. Hide a column from a group (see the ) if they should not take its values away.
Steps: move a whole space
Export / Import is in the space menu and needs Owner.
Choose Export / Import. The dialog is titled Export / Import workspace.
On Export, choose the scope (Export the entire workspace or Export only selected documents), whether to Export text documents, and Table data: Export the rows or Structure only.
Press Start export, then Download export. You get one JSON file with documents, tables, forms, dashboards, portal users and access.
In the other space, open Export / Import, go to Import, press Choose export file…, then confirm. The warning says how many documents, rows and assets will be added. Existing content is kept and the imported items are added next to it.
Tick Leave automations and connectors switched off when moving a live space, so nothing sends mail or syncs until you turn it on.
Careful: the export file carries connector credentials and portal user emails. Anyone who holds the file can recover those credentials. Treat it like a password file and delete it when done.
Importing the same file twice adds everything twice. After an import, read the notes: internal-user grants and group members are not transferred (give those rights again on the new space), and files that could not be fetched are listed for re-upload.
Steps: duplicate a space
Choose Duplicate project in the space menu (owners). On a demo space the same slot reads Use as a template.
Give the copy a name and an address (Name of the new project, Address (slug)).
Under Table data choose Copy the data or Structure only.
Press Create copy. When it finishes, press Open the copy.
What a copy does and does not carry
Owner copy (Duplicate project) | Demo copy (Use as a template) | |
|---|---|---|
Documents, tables, views, forms, dashboards, spreadsheets | Copied | Copied |
Rows | As you choose | As you choose |
Images and files | Shared with the original, not duplicated | Same |
Connector credentials, portal users, groups and their grants | Copied | Not copied |
Automations that send mail or messages, call outside services or spend AI credit | Copied but switched off; the dialog counts them | Same |
Other automations | Copied and running | Same |
Published pages and portal access | Switched off in the copy | Same |
Your own AI key, backup settings, allowed web origins, custom domains, space features | Never copied | Never copied |
Branding, chat widget settings, attachment policy, automation limits | Copied | Copied |
The copy is a new space that you own. It counts against your plan like any other space. Review the switched-off automations before turning them on: they still carry the original's settings.
Modules
A module is a ready-made set of tables, forms, dashboards and automations for one part of a business, such as bookings or invoicing. Owners install them from Set up from modules, by business type or by module. Shared foundations are added automatically and reused if they exist. Import module… adds a package from a file; imported packages are marked Community and Unverified until trusted. Packages carry structure only, never rows, and never portal exposure: share things again explicitly after installing. Integrators build and ship packages; see business guide, Part B.
How to check it worked
Import: the progress screen ends with counts; open the table and spot-check rows. For a schedule, Scheduled imports shows Last run.
Export: open the file and compare the columns and row count.
Space export/import: the summary line lists documents, rows, assets, images and portal users imported.
Duplicate: Your copy is ready. Open it and check the switched-off automations.
Undo / what can go wrong
Updating a profile that automations use changes what they do on their next run.
A wrong Match by column with Update overwrites rows.
A failed duplicate is rolled back by deleting the new space.