Migrate from NV Desk to HubSpot Service Hub

NV Desk Cases map directly to HubSpot Service Hub Tickets. The Case status (Open, Pending, Resolved, Closed) maps to a HubSpot Ticket pipeline status value. We configure the destination pipeline before migration using the HubSpot Tickets API to set the correct pipeline name, status labels, and display order matching the NV Desk deployment. Priority and SLA deadline fields map to HubSpot Ticket Priority and the SLA object on Professional tier.

NV Desk Customer profiles (name, email, phone, company, address) map to HubSpot Contacts. The email address is the dedupe key. If the NV Desk Customer record includes a company name without a separate Company record, we create a HubSpot Company during migration and link the Contact. Company-to-Contact resolution happens before Contact insert so that the association is valid at insert time.

NV Desk deployments that use separate Company records map to HubSpot Companies. Domain names from NV Desk become the Company Website field and are used as the dedupe key. Companies are inserted before Contacts so that Contact-to-Company lookups resolve on insert.

NV Desk Agent records (name, email, team assignment, role) map to HubSpot Service Hub Users. We resolve agents by email match against the HubSpot destination account. Any NV Desk Agent without a matching HubSpot User goes to a reconciliation queue for your admin to provision before record import resumes. Inactive NV Desk agents are mapped to HubSpot Users with the inactive flag set.

NV Desk Teams map to HubSpot Teams (available from Professional tier). We preserve team structure and map team-based routing rules to HubSpot workflow-based routing. Teams are configured in HubSpot before Ticket migration so that assignment rules can reference the correct team names.

NV Desk custom fields on Cases are inventoried during scoping and mapped to HubSpot custom ticket properties. Field types (text, number, date, dropdown, checkbox) are mapped to equivalent HubSpot property types. Fields with no direct HubSpot equivalent are flagged for your admin to decide: create a new property, use an existing one, or drop the field. Custom ticket properties require Professional tier or above.

NV Desk multi-channel conversation threads attached to Cases migrate as Communication Log entries in HubSpot Tickets. Each thread entry includes the channel metadata (voice call note, email body, chat message, social post), timestamp, and the agent or customer who authored it. Channel type is preserved as a Communication Log metadata field. Thread ordering is preserved by timestamp.

File attachments on NV Desk Cases migrate as Files attached to the corresponding HubSpot Ticket. We use chunked transfer for large attachments exceeding HubSpot's file size limit. Inline images embedded in conversation threads are flagged separately (see Gotchas) because HubSpot cannot preserve inline images in Communication Logs during standard migration.

Tags applied to NV Desk Cases for categorization migrate as HubSpot Ticket Tags. Tag naming collisions are resolved during the mapping phase by prefixing with the source object name if needed.

NV Desk SLA configurations (response and resolution targets per team or Case type) map to HubSpot SLA Policies available on Professional tier. We document the SLA rules during scoping and map them to the destination SLA object. SLA thresholds become First Response Time and Next Job Time targets in HubSpot.

NV Desk KB articles and categories migrate where accessible via export. HTML content is preserved and reformatted to match HubSpot's knowledge base content schema. We recommend using HubSpot's pre-built Knowledge Base Importer (knowledge.hubspot.com) for bulk KB migration alongside our structured data migration. Attachments on KB articles do not migrate and are flagged for manual reattachment.

NV Desk's nine pre-built contact center integrations are configuration-level and tied to the NV Desk deployment. They do not migrate as data. We document which integrations are active in the NV Desk deployment during scoping so your team can plan the parallel reconfiguration with your contact center platform and HubSpot.