Migrate from Kaseya VSA to HubSpot Service Hub

Kaseya VSA Organizations (top-level tenant containers, especially relevant for MSPs with multiple customer accounts) map directly to HubSpot Companies. We use the Organization name as the Company name and preserve the organization's address, custom fields, and billing contact as Company properties. If the customer uses Organizations to represent internal cost centers rather than end customers, we recommend mapping those to HubSpot Teams or a custom object during scoping.

VSA Sites (sub-containers within Organizations representing physical locations or client subdivisions) do not have a direct HubSpot equivalent. We map Site assignments to a custom multi-select picklist on the HubSpot Company, or to HubSpot Teams if the customer uses Sites to segment internal technician groups. The customer chooses the strategy during scoping based on whether Sites represent customer locations or internal groupings.

VSA Service Desk Tickets migrate to HubSpot Tickets. We map VSA ticket status, priority, category, and custom fields to HubSpot Ticket properties. Ticket conversations and internal notes migrate as HubSpot Ticket engagement records (email replies stored as internal notes, external replies stored as ticket replies). The VSA ticket creator becomes the HubSpot Ticket requester; if the requester email does not match an existing HubSpot Contact, we create a Contact record during migration.

VSA ticket requesters map to HubSpot Contacts. We use the requester's email address as the dedupe key and create Contact records for any requester not already in the destination HubSpot portal. First name, last name, email, and phone migrate directly; custom field values on the requester record migrate to HubSpot Contact properties.

VSA Organization-level custom fields (assigned at the Global, Organization, or Site context) migrate to HubSpot Company custom properties. We pre-create the custom properties in HubSpot during schema preparation with appropriate field types (text, number, date, dropdown). If the VSA custom field count exceeds HubSpot's property limits for the selected tier, we prioritize fields used in ticket filtering and reporting and archive the remainder as a documented reference list.

VSA Service Desk Ticket custom fields migrate to HubSpot Ticket custom properties. Note from pair-specific evidence that HubSpot forms cannot populate custom Ticket properties, which limits the use case for ticket-level custom fields in new workflows; we flag this constraint during scoping so the customer can evaluate whether the migrated field is used in automations that require form population.

Kaseya VSA Agents (managed endpoints) do not have a direct HubSpot Service Hub equivalent because Service Hub is not an RMM platform. If the customer's VSA tickets reference specific endpoints as the subject of the ticket (e.g., server outages, device failures), we create a custom object or a Ticket tagged with a custom property carrying the endpoint hostname. The technician assigned in VSA maps to a HubSpot Contact flagged as an internal user for ticket assignment purposes.

VSA Agent Procedures (CMD, PowerShell, and VSA-native scripting) cannot migrate to HubSpot Service Hub because Service Hub has no equivalent automation execution engine for endpoint management tasks. We deliver a written inventory of all Agent Procedures organized by folder, with trigger conditions, script content summary, and recommended HubSpot Workflow or external automation tool (Power Automate, Make) equivalent for the customer's IT team to rebuild post-migration.

VSA Monitor Sets (alerting and threshold configurations assigned to Agents) have no HubSpot Service Hub equivalent. We deliver a written inventory of all Monitor Sets with their assigned Agents, threshold values, and alert recipients so the customer's IT team can design equivalent alerting using HubSpot Workflows (for ticket creation on CRM events) or external monitoring tools integrated via HubSpot's API.

VSA Patch Policies (scheduled patching, approval rules, and reboot handling) are RMM-native configurations with no HubSpot Service Hub equivalent. We deliver a written inventory of all Patch Policies with their schedules, approved patch lists, and reboot settings for the customer to evaluate in the context of their chosen RMM replacement or supplemental tooling.

VSA Event Sets (system event-to-procedure trigger mappings) are automation logic specific to the VSA execution environment. HubSpot Service Hub cannot execute endpoint event handlers. We deliver a written inventory of Event Sets with their event triggers, associated procedures, and assigned Agents so the customer can design equivalent automation flows in their chosen replacement tooling.

VSA Agent Groups (dynamic or static collections of Agents used for targeted procedure deployment) do not map directly to HubSpot objects. If Agent Groups represent customer segments, we recommend mapping them to HubSpot static lists or a custom contact property. If they represent internal technician groupings, HubSpot Teams is the appropriate equivalent. We confirm the mapping strategy during scoping.