Zendesk to Freshservice: moving internal IT off a customer support tool
Short answer
Zendesk works for internal IT support when you're small (under 50 employees), need basic ticketing fast, and don't require asset management or change control. Migrate to Freshservice when you need ITSM processes (incident, problem, change), asset lifecycle management, or a service catalog — features Zendesk lacks or charges extra for. What moves: tickets, users, groups, macros (converted to Freshservice automations), knowledge base, attachments. Timeline: 6-8 weeks. Use Help Desk Migration for bulk transfer, or Zendesk API + Freshservice CSV import for custom mapping. Common split: keep Zendesk for external customer support, move internal IT to Freshservice. They coexist via separate email routing and portals.
When Zendesk works for IT and when it doesn't
Zendesk works for internal IT if:
- You're under 50 employees and need basic ticketing (email-to-ticket, agent assignment, simple SLAs). Zendesk's simplicity gets you operational fast.
- You already use Zendesk for customer support and want to add a separate IT brand/portal without buying another tool. Zendesk supports multi-brand setups.
- Your IT team is lean (1-3 agents) and doesn't need ITSM processes like change management, asset tracking, or a CMDB. If you're just routing tickets and tracking resolution time, Zendesk suffices.
Zendesk doesn't work for IT when:
- You need asset management. Zendesk has no built-in IT asset lifecycle tracking (hardware inventory, software licenses, warranty dates). You'd need a third-party integration or spreadsheet workaround.
- You need change management. Zendesk tickets work for incidents and requests, but change control (CAB approvals, risk assessment, change calendar) isn't supported. Freshservice includes change workflows out of the box.
- You need a service catalog. Zendesk's request forms are basic (email-style forms). Freshservice's service catalog is visual, with conditional logic, approval paths, and provisioning workflows.
- You're managing IT for 100+ employees. At scale, Zendesk's lack of ITSM structure (problem management, CMDB, release management) creates operational debt. You'll spend time building workarounds that Freshservice provides natively.
- Cost becomes prohibitive. Zendesk Suite Professional ($115/agent/month) with add-ons (advanced AI, analytics) rivals Freshservice Pro ($99/agent/month), which includes ITSM features Zendesk doesn't have.
The breaking point:
Most teams outgrow Zendesk for IT when they hire their third or fourth IT agent, or when someone asks "where do we track which employees have which laptops?" If you're answering ITSM questions with spreadsheets and Zendesk custom fields, you need purpose-built ITSM.
What moves cleanly vs what breaks
| Data type | Migration outcome | Notes |
|---|---|---|
| Tickets | ✓ Moves cleanly | Export from Zendesk (API or CSV), import to Freshservice. Ticket fields map: status, priority, requester, assignee, group, tags. Zendesk ticket IDs won't preserve; add old ticket# as Freshservice custom field for reference. |
| Ticket comments | ✓ Moves cleanly | Zendesk public/private comments migrate to Freshservice as notes. Timestamps and user attribution transfer. Formatting (bold, links) transfers if exported as HTML. |
| Attachments | ✓ Moves cleanly | Help Desk Migration tool downloads Zendesk attachments and re-uploads to Freshservice tickets automatically. Manual migration: download via Zendesk API, upload to Freshservice via API. |
| Users & requesters | ✓ Moves cleanly | Export Zendesk users (name, email, role, org), import to Freshservice. If using SSO (Okta, Azure AD), users auto-provision in Freshservice on first login. Passwords don't migrate (SSO or email invite for password reset). |
| Groups | ✓ Moves cleanly | Zendesk groups (agent assignment groups) map to Freshservice groups. Recreate groups manually in Freshservice, assign members. Group memberships can be scripted if you have many groups. |
| Macros | ⚠ Rebuild required | Zendesk macros (canned responses, ticket field updates) don't migrate directly. Export macro definitions as reference, rebuild as Freshservice canned responses or automations. Simple macros (text replies) migrate fast; complex macros (field updates, conditional logic) require manual configuration. |
| Automations & triggers | ⚠ Rebuild required | Zendesk automations (time-based rules) and triggers (event-based rules) must be recreated in Freshservice automation builder. Export Zendesk rules as documentation, rebuild logic in Freshservice. Most common rules (assignment on category, SLA breach alerts) are straightforward. |
| SLAs | ⚠ Rebuild required | Zendesk SLA targets (response time, resolution time) don't migrate. Recreate in Freshservice SLA Management. Business hours, holidays, and SLA targets must be reconfigured. Historical SLA data (met/breached) is preserved in migrated tickets as metadata but won't populate Freshservice SLA reports retroactively. |
| Knowledge base | ✓ Moves cleanly | Export Zendesk Guide articles (HTML), import to Freshservice Knowledge Base via API. Categories, sections, and article visibility (public/internal) must be recreated in Freshservice, then articles assigned to categories. |
| Organizations | ✓ Moves cleanly | Zendesk organizations (customer companies) map to Freshservice companies. Export org data (name, domain, custom fields), import to Freshservice. User-to-org associations migrate with user import. |
| Custom fields | ⚠ Partial | Zendesk custom ticket/user fields must be recreated in Freshservice. Field values migrate with tickets/users if you map fields correctly. Dropdown options, checkbox labels, and field validations require manual setup in Freshservice. |
| Integrations | ✗ Rebuild required | Zendesk integrations (Slack, SSO, email routing, third-party apps) must be disconnected and reconnected to Freshservice. Freshservice supports Slack, Okta, Azure AD, Google Workspace, Microsoft Teams. Other integrations: check Freshservice marketplace or use webhooks/API. |
Migration approach and tools
Recommended: Help Desk Migration
Cloud service (helpdeskm igration.com) that connects Zendesk and Freshservice, maps fields, and transfers tickets, users, attachments, and knowledge base in bulk. Cost: $199-$1,499 based on record count. Timeline: 1-2 days for bulk migration after configuration.
Pros: Fast, handles attachments automatically, no scripting required, includes support. Cons: Doesn't migrate automations/triggers (manual rebuild required).
Alternative: Zendesk API + Freshservice CSV import
Export Zendesk data via API (tickets, users, comments), format as CSV, import to Freshservice. Cost: Free (developer time). Timeline: 1-2 weeks for scripting, testing, and batch imports.
Pros: Full control over data transformation, no third-party cost. Cons: Requires developer to write scripts, handle API pagination, and manage attachments separately.
Phased migration plan (6-8 weeks)
Phase 1: Discovery & Freshservice Setup (Weeks 1-2)
- Audit Zendesk: ticket volume, custom fields, macros in use, active triggers/automations, knowledge base article count.
- Provision Freshservice instance: create agent accounts, configure groups, integrate SSO (Okta, Azure AD).
- Configure Freshservice workflows: incident/request statuses, SLA targets, business hours, agent roles.
- Rebuild service catalog: common request types (password reset, hardware request, software access) with forms and approval paths.
- Document field mapping: Zendesk status → Freshservice status, priority, category, custom fields.
Phase 2: Data Migration & Automation Rebuild (Week 3)
- Configure Help Desk Migration: connect Zendesk + Freshservice, map fields, select data scope (all tickets or last 12 months).
- Run test migration: migrate 100-200 sample tickets, verify data accuracy (ticket fields, comments, attachments, user associations).
- Rebuild Zendesk automations in Freshservice: export Zendesk triggers/automations as reference, configure equivalent Freshservice automation rules.
- Migrate knowledge base: export Zendesk Guide articles (HTML), create Freshservice KB categories, import articles via API or manual copy-paste for small KB.
- Recreate macros: convert Zendesk macros to Freshservice canned responses (common replies, field updates).
Phase 3: UAT & Agent Training (Week 4)
- Test Freshservice workflows: create test tickets, verify assignment rules, SLA timers, escalations, notifications.
- Train IT agents: Freshservice UI walkthrough, ticket management, knowledge base search, asset management (if enabled).
- User acceptance testing: agent team tests ticket creation, updates, canned responses, reporting.
- Fix identified issues: adjust automations, SLA targets, notification templates based on UAT feedback.
Phase 4: Final Migration & Cutover (Week 5)
- Freeze Zendesk: stop new ticket creation 24 hours before cutover (or set Zendesk to read-only).
- Run full migration: migrate all Zendesk tickets, users, attachments to Freshservice. Typical runtime: 4-12 hours for 5k-20k tickets.
- Validate migration: spot-check 50+ tickets, verify open ticket assignments, test knowledge base links.
- Switch email routing: update DNS/mail server to route helpdesk@, it@ emails to Freshservice instead of Zendesk.
- Update self-service portal: replace Zendesk portal link with Freshservice portal on intranet, Slack, employee onboarding docs.
- Announce cutover: email to organization: "IT helpdesk is now at [Freshservice URL]. Old Zendesk tickets are available read-only for 30 days."
Phase 5: Hypercare (Weeks 6-7)
- Monitor ticket flow: check for email routing issues, missed assignments, SLA breaches.
- Agent support: daily check-ins with IT team, answer questions, adjust workflows based on real ticket volume.
- Knowledge base optimization: identify ticket categories without KB articles, publish new solutions.
- Decommission Zendesk (optional): if keeping Zendesk for customer support, disable IT brand/portal and archive IT tickets. If migrating fully, export final Zendesk archive and cancel subscription.
Common pitfalls
1. Not separating customer support from IT support
If you use Zendesk for both external customers and internal IT, clarify the split: keep Zendesk for customer-facing support, migrate only IT tickets to Freshservice. Fix: Filter Zendesk data during migration — export only tickets tagged "IT" or submitted to IT brand/email address.
2. Assuming macros migrate automatically
Zendesk macros (agent shortcuts) are critical for agent productivity. They don't migrate; agents lose muscle memory post-cutover. Fix: Export top 20 most-used macros from Zendesk, recreate as Freshservice canned responses before cutover. Train agents on new shortcuts during UAT.
3. Neglecting knowledge base migration
Teams focus on tickets and forget the knowledge base. Post-cutover, agents can't find documented solutions, ticket volume spikes. Fix: Migrate knowledge base in Week 3, test KB search during UAT. Publish Freshservice KB URL to agents and end users before cutover.
4. Email routing misconfiguration
Cutover day: emails to helpdesk@ still go to Zendesk, or go to Freshservice but don't create tickets. Users get confused, tickets are lost. Fix: Test email routing 48 hours before cutover. Send test emails to helpdesk@, it@, support@ — verify they create tickets in Freshservice and trigger agent notifications.
5. No communication plan
End users show up Monday morning, their Zendesk portal bookmark is dead, and they don't know where to submit tickets. Fix: Email the organization 1 week before cutover: "IT helpdesk is moving to Freshservice on [date]. New portal: [URL]. Bookmark it now."
Pre-migration checklist
Discovery
- Zendesk data audit: ticket volume, custom fields, macros, triggers, KB article count.
- Field mapping documented: Zendesk status → Freshservice status, priority, category.
- Migration tool chosen: Help Desk Migration or custom scripts.
- Cutover date set (avoid month-end, quarter-end, or major releases).
Freshservice configuration
- Freshservice instance provisioned: agents created, groups configured, SSO integrated.
- Workflows configured: incident/request statuses, SLAs tested.
- Service catalog built: request forms, approval workflows.
- Automations recreated: Zendesk triggers → Freshservice automation rules.
- Macros converted: Zendesk macros → Freshservice canned responses.
- Knowledge base categories created, articles imported.
Training & communication
- Agent training completed: Freshservice UI, ticket management, KB search.
- End-user communication sent: new portal URL, cutover date, what's changing.
Migration execution
- Test migration completed: 100-200 tickets migrated, validated.
- Email routing tested: helpdesk@ emails create tickets in Freshservice.
- Final migration window scheduled: Zendesk frozen, full data export started.
Frequently asked questions
How long does a Zendesk to Freshservice migration take?
Plan 6-8 weeks: 1-2 weeks discovery and Freshservice configuration, 1 week data mapping and test migration, 1 week UAT, 1 week final migration and cutover, 1-2 weeks hypercare. Faster than ServiceNow migrations because Zendesk data is simpler (no complex CMDB or workflows).
Will I lose ticket history when migrating from Zendesk?
No. Tickets, comments, and attachments migrate via Zendesk API export and Freshservice import. Help Desk Migration tool handles bulk transfer automatically. Zendesk ticket IDs won't preserve; add old ticket# as a custom field in Freshservice for reference.
Can I keep using Zendesk for customer support and use Freshservice for IT?
Yes, this is the most common split. External customer support stays in Zendesk, internal IT support moves to Freshservice. Route emails: support@ goes to Zendesk, helpdesk@ or it@ goes to Freshservice. Users submit to different portals depending on request type. Both systems coexist; no integration required.
Does Freshservice cost more than Zendesk?
For IT-only use, Freshservice and Zendesk have similar pricing: Zendesk Suite Team $55/agent/month, Freshservice Growth $49/agent/month (annual, as of Oct 2026). Freshservice includes ITSM features (asset management, change management, CMDB) that Zendesk lacks or charges extra for. See our pricing comparison.
What if the migration fails?
Keep Zendesk active (not canceled) for 2-4 weeks post-cutover. If Freshservice has critical issues, revert: switch email routing back to Zendesk, reactivate agent access, communicate rollback to users. Test rollback procedure during UAT so you're not improvising in a crisis.
Should I migrate closed tickets older than 2 years?
No, unless required for compliance/audit. Old closed tickets clutter Freshservice and slow search. Migrate open tickets + closed tickets from the past 12-24 months. Archive older Zendesk tickets as CSV backup. You can always reference old Zendesk data if needed post-migration.
Need help migrating from Zendesk to Freshservice?
We plan and execute ITSM migrations. Bring us your Zendesk audit, your ITSM requirements, and your timeline — we'll handle data migration, workflow configuration, UAT, and cutover.