Skip to content

Migration guide · Customer Service

Zendesk to HubSpot Service Hub migration

ZendeskHubSpot Service Hub

Short answer

Migrating from Zendesk to HubSpot Service Hub moves tickets, conversations, users, organizations and help center articles into HubSpot tickets, contacts, companies and the knowledge base, so service teams work in the same CRM as sales and marketing.

Why firms make this move

Consolidating help desk and CRM removes integrations and gives service reps full relationship context. The main work is mapping ticket fields and statuses, migrating history and rebuilding macros, SLAs and routing.

What moves

  • Tickets with comments and attachments
  • Users and organizations as contacts and companies
  • Help center articles
  • Macros as snippets or templates
  • Ticket fields, statuses and tags

How the data maps

FromTo
TicketTicket
UserContact
OrganizationCompany
ArticleKnowledge base article
MacroSnippet / template
TriggerWorkflow

See the field-by-field map ↓

What to watch out for

  • Ticket comment history volume
  • Attachment storage
  • SLA and routing rules to rebuild
  • Customer-facing links to old help center

How Vantage Point runs the migration

  1. Inventory and design pipelines
  2. Map fields and statuses
  3. Migrate history and articles
  4. Rebuild routing, SLAs and automation
  5. Redirect help center URLs
  6. Go live and hypercare

Typical timeline

Typically 4 to 8 weeks.

Frequently asked questions

Does ticket history migrate?

Yes, including comments and, where needed, attachments.

What about our help center links?

We migrate articles and set up redirects so existing links keep working.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Zendesk to HubSpot Service Hub: field by field

13 mappings we start from on this migration, 9 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Ticketsubject / description Ticketsubject / content req direct
Ticketstatus Tickeths_pipeline_stage req picklist map new, open, pending, solved, closed → pipeline stages.
Ticketpriority Tickeths_ticket_priority picklist map
Ticketrequester TicketContact association req association
OrganizationOrganization Companyname / domain direct
Ticketassignee Tickethubspot_owner_id lookup
GroupGroup Team— lookup
Tickettags TicketMulti-checkbox property picklist map
TicketCustom ticket fields TicketCustom properties direct
Ticket commentPublic and private comments Note / email on ticket— manual review Keep comment order and authors. Private comments become notes.
MacroMacro text Snippet / template— rebuild
Help Center articleArticle Knowledge base article— direct
SLA policyTargets SLA settings— rebuild

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.