SuperOps data retention: ticket audit history and asset exports

At a glance

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.

Published Updated

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.

Capture evidence before it becomes unavailable

Decide which audit evidence your MSP needs and ask SuperOps for a supported capture method before the viewing window expires. A ticket Data Report has its own selected fields; it should not be assumed to include every Ticket Audit entry. Similarly, a current asset report is not a historical sequence of all past asset states.

For account offboarding, download required exports while access remains available, confirm they open, and retain the vendor's written answers about remaining data. This guide makes no post-closure recovery promise.

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.

Official source

Ticket Audit in SuperOps

Related SuperOps integration

Review current SuperOps backup coverage and availability.