Migrate from Kaseya VSA to Zoho Desk

Kaseya VSA Organizations are the top-level tenant containers, especially relevant for MSPs with multiple customer environments. Zoho Desk uses Departments as the primary organizational unit, with Teams nested within Departments. We map each Kaseya Organization to a Zoho Desk Department, and create Teams within each Department representing the Kaseya Sites under that Organization. Multi-tenant MSP structures with separate Organizations for each client map cleanly to separate Zoho Desk Departments, preserving billing and reporting separation.

Kaseya Sites are sub-containers within an Organization representing physical locations or client sub-divisions. Site assignments on Agents are preserved as Team assignments in Zoho Desk. Each Kaseya Site becomes a Zoho Team under the corresponding Department. Agents linked to a Site map to the corresponding Team, and ticket assignment rules can be configured to route by Team.

Kaseya VSA Service Desk Tickets export via Import Center XML and include TicketId, TicketNumber, Summary, CustomFieldOrder, CustomFieldCaption, CustomFieldName, CustomFieldValue, and CustomFieldType from the Data Warehouse API. We map Ticket.Status to Zoho Desk Ticket Status, Ticket.Priority to Priority, Ticket.AssignedTo to the agent's email-matched Zoho Agent record, and ticket history conversations to Zoho Desk Thread records with author attribution. The Data Warehouse API CustomFieldDetails endpoint returns custom field values per ticket; we flatten the context-level field hierarchy (Global, Org, Site, Agent Group, System) into Zoho's module-level custom fields.

Kaseya VSA Service Desk Ticket Definitions define the form structure, field types, and required fields for tickets. Zoho Desk uses Layouts and Fields per Department to control which fields appear on tickets and their required status. We map Kaseya's Ticket Definition field types (text, dropdown, date, numeric, checkbox) to Zoho field types (single-line, multi-line, picklist, date, number, checkbox). Custom fields defined at the Ticket Definition level become Zoho Desk custom fields added to the relevant Department layout before migration.

Kaseya VSA Service Desk Message Templates are canned response templates used in ticket replies. These map to Zoho Desk Email Templates (Setup > Templates > Email Templates) which can be associated with departments and used in automated responses or manual macros. We extract template body content and variable placeholders from the Import Center XML and create equivalent Zoho Desk templates with Zoho's {ticket.ticket_number}, {contact.name}, and {ticket.status} variable syntax.

Kaseya VSA Service Desk Holiday definitions control SLA calculation during business hours exclusions. These map to Zoho Desk Holidays (Setup > Office Hours and Holidays) per Department. We extract holiday dates and descriptions from the Import Center XML and configure them in Zoho Desk, noting that Zoho's SLA timer pauses during Holiday periods as configured.

Kaseya VSA Agents are managed endpoints with hostname, OS, last check-in, and status. Zoho Desk does not have a native RMM agent model. If the migration scope includes Kaseya Service Desk tickets that reference Agents as the affected device, we create Zoho Desk Contacts representing those devices and store the original Machine ID and Agent ID in custom fields (vsa_machine_id__c and vsa_agent_id__c) for reference. This is a reference mapping, not a full endpoint migration.

Kaseya VSA Service Desk Tickets have a requester (Contact) associated with each ticket. These contacts export from the Data Warehouse API with name, email, phone, and Organization association. We map Kaseya requester contacts to Zoho Desk Contacts, using email as the dedupe key. Organization-level contacts map to Zoho Accounts for companies, with individual requesters linked to the Account.

Kaseya VSA Organizations that represent companies (not MSP client containers) map to Zoho Desk Accounts. We use the Organization name as Account Name, the Organization's primary contact email as the Account email, and store the original Organization ID in a custom field (vsa_org_id__c). If the Organization is an MSP tenant container rather than a customer company, it maps to a Zoho Desk Department instead, and we create separate Accounts for any customer organizations nested within.

Kaseya VSA Views define saved ticket list configurations with filters and column selections. Zoho Desk Custom Views serve the same purpose: saved filter combinations scoped to a Department. We map Kaseya View filter criteria (status equals, priority equals, assigned agent equals, date range) to Zoho Desk's saved view filter syntax. Column selections map to the Zoho view column picker.

Kaseya VSA Agent Procedures (CMD/PowerShell scripts), Monitor Sets (alerting thresholds), Patch Policies (automated patching schedules), and Event Sets (trigger-action rules) have no Zoho Desk equivalent because Zoho Desk is a pure helpdesk without RMM capabilities. We do not migrate these as data. We deliver a written inventory of each object with its configuration details (procedure script content, monitor threshold values, patch approval rules, event trigger conditions) so the customer's admin can evaluate alternatives: native Zoho Desk Blueprint automation for ticket routing, Zoho Flow for cross-app automation, or a dedicated RMM tool for endpoint management post-migration.

Kaseya VSA Machine ID Templates encode standardized endpoint configurations and are explicitly listed in Kaseya's migration documentation as an Import/Export type. Zoho Desk has no endpoint management or Machine ID concept. We document the Machine ID Template configurations (template name, assigned machines, configuration parameters) in the migration inventory and flag that endpoint standardization requires a dedicated RMM tool post-migration if the customer no longer uses Kaseya VSA for endpoint management.