Zendesk Support to HubSpot
Zendesk Support is a ticketing help desk with users, organizations, tickets, comments, attachments, Help Center articles and side conversations.
Zendesk Support data can move into HubSpot, landing mainly in Service Hub. 4 of 10 mapped objects move directly (Users (end-users), Organizations, Tickets and Attachments); 5 items need manual work and 2 do not move. Plan roughly 1-3 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Zendesk Support
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<10k tickets
CSV or tool-based migration with a basic rebuild.
Mid migration
10k-250k tickets
Tool-based migration with attachments and workflow rebuild.
Large migration
>250k tickets
API extraction, custom objects, SLA redesign and phased cutover.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Zendesk Support: what you need to get in, what lands in HubSpot, and what will not.
REST (Zendesk API v2) with incremental export endpoints
Zendesk subdomain plus an API token or OAuth grant, and HubSpot authorization for the migration tool or private app.
Per-minute account limits by plan: Team 200, Growth/Professional 400, Enterprise 700, Enterprise Plus 2,500. Incremental exports are limited to 10 requests per minute (30 with the High Volume add-on).
Choose your route
How will you move the data?
No native connector was found.
- You need: Zendesk subdomain plus an API token or OAuth grant, and HubSpot authorization for the migration tool or private app.
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- View export to CSV (up to 1,000 tickets, no comments)
- Full data export (JSON/CSV/XML, roughly once every 7 days)
- Incremental Exports API (cursor-based, up to 1,000 records per page)
- Ticket comments API
- Attachments exported as URLs only
Limits: Per-minute account limits by plan: Team 200, Growth/Professional 400, Enterprise 700, Enterprise Plus 2,500. Incremental exports are limited to 10 requests per minute (30 with the High Volume add-on).
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Zendesk Support
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Users (end-users) | Contacts | yes | Zendesk users map to HubSpot Contacts. |
| Organizations | Companies | yes | Watch for duplicate company records. |
| Tickets | Tickets | yes | Status, priority, tags and custom fields move. Each ticket maps to a pipeline and stage, and custom statuses need manual mapping. |
| Ticket comments / conversations | Emails | partial | A CSV export cannot carry full conversations. Tools can carry them, but imported threads may show as a flat log. |
| Internal notes | Notes | partial | A guide lists notes as associated with ticket records. This depends on the tool used. |
| Attachments | Files | yes | Zendesk exports attachment URLs. HubSpot Files can import from URL. |
| Help Center articles | Custom objects | partial | Tool vendors say articles migrate to Service Hub. The HubSpot target (knowledge base) is not a listed HubSpot object, so verify it. |
| Agents (users) | Contacts | partial | Agents are not CRM contacts. Recreate them as HubSpot users and owners, and keep Zendesk agent IDs for ticket ownership mapping. |
| SLA policies | Tickets | manual | No source describes SLA migration. Rebuild SLAs in HubSpot and validate the semantics. |
| Macros, triggers, views | Tickets | manual | Recreate views and macros as HubSpot templates and workflows. |
What to expect
Imported tickets often display as a flat message log, not as native threads.
After Zendesk is switched off, HubSpot receives no new Zendesk responses.
Automations do not transfer. Guides recommend recreating them as workflows.
Custom fields need HubSpot properties first.
Agents must exist in HubSpot before ticket owners can be assigned.
No source documents SLA migration.
Tags have to be mapped to properties or lists.
Use an API-based tool and review a sample batch.
Use 1,000 records per page, back off on Retry-After, and consider the High Volume add-on.
Use incremental exports for the delta before cutover.
Move the files into HubSpot Files before cancelling Zendesk.
Export in smaller date ranges.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Zendesk API and export facts come from the Zendesk developer docs and secondary guides. HubSpot-side mapping rests on vendor and partner pages and community posts, not HubSpot docs. SLA, macro, and trigger semantics were not researched.
Sources
Related migrations
Frequently asked questions
How do I migrate Zendesk Support to HubSpot?
1. Audit ticket volume, custom fields, forms, tags, organizations and attachments in Zendesk. 2. Generate a Zendesk API token or OAuth client and confirm your plan's rate limit. 3. Create HubSpot ticket pipelines, stages and custom properties that match the Zendesk fields. 4. Create HubSpot users, teams and permissions for Zendesk agents.
What data can move from Zendesk Support to HubSpot?
These objects move directly: Users (end-users), Organizations, Tickets and Attachments. Check the mapping table for partial and manual items.
What does not move from Zendesk Support to HubSpot?
Native threaded conversation rendering for imported tickets and Live Zendesk updates after cutover. Plan to rebuild or retire these.
How long does a Zendesk Support to HubSpot migration take?
Small (<10k tickets): 1-3 weeks. Mid (10k-250k tickets): 3-8 weeks. Large (>250k tickets): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Zendesk Support?
Zendesk subdomain plus an API token or OAuth grant, and HubSpot authorization for the migration tool or private app.
Is there a native HubSpot connector for Zendesk Support?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Zendesk Support data?
Check: Support tickets may contain health, financial or payment data typed by customers, Minors' data possible and Attachments may hold sensitive documents. Agree consent, retention and access rules before exporting.
Moving Zendesk Support into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner