SuperOps data retention: ticket audit history and asset exports
SuperOps documents a rolling 30-day window for ticket audit history. That period applies to ticket audit entries, not every asset, report or backup. Device-history and account-closure retention need separate confirmation. RMMBackup provides read-only SuperOps snapshots, record history, and ZIP exports for supported collections.
Understand the documented 30-day SuperOps ticket-audit window without applying it to asset history, reports or account closure.
On this page
Understand the verified ticket-audit window
Open a ticket and inspect its Ticket Audit tab. SuperOps says entries older than 30 days are automatically removed from that rolling history. The Ticket Audit guide identifies this as the audit trail for ticket actions; it does not say the ticket itself is deleted after 30 days.
The guide does not document a user-adjustable extension of that window. Confirm any account-specific options with SuperOps before relying on a longer history.
Ask separate questions for assets and reports
| Data | What remains to confirm |
|---|---|
| Device inventory and asset activity | Retention while managed and after hard deletion |
| Script execution output | Lookback, export coverage and any adjustable limits |
| Generated report files | Download-link expiry and ability to regenerate |
| Closed account | Export-access deadline, disposal terms and possible assistance |
Do not transfer the ticket-audit limit to these datasets. The report and re-registration documentation does not establish a universal SuperOps retention period.
Give independent copies their own policy
Keep original CSV and JSON files with provider/account identity and capture time. Set an MSP retention period that matches the intended audit or handover use, and periodically verify older copies are readable. Deleting an active platform record does not itself edit a file or RMMBackup snapshot already captured, but either copy only preserves the data captured at that time.