ZendeskHubSpot

Zendesk to HubSpot migration

Migration specialists move your tickets, public replies and internal notes into HubSpot, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated November 2026 · 16 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Zendesk to HubSpot at a glance

A Zendesk to HubSpot migration moves support history onto the CRM your sales team already uses: tickets into a Service Hub pipeline, end users into contacts and organizations into companies. Every public reply arrives as an email activity and every internal note as a note, at its original time. Zendesk keeps running until a final delta sync.

Objects mapped
16
in this route's mapping
Typical timeline
About 10 business days end to end
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours
Who it is for
Support teams leaving Zendesk to work tickets in HubSpot Service Hub, next to the contacts, companies and deals their sales team already keeps in HubSpot.
What does not move
Zendesk triggers, automations, macros, SLA policies, views and reports. We document each one so your admin can rebuild it as a HubSpot workflow, snippet, help desk SLA or report.
What sets the scope
Ticket and comment count, side conversations, attachment volume, Help Center size and languages, brands, and how much of your HubSpot daily API limit other apps already use.

What moves

What moves from Zendesk to HubSpot

Zendesk tickets become HubSpot tickets in a Service Hub pipeline, end users become contacts, organizations companies, public replies email activities, internal notes and side conversations notes, and Help Center articles knowledge base articles.

  • 16 included
ZendeskHubSpot
  • End usersContacts

    Matched on email, the identifier HubSpot uses for contacts, so an existing sales contact is updated, not duplicated.

  • OrganizationsCompanies

    Matched on domain where Zendesk has one. A user in several organizations gets one primary company and further associations.

  • AgentsUsers (ticket owners)

    Mapped to HubSpot users by email. Users must exist first, because HubSpot creates owners from users.

  • GroupsTeams

    Set up as HubSpot teams before the load, so tickets keep the same routing.

  • TicketsTickets

    Subject, description, priority, owner and pipeline stage, with the Zendesk ticket ID in a unique property for the delta sync.

  • Ticket statusesTicket pipeline stages

    New, open, pending, on-hold, solved and closed become stages, each marked open or closed.

  • Public repliesEmail activities

    In order on the ticket timeline, incoming for customer messages and outgoing for agent replies.

  • Internal notesNotes

    Internal only in HubSpot, with the original author and time. Notes over 65,536 characters are scoped during the free sample.

  • Side conversationsNotes

    One note per side conversation, with its participants and the time of each message.

  • Attachments and inline imagesFiles

    Uploaded to HubSpot files and attached to the email activity or note they came with.

  • Ticket fields and formsTicket properties and pipelines

    Drop-downs become dropdown select properties; forms map to pipelines or to a property, agreed on the call.

  • User and organization fieldsContact and company properties

    Created as custom properties before contacts and companies load.

  • TagsMultiple checkboxes property

    One checkbox option per tag in use, so tickets can still be filtered by tag.

  • CCs and followersAssociated contacts

    Each person copied is associated to the ticket as a contact, so the thread's audience stays visible.

  • Help Center categories and sectionsKnowledge base categories and subcategories

    Built in HubSpot before articles load, because the API cannot create them.

  • Help Center articlesKnowledge base articles

    Loaded as drafts with their tags; tables are checked article by article.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Zendesk to HubSpot as-is

Triggers, automations, macros, SLA policies and views are Zendesk configuration, so they are listed for rebuilding as HubSpot workflows, snippets and help desk SLAs.

