How to back up SuperOps data
RMMBackup keeps a separate, read-only history of supported SuperOps clients, users, assets, inventory, alerts, scripts, custom fields, activity, and documentation. Use the guide below to connect SuperOps and verify your first snapshot.
Back up supported SuperOps assets, clients, inventory, alerts, scripts, custom fields, activity, and documentation.
On this page
Choose a SuperOps backup method
| Method | Useful for | Important limitation |
|---|---|---|
| Native Data Report | Export selected module columns, filters, grouping, client scope, and dates to CSV through an emailed link | Each report covers its chosen module and related fields; it is not a complete account archive |
| GraphQL script | Query selected documented MSP API fields as JSON | Your code must handle token and tenant scope, regional endpoint, pagination, GraphQL errors, storage, and completeness |
| RMMBackup | Take repeatable snapshots of supported SuperOps data, browse versions, and download snapshot ZIPs | Coverage is limited to the supported data below |
The SuperOps Data Reports guide documents CSV output for asset, alert, client, requester, and other module reports. Use native reports to verify key inventories even when recurring API snapshots are configured.
See the SuperOps integration for the SuperOps data RMMBackup can back up.
What RMMBackup backs up from SuperOps
| Collection group | Captured data | Boundary |
|---|---|---|
| Clients and people | Clients, sites, requesters, associations, stages, technicians, groups, roles, teams, business functions, designations, holidays | Visibility follows the API token's user permissions and tenant scope |
| Assets and inventory | Monitored and unmonitored assets, hardware summaries, disks, installed software, patches | Detail collections depend on successfully captured parent assets |
| Operations | Alerts, scripts, asset activity, asset user-login history | Source query availability and permissions apply |
| Fields and classes | Client, contact, asset, and asset-class custom-field definitions; device categories | Definitions are preserved separately from every value relationship the source may expose |
| Documentation | IT documentation categories and records, knowledge-base collections and articles | Limited to documented MSP GraphQL queries |
RMMBackup does not capture SuperOps service desk or financial modules. It stores the selected fields and original GraphQL responses, checks both transport and GraphQL errors, and marks an unavailable selected collection as failed rather than empty.
Set up recurring SuperOps backups
- Create and verify a RMMBackup account.
- Follow the SuperOps API token guide to collect the token, customer subdomain, and US or EU tenant region.
- In Settings > Integrations, choose SuperOps, enter those values, and select collections the token can read.
- Save and validate. Confirm client and asset scope instead of assuming an empty list means invalid credentials.
- Run a manual backup and inspect every collection result and representative record.
- Export a native asset Data Report for comparison, then inspect the RMMBackup snapshot ZIP.
Free allows one accepted manual backup attempt per rolling 24 hours across the MSP account, keeps the latest fully successful snapshot accessible, and does not schedule automatic backups. Full Access allows two accepted manual attempts per rolling 24 hours for this vendor, keeps ongoing accessible history, and adds a daily automatic schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it. See pricing.
Browse history and export captured data
Accessible SuperOps records can be browsed and compared across backups. A backup ZIP contains the original saved records, a contents summary, and source responses. Follow the SuperOps export guide to compare this history with SuperOps Data Reports.
RMMBackup preserves stable record identities and original source responses while tracking the result of each selected data type.
Preserve SuperOps data before switching providers
Create native Data Reports for critical modules and capture a complete RMMBackup snapshot before revoking the token. Verify asset IDs, client/site relationships, custom fields, and required documentation in both paths. Use the migration checklist and SuperOps configuration guide; neither output automatically imports into another platform.
Review records from deleted devices
If a SuperOps asset was captured before removal, an earlier accessible snapshot can retain the returned details. A later complete collection can establish an absence only where that collection supports deletion detection; hardware summaries explicitly do not. RMMBackup cannot recover pre-backup records or re-enroll an asset. See SuperOps deleted-device guidance and SuperOps retention notes.
Frequently asked questions
Can I export SuperOps data to CSV?
Yes. SuperOps documents CSV export for Data Reports, with columns, filters, grouping, client scope, and dates chosen for that report.
Does RMMBackup back up SuperOps tickets and invoices?
No. The current collector intentionally excludes ticketing, contracts, billing, invoices, payments, and other financial data.