Kaseya VSA data retention: version-specific logs and reports

At a glance

Plan VSA retention around the version you use and the records your team needs. Keep dated device, report and configuration exports independently, and confirm account-closure deadlines before ending access.

Separate legacy VSA log-history controls from VSA 10 retention and account-closure requirements.

Published Updated

On this page

Keep legacy settings in their version context

The official VSA 9.5 Policy Management guide describes Log History settings that control days of log entries and archival behavior. Use those settings for VSA 9.5; VSA 10 has its own account settings and terms.

Plan the history you need from VSA 10

List the device inventory, audit events, workflow executions and reports your MSP needs to keep. For each, record how far back you can view and export data, whether retention can be changed, and what remains after a device is removed. Ask Kaseya support for account-specific deadlines before offboarding.

Download the files you need before account access ends. Confirm when access stops and whether later export requests are available under your agreement.

Retain independent originals

Keep device CSVs, report results and native configuration files with source version and capture time. Decide how many historical copies your MSP needs before implementing cleanup. A downloaded report's continued availability in your archive does not establish that Kaseya can reconstruct the source record later.

Official source

Kaseya VSA 9.5 Policy Management guide