Move tickets, users, organizations and the full conversation history out of Zendesk into HubSpot
Zendesk models support around tickets, users and organizations. HubSpot models the same work as tickets tied to contacts and companies, sitting on the same records your sales team already uses. We map the two data models before we touch production, so nothing silently disappears on cutover weekend.
What actually moves
What we migrate from Zendesk, and how it lands in HubSpot
Records and history
Zendesk users become HubSpot contacts, organizations become companies, and tickets become HubSpot tickets tied to those records. Ticket conversations, internal notes and status-change dates move into the activity timeline, not just the current field values.
Structure and routing
Groups, custom ticket fields, tags and priority all need a target in HubSpot's data model. We map each one to a property, pipeline stage or ticket pipeline before import, so filtering and reporting still work on day one.
Automation, rebuilt not copied
Zendesk triggers, automations and macros do not import as-is. We rebuild the ones your team relies on as HubSpot workflows and snippets, and we quietly retire the rules nobody has touched in a year.
Data model differences
Where Zendesk and HubSpot disagree, and why it matters on cutover
Users and organizations vs contacts and companies
- - Zendesk centres on end users and organizations for support
- - HubSpot uses contacts and companies shared across sales, marketing and service
- - A user with three email addresses can split into duplicate contacts if not deduplicated first
- - We map identities and merge before import, not after
A Zendesk ticket is not a HubSpot ticket
- - Zendesk ticket status, type and priority live as native fields
- - HubSpot ticket state is driven by pipeline stages you define
- - Custom Zendesk fields need explicit target properties
- - We design the ticket pipeline first, then map statuses onto it
Comments and internal notes
- - Zendesk keeps public replies and private internal notes on the ticket
- - HubSpot stores these as timeline activities on the ticket and contact
- - Naive imports keep the current text but drop timestamps
- - We preserve who said what and when, so history stays auditable
Groups and triggers vs workflows
- - Zendesk routes with groups, triggers, automations and SLAs
- - HubSpot routes with ticket pipelines, workflows and SLA rules in Service Hub
- - There is no one-to-one import for this logic
- - It gets rebuilt to match how the team works now, not five years ago
Tags vs structured properties
- - Zendesk reporting leans heavily on free-text tags
- - Tag sprawl makes clean HubSpot reporting hard if imported raw
- - We convert the tags that carry meaning into structured properties
- - The rest are archived, not dragged into the new portal
How we keep the desk open during cutover
- - Full mapping and a sandbox dry-run before touching production
- - Migration windows scheduled off peak support hours
- - Delta import for tickets created during the cutover window
- - Agents keep answering while records move behind them
Straight answers
Migrating from Zendesk to HubSpot: common questions
Will we lose ticket history when we move off Zendesk?+
No, if the migration is designed around the data model rather than a raw export. We map Zendesk users, organizations and tickets to HubSpot contacts, companies and tickets, and we preserve conversation timestamps and status-change dates as timeline activities. A naive import keeps the current field values but drops the dates that let you report on resolution time and history.
Do Zendesk triggers, automations and macros transfer automatically?+
No. Zendesk routing logic does not import into HubSpot as-is. We rebuild the triggers and automations your team relies on as HubSpot workflows, and macros as snippets and canned responses. This is the moment to retire rules nobody uses, rather than copy old chaos into a new portal.
How do you keep support running during the migration?+
We map everything and run a sandbox dry-run before touching production, then schedule the cutover outside peak support hours. Tickets created during the migration window are captured in a delta import, so agents keep answering while records move behind them. HubSpot's own guidance is to migrate gradually in tested steps rather than in one risky pass, which is exactly how we run it. See HubSpot's data migration guidance.
What happens to our Zendesk tags?+
Tags that carry real meaning become structured HubSpot properties; the rest are archived. Zendesk reporting leans on free-text tags, and importing them raw creates tag sprawl that makes clean HubSpot reporting hard. We decide the target for each tag before import, not after.
Is a clean import enough to call the migration a success?+
No. A green import is the easy half. The migration only pays back when agents actually work in the new ticket pipeline and stop reaching for the old tool. We plan the ticket pipeline, workflows and agent training around how the team handles support today, because a desk that has lived in Zendesk for years will not switch on the strength of a clean data load alone.
Who should run a Zendesk to HubSpot migration?+
Someone who knows the HubSpot data model and API quirks, not just how to run a CSV export. HubSpot's own guidance recommends people with expertise designing and implementing HubSpot solutions for anything beyond the smallest standardized moves. For a support desk with real ticket history and routing logic, that difference shows up on cutover weekend. See HubSpot's guidance on migration skill sets.
When is staying on Zendesk the right call?+
Stay on Zendesk if support is your entire business, your team runs a high-volume, deeply Zendesk-specific setup, and sales and marketing live elsewhere with no plan to consolidate. HubSpot wins when you want tickets on the same records as your deals and marketing, so support, sales and marketing share one view of the customer. If that shared view is not a goal, a migration adds cost without a payoff.
After the cutover
Where this fits with the rest of your HubSpot build
Service Hub, set up properly
Once tickets land in HubSpot, they need pipelines, SLAs, routing and a help desk that works for agents. We build Service Hub around how your team handles support, not a generic template.
One clean source of truth
Support data is only useful when it sits on deduplicated contacts and companies shared across the business. We handle the data model, dedup and governance so tickets tie to the right records.
30 min, honest read
Thinking about moving your support desk off Zendesk?
Tell us your Zendesk setup and ticket volume. We come back with a mapping plan, a downtime estimate, and a straight answer on whether the move is worth it.