Zendesk to HubSpot migration, nothing lost.

I move support teams from Zendesk to HubSpot Service Hub with their ticket history intact, while the team keeps working. Support ends up on the same records as sales, so everyone sees the whole customer.

A Zendesk to HubSpot migration moves your tickets, their history, your customers and your support team into HubSpot Service Hub, then rebuilds the automation and reporting the HubSpot way. Done well, the team switches from one system to the other with little or no downtime. Plan on about a month of project time.

How it works, in detail

What a Zendesk move with me covers

This is the work from my most recent one: an international B2B technology firm, with support teams across three continents, moving from Zendesk to HubSpot Service Hub.

  • Counting everything first. A full extract of both systems, record by record, so every estimate came from real numbers. Over half the tickets turned out to be automated alerts, so we agreed to archive those rather than move them.
  • Cleaning the data across both systems. Companies, customers and sites had been mixed together in Zendesk and HubSpot. The team reviewed every account in a workbook, duplicates were merged by people rather than guesswork, and sites got their own records, linked back to the right company and contacts.
  • A config review, line by line. Every field, form, group, SLA, macro, trigger, automation, view, tag and connected app went into one workbook, then a decision call. The rule: if nobody uses it, it doesn't get rebuilt.
  • Rebuilding how support works, with each regional team. SLAs by priority, automations for when a ticket arrives and when it closes, escalation routes, Slack notifications, Jira for engineering, satisfaction surveys on close, and AI categorisation of tickets.
  • Checking every app and integration. What each one did, and whether to rebuild, replace or drop it, including monitoring alerts that now run in their own pipeline.
  • Tested transfers. Dry runs and small test batches before the real move, then every record read back and checked, and every open ticket matched to its owner.
  • Teams, views and the knowledge base. Teams, permissions and views set up by region, and the help articles moved and published with their links fixed.
  • Training for every team. Live sessions for each regional team and for product and engineering, each with its own clear, screenshot-led pack and a recording to keep.
  • Switch-over and hypercare. An agreed switch-over time, with Zendesk kept as a fallback, then focused, quick support through the first week, with every issue tracked until it's closed.

How the move works

  1. Look at what you have. What's in Zendesk, what's actually used, and what's worth bringing.
  2. Agree where it goes. How your customers, tickets and teams should be set up in HubSpot, signed off before anything moves.
  3. Move and test. The history goes across while your team keeps working in Zendesk, and the routing, automation and reporting are rebuilt the HubSpot way.
  4. Switch over. At an agreed time, with a written plan, so the team finishes in one system and starts in the other.
  5. Train and support. Training and a recorded session for each team, a week of hypercare after go-live, then ongoing development if you want it.

Moving sales off Salesforce or Pipedrive at the same time? It can run as one project. See my HubSpot migration services.

Questions people ask

How long does a Zendesk to HubSpot migration take?

From 1 month of project work. The transfer itself can run for days with years of tickets and attachments, so it runs in the background while your team keeps working in Zendesk. What sets the pace is usually decisions on your side: what to bring, how routing should work and when to switch.

Will customers notice the move?

They shouldn't. The risk is a customer replying to an old Zendesk email and opening a fresh ticket in HubSpot. I handle that with a short 'we've moved' email on open tickets before switch-over and a workflow that merges stray replies into the original ticket.

Will we have downtime?

Usually not. On my last Zendesk move the team stopped using Zendesk at an agreed time and carried on in HubSpot, with no downtime. Where a short pause can't be avoided, I keep it as small as possible, tell everyone well in advance and put a plan in place for that window.

Do we need Service Hub Enterprise?

Not to migrate. Professional takes the data. Enterprise is worth it if you need extra objects, such as customer sites or assets, or more advanced routing. I'll tell you which on the first call.

Should we move every ticket?

Usually not. Automated alerts, notifications and spam all sit in Zendesk as tickets. We agree what's worth keeping, so the move is quicker and your team's views only show tickets a person needs to deal with.

How do you train the team?

Live sessions for each team, timed for their region, with a guide built from screenshots of your own HubSpot and a recording to keep. Support, product and engineering each get training built around how they work.

What happens after go-live?

A week of hypercare: I'm close at hand, quick to respond, and every issue is tracked until it's closed. After that, I can stay on for ongoing development, or hand over fully.

Can you move our help centre articles too?

Yes. Articles move into HubSpot's knowledge base, internal ones stay internal, and links are fixed so nothing points back to Zendesk.

What happens to integrations like Jira and Slack?

I go through every app and integration connected to Zendesk and agree with you whether to rebuild, replace or drop it. Jira and Slack both connect to HubSpot, so escalations and alerts keep flowing.

Where to next

Thinking of leaving Zendesk?

Book a short call. Tell me roughly how many tickets, agents and regions you have, and when the Zendesk renewal lands. I'll tell you what I'd do and what to decide first.

Book a call