HubSpot migration

Zendesk to HubSpot: Moving Support (and Zendesk Sell) Without Copying the Mess

How to move Zendesk Support to HubSpot Service Hub, or Zendesk Sell to HubSpot before its 2027 end of life: design first, what moves, seats, portals, AI and the cutover.

By Rikki Lear, Imagine Growth · 16 November 2026 · 13 min read

Zendesk to HubSpot: Moving Support (and Zendesk Sell) Without Copying the Mess

Short answer: Treat it as a rebuild, not a copy. Design the help desk (or sales process) you want in HubSpot first, then move only the Zendesk data that fits that design. Count who actually works tickets before buying seats, because it’s often far fewer than your Zendesk user count. Time the cutover against your Zendesk contract, and if you’re on Zendesk Sell, against its end of life in August 2027. Add AI after the basics are live, not on day one.

Two kinds of Zendesk conversation landed on my desk this year:

  • Support teams moving Zendesk Support into HubSpot Service Hub, usually because sales and marketing are already in HubSpot and the two systems don’t talk properly.
  • Sales teams on Zendesk Sell, which Zendesk has announced will reach end of life on 31 August 2027. That move isn’t optional, so the question is just how to do it well.

They need different handling, so I’ll cover both.

Part one: Zendesk Support to HubSpot Service Hub

Don’t copy what you have

Every help desk I’ve looked at had years of views nobody uses, priorities that only exist in someone’s head, and reports measuring the wrong things.

The best brief I’ve had this year came from a support lead at a UK software company. She didn’t want what they had in Zendesk duplicated. She wanted to design the help desk her clients should have, then bring across the data that fits it. And the bar she set was clear: “Nothing can go wrong, no data can be lost.”

That’s the right order. Design, then migrate.

What to design before anything moves

  • Ticket pipelines and stages. Usually far simpler than the Zendesk setup.
  • Priorities and SLAs. Written down, so a person or an AI agent can apply them the same way. In that software company’s case, most of their definitions and priority rules had never been documented. Writing them down became part of the project.
  • Routing. Which tickets stay with support, which go to product or technical services, and how anything handed to Jira comes back.
  • Knowledge base. What customers can answer for themselves before raising a ticket.
  • Customer portal. What customers can see and do: ticket history, guides, training, release notes.
  • Reporting. Resolution time and first-contact resolution, not just time to first reply.

What moves, and what doesn’t

Moves well Needs a decision Gets rebuilt
Tickets and conversations Old ticket history (all of it, or a recent window?) Triggers, macros and automations
Contacts and companies, with associations Attachments Views and dashboards
Knowledge base articles (with tidying) Portal features with no direct HubSpot equivalent SLAs and routing rules

Watch the portal. Zendesk portals often carry extras that HubSpot doesn’t do the same way. The software company’s portal let customers vote on product ideas. HubSpot doesn’t do that natively, so we flagged it early and agreed what replaces it, rather than discovering it at go-live.

Seats: count carefully

Not everyone who touches Zendesk needs a paid Service Hub seat in HubSpot. In the software company’s case, roughly 35 people had Zendesk access, but they estimated only about a dozen actually work tickets. HubSpot’s View-Only seats are free, so people who only need to look at tickets don’t need a paid seat.

HubSpot’s pricing changed in October 2026 for new EMEA customers, who now buy per seat with monthly credits. Model the seats you really need before you talk to HubSpot. More in what HubSpot licences really cost.

Where AI fits

After the basics, not before. AI ticket triage, suggested replies and a customer agent answering from your knowledge base all work far better once priorities are written down and the knowledge base is clean.

Teams are also, understandably, nervous about it. The software company asked for AI to wait until phase three, once the team was comfortable with the new help desk. That’s sensible.

When you do get there, the results can be quick. For FP Alpha, a New York wealthtech company, we built a knowledge base on HubSpot Service Hub and a live AI agent that answers from it and cites its sources. Discovery to live took about five weeks, at a fixed $8,450. It’s written up in our FP Alpha case study.

A realistic plan

  1. Design. Pipelines, SLAs, routing, portal and reporting, agreed in writing.
  2. Build. Service Hub configured to the design, automation rebuilt.
  3. Migrate. Only the data that fits the new model, tested first.
  4. Train and go live. On your own help desk.
  5. AI. Triage, suggested replies and agents, once the basics are trusted.

And find your Zendesk renewal date first. The software company’s biggest worry was being “slow rolled into a Zendesk renewal” because nobody knew exactly when it fell.

Part two: Zendesk Sell to HubSpot

The deadline is real

Zendesk has announced that Zendesk Sell reaches end of life on 31 August 2027, after which syncs and integrations stop working. If you’re on Sell, you’re moving somewhere. Start early enough to do it properly rather than in a panic.

The data model is different

Zendesk Sell uses a lead record that becomes a contact and a deal when it converts. HubSpot doesn’t work that way. So thousands of leads may need splitting into the right objects, with the ones that don’t fit cleanly held back for review rather than forced in.

Real questions from a real scoping call

One owner I spoke to this year, running a technical services business, wanted:

  • All his data moved, including around 200,000 internal notes
  • Custom fields mapped and validated, but not every legacy field kept
  • His Zapier zaps, Power Automate flows, QuickBooks, Mailchimp and quoting software connections preserved or rebuilt, because the current flows were “a bit fragile”
  • 13 to 14 GB of documents left where they were, in SharePoint, with links from HubSpot

He also had a quote from a data-migration specialist to move the data and custom fields in a week. That’s a fair benchmark for the data alone. What it doesn’t cover is the lead-splitting decisions, the integrations, the automation and the training. When you compare quotes, compare the whole job.

Licences

He’d already bought HubSpot Starter and wanted to stay there to avoid extra licence costs. That’s a reasonable call for a small team, as long as you check which features you’ll need (custom objects and some automation need higher tiers). See which HubSpot tier you actually need.

What it costs

A migration to HubSpot with us starts at £9,500, $12,000 or €11,000, fixed after a source audit. A help desk redesign before migration is scoped as part of that audit. HubSpot licences are separate and stay in your name. Full breakdown in how much a HubSpot migration costs.

Frequently asked questions

Can you migrate from Zendesk to HubSpot Service Hub? Yes. Tickets, conversations, contacts, companies and knowledge base content move well. Triggers, macros, views and SLAs are rebuilt in HubSpot.

Should we copy our Zendesk setup into HubSpot? No. Design the help desk you want first, then migrate only the data that fits it.

How many HubSpot Service Hub seats do we need? Only for people who actually work tickets, which is often far fewer than your Zendesk user count. Check HubSpot’s current seat rules before buying.

When does Zendesk Sell end? Zendesk has announced Zendesk Sell’s end of life on 31 August 2027, after which syncs and integrations stop.

How do Zendesk Sell leads map to HubSpot? Zendesk Sell leads convert into contacts and deals, so they need splitting into the right HubSpot objects during mapping, with unclear records reviewed rather than forced in.

Should we add HubSpot AI to support on day one? Usually not. Get priorities, routing and the knowledge base right first, then add AI triage and agents as a later phase.

How much does a Zendesk to HubSpot migration cost? With Imagine Growth, from £9,500, $12,000 or €11,000, fixed after a source audit. HubSpot licences are separate.

Sources: Zendesk Sell end of life notice, via Zoho. Next: how much a HubSpot migration costs, or how we run a HubSpot migration.

Keep reading