How to export SuperOps assets, reports and API data
Use SuperOps Data Reports when you need a targeted spreadsheet, or use RMMBackup to keep repeatable snapshots of supported clients, users, assets, inventory, alerts, scripts, activity, and documentation.
Export SuperOps reports or keep repeatable snapshots of supported assets, clients, inventory, alerts, scripts, activity, and documentation.
On this page
Export an asset list or another module report
The SuperOps tools comparison separates selected report CSVs from client/requester/site imports; neither establishes a complete device-history migration.
- Open Modules > Reports, select Custom, and create a Data Report.
- Choose the key module, such as assets, and select the columns you need.
- Configure filters and grouping, then check the report's scope.
- Select Export CSV and use the download link sent by email.
The Data Reports guide covers module-oriented reports. Create separate reports for the business records you need; an asset list alone does not preserve all client, ticket or activity details.
Choose the format you need
| Method | Output | What it contains |
|---|---|---|
| Custom Data Report | CSV | Selected report columns, filters and grouping |
| Official GraphQL queries | JSON response | Fields selected in a documented query |
| Open a CSV in Excel | Spreadsheet working copy | A working copy made from the original CSV |
SuperOps documents CSV output for the Data Report workflow. Keep the downloaded CSV unchanged and make any presentation or spreadsheet conversions from a copy.
Collect documented asset data through the API
The official SuperOps API reference documents getAssetList with assets and listInfo, as well as separate asset-detail queries such as getAssetSoftwareList and getAssetDiskDetails. A list query should not be assumed to include all of those details.
Choose fields from the documented schema, follow its list/pagination contract, and preserve native JSON responses. Check both request failures and GraphQL errors before marking a collection complete. Keep authentication secrets separate from response archives and logging. Do not interpret partial results as a complete inventory.
Can you export all SuperOps data?
Build a list of the modules, fields, attachments and history your team needs. Match each item to a report or API query, then check a sample of the output before offboarding.
For example, compare several exported assets' identifiers and client/site context with the console, then check whether required custom fields survived the report selection. Keep report filters, capture time, row counts and native originals together.
Plan the next step
For a move, review SuperOps import and deployment guide, then use the RMM migration checklist. Check the selected native tool before transforming files; an export is not automatically a destination import package. The migration use case explains how successfully captured records remain useful as a separate reference within your plan's accessible history.