How to Migrate from Zendesk to HubSpot Service Hub 2026
TL;DR: Migrate from Zendesk to HubSpot Service Hub in 4–6 weeks. Save $245–2,985/month depending on team size. Export tickets via Zendesk API, import into HubSpot, migrate configurations, train team, go live. This guide covers the exact process with timeline, cost savings calculator, and go-live checklist.
- 5-person team: Zendesk $245/mo → HubSpot $50/mo = $195/mo saved ($2,340/year)
- 10-person team: Zendesk $495/mo → HubSpot $120/mo = $375/mo saved ($4,500/year)
- 15-person team: Zendesk $2,985/mo → HubSpot $120/mo = $2,865/mo saved ($34,380/year)
Why Migrate from Zendesk to HubSpot?
Zendesk costs scale per agent ($49–$199/agent/month), making it expensive for teams 10+. HubSpot Service Hub charges a flat rate ($0–120/month) with unlimited agents. For a 10-person team, HubSpot saves $375–4,500/year.
Additional reasons to switch:
- CRM Integration: HubSpot bundles ticketing + CRM + email. No separate data silos.
- Simpler Setup: HubSpot has fewer menus, faster onboarding (1–2 weeks vs Zendesk's 4–8 weeks).
- Automation: HubSpot's workflows are intuitive; Zendesk requires custom code for advanced logic.
- Unlimited Agents: Add team members without cost increases.
Pre-Migration Checklist (Week 1)
- Audit Zendesk Setup
- Document all custom fields (ticket, organization, user)
- List all automation rules, triggers, and views
- Export contact list with all fields
- Note all integrations (Slack, email, webhooks)
- Set Up HubSpot Service Hub
- Create HubSpot account (if not existing)
- Upgrade to Service Hub (Professional or Enterprise)
- Configure basic ticketing settings
- Set team roles and permissions
- Create Migration Timeline
- Assign migration owner (1 person accountable)
- Reserve 4–6 weeks for full migration
- Plan parallel run period (1–2 weeks)
- Announce migration to team
Data Export & Import (Weeks 2–3)
Step 1: Export Zendesk Data
Use the Zendesk API to export tickets, contacts, and metadata:
curl -u {email}:{token} https://zendesk.com/api/v2/tickets.json?page=1 > tickets_export.json
Export checklist:
- All tickets (open + closed + archived)
- Contact/organization records
- Custom field definitions
- Ticket tags and categories
- Audit logs (optional, for compliance)
Note: Zendesk rate limits API calls to 200/minute. For large exports (10k+ tickets), budget 2–4 hours per export run.
Step 2: Map Zendesk Fields to HubSpot
| Zendesk Field | HubSpot Equivalent | Notes |
|---|---|---|
| Ticket ID | Ticket Number (auto-generated) | Use original ID as external reference |
| Requester | Contact (email) | Will auto-link to existing contact in HubSpot |
| Custom Fields | Custom Properties | Create before import; match data types |
| Tags | Custom Property (text list) | Parse comma-separated values |
| Status (open/closed) | Ticket Status (same options) | Map directly; test on sample first |
Step 3: Import to HubSpot
Use HubSpot's Tickets API or CSV import:
- Prepare CSV: Format exported data with HubSpot column headers
- Test Import: Import 50–100 sample tickets first, verify data integrity
- Batch Import: Upload full ticket set (HubSpot recommends <10k per batch)
- Verify Contacts: Check that imported tickets linked to correct contacts
- Contact mismatch: If contact email doesn't exist in HubSpot, ticket won't link. Create contacts first via separate import.
- Date format: Ensure timestamps match HubSpot format (ISO 8601). Test with 1–2 tickets first.
- Custom field data types: If you're importing a number to a text field, it will fail. Verify field types match.
Configuration & Automation (Week 3–4)
Set Up Ticket Workflows
HubSpot's workflow builder is simpler than Zendesk. Recreate your automation rules:
- Auto-response: When ticket created, send confirmation email (HubSpot does this by default)
- Routing: Assign tickets to team members based on tag or category
- Escalation: Auto-escalate unresolved tickets after 3 days
- Closure: Auto-close resolved tickets after 1 week if no reply
Reconfigure Integrations
HubSpot integrates with Slack, Teams, and Discord. Re-establish notifications:
- Slack: Connect workspace, configure ticket creation and update notifications
- Email: Set up shared inboxes for each support team
- Third-party: Custom webhooks (HubSpot supports outgoing webhooks)
Parallel Run & Training (Weeks 4–5)
Run Both Systems in Parallel
Timeline: 2–3 weeks
Continue using Zendesk for new tickets while testing HubSpot:
- Route new emails to both systems (via email forwarding)
- Resolve tickets in HubSpot, copy updates to Zendesk (to avoid losing data)
- Document any workflow differences or missing features
- Collect team feedback on usability
Team Training
Budget 4–6 hours for team training:
- 30 min: HubSpot platform overview (tickets, contacts, workflows)
- 45 min: How to create, update, and close tickets
- 45 min: How to use automations and templates
- 30 min: Q&A, role-specific training (admin, agent, manager)
Create a quick reference guide for agents (1-page PDF with 10 key workflows).
Go-Live Checklist (Week 5–6)
- All tickets imported and verified
- All custom fields created and tested
- All automations recreated and tested
- Team trained and signed off
- Integrations (Slack, Teams) configured
- Email forwarding setup (new emails → HubSpot only)
- Backups of Zendesk data taken (keep for 30 days)
- Go-live date communicated to customers
Day of Go-Live
- Stop creating new tickets in Zendesk
- Update support email to route to HubSpot
- Send announcement: "We've moved to a new support system for faster responses"
- Monitor incoming tickets for 4 hours (assign 1 person to check for issues)
- Have Zendesk support line open for 1 week (if critical issue arises)
Post-Go-Live (Week 6+)
- Monitor ticket volume and response times (week 1–2)
- Collect team feedback on first 100 tickets resolved in HubSpot
- Optimize workflows based on real usage patterns
- Cancel Zendesk subscription after 30-day grace period (if confirmed stable)
Cost Savings Summary
Zendesk → HubSpot savings:
| Team Size | Zendesk Cost (Annual) | HubSpot Cost (Annual) | Annual Savings | Migration Cost* | Break-Even |
|---|---|---|---|---|---|
| 5 agents | $2,940 (Team) | $600 (Starter) | $2,340 | $500–800 | 3 months |
| 10 agents | $5,940 (Professional) | $1,440 (Professional) | $4,500 | $800–1,200 | 2 months |
| 15 agents | $35,820 (Enterprise) | $1,440 (Professional) | $34,380 | $1,200–1,500 | 1 month |
*Migration cost = internal labor (40–60 hours), third-party consultant (optional), data cleaning.
Risks & Mitigation
- Slow data import: Zendesk API has rate limits. Use batching and schedule imports during off-hours.
- Lost custom workflows: Zendesk's trigger system is more flexible. Document all rules; recreate manually if needed.
- User adoption friction: HubSpot's UI is different. Training + quick reference guide reduces resistance.
- Integration gaps: Zendesk has more third-party apps. Check HubSpot app marketplace before migrating.
Final Recommendation
For teams 10+ people, migrating from Zendesk to HubSpot Service Hub is a no-brainer: 4–6 weeks of effort, $34k+/year in savings. The migration is low-risk (old data preserved, parallel run possible), and HubSpot's interface is actually simpler for most teams.
Start migration if: Your Zendesk bill exceeds $300/mo, or your team has 8+ agents.
Stay on Zendesk if: You need advanced routing rules, SLA management, or have highly customized automations that don't map to HubSpot.
Related Resources
- Intercom vs Zendesk vs HubSpot Service Hub Pricing Comparison — Full pricing and feature breakdown
- SaaS Renewal Negotiation Checklist — How to negotiate Zendesk discounts before migrating
- SaaS Tool Duplication Audit — Find support tool overlaps in your stack
- PricePulse ROI Calculator — Calculate total SaaS stack savings