Migrate your Kaseya VSA data

Agents are the primary managed-device object in VSA. Standard fields include hostname, OS, last check-in, and status. We preserve Agent records in full during XML export and re-establish the endpoint identity at the destination, flagging any Machine ID reassignment that may occur during the transfer.

Organizations are the top-level tenant container, especially relevant for MSPs with multiple customer accounts. We export and import Organization structures and their associated settings as part of the automation solution migration via Import Center.

Sites are sub-containers within an Organization, typically representing physical locations or client sub-divisions. Site assignments on Agents are preserved during migration and must be re-mapped if the destination VSA uses a different organizational hierarchy.

Agent Groups are dynamic or static collections of Agents used for targeted procedure deployment and monitoring. Group memberships are exported as part of the agent configuration. We verify group names and membership rules on the destination to ensure dynamic groups evaluate correctly post-migration.

Agent Procedures are the core automation unit in VSA, supporting CMD, PowerShell, and VSA-specific scripting. Folders of procedures can be exported as a single XML via Import Center. We sequence folder dependencies and validate script references during import to handle any cross-procedure calls.

Service Desk Tickets and their Definitions are migratable via Import Center XML export. Ticket history, conversations, and custom fields may require field-level mapping to the destination helpdesk schema. We flag which ticket associations and attachments are preserved versus flattened during the export.

Monitor Sets define the alerting and threshold configuration for Agents. They are among the explicitly listed migration types in Import Center. We export Monitor Sets alongside Agent configurations and verify that monitoring policies re-apply correctly to the destination's agent population.

Patch Policies control automated patching schedules, approval rules, and reboot handling. Kaseya's documentation explicitly names Patch Policies as a migratable object via Import Center. We export the policy definitions and apply them to matching agent groups on the destination VSA.

Custom Fields can be assigned at Global, Organization, Site, Agent Group, or System context levels. Custom reports have a 40-field limit. We export custom field definitions alongside agent data and remap field contexts to the equivalent structure on the destination, flagging any fields exceeding the destination's limits.

Packages define distributable software bundles and are listed as a migration type in Import Center. Package dependencies and distribution schedules are preserved. We flag any packages referencing third-party repositories or credentials that may not exist on the destination environment.

Machine ID templates encode standardized endpoint configurations and are explicitly named in Kaseya's migration documentation. They can be exported alongside machine ID settings. We map template assignments to destination agents to maintain consistent baseline configurations post-migration.

Event Sets define which system events trigger alerts or procedures and are listed as a migratable automation solution in Import Center. We export Event Set configurations and validate that equivalent event sources are available in the destination environment.