Zendesk to HubSpot migration.
Tickets and pipeline on the same record. The reason to move support into HubSpot is not the ticketing. It is that the account manager can finally see that the customer raised four tickets before the renewal conversation. The migration is mostly rebuilding the automation Zendesk was running.
Support knows. Sales finds out at renewal.
Two systems, two contact databases, and a customer whose frustration is entirely invisible on the deal record. Every business with a separate help desk has this problem and most of them manage it with a weekly export. It does not survive contact with a churn conversation.
Four tickets. Nobody told the renewal.
Zendesk — the split viewWhat does not come across in an export.
Macros and triggers rebuild
Zendesk triggers, automations and macros are the accumulated operating procedure of the support team. They rebuild as HubSpot workflows and snippets, and the rebuild is a chance to delete the two thirds nobody fires any more.
SLA policies work differently
Zendesk SLA policies with business hours and multiple targets map onto HubSpot SLAs with less granularity. Teams with contractual SLAs need this checked against the contract, not against the tool.
The help centre is a website
Guide articles, categories, sections and their URLs are indexed and linked. Moving them into the HubSpot knowledge base is a content migration with its own redirect map, exactly like a CMS move.
Side conversations and internal notes
Side conversations have no clean equivalent. Internal notes carry. Anything that lived in a side conversation with a supplier needs a decision about whether it is history worth keeping.
CSAT history
Satisfaction ratings and their comments are the only longitudinal measure of support quality most teams have. They migrate as custom properties or feedback submissions rather than disappearing with the tool.
Custom ticket fields and forms
Multiple ticket forms with conditional fields become HubSpot pipelines and conditional properties. The mapping is usually where teams discover they have four forms doing one job.
The sequence, start to cutover.
Discovery
Object counts, custom fields, automation and the integrations that will break on the way out, read from the source system rather than from a questionnaire.
Mapping
Field by field, including what will not carry across, agreed and signed before anyone exports anything.
Dry run
A complete rehearsal into a sandbox portal, reconciled against source counts so the gaps surface a month early rather than on cutover night.
Automation rebuild
Workflows, sequences and routing rebuilt to the new model rather than transliterated from the old one, which is how a migration inherits a decade of workarounds nobody remembers writing.
Cutover
A dated switch with the legacy system read-only for a defined window, and a rollback that was tested rather than assumed.
Post-migration support
A named engineer through the first full reporting cycle, which is when the questions actually arrive.
The agents were not asked.
Support migrations get decided by revenue leadership and lived by agents who handle sixty conversations a day. If the new queue takes three more clicks per ticket, the migration failed regardless of what the integration does. We build the agent view first and test it with the people who will sit in it.
What people ask before they commit.
Can we keep our ticket history?
Yes. Tickets, their conversation threads, attachments and internal notes migrate and attach to the matching contact and company, which is the whole point of the move.
What about our help centre URLs?
They get a redirect map, the same as a website migration. Support articles often carry meaningful organic traffic, and losing it is an avoidable own goal.
Is HubSpot Service Hub as capable as Zendesk?
For most mid-market support teams, yes, and the shared record is worth more than the features you lose. For high-volume support operations with complex routing and contractual SLAs, we will tell you honestly if the answer is no.
How long does it take?
Four to eight weeks. The variables are ticket volume, help centre size and how much of the Zendesk automation turns out to still be in use.
Can we run both during transition?
For a short overlap, with new tickets going to HubSpot and old ones closing out in Zendesk. Splitting live conversations across two systems is worse than either option.
Where people go from here.
Support and revenue on one record.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.