Zendesk to HubSpot Service Hub migration
We migrate Tickets, Users, Organizations, and Help Center articles from Zendesk into HubSpot Service Hub using authenticated API pulls that bypass Zendesk's tier-gated export UI, with Organizations mapped to Companies, Tags converted to multi-select properties, and every active SLA Policy and Automation documented for your admin to rebuild in HubSpot's workflow builder.
FlitStack AI migrates tickets, contacts, companies, users and multi-select properties from Zendesk to HubSpot Service Hub, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 6-10 weeks.

What moves from Zendesk to HubSpot Service Hub?
Moving from Zendesk to HubSpot Service Hub is a structural migration that spans two fundamentally different platform philosophies: Zendesk is a dedicated helpdesk where every customer interaction is a Ticket with deep routing, SLA, and automation primitives; HubSpot Service Hub is a CRM layer where Tickets live on the same Contact and Company records that sales and marketing use.
Read the full summary
We handle the object model translation — Organizations to Companies, Tags to multi-select properties, Comments to conversation threads — and we preserve timestamp fidelity across all imported conversations. HubSpot has no native Side Conversations equivalent, no Tags-as-objects, and no event-driven Triggers; we flag each gap explicitly so your admin rebuilds with full context. We do not migrate Triggers, Automations, SLA Policies, Macros, or Help Center routing rules as code; we deliver a written inventory of each with recommended HubSpot Workflow equivalents for your team to rebuild.
Ticket → Ticket
Zendesk Tickets map to HubSpot Tickets with direct field translation: status maps to Ticket status, priority maps to Ticket priority, requester maps to the primary Contact lookup, assignee maps to the HubSpot Owner (User), and group maps to a HubSpot Team.
How it maps
Comment threads migrate as conversation entries preserving public/private visibility distinction. Custom fields on Zendesk tickets map to custom properties on the HubSpot Ticket object. We use HubSpot's Tickets API (REST) with batched imports and parent-record resolution for Contact and Owner lookups.
User (End-User / Requester) → Contact
Zendesk end-users (requesters) map directly to HubSpot Contacts.
How it maps
We pull the full user profile including name, email, phone, locale, organization membership, and custom fields, and import as HubSpot Contact properties. Multiple email addresses on a Zendesk user become secondary Contact properties or are consolidated to the primary email as the dedupe key.
Organization → Company
Zendesk Organizations map to HubSpot Companies.
How it maps
The organization's domain name becomes the Company domain property, and all members of the Zendesk organization are linked to the HubSpot Company via the Company association on each Contact. Cross-references between Zendesk organizations (parent-child relationships) migrate as HubSpot Company parent-company associations.
Agent → User
Zendesk Agents map to HubSpot Users by email address.
How it maps
We extract agent role assignments (Admin, Agent, Light Agent) and group memberships during scoping and preserve them in a custom property on the HubSpot User for later use in permission configuration. Agents without a matching HubSpot User go to a reconciliation queue; the customer's admin provisions missing users before record import.
Tag → Multi-Select Property
Zendesk tags applied to Tickets, Users, and Organizations do not have a native HubSpot equivalent — HubSpot tags are mini-filters in the CRM, not a data object.
How it maps
We convert Zendesk tags to HubSpot multi-select properties on the Contact, Company, and Ticket objects, one property per Zendesk tag taxonomy. The customer chooses the target property names during scoping.
Comment / Conversation → Conversation Thread
Zendesk Ticket comments (public replies and internal notes) migrate to HubSpot Ticket conversation entries preserving the author (Contact or Agent/User), timestamp, and visibility (public vs internal).
How it maps
Internal notes from Zendesk Side Conversations migrate as HubSpot internal ticket properties or as notes on the related Deal if the Side Conversation referenced a deal context.
- TicketTicket1:1
- UserContact1:1
- OrganizationCompany1:1
- AgentUsertransformed
- TagMulti-Select Propertytransformed
- CommentConversation Thread1:1
+ 9 more in the mapping below
How Zendesk and HubSpot Service Hub differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Zendesk | HubSpot Service Hub |
|---|---|---|
| Platform paradigm | Standalone helpdesk — Tickets are the primary object across email, chat, phone, social | CRM layer — Tickets live on Contacts and Companies, shared with sales and marketing |
| Tagging model | Tags as first-class objects applied to Tickets, Users, Organizations | Tags as mini-filters only — functional tagging requires multi-select properties on Contacts and Tickets |
| Internal notes | Side Conversations as separate internal thread attached to a Ticket | No native Side Conversations equivalent — internal notes on Deals or internal Ticket properties |
| Automation primitives | Event-driven Triggers, hourly Automations, SLA Policies as separate rule types | HubSpot Workflows are property-triggered and schedule-based but lack a direct Trigger analog |
| Multi-brand routing | Up to 300 Brands with independent email, Help Center, and routing | No multi-brand abstraction — routing by brand requires Inbox segmentation and manual setup |
| Knowledge base export | No native full-KB export — requires Help Center API scripting | Knowledge base import via HubSpot CMS API with section and article hierarchy recreation |
| Custom objects | Enterprise-only Custom Objects v2 with lookup relationships to Tickets | Custom Objects available on Enterprise tier ($150/seat/mo) with associations to Tickets |
What to watch for in a Zendesk to HubSpot Service Hub migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
HubSpot Tags are filters, not a data object
Zendesk tags are first-class string labels applied to Tickets, Users, and Organizations with a full API object.
How we handle it
HubSpot's tag functionality is limited to CRM-level mini-filters for visual record grouping — they do not exist as a property that can be queried, used in automation, or set via API on Tickets. During migration, we convert Zendesk tag sets to HubSpot multi-select properties on Contact, Company, and Ticket objects, one property per tag taxonomy. This is a structural translation that must be designed during scoping; tags that are used in Zendesk routing rules, triggers, or SLA conditions require a HubSpot Workflow alternative documented separately.
Zendesk Side Conversations have no HubSpot equivalent
Zendesk Side Conversations are separate internal discussion threads attached to a Ticket, used by agents to collaborate without the requester seeing.
How we handle it
HubSpot Service Hub has no Side Conversations concept — internal ticket notes exist but are not a separate thread model. We migrate Side Conversation content as internal notes on the HubSpot Ticket, documenting the original Side Conversation author and timestamp for audit. If the Side Conversation referenced a deal context, we migrate the content as notes on the associated Deal record.
Migrated closed ticket history is not visible to end users
When Zendesk tickets are migrated to HubSpot, the end user's portal view does not automatically display the full historical ticket thread.
How we handle it
HubSpot's customer portal shows new ticket conversations initiated within HubSpot; legacy Zendesk ticket history requires the customer to access it via the CRM record or a configured customer portal article. We document this behavior explicitly and recommend that customers configure a knowledge base article explaining where historical tickets are visible post-migration, or plan a customer-facing communication about the portal change.
API rate limits on both platforms require batch chunking
Zendesk's REST API rate limits vary by plan tier ( Essentials 200 requests/minute, Team 700, Suite Growth 1,000, Suite Professional 2,000, Suite Enterprise 2,500).
How we handle it
HubSpot's API has tiered limits (Starter 100 calls/10 seconds, Professional 150, Enterprise 200). We implement batch chunking with exponential backoff on both pull (Zendesk) and push (HubSpot) sides, and we chunk ticket comment threads to avoid single-record API calls dominating the budget. For accounts with millions of ticket comments, a staged migration with delta sync is required.
Triggers, Automations, and SLA Policies require admin rebuild
Zendesk Triggers fire immediately on ticket events, Automations run hourly on up to 1,000 tickets per batch, and SLA Policies define first-response and resolution targets per ticket type — all with no direct HubSpot equivalent.
How we handle it
HubSpot Workflows are property-triggered and schedule-based, but multi-condition event-driven triggers require redesign. We do not migrate these as code. We deliver a written inventory of every active Trigger, Automation, and SLA Policy with its conditions, actions, and a recommended HubSpot Workflow equivalent for your admin to rebuild.
How the migration runs
Discovery and plan-tier audit
We audit the Zendesk account across plan tier (Team through Enterprise Plus), active Tickets, Organizations, Users, Help Center article count, tag taxonomy, Side Conversation volume, and active Trigger/Automation/SLA Policy count.
What this step covers
We confirm the destination HubSpot account tier (Starter through Enterprise) and flag whether Custom Object support is needed. We also identify any plan-gated API endpoints relevant to the migration scope, including whether the account is on a tier that requires API-scripted export rather than native export UI.
Field mapping and tag translation design
We design the field mapping table mapping each Zendesk Ticket, User, Organization, and custom field to a typed HubSpot property.
What this step covers
Tags are assigned to target multi-select properties per taxonomy. Side Conversations are routed to Ticket internal notes or Deal notes. SLA Policy definitions are extracted as structured records for the rebuild inventory document. Custom Objects are mapped to HubSpot Custom Objects if the destination is on Enterprise, or flattened to Ticket custom fields if not.
Sandbox migration and reconciliation
We run a representative sample migration into a HubSpot test account or sandbox equivalent, migrating a random sample of 100-200 tickets with associated Contacts, Companies, and attachments.
What this step covers
The customer's operations lead reviews the output, spot-checks field mapping accuracy, confirms tag translation behavior, and validates that Side Conversations and internal notes landed correctly. Mapping corrections happen here before production migration.
Production migration in dependency order
We execute the full production migration in dependency order: Contacts (from Zendesk Users), Companies (from Zendesk Organizations), then Tickets with Contact and Company lookups resolved, then conversation threads and attachments, then Help Center articles, then Custom Objects last.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Zendesk write access is suspended during the production migration window to prevent data divergence.
Cutover and delta sync
We freeze Zendesk writes at a defined cutover timestamp, run a final delta migration of any records created or modified since the last batch, then hand off HubSpot as the active system of record.
What this step covers
We deliver the Trigger, Automation, SLA Policy, Macro, and View inventory documents to the customer's admin team with recommended HubSpot Workflow equivalents for each.
Hypercare and rebuild support handoff
We support a one-week hypercare window resolving any reconciliation issues raised by the customer support team during the first days of live HubSpot operations.
What this step covers
We do not rebuild Triggers, Automations, SLA Policies, or Macros as HubSpot Workflows within the migration scope; that is a separate engagement. We are available to answer questions about the inventory documents during hypercare.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with ticket volume, custom object count, and the number of Zendesk automation rules requiring documentation for rebuild. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Zendesk to HubSpot Service Hub →Why teams move from Zendesk to HubSpot Service Hub
- Teams running Zendesk alongside HubSpot CRM maintain two contact databases and lose ticket context at every handoff between support and sales. HubSpot Service Hub puts Tickets on the same Contact and Company records that sales and marketing use, eliminating the data silos that drive the migration. G2 reviewers on both platforms cite the unified CRM record as the primary driver for the switch.
- Per-agent pricing at Zendesk Enterprise ($150-169/seat/mo) plus AI add-ons, high-volume API access, and plan-gated features creates billing surprises that compound as headcount grows. HubSpot Service Hub at Professional ($90/seat) includes built-in AI capabilities (Breeze Customer Agent), CSAT surveys, and knowledge base without additional per-resolution charges, making the effective cost more predictable for teams that need full functionality.
- Zendesk's deep automation primitives — Triggers, Automations, SLA Policies — work well within Zendesk but have no direct equivalent in other platforms. Teams migrating to HubSpot consolidate automation under one vendor umbrella and accept that triggers and SLA policies must be rebuilt as HubSpot Workflows rather than imported. The consolidation benefit outweighs the rebuild cost for teams already paying for HubSpot Marketing and Sales.
- Zendesk's native export UI is gated behind Professional and Enterprise plans, forcing lower-tier accounts to use API scripting to extract ticket and Help Center data. This restriction, combined with tier-gated Custom Objects on lower plans, pushes teams toward HubSpot where data portability is a documented feature rather than a plan-gated limitation.
- Zendesk's Help Center requires API scripting for full export, with no native bulk-download option. Articles, section hierarchy, translations, and Dynamic Content must be pulled separately from different API endpoints. Teams with large knowledge bases cite this as a hidden migration cost that a service provider like FlitStack AI handles but DIY migrations frequently underestimate.
Questions, answered
Zendesk to HubSpot Service Hub migration questions
How long does a Zendesk to HubSpot Service Hub migration take?
Most migrations land between six and ten weeks for accounts with up to 50,000 Tickets, 5,000 Organizations, and no Enterprise-gated Custom Objects. Migrations with large Help Center article libraries (over 1,000 articles), Enterprise Custom Objects with lookup relationships, complex multi-brand routing across 5+ Zendesk Brands, or accounts requiring delta sync for in-flight tickets during the migration window move to ten to sixteen weeks.
Do Zendesk Triggers, Automations, SLA Policies, and Macros migrate to HubSpot?
No. Triggers, Automations, and SLA Policies are Zendesk-specific rule engines that do not map to HubSpot Workflows as code. Macros translate to HubSpot Snippets for content but lose conditional logic and variable substitution. We do not rebuild them. We deliver a written inventory of every active Trigger, Automation, SLA Policy, Macro, and View with its conditions, actions, and a recommended HubSpot Workflow or Snippet equivalent for your admin to rebuild post-migration.
We already use HubSpot CRM for sales. Can we just add Service Hub?
Yes, and this is one of the most common migration patterns. Teams running HubSpot Sales Hub or Marketing Hub alongside Zendesk consolidate by adding Service Hub to the existing HubSpot account, migrating only the support workload. We map Zendesk Contacts to existing HubSpot Contacts (deduped by email), Zendesk Organizations to existing HubSpot Companies (deduped by domain), and link Tickets to the matched Contact and Company records. Overlapping data is reconciled during scoping rather than duplicated.
Will we lose ticket history and attachment files?
No. We migrate full ticket histories including comment threads, timestamps, public and internal notes, and file attachments via authenticated API pulls. Attachments are downloaded from Zendesk, preserved with their MIME type and filename, and uploaded to HubSpot via the HubSpot Files API with links back to the Ticket. Zendesk's plan-gated export UI does not restrict our API-based pull — we use Zendesk's REST API directly regardless of account tier.
How do we handle Zendesk Help Center articles and knowledge base content?
Zendesk's Help Center has no native bulk export. We use the Help Center API endpoints to iterate over sections and articles, downloading HTML article body, section hierarchy, author attribution, and translations for Dynamic Content items. We create HubSpot Knowledge Base articles via the CMS API, preserving article structure, attachments, and locale settings. We deliver a URL mapping document for any existing Zendesk Help Center links to be redirected to the new HubSpot Knowledge Base URLs.
Can FlitStack AI migrate Zendesk Custom Objects to HubSpot?
Yes, if the destination HubSpot account is on Enterprise tier ($150/seat) which includes Custom Object support. We map Zendesk Custom Object schemas to equivalent HubSpot Custom Object definitions including all custom fields and lookup relationships. If the destination is on Starter or Professional, we flatten Custom Object data into Ticket custom fields and deliver a supplementary table with the relational data documented for future Custom Object migration once the account upgrades.
What is the biggest risk in this migration?
The workflow rebuild. Teams consistently underestimate how much institutional process lives in Zendesk Triggers, Automations, and SLA Policies that were never formally documented. We audit all of it before migration starts and deliver a written map for rebuild. The teams that skip this step are the ones who rebuild the same broken workflows in HubSpot. Side Conversation loss and tag translation gaps are the second and third most common post-migration surprises — we address both in the scoping phase.
Related migrations
HubSpot implementation
Set up HubSpot Service Hub and migrate into it as one engagement.
See the service → Intercom to HubSpot Service HubMapping · history · rollbackFreshdesk to HubSpot Service HubMapping · history · rollbackSalesforce Service Cloud to HubSpot Service HubMapping · history · rollback Zendesk to FreshdeskMapping · history · rollbackZendesk to IntercomMapping · history · rollbackZendesk to Salesforce Service CloudMapping · history · rollbackSources: official documentation
Get a quote
Moving from Zendesk to HubSpot Service Hub?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot Service Hub setup with you, then send a quote.
Get a quote