Export Kaseya VSA data: VSA 10 device CSVs, reports and API

At a glance

VSA 10 exports Device Management search results to CSV. Advanced Reporting also offers Excel, PDF, JSON and other output formats, and an official API supports programmatic collection. These instructions are for VSA 10; do not apply them unchanged to VSA 9. RMMBackup does not currently back up Kaseya VSA directly.

Export filtered VSA 10 device lists to CSV and Advanced Reporting results to Excel, PDF or JSON; keep VSA 9 procedures separate.

Published Updated

On this page

Export the VSA 10 device list

  1. Open Modules > Devices > Device Management.
  2. Set the organization, scope and device filters required for your export.
  3. Choose the columns in View Options and review the results.
  4. Use the additional actions menu to export the current results to CSV.

The Device Management reference documents this export. Keep the selected filters with the file. A filtered result is not necessarily every device in the account.

Export report results

Open Modules > Advanced Reporting with View Reporting and run reports permission. Select a report, review its parameters and preview, then use the viewer's export function. Available formats include PDF, Excel, Word, CSV, HTML, image and JSON. See Advanced Reporting.

A JSON report export is still the report's selected data. It is not automatically the raw device API response or a complete collection of audit records.

Use the official VSA 10 API

The API guide links to the public reference and your instance's /api documentation. It describes REST/OData lists with paging, filtering and sorting, plus third-party tokens restricted by organization and endpoint permissions.

Create a read-only collection plan from that reference: record each endpoint, required fields and pagination rules, then preserve original responses and completion status. Keep token secrets separate from capture files and logs. This guide does not claim that every VSA configuration or historical resource has a supported read endpoint.

Keep VSA 9 and VSA 10 capture plans separate

Kaseya documents an explicit translation path from VSA 9 agent-procedure XML to VSA 10 workflows. That version boundary is a reason to record the source product and version with every export; it is not evidence that the two device models or APIs are interchangeable. See the workflow conversion reference.

For a handover, compare CSV row counts with the filtered device view, check organization/site identity on a sample, and preserve report parameters. Capture policies and automation separately. Keep inventory, configuration files and reports together to cover the different details your team needs.

Official source

Finding and managing devices