Migrate from Service Desk Panel to HubSpot Service Hub

Service Desk Panel tickets map directly to HubSpot Service Hub tickets with subject, description, status, priority, and owner preserved. Source ticket ID is stored in a custom property for audit traceability. HubSpot ticket pipelines (Professional and above) are configured during migration scoping if the source uses multiple ticket queues or categories. Closed-date and resolution timestamps migrate as custom properties when the destination ticket model does not natively preserve them.

Source customers (end users submitting tickets) map to HubSpot Contacts. We match by email address as the dedupe key. If a matching HubSpot Contact already exists, we link the ticket to the existing record; otherwise we create a new Contact. Name, email, phone, and any custom contact fields migrate directly. Customer-company association migrates as a HubSpot Company lookup when the source uses an organization field.

Source organizations attached to tickets map to HubSpot Companies. The company name becomes the Company name field; domain and description migrate where available. Company is created before any Contact import so that the Contact-Company association is satisfied at insert time.

Service Desk Panel agents map to HubSpot Users by email address. We extract the full agent roster from the source API and match against the destination HubSpot portal's User table. Any agent without a matching User record is held in a reconciliation queue for the customer to provision before record import. Inactive or deleted source agents can be reassigned to a designated fallback User during migration.

HubSpot Service Hub does not have a native Teams object equivalent to Service Desk Panel's group assignment. We map source team names to a custom single-select dropdown property (e.g., support_team__c) on the Ticket object. The customer creates the property with the relevant team values in HubSpot before migration, and we populate it during import. Alternatively, teams can be routed to HubSpot inbox assignments if the team count matches the inbox routing model.

Conversation messages on each source ticket migrate as HubSpot Ticket Comments in chronological order. Author attribution (agent vs. customer) is preserved using the contact or user email match. HTML formatting in message bodies is preserved as-is; HTML stripping occurs only if HubSpot rejects the format during test import. Public vs. private comment visibility is inferred from the source platform's visibility flags.

File attachments associated with source ticket conversations migrate as file attachments on the corresponding HubSpot Ticket Comment. We download from the source platform's attachment URL (if exposed via API) and re-upload to HubSpot. If the source platform only provides a filename reference without a direct download URL, we flag this for manual export during scoping and document the file list in the migration package.

Tags on source tickets migrate as HubSpot Ticket Tags. HubSpot natively supports tags on tickets; we import the tag array as-is. Tags are not deduplicated by default, so the customer reviews post-migration whether consolidation is needed. Tags used for categorization rather than ticket grouping migrate as a custom multi-select field if tags are preferred as a structured property over a free-form tag.

Custom ticket fields (dropdown, text, date, number, checkbox) are matched to HubSpot Ticket custom properties by field label and data type. The customer reviews and approves the mapping during a mapping review session before import begins. Dropdown fields on the source must have matching option values created in HubSpot before migration; we flag any values without a HubSpot match for the customer to add. Custom fields that have no HubSpot equivalent are flagged and carried as text properties for manual post-migration cleanup.

SLA policy configuration (first response time, resolution time, business hours, escalation rules) is not exportable in a portable format. Service Desk Panel SLA definitions are documented during discovery, and we deliver a written SLA rebuild guide specifying the HubSpot equivalent (using Service Hub automation with delays and ticket property conditions) for the customer's admin to implement before go-live.

Source KB articles migrate to HubSpot Knowledge Base articles. We extract title, body (preserving HTML), category, subcategory, tags, and URL slug. Nested JSON structures within article bodies (common in Service Desk Panel exports) require JSON escaping before HubSpot import; we handle escaping during the transform phase. Knowledge Base is a separate product tier in HubSpot and must be licensed separately; we confirm licensing status during scoping.

Automated rules, routing logic, trigger actions, and macro conditions are not exportable in a portable format. We document every active automation identified during discovery (trigger type, conditions, actions, affected ticket queues) and deliver a rebuild guide mapping each to HubSpot Service Hub automation with equivalent trigger-action steps. The customer plans time for rebuild before go-live; Service Hub automation is available from Professional tier.