Migrate your Vision Service Desk data

Core ticket object in Vision Service Desk. We extract all ticket fields including priority, type, status, requester, assignee, custom fields, timestamps, and threaded conversations. Full history and attachments are preserved. Cloud instances expose tickets via REST API; on-premises instances require CSV export or database read access.

End-user accounts that submit tickets via portal. We migrate client profiles including contact details, portal preferences, and associated ticket history. Client-side custom fields are mapped to the corresponding destination user property.

Internal support staff accounts with roles and permissions. We migrate staff records with their team assignments, access rights, and admin status. Staff hierarchy including Super-Admins and Team Managers is preserved during import.

Organization-level groupings for clients, enabling tree-structure ticket views with company counts. We preserve company-to-contact relationships and company-specific custom fields during migration.

Articles are organized by category and linked to topics. We migrate article content, category assignments, and article-to-topic associations. Custom article fields require value mapping to the destination knowledge base schema.

Hierarchical category structure organizing knowledge base articles. We preserve the category tree and re-map article associations to the destination category hierarchy.

Multiple SLA plan configurations with calendar-based response and resolution targets. We migrate SLA plan definitions but advise customers to reassign SLA tiers to destination plans since SLA engines vary between platforms.

Custom fields for ticket creation, client registration forms, and user data capture. We extract field definitions and values but require field-type mapping because drop-down, multi-select, and date field rendering differs across destination systems.

Ticket classification metadata used for filtering and automation. We migrate tag assignments per ticket and reconstruct label/flag taxonomies in the destination system.

Workflow rules covering ticket auto-assign (round robin), auto-close, and dispatch. We extract workflow definitions and attempt to map them to destination automation constructs, though complex conditional chains may require manual recreation.

Asset records linked to CI items tracked in the Configuration Management Database. We migrate asset records and CI relationships, noting that CMDB mapping depends heavily on the destination's asset schema structure.

Problem records linked to related incidents. We migrate problem records and their incident associations. Note that not all help desk platforms expose a separate Problem object.

Change request records with approval workflows and schedules. We extract change records and approval status history. Approval chain reconstruction in the destination depends on that platform's workflow engine.