Zendesk to Freshservice Migration 2026: Tickets into an ITSM Desk
Plan a Zendesk to Freshservice migration for IT tickets: map records to ITIL types, check export and import limits, rebuild SLAs. Use the checklist.
Published Updated 13 min read

On this page
A Zendesk to Freshservice migration moves tickets, comments, users, organizations and Guide articles into Freshservice, but each Zendesk ticket has to land as the right ITIL record: an incident, a service request or a problem. Triggers, automations, macros and SLA policies do not move. You rebuild them in Freshservice.
This guide is for IT teams moving internal IT support off Zendesk Support or Zendesk for Employee Service. It maps record types, sets export limits beside import limits, and ends with a cutover checklist.
Why IT teams move from Zendesk to Freshservice
The usual trigger is that internal IT support outgrows a single ticket queue. Zendesk models all IT work as one ticket object, typed question, incident, problem or task (Zendesk Tickets API docs, as of 26 Oct 2026).
Freshservice separates the record types and gates them by plan: incident and knowledge management on Starter at $19, service catalog and SLA management on Growth at $49, and problem, change and release management on Pro at $99, per agent per month billed annually (Freshworks pricing page, as of 26 Oct 2026). Our Freshservice pricing guide and Freshservice explainer go deeper. In a press release dated 29 Jul 2026, Freshworks said it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management Platforms.
Staying is a real option. Zendesk IT asset management became generally available on 11 May 2026, with up to 500 asset records per account on Suite Growth and above (Zendesk announcement, as of 26 Oct 2026). Employee Service costs $29, $59 and $99 per agent per month paid yearly for Suite Team, Growth and Professional, with SLAs and service catalog from Growth (Zendesk pricing page, as of 26 Oct 2026). If Jira Service Management is the other contender, see our Zendesk to Jira migration guide.
The verdict: move when you need problem, change and asset records working together; stay if a ticket queue with a service catalog covers your IT work.
What moves, what gets rebuilt, what's at risk
Data moves. Configuration is rebuilt. Running SLA timers never move, because the target clock starts when the record is created.
| Moves (data) | Rebuilt in Freshservice (configuration) | At risk (needs a plan) |
|---|---|---|
| Tickets, as incidents, service requests or problems | Triggers and automations, as Workflow Automator workflows | Running SLA timers and breach history |
| Public comments and internal notes | Macros, as canned responses | Original created dates and comment authors |
| End users, agents and organizations, as requesters, agents and departments | SLA policies and business hours | Private attachments on short-lived URLs |
| Groups, tags and custom field values | Views, ticket forms and field conditions | Archived tickets |
| Attachments | Statuses and the priority matrix | Side conversations and CSAT responses |
| Guide categories, sections and articles | Service catalog items and approvals | Problem-to-incident links |
Zendesk automations "run every hour on all your tickets that are not closed" (Zendesk help center, as of 26 Oct 2026); automations and triggers both become event-based or scheduled workflows in Freshservice. Zendesk SLA policies measure seven metrics, while Freshservice sets SLA targets by priority (Zendesk and Freshservice help centers, as of 26 Oct 2026). So SLA policies are redesigned, not mapped.
Zendesk to Freshservice field mapping
Record type, status and priority matter most, because they drive SLAs and reporting.
Ticket types to ITIL record types
Freshservice's ticket API supports only the incident type and lists a separate Create a Service Request endpoint (Freshservice API docs, as of 26 Oct 2026). Problems have their own endpoints and need Pro.
A workable rule: incidents and most questions become incidents, Employee Service catalog requests become service requests, and problem tickets become problems, with each problem_id rebuilt as an association. Decide tasks by group or form.
Statuses, priorities and people
Freshservice lets you toggle the SLA timer for Pending and custom statuses (Freshservice statuses article, as of 26 Oct 2026), so map Zendesk on-hold to a custom status with the timer off if hold time should not count. Its priority matrix article defines "Priority = Impact x Urgency" for incidents and says requesters cannot pick a priority on a service request (Freshservice priority matrix article, modified 20 Jun 2024, as of 26 Oct 2026). Decide whether imported priorities should survive recalculation.
Freshworks' Zendesk guide maps organizations to departments. The catch: for a user with several organization memberships, Zendesk's organization_id returns only the default one (Zendesk Users API docs, as of 26 Oct 2026). Freshservice imports requesters from CSV only, with locations created first.
Notes, attachments and knowledge articles
A Zendesk comment with public: false is an internal note. Freshservice private notes are "only visible to agents logged in to your service desk", while public notes show to the requester on the portal (Freshservice support articles, as of 26 Oct 2026). Map public: false to a private note, or IT-only discussion reaches requesters.
Zendesk accepts inbound attachments up to 50 MB per file, while Freshservice caps a ticket's attachments at 40 MB in total (Zendesk help center; Freshservice API docs, as of 26 Oct 2026).
For knowledge, Zendesk has "no CSV export button for Knowledge content", so Guide exports run through the Help Center API (Zendesk help center, as of 26 Oct 2026). Freshworks maps Guide sections to Freshservice folders, which can be visible to all users, all agents or chosen departments. Re-host inline images, load translations after setting up secondary languages, then rewrite links between articles.
| Zendesk | Freshservice | Decision |
|---|---|---|
| Ticket type incident | Incident | Default target |
| Ticket type question or task | Incident or service request | Classify by group, form or tag before load |
| Ticket type problem + problem_id | Problem linked to incidents | Needs Pro plan or above |
| Status new, open | Open (API value 2) | Direct |
| Status pending, on-hold | Pending (3) or a custom status | Set SLA timer per status |
| Status solved, closed | Resolved (4), Closed (5) | Direct |
| Priority urgent, high, normal, low | Urgent (4), High (3), Medium (2), Low (1) | Check against the priority matrix |
| Public comment / internal note | Public note or reply / private note | Map visibility |
Values from the Zendesk Tickets API docs and Freshservice API docs, as of 26 Oct 2026.
Export from Zendesk, import into Freshservice
Zendesk has four export routes, compared step by step in how to export tickets from Zendesk; Freshservice has no documented customer import tool.
Export from Zendesk
| Method | Availability | What it holds | Limits |
|---|---|---|---|
| Incremental export API | All plans | Tickets, ticket events (full comments only with the comment_events sideload), users, organizations | Up to 1,000 items per page; 10 requests/min, 30 with High Volume |
| JSON export | Suite Growth and above, Support Professional and Enterprise; off by default | Tickets (with comments), users or organizations, as newline-delimited JSON | Comments omitted for tickets over 1 MB; 31-day increments above 1 million tickets |
| CSV export | Same plans | Ticket fields, except multi-line text, multi-select and custom date fields | No comments, descriptions or deleted tickets |
| XML export | Same plans | Account settings, groups, organizations, tickets with comments, users; no custom ticket, user or organization fields | 500 MB, about 200,000 tickets; unavailable above 200,000 |
Source: Zendesk data export article, incremental exports docs and rate limits docs, as of 4 Nov 2026.
Zendesk's export article does not list attachment files in any of the three file exports, and it notes that AI agent tickets cannot be exported. For a full API export, pull each object from its own endpoint (Zendesk developer docs, as of 4 Nov 2026):
GET /api/v2/incremental/tickets/cursor?start_time={unix_time}
GET /api/v2/incremental/ticket_events?start_time={unix_time}&include=comment_events
GET /api/v2/tickets/{ticket_id}/comments
GET /api/v2/tickets/{ticket_id}/audits
GET /api/v2/tickets/{ticket_id}/metrics
GET /api/v2/incremental/users/cursor?start_time={unix_time}
GET /api/v2/incremental/organizations?start_time={unix_time}
GET /api/v2/organization_memberships
GET /api/v2/attachments/{attachment_id}
The incremental endpoints are admin-only. List Comments returns up to 100 comments per page, and each attachment comes back with a content_url; add include_inline_images=true to list inline images too (Zendesk Ticket Comments API). Zendesk warns that a content_url may point to an externally hosted file, so check the domain before sending credentials (Working with url properties). Custom field definitions come from the List Ticket Fields, List User Fields and List Organization Fields endpoints.
Archived tickets are the first trap. In most cases Zendesk archives a ticket 120 days after it closes, and sooner on accounts with extremely high ticket volumes. Archived tickets drop out of views and rules, but the incremental export and the data exports still return them. So do most ticket API endpoints; the exceptions are List Tickets, Count Tickets, Count Ticket Comments, List Ticket Metrics, List Ticket Audits, Bookmarks and Ticket Skips (Zendesk archiving article, as of 4 Nov 2026). Don't reconcile with the count endpoints, and pull SLA metrics and audits per ticket. Deleted tickets appear in the incremental stream unless you set exclude_deleted, and Zendesk scrubs their user-provided data 30 days after deletion (Using the Incremental Exports API, as of 4 Nov 2026). Keep Zendesk live until sign-off: reactivation after cancellation is possible only within 90 days (Zendesk help center, as of 26 Oct 2026).
Import into Freshservice
Freshservice's Data Migration help folder holds two articles, both for migration partners (Freshservice support site, as of 26 Oct 2026). For customers, the only public guidance is a Freshservice Community Manager reply in a thread from 19 Nov 2021: support "would have to perform a CSV migration from our end". The other route is scripting the public API.
The public API allows 100, 200, 400 and 500 calls per minute on Starter, Growth, Pro and Enterprise, and Create Ticket has its own sub-limit of 50, 80, 140 or 160 (Freshservice API docs, as of 26 Oct 2026). A partner migration token raises this to 700 per minute for an approved window. The partner Bulk APIs take 50 tickets or notes per request at 10 requests per minute per bulk endpoint, still marked "[To be confirmed post load testing]"; errors "cannot be retried automatically", and attachments must be public URLs (Freshservice Bulk API article, modified 24 Nov 2025, as of 26 Oct 2026).
The Bulk API suppresses assignment, CC and association emails, but Slack, Teams, business rules and workflows are not muted, so switch them off first.
What drives the effort
Ticket count alone does not set the effort. Comment volume does: each Zendesk comment after the first becomes its own Freshservice note and write call, so short password resets and long change discussions need very different API budgets.
The import route decides who owns the risk. A scripted import keeps control in-house, but your team owns retries and rate limits; the Bulk API writes more per call, but failed records must be resubmitted.
Zendesk to Freshservice migration plan in phases
Run the move as a controlled change, with a go/no-go per phase.
- Discover. Count tickets, comments and attachments by type, status, group and year, archived included. Decide how much history is in scope; see our guide to migrating ticket history.
- Map. Fix record type, status and priority rules and the rebuild list, then create fields, groups, departments and locations.
- Test migration. Load a sample with the largest tickets and private attachments, and check note visibility as a requester. Our test migration checklist lists what to sign off.
- Cutover with delta sync. Load history before the freeze window, then sync tickets changed since the last run, with workflows and notifications off.
- Reconcile. Compare counts by record type, status and group, then sample notes, attachments and links. Freshservice's standard ticket export excludes conversations and internal notes and caps each export at 10,000 tickets (Freshservice exporting tickets article, modified 13 Jun 2026), so check notes through the API.
- Hypercare. Keep Zendesk read-only and watch SLA breaches and routing. Freshworks' Bulk API article warns that search and analytics "will not update in real time during the migration".
Pair-specific failure points
- Everything lands as an incident. It is the easy API path, and it breaks request reporting.
- Private attachments expire. On Zendesk accounts created on or after 5 Dec 2024, or using messaging, private attachment URLs are short-lived (Zendesk help center, as of 26 Oct 2026). The Bulk API needs public URLs, so stage files first.
- Oversized files fail quietly. Bulk API attachments over 40 MB per entity are rejected, but the ticket or note is still created (Freshservice Bulk API article, as of 26 Oct 2026).
- Requesters get flooded. Workflows keep running during a bulk load unless you switch them off.
Zendesk to Freshservice migration checklist
- Confirm the Freshservice plan covers problem, change and SLA.
- Ask Zendesk to enable data exports, and inventory tickets, comments and attachments, archived included.
- Write record type rules for questions, tasks, catalog requests and problems.
- Agree status, priority and SLA timer mapping.
- Create locations, departments, groups and custom fields, then import requesters and agents by CSV.
- Add fields for the Zendesk ID, original created date and SLA metrics.
- Stage private attachments before their URLs expire.
- Export Guide articles, images and translations.
- Turn off workflows, business rules and notifications for the load window.
- Run a test migration, then reconcile counts and note visibility.
- Cut over with delta sync, and keep Zendesk active until sign-off.
- Rebuild triggers, automations, macros, views and SLA policies.
Facts checked November 4, 2026 from Freshservice API docs, Freshservice support, Freshservice pricing, Zendesk developer docs and Zendesk help center. No vendor paid for this article. How we research
FAQ
Can I import Zendesk tickets into Freshservice myself?
Not through a documented self-service importer; Freshservice's Data Migration help folder covers only partner processes. You can script the public API, which allows 100 to 500 calls per minute by plan (Freshservice API docs, as of 26 Oct 2026), or ask Freshworks about current options.
How long does a Zendesk to Freshservice migration take?
There is no neutral public benchmark. Freshworks, which sells the destination platform, says small organizations "might complete migration in days, while large enterprises may require weeks" (Freshworks Zendesk guide, as of 26 Oct 2026). Duration depends on ticket, comment and attachment volume, rate limits on both sides, history in scope and the number of test cycles.
Do Zendesk triggers, macros and SLA policies migrate to Freshservice?
No. They are configuration, not data. Freshworks' own guide lists SLA policies, business rules, triggers and automation rules as manual reconfiguration. Triggers and automations become Workflow Automator workflows, macros become canned responses, and SLA policies are rebuilt per priority. Running SLA timers do not carry over.
Will Zendesk ticket dates and authors be kept?
Not automatically. Freshservice's API describes created_at only as "Ticket creation timestamp", and the Bulk API article does not address original timestamps, so keep the Zendesk ID and created date in custom fields. Bulk API notes carry a user_id, so create comment authors as users before loading notes.
Can we keep using Zendesk during the migration?
Yes. Load history first, delta-sync tickets changed since the last run, and freeze Zendesk only for the final cutover window. Keep the account active until reconciliation is signed off, because Zendesk allows reactivation only within 90 days of cancellation (Zendesk help center, as of 26 Oct 2026).
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. GARTNER and MAGIC QUADRANT are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


