What it does

Reports support two kinds of export: data downloads (CSV, Excel, PDF) capture what a report currently shows, for use outside the platform. Report packages export the report's definition as a portable file, so another Medtrics environment can import and recreate it — with no data carried along.

Who it's for

Program administrators, directors, coordinators, and institution administrators who need report output for meetings and records, or who standardize reports across environments — for example, moving a proven report from one deployment to another.

How it works

Downloading data. Open a report and use the download menu to export the current view as CSV, Excel, or PDF. CSV and Excel capture the tabular data. PDF captures the rendered report. Every download is recorded in the report's access log with the format used, so authors and auditors can see when data left the platform.

Exporting a report package. From a report card's menu on the Reports list, Export produces a .medtrics-report.json file containing the report's title, layout, tags, visibility setting, data-query definitions, and a list of the data models it needs. It deliberately contains no result data and no AI conversation history.

Importing. On the Reports list, Import Report accepts a package file. The platform validates it and warns if any required data models aren't available. It also checks whether the same report was imported before. If so, choose Update Existing Report or Import as New Copy. Imported reports arrive as drafts; publish them from the Reports list when ready.

Before you start

You need the program administration or institution portal, and view or create access to the Reports list in your target environment.
For an import, have the .medtrics-report.json package file ready. Downloading data only needs an open report — no file to prepare.

Do this

Open Reports (/analytics/reports), find the report you want to move, and open its ⋯ menu → you should see Export among the row actions.
Select Export → the platform downloads a .medtrics-report.json file containing the report's definition, not its data.
In the target environment, open Reports and select Import Report → the import dialog opens with a dropzone for the package file.
Drop or browse to the file → the dialog checks compatibility and lists any required data models that aren't available in this environment.
If the report was imported before, choose Update Existing Report or Import as New Copy; otherwise select Import as New Report → you should return to the Reports list with the imported report showing a Draft badge.
Open the imported report's ⋯ menu and select Publish when it's ready → the Draft badge clears and the report becomes visible to its audience.

You're done when

The imported report appears on Reports in the target environment.
Any missing data models are listed in the import dialog, so you know which sections won't show data yet.
The report is published (no Draft badge) once you've checked it and are ready for others to see it.

Boundaries and limits

Report packages carry the report definition only, never result rows, snapshots, or the AI conversation history that built the report. They're safe to move between environments without transferring records.
Data downloads (CSV, Excel, PDF) reflect only what you can currently see, and each one is written to the audit trail.
Import validation warns about missing data models but doesn't create them. Sections using models the target environment lacks won't return data until those models are available.
Duplicate detection is based on the package's origin. Re-importing the same source report is flagged, and you must choose update or new copy.
Imported reports always start as drafts, regardless of the visibility recorded in the package. They must be published before their audience sees them.
PDF export captures the report as currently rendered on screen. Content that fails to load isn't in the PDF.

Common questions

Q: What is in the .medtrics-report.json file? Is it safe to email? A: It contains the report's structure and query definitions, not data — no trainee records, results, or chat history. Treat it like a template file.

Q: Can I import a report from a completely different organization? A: Yes, if you have the package file. Import checks whether the needed data models exist in your environment and warns about any that are missing.

Q: We fixed the source report — how do we update the copies? A: Export a fresh package and import it in the target environment; import recognizes it as an update and offers to update in place instead of creating a duplicate.

Q: Are downloads tracked? A: Yes. Each CSV, Excel, and PDF download writes an entry to the report's access log, visible to the author and administrators in the access audit.

Exporting Report Data and Moving Reports Between Environments