Satisfaction ratingsOn request
In HubSpot: Ticket propertiesHubSpot's survey responses API is read-only, so each score and comment moves as a property on the ticket.
Custom objectsOn request
Moved when your HubSpot account is on an Enterprise tier, which custom objects need.
Ticket auditsOn request
In HubSpot: Note on the ticketA summary of the change history, written as one note, for teams that need it.
BrandsOn request
In HubSpot: Ticket property or separate knowledge basesAgreed on the scoping call: a ticket property, or one knowledge base per brand where your HubSpot account has several.
Triggers and automationsNot migrated
In HubSpot: WorkflowsListed with their conditions and actions, then rebuilt by your admin as HubSpot ticket workflows.
MacrosNot migrated
In HubSpot: Snippets and templatesEach macro's text and field changes are documented so it can be recreated.
SLA policiesNot migrated
In HubSpot: Help desk SLAsSet up again in HubSpot; first reply and resolution times on solved tickets move as properties.
Views, reports and dashboardsNot migrated
Rebuilt on the migrated properties, with the Zendesk ticket ID kept for matching old reports.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Zendesk to HubSpot migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We agree which brands, date ranges and Help Center sections move, whether side conversations and satisfaction ratings come across, and which HubSpot ticket pipeline each Zendesk form feeds.

    • Connect both accounts

      You0.5 day

      You approve a Zendesk OAuth client and install a HubSpot app with ticket, contact, company and file scopes. Agents who will own tickets are added as HubSpot users first.

    • Pipeline and property build

      Both1 day

      Zendesk statuses become stages of a ticket pipeline, each marked open or closed. Custom ticket fields, tags and the original date fields become HubSpot ticket properties.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, chosen for the longest threads, side conversations and largest files, loaded into HubSpot with notifications off.

    • You review the sample

      You1 day

      Your leads open the tickets in the help desk and check reply order, internal notes, owners, files and the original date properties.

    • Full load

      MigrateX2-3 days

      Companies and contacts first, then tickets matched on the Zendesk ticket ID, then email activities, notes and files, then the associations between them, paced to your daily API limit.

    • Delta sync

      MigrateX0.5 day

      Zendesk tickets changed since the full load are updated on the same ticket ID, and only their new comments are added, so nothing appears twice.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Zendesk tickets against HubSpot tickets per status and year, comments against email activities and notes, and attachments against files.

    • Sign-off

      You1-2 days

      Your team spot-checks a random set, ticket workflows go back on, and Zendesk stays read-only with a rollback plan until you sign off.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 3 solved
  • 4 handled
  1. 01SolvedMost critical

    A Zendesk comment becomes either an email or a note in HubSpot

    The problem

    Zendesk keeps public replies and internal notes in one comment list, told apart by the public flag. HubSpot has no such list on a ticket: past messages cannot be written into an inbox thread, because a message posted through the Conversations API is sent from the channel to the customer.

    How we handle it

    Public replies load as email activities on the HubSpot ticket, with direction set so customer messages read as incoming. Internal notes load as notes, which HubSpot never shows to the customer. Nothing is posted to a live channel, and you check the order on the free sample.

    Source: HubSpot developer documentation, checked 15 Nov 2026

  2. 02Handled

    Zendesk created and solved dates need their own properties

    The problem

    HubSpot's knowledge base says Create date is read-only on every object except deals, while its ticket property page says users can edit a ticket's Create date. A Zendesk ticket loaded without a plan would show the migration day as its start.

    How we handle it

    Each ticket gets Zendesk created and solved dates in dedicated date properties that reports can use, and we test whether Create date accepts the original value during your free sample. Comment times are kept on every activity.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  3. 03Handled

    Long Zendesk internal notes outgrow a HubSpot note

    The problem

    A HubSpot note body holds at most 65,536 characters. Zendesk internal notes with pasted logs or stack traces can run longer, and a single Zendesk ticket can hold up to 5,000 comments.

    How we handle it

    How a Zendesk note over that limit is carried, for example in numbered parts, is scoped with you during the free sample, and tickets with the longest threads are picked for that sample so you see them first.

    Source: HubSpot developer documentation, checked 15 Nov 2026

  4. 04Solved

    Side conversations sit outside the Zendesk comment list

    The problem

    Side conversations exist only with Zendesk's Collaboration add-on, and each one keeps its messages as events of its own. An export that reads ticket comments finishes without them and reports no error.

    How we handle it

    We list the side conversations of each ticket, read their events, and add each one to the HubSpot ticket as a note naming its participants, with the time of every message.

    Source: Zendesk developer documentation, checked 13 Nov 2026

  5. 05Handled

    Creating tickets in HubSpot can notify agents and start workflows

    The problem

    HubSpot warns that ticket creation and assignment while history moves into the help desk may trigger notifications and enrol tickets in ticket workflows. Thousands of historical Zendesk tickets can flood your agents' inboxes.

    How we handle it

    Your admin and our engineer list the ticket workflows and notification settings before the production run, switch them off for the load, and switch them back on after the delta sync. The free sample proves nobody is notified.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  6. 06Handled

    The Help Center needs its categories built before articles land

    The problem

    HubSpot's Knowledge base API is in beta, creates new articles as drafts and cannot create categories or tags. Zendesk organises articles into categories and sections, which have to exist in HubSpot first.

    How we handle it

    Zendesk categories become knowledge base categories and sections become subcategories, set up before any article loads. Articles arrive as drafts with their tags, and your team publishes them in one reviewed batch.

    Source: HubSpot developer documentation, checked 15 Nov 2026

  7. 07Solved

    A token-based Zendesk export can stop mid-project

    The problem

    Zendesk will switch off API tokens permanently on 30 April 2027, and since 27 October 2026 existing accounts cannot create new ones. A long history export or a late delta sync that relies on a token is at risk.

    How we handle it

    MigrateX reads Zendesk through an OAuth client you approve, so the export and the final delta sync keep working through cutover.

    Source: Zendesk developer documentation, checked 14 Nov 2026

Technical profile

What makes this route technical

Zendesk keeps comments out of its ticket export and archived tickets out of its list calls, while HubSpot paces the load through one daily API budget shared with your other apps.

Exporting from Zendesk: comment bodies need a sideload
Zendesk's incremental ticket export carries no comment bodies. The ticket events export returns full comment data only when it is called with include=comment_events, which is how every reply and note is read without one call per ticket.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: deleted tickets are in the stream
By default, Zendesk's incremental export includes deleted tickets in the ticket stream. They are filtered out before the HubSpot load, so a ticket your team removed does not come back.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: the per-minute ceiling by plan
Zendesk allows 200 Support API requests a minute on Team, 400 on Growth and Professional, 700 on Enterprise and 2,500 on Enterprise Plus. The High Volume API add-on lifts a qualifying plan to 2,500 a minute, in place of its plan limit rather than on top of it.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: archived tickets keep their audits apart
Zendesk's List All Ticket Audits endpoint leaves archived tickets out. Their audit records come from List Audits for a Ticket, one ticket at a time and without pagination.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into HubSpot: every comment keeps its time and author
HubSpot email and note activities take hs_timestamp, which places each one on the ticket timeline at the original Zendesk comment time, and hubspot_owner_id, which names the agent shown as its creator.

Source: HubSpot developer documentation, checked 15 Nov 2026

Importing into HubSpot: one daily budget for every app
A HubSpot Professional account gets 625,000 API requests a day and an Enterprise account 1,000,000, shared by every app installed. Associations written through HubSpot's associations API have their own allowance of 500,000 requests a day.

Source: HubSpot developer documentation, checked 15 Nov 2026

Facts checked 15 Nov 2026 against Zendesk and HubSpot documentation. Each fact links its source.

Zendesk to HubSpot questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How do I migrate Zendesk to HubSpot Service Hub?

Build the HubSpot side first, then load in order. Ticket pipeline, properties and users come first; then companies and contacts, tickets, replies and notes, files and the links between them; then a delta sync at cutover. Our default plan takes about 10 business days, and the free sample shows the real pace on your own tickets.

Can Zendesk tickets be imported into the new Service Hub help desk?

Yes. Zendesk tickets land in the help desk workspace, which needs Service Hub Professional or Enterprise, with each conversation on the ticket timeline as email activities and notes. HubSpot accounts created after 1 April 2024 keep tickets in the help desk only, so that is where your agents will find them.

Will our Zendesk tickets keep their original created and solved dates in HubSpot?

Yes, in dedicated date properties on every HubSpot ticket that your reports can use, and every reply and note keeps its original time on the timeline. Whether HubSpot's own ticket Create date takes the Zendesk value is confirmed during your free sample.

Do public replies and internal notes stay separate on the HubSpot ticket?

Yes. Zendesk public replies become HubSpot email activities and internal notes become HubSpot notes, each in its original order, so the customer-facing thread and the agents' discussion stay apart and no customer is emailed by the load.

What happens to Zendesk side conversations and attachments in HubSpot?

Both come across. Each Zendesk side conversation becomes a note on its HubSpot ticket, and attachments and inline images are attached to the reply or note they belonged to, up to 2 GB a file on paid HubSpot plans.

Can HubSpot Smart Transfer move Zendesk data instead, and what does it leave out?

Smart Transfer covers the basics, with limits. It maps Zendesk users, organizations, tickets, agents and groups, moves comments as notes in a one-time pass that never resyncs, needs a Super Admin, and needs Data Hub for custom field mappings. It also switches on the workflows it creates from your triggers, which a history load usually should not do.

Do our Zendesk triggers, automations and macros come across to HubSpot?

Not as working rules. They are Zendesk configuration, so MigrateX documents each trigger, automation and macro with its conditions and actions, and your admin rebuilds the ones still needed as HubSpot workflows, snippets and templates. SLA policies are set up again as help desk SLAs, and views and reports are rebuilt.

Will the Help Center move to the HubSpot knowledge base with its categories and sections?

Yes. Zendesk Help Center categories and sections become HubSpot knowledge base categories and subcategories, and articles arrive as drafts with their tags and images, in your primary language unless more languages are scoped. Article URLs change, and we hand over a redirect map.

What does a Zendesk to HubSpot migration cost?

It is priced on what moves: tickets and the comments, side conversations and attachments on them, Help Center articles, brands, and any custom objects. A free sample migration of 100 of your records comes first, and your fixed quote follows within 24 hours.

How it compares

Four ways to run Zendesk to HubSpot

The same data, moved four different ways. This is what changes between them.

Object coverage (cases, emails, comments, files, Knowledge)

  • MigrateX

    Every object in the mapping on this page, plus the ones you ask for during scoping.

  • Automated migration software

    Tickets and contacts are covered. Linked records, files and knowledge often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Public replies vs internal notes

  • MigrateX

    Each entry is posted separately, private stays private, public stays public.

  • Automated migration software

    Threads usually arrive, but per-entry author and visibility can be flattened.

  • Vendor CSV import

    Notes collapse into one field on the ticket, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Attachments

  • MigrateX

    Uploaded against the right note, and re-hosted with a link when they exceed the HubSpot cap.

  • Automated migration software

    Supported up to the destination cap. Oversize files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. Support answers tickets.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a Zendesk to HubSpot migration

Related routes

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your HubSpot move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.