Migrate from Vision Satellite Help Desk to HubSpot Service Hub

Vision Tickets map directly to HubSpot Tickets. Each ticket's ID, subject, description, status, priority, source, and pipeline stage migrate as typed HubSpot properties. Threaded comments are split: private staff notes route to HubSpot's internal conversation history and client-visible replies route to the public ticket conversation thread. Multi-agent assignments stored as comma-separated values are split and the primary assignee maps to the HubSpot Ticket owner field; secondary assignees are written to a custom multi-select property for visibility.

Vision Clients export with name, email, phone, and organization linkage. We map them to HubSpot Contacts preserving email as the dedupe key. Vision's client-to-organization linkage becomes the HubSpot Contact's associated Company relationship resolved via the Organization-to-Company mapping. Client custom fields map to HubSpot Contact custom properties with type matching (string, boolean, date, number, select, multi-select).

Vision Organization records (org name, domain, custom fields) map to HubSpot Companies. The Vision org domain becomes the HubSpot Company website field and serves as the dedupe key during import. Client-to-Organization foreign key linkage is preserved as the Contact-to-Company association in HubSpot. Organization custom fields map to HubSpot Company custom properties.

Vision Staff Agent records include name, email, role, and department. Role names vary across Vision tiers (Agent, Supervisor, Admin) and are normalized to a standard set during transformation. We match Staff Agents to HubSpot Users by email for the owner assignment on Tickets, Contacts, and Companies. Staff without a matching HubSpot User enter a reconciliation queue for the customer's admin to provision before record import resumes.

Vision custom fields on tickets, clients, and organizations export as additional columns in CSV. We flag each custom field during scoping, determine type compatibility with HubSpot property types, pre-create the equivalent HubSpot custom properties before migration, and map source values directly. Custom field order and grouping in Vision forms are not preserved in HubSpot; we document the original layout for the admin to recreate in HubSpot's property settings.

Vision Tickets carry separate Labels, Tags, and Flags as multi-select columns. Each is split into individual values and mapped to HubSpot Tags on the Ticket object. Flags are Vision-specific with no HubSpot equivalent; we map them to a custom multi-select property flag__c to preserve the taxonomy. If the customer used Tags for content classification rather than ticket categorization, we offer Topic mapping as an alternative during scoping.

Vision KB articles and folder structure export via the reporting module with HTML formatting intact. We strip or preserve HTML depending on whether the destination article editor supports rich text, remap category folders to HubSpot knowledge base sections, and create articles with the original author and timestamps. Article attachments migrate as linked file references. HubSpot knowledge base must be enabled in the destination portal before migration.

File attachments on Vision tickets export as file references. We extract the files, validate them against HubSpot's attachment size limits (20 MB per file), re-upload to the HubSpot file storage, and relink to the corresponding ticket record. Inline images embedded in ticket descriptions and comments are handled as separate file uploads with references updated in the migrated text.

Vision approval workflow records (Pro tier and above) export with requester, approver, status, and timestamps. HubSpot Service Hub does not have a native approval object; approvals are handled through automation rules or recreated as a custom approval object with custom fields for approver, status, and timestamps. We map the approval chain as a sequence of records and document the original workflow logic for the admin to rebuild as HubSpot workflows.

Vision Satellite Help Desk's multi-location model uses shared ticket pools across satellite locations. We map each Vision satellite location to a HubSpot Team, preserving the location name and routing the satellite's ticket pool to the corresponding team's inbox. This requires HubSpot Service Hub Professional or above for multi-team routing. If the customer used the shared pool model, tickets are distributed to the team mapped to the satellite where the ticket originated.

Vision ticket conversations split into private staff notes and client-visible replies. We preserve this distinction in HubSpot by routing private notes to the ticket's internal activity log and client replies to the public conversation thread. Comment author, timestamp, and attachments migrate with each entry. Comment privacy (private vs. public) is a Vision-specific attribute with no direct HubSpot equivalent, so we use the internal activity vs. conversation thread routing to preserve the intent.

Vision Reports are configuration objects (charts, grids, dashboards) rather than data records. These cannot be migrated programmatically. We deliver a written inventory of every Vision report with its data source objects, filters, and visualizations, and the customer's admin recreates them in HubSpot's reporting module post-migration. The inventory includes report names, column definitions, and filter logic captured during scoping.