Back up Kaseya VSA policies, profiles and automation

At a glance

VSA 10 documents native policy and profile exports plus workflow downloads. VSA 9 agent procedures use a separate XML export path. Preserve the native files and their source version; a conversion or import is not guaranteed to reproduce every behavior. RMMBackup does not currently back up Kaseya VSA directly.

Preserve VSA 10 policy, profile and workflow files, and distinguish them from VSA 9 agent-procedure XML exports.

Published Updated

On this page

Export policies and profiles in VSA 10

Under Administration > Configuration, inspect Profiles and Policies. Use the item's export icon to save profiles as .pcmpr and policies as .pcmpol. Kaseya describes these as proprietary files that should not be edited before import. See Policies overview.

Keep each original with its name and capture date. Record targeting, extensions and organizational assignments separately until you have verified what the file contains. A profile contains settings; the policy also determines where settings apply.

Preserve workflows and older agent procedures

In Automation > Automation Hub, open the appropriate folder's Workflows tab and use the workflow export action. The current workflow guide documents .wfl downloads.

For VSA 9, the same guide documents right-clicking an agent procedure or folder and choosing Export Procedure to save XML. VSA 10's translator evaluates compatibility; preserve the original XML before evaluating any conversion. Do not rename an XML procedure file to a workflow extension.

Record dependencies and custom fields

Our suggested manifest has columns for source version, native file, policy targets, script dependencies and required custom fields. Preserve source scripts and referenced files from your own maintained repository as well. Keep secret values out of the manifest.

For example, a workflow referring to a custom field needs both the field's intended meaning and the expected value on the target device. A policy export should not be assumed to back up all per-device values, attachments or execution history.

Verify scope before planning restoration

Check the official API reference if you need repeatable configuration capture; do not assume a device inventory response includes every policy definition. The verified methods here are native file exports. Importing or translating them is vendor-specific work requiring a controlled test of dependencies and targeting. RMMBackup does not currently back up VSA or perform automated restore.

Official source

VSA 10 policies overview