Export & Import Reports

Move a report between PersivX instances as a single JSON file.

A report can be exported in full and recreated elsewhere. This is how you move work from a development instance to a production one, hand a template to another team, or keep a copy outside the platform.

Exporting

In the report builder, open the report configuration panel and choose Export entire report as JSON under Advanced.

The export captures the whole composition:

The report itself — name, layout, and the position of every tile
Report settings — IP allow-list, protection, installable-as-app, and drill-through configuration
Every visualization on it, with its attributes, query config, visual config, and any models used
Visuals nested inside sections and tabs, not just top-level tiles

Importing

On the destination instance, create a new report from the exported JSON. PersivX rebuilds the report and all of its visualizations from the file.

⚠️ Data Doesn't Travel With the Report An export describes a report, not the data underneath it. The destination instance needs its own datasource with the objects and attributes the report expects — otherwise visuals will fail to resolve their fields.

What to Check After an Import

Datasource — that the report is pointing at the right one on the new instance
Relationships — that the Relationship Manager has the joins the report's queries rely on
Custom attributes — that any custom attributes the visuals use exist on the destination datasource
Sharing — access is granted per instance and does not come across in the file
Subscriptions and alerts — these are configured per instance and need setting up again

💡 Moving Between Environments, Not Instances To promote a report from dev to production within one instance, don't export and re-import — use a release pipeline, which preserves version history and approvals.

Sections and Components

Sections and their child components can also be exported and imported on their own, which is useful for reusing a block of a report — a standard header, a common KPI row — across several reports rather than rebuilding it each time.