Migrate your HubSpot Service Hub data

Tickets are HubSpot's primary support object. We map them 1:1 with standard fields (subject, status, priority, source) and preserve all custom ticket properties. For Zendesk migrations, we reconstruct the ticket structure but acknowledge that side conversations require manual re-creation or a custom workaround in HubSpot.

Contacts map directly across platforms. Standard properties (name, email, phone, lifecycle stage) migrate cleanly. We flag any custom contact properties that need mapping to destination field names and warn if the destination uses a different lifecycle stage taxonomy.

Companies are a standard HubSpot CRM object shared across all hubs. We map company properties and associations to contacts. If the destination CRM uses a different account hierarchy model, we flatten or restructure accordingly during migration.

HubSpot stores individual email, chat, and call events as separate engagement objects linked to tickets. We reconstruct these into threaded conversations for most destinations, but the association metadata may not survive the translation intact. We flag this during scoping so customers can decide whether to include partial history.

Articles can be exported via API and migrated to alternatives like Zendesk Guide or Intercom Articles. We handle the article body, category structure, and publish status. HubSpot-specific features like article performance analytics do not have equivalents in most destination platforms.

HubSpot CS Hub provides health score calculations based on engagement data. We migrate the raw engagement data but cannot guarantee that health score algorithms will produce identical results in the destination system. We recommend re-running health score calculations post-migration.

Custom Objects are only available on Enterprise tier. If you are migrating from a lower HubSpot tier that did not use Custom Objects, this is not a concern. For Enterprise-to-Enterprise migrations, we map custom object records and their associations, though schema differences must be resolved during field mapping.

Ticket pipelines and their stages migrate as a configuration artifact. We extract the pipeline name, stage names, display order, and probability percentages. If the destination has fewer stage slots, we consolidate and warn which stages were merged.

HubSpot users and owners map directly. We migrate user records including name, email, role, and team assignments. Active versus inactive status is preserved. If two-factor auth is required by the destination, we flag this as a pre-migration step for the customer.

Tags on tickets and contacts migrate as string values. HubSpot does not enforce a global tag taxonomy, so tags from multiple sources may have naming collisions. We deduplicate and prefix where necessary to avoid silent data loss.

File attachments on tickets and emails can be exported via HubSpot's API. We migrate them to the destination as file references or attachments. Large attachment volumes affect migration speed and may require chunked processing to stay within rate limits.

Post-conversation survey responses are stored as a HubSpot object linked to tickets. We map response scores and free-text answers. The destination platform must support CSAT data to preserve this, otherwise we export it as a report CSV.