Data Import

Data Import loads a previously exported file—JSON, or ZIP if the workspace filesystem was included—into the current workspace. Create that file with Data Export.

Importable Elements

The following elements can be imported:

• Reports
• Subreports
• Templates
• Themes
• Global Parameters
• Report Types
• Languages
• Page Types
• Reusable Parameter Definitions
• Reusable Data Source Definitions
• Global Data Sources
• Dictionaries
• Parameter Groups
• Custom Components
• Default Reports
• File Management

You can also import filesystem content from the File Management page directly.

Handling Dependencies

Critical external dependencies (never in the export) must already exist in the target workspace if imported items reference them; otherwise the import fails:

• External Databases
• Google Cloud Service Accounts
• API Connections

They are used by Reusable Parameter Definitions and Reusable Data Source Definitions.

Missing references:

• If any element references another element by name (for example a template referencing a theme, a report referencing a template or subreport, a dictionary referencing a language, or a report type referencing page types) and that referenced element is not in the target workspace and is not included in the same import, the import fails.
• Missing file references (for example an image not present in the export) still allow the import to finish, but paths show up broken.

Not Included in the Import

Note

The following are not part of the import:

• Databases (connection strings)
• Emails (SMTP configuration)
• AI Integrations
• Workspace Users and Roles

The export and import cover only the workspace elements listed under Importable Elements above; any other workspace-level configuration is also excluded.

These must be configured manually in the target workspace.

Using Data Import

1. Go to Workspace Configuration → Import/Export → Data Import.
2. Click Import Data and choose the exported file.
3. Review the items and select or deselect what you want to import.
4. Click Import Selected.

When an imported element already exists in the target workspace, choose how to resolve the conflict: Stop aborts the import, Keep existing leaves the current workspace version, and Replace overwrites it with the imported version.

Note

Pay attention to dependencies when importing data. Make sure critical external resources (databases, service accounts, API connections) exist in the target workspace before importing.

Font Installation

The left sidebar includes a toggle to automatically install all fonts detected in the import archive. This is useful when the archive contains fonts needed for document conversion (such as PPTX).

Note

Fonts are installed globally and affect all workspaces. All font installation uses a keep existing approach—fonts already present on the system are not replaced.

Bootstrapping a Workspace at Startup

ImportFilePath accepts the JSON export file. FileSystemImportPath accepts the filesystem content (directory or files). If the export produced a ZIP, extract it first—point ImportFilePath at the JSON inside and FileSystemImportPath at the filesystem content. See Workspace Initialization for details.