Export & Import Workspaces

Export a workspace as a single .zip file and import it again — into the same account, a different account, or a fresh InfoLobby install. Use this to back up a workspace, hand a template to a colleague, or duplicate a working setup as the starting point for a new project.

The archive is self-contained: tables, fields, records, attachments, views, reports, webforms, and flows are all bundled together.

What's included

  • Schema — every table you choose, with their fields, settings, and any tabs.
  • Records — optional. Toggle "Records (data)" off if you only want the structure.
  • Attachments — optional. File-field uploads and email attachments are bundled inside the zip.
  • Comments & emails — optional. Comments and email threads attached to records.
  • Flows — optional. Both visual (drag-and-drop) and code-mode (PHPScript) flows.
  • Views, Reports, and Webforms — always included with the tables they belong to.

What's NOT included

  • Integrations (SMTP servers, OAuth tokens, MySQL servers). These are account-specific and contain encrypted credentials. Flows reference integrations by name; on import you'll see which names need to exist on the target account before flows will run.
  • History / activity log entries from the source workspace.
  • Embedded webform links — webform IDs are regenerated on import, so any forms you've embedded on external websites need to be re-embedded.
  • External lookup fields — if a lookup points to a table that was not included in the archive, you can map it to an existing table in the same account/database. Unmapped fields are omitted and their record values are discarded.
  • Calc fields referencing tables outside the import — formulas that reference another table (e.g. @{tbl:item_count} or @{tbl:sum:field}) are rewritten to the new target IDs automatically when the referenced table is included or reused during import. If a referenced table isn't available, the calc field is dropped and a warning lists it by name.

Exporting

  1. Open the Workspaces page.
  2. Click the … menu on the workspace card and choose Export… (admin only).
  3. Pick which tables to include and toggle Records, Attachments, Comments, Flows.
  4. Click Export. A progress modal streams updates while the archive builds.
  5. The browser downloads <workspace-slug>.zip when finished.

Importing

  1. From the Workspaces page, click Import Workspace… in the org-level menu, or Import… in a specific workspace's … menu.
  2. Choose the .zip archive.
  3. The system reads the manifest and shows:
    • The size of the archive (tables, records, attachments)
    • Integration names referenced by the source flows that don't exist on the target account
    • Any code-mode flows that will be imported verbatim and need manual review
  4. Choose the destination:
    • New workspace — gives the import a fresh workspace name. If your account has external MySQL integrations, choose the database and storage to use; the form starts with your newest workspace's choices.
    • Merge into existing — adds (or replaces) tables in a workspace you already own.
    • If table names collide during a merge, choose rename, skip, or overwrite.
  5. Click Import. A progress modal streams updates while everything is recreated.
  6. When done, the page reloads on the new (or merged) workspace.

Cross-account portability

Archives are account-agnostic. The source account ID, user IDs, and API-key references are stripped during export. Anything created on import is attributed to you (the importing user). User mentions in old comments are preserved as plain text but no longer link to a profile.

Code-mode flows

Flows that use raw PHPScript can't be safely re-mapped automatically — the script may reference tables, integrations, or record IDs by hard-coded string. They're imported as-is. Open each one after import and verify any table or connection names referenced in the code.

Quotas

If the archive's record count or attachment size would push the target account over its plan limit, the import is blocked before any tables are created. Upgrade the plan or remove data first.