Skip to content
Get a quote

Freshservice to Zendesk migration

We migrate Tickets, Agents, Requesters, Assets, Changes, and Problems from Freshservice into Zendesk with parent-record dependency resolution, SLA policy reconstruction, and every API rate-limit constraint on both platforms accounted for before any data moves.

Short answer

FlitStack AI migrates tickets, agents, end users, organizations and configuration items from Freshservice to Zendesk, 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: 3-5 weeks.

By

Source Freshservice
DestinationZendesk
TicketAgentEnd UserOrganizationConfiguration Item
Mapped field by field · sample run · one-click rollback

What moves from Freshservice to Zendesk?

Moving from Freshservice to Zendesk is an ITSM-to-support-desk structural migration.

Read the full summary

Freshservice organizes work around ITIL constructs — Changes, Problems, Releases, and a built-in CMDB — that require deliberate re-mapping when landing in Zendesk, which was designed for customer support workflows rather than internal IT service management. We handle the object-level mapping in dependency order: Requesters (Users in Zendesk) before Tickets, Agents before group assignments, Assets as configuration items in Zendesk's asset inventory, and Changes and Problems as mapped Ticket records with custom field tags that preserve the original Freshservice ITIL classification. We do not migrate Freshservice automations, SLA escalation rules, or Service Catalog items as working code; we deliver a written inventory of every active automation and escalation with the recommended Zendesk equivalent for the customer's admin to rebuild. Custom Objects from Forest and Enterprise plans cannot define native associations in Freshservice and are stored in Zendesk as tagged text fields with a documented schema gap in the migration report.

1:1

Ticket → Ticket

Freshservice Tickets map directly to Zendesk Tickets with all standard fields (subject, description, status, priority, type, group, agent) preserved via the Zendesk tickets API.

How it maps

Freshservice's agent and group assignments map to Zendesk's assignee_id and group_id using our pre-built lookup tables. Custom ticket fields migrate as Zendesk ticket fields with equivalent types (text, dropdown, checkbox, date). Conversation threads (public replies and internal notes) migrate as Zendesk comments with the public/private flag preserved.

1:1

Agent → Agent (User with agent role)

Freshservice Agents map to Zendesk end-users with agent roles.

How it maps

We extract agent records by email, map the Freshservice role (Agent, Service Manager, Full Administrator) to the nearest Zendesk role (agent, admin), and resolve group memberships to Zendesk group membership. Agents without a matching Zendesk user account enter a reconciliation queue for the customer's Zendesk admin to provision before ticket import begins.

1:1

Requester → End User

Freshservice Requesters map to Zendesk end-users who submit tickets.

How it maps

The Freshservice requester contact model (name, email, primary phone, organization) maps directly to Zendesk User fields. Requester organization membership in Freshservice maps to Zendesk Organization membership. Requesters are migrated before tickets so that the requester_id reference is satisfied at ticket insert time.

1:1

Organization → Organization

Freshservice Organizations map to Zendesk Organizations.

How it maps

Freshservice's domain-based auto-grouping logic is translated to Zendesk organization membership rules. Organization custom fields migrate as Zendesk organization fields. We use the organization name as the dedupe key during import to avoid creating duplicate organizations for the same entity.

1:1

Asset → Configuration Item (via Asset custom fields or Zendesk Asset Management on Enterprise)

Freshservice Assets (hardware, software, network items tracked in the CMDB) migrate to Zendesk as tagged ticket fields or as records in Zendesk's separate Asset Management workspace (available on Enterprise Suite).

How it maps

Freshservice asset type, serial number, vendor, and CI relationships map to Zendesk custom asset fields. Large CMDB hierarchies with parent-child relationships are stored as text fields on the related Zendesk ticket with a flat export for the customer's asset management team to reconstruct post-migration.

1:N split

Change → Ticket (tagged as Change)

Freshservice Changes track planned IT environment modifications with risk level, approval workflow, and associated CIs.

How it maps

Zendesk has no native ITIL Change object, so we map Changes to Zendesk Tickets with a custom field 'fs_change_type' capturing the original Freshservice change type (Normal, Standard, Emergency) and 'fs_risk_level' preserving the risk assessment. The approval status migrates as a dropdown field. Customers who need formal Change management post-migration use Zendesk's Change Management product as a separate tier.

What moves13 objects
FreshserviceZendesk
  • TicketTicket1:1
  • AgentAgent1:1
  • RequesterEnd User1:1
  • OrganizationOrganization1:1
  • AssetConfiguration Item1:1
  • ChangeTicketsplit

+ 7 more in the mapping below

How Freshservice and Zendesk 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.

DimensionFreshserviceZendesk
Platform focusITSM-first with ITIL modules (Changes, Problems, Releases, CMDB) built inCustomer support and omnichannel service with optional ITSM add-on
Asset managementNative CMDB with automated network and endpoint discovery on Growth and aboveAsset tracking available as Zendesk Explore dashboards or a separate asset management workspace on Enterprise Suite
Custom objectsCustom Objects on Forest and Enterprise only; no associations to native objectsNo native custom object equivalent; custom fields and tags handle extensibility
Pricing modelAgent-based licensing with free requesters; Freddy AI as a paid add-onPer-agent pricing with omnichannel and advanced AI as paid add-ons; starts at Suite Team tier
SLA policiesNative SLA management on Starter and above with calendar-based breach calculationSLA policies available on Support Team and above; managed per ticket field and business hours
Change and problem managementNative Change and Problem modules with risk assessment and approval workflowsNo native Change or Problem ITIL objects; modeled as tagged ticket types or separate Zendesk products
Service catalogService catalog with multi-step request forms on Growth and aboveNo native service catalog; Request Management is a separate product tier

What to watch for in a Freshservice to Zendesk migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Zendesk has no native Change or Problem ITIL objects

Freshservice organizes IT work around ITIL modules — Changes, Problems, Releases — that are core to the platform.

How we handle it

Zendesk and Suite Team/Growth do not include native Change or Problem management objects. We map Changes to Zendesk Tickets with custom fields preserving the original Freshservice change type and risk level, and Problems as tagged tickets with related incident IDs stored as text references. Customers who need formal Change management after migration must separately license Zendesk's Change Management product. We document every Change and Problem record in the migration inventory so the customer's admin understands the gap before go-live.

high

Freshservice API rate limits must be raised before migration

Freshservice applies per-minute API rate limits that scale by plan: Growth ~200/min, Pro ~400/min, Enterprise ~700/min.

How we handle it

During a large migration, these limits become a bottleneck. We request elevated limits via the Freshservice migration partner process before migration begins. If we exceed the limit, the API returns 429 responses and we back off and retry with exponential delay. Failing to request the limit increase upfront is the most common cause of timeline overruns on this migration pair. We coordinate with the customer's Freshservice admin to submit the rate-limit increase request at least two weeks before the migration window.

medium

Custom Objects cannot define associations to native Freshservice objects

Custom Objects in Freshservice (Forest and Enterprise plans only) explicitly do not support creating relationships to native objects like Tickets, Assets, or Changes.

How we handle it

When migrating from Freshservice Forest or Enterprise with active Custom Objects that reference tickets or assets, we store the related record ID as a text field rather than a native association, and we document this gap clearly in the migration report. Zendesk has no custom object equivalent, so the association gap persists at the destination. The customer should assess during scoping whether those custom object records need to be restructured as Zendesk ticket custom fields or exported to a separate database.

medium

Zendesk's /imports endpoint requires users before tickets

Zendesk's bulk import endpoints require that requester and agent User records exist before ticket records can be created and associated.

How we handle it

A common migration failure is attempting to import tickets before all users are loaded, which results in orphaned tickets with no assignee or requester. We sequence the migration strictly: Users and Organizations first, then Tickets with the user IDs resolved, then Activity history. For Freshservice migrations with large agent and requester bases (over 5,000 users), this sequencing extends the migration timeline but is non-negotiable for data integrity.

low

Attachment re-hosting and inline image rewriting

Freshservice ticket attachments and inline images are hosted on Freshservice's file servers and referenced by Freshservice-specific URLs.

How we handle it

When migrating to Zendesk, these attachments must be downloaded from Freshservice, re-uploaded to Zendesk's attachments API, and the ticket comment content must be rewritten to replace Freshservice CDN URLs with Zendesk asset URLs. Files exceeding Zendesk's 25 MB per-attachment limit are flagged and stored as external links in a custom ticket field. This re-hosting step adds processing time proportional to total attachment volume.

How the migration runs

  1. Discovery and scoping

    We audit the source Freshservice instance across plan tier (Starter/Growth/Pro/Enterprise), active agent count, total requester count, ticket volume and age distribution, asset inventory size, and the presence of Forest-tier or Enterprise-tier Custom Objects.

    What this step covers

    We inventory active Freshservice automations, SLA policies, escalation rules, and Service Catalog items. We assess the Zendesk destination plan tier (Suite Team/Growth/Professional/Enterprise) to confirm which destination features are available. The discovery output is a written migration scope, a pair-specific object map, and a migration sequence plan that accounts for Freshservice API rate limits on the source side and Zendesk's /imports user-first requirement on the destination side.

  2. Field and schema mapping

    We document the mapping between Freshservice field names and Zendesk field equivalents, including custom ticket fields, user fields, and organization fields.

    What this step covers

    We identify Freshservice Change, Problem, and Release records that require custom field reconstruction in Zendesk and define the target custom field schema. We map Freshservice SLA policy assignments to Zendesk SLA policies and flag any SLA calendar configuration that must be set up in Zendesk before migration. We confirm the custom field strategy for Freshservice Custom Objects that have no native Zendesk equivalent.

  3. Test migration into a Zendesk sandbox or staging account

    We run a limited migration using a recent data sample (typically the last 90 days of tickets plus all active agents and requesters) into a Zendesk staging environment.

    What this step covers

    We validate field mappings, user associations, ticket thread integrity, and attachment re-hosting. The customer reconciles a random sample of 25-50 migrated records against the Freshservice source. Any mapping corrections are applied to the migration scripts before production migration begins. This step is the last opportunity to catch data model mismatches without affecting live systems.

  4. User and organization migration

    We migrate Freshservice Agents and Requesters to Zendesk Users in dependency order: organizations first (to satisfy the organization_id on users), then agents, then requesters.

    What this step covers

    We resolve Freshservice group memberships to Zendesk group memberships. Agents without matching Zendesk user accounts are flagged in a reconciliation queue for the customer's Zendesk admin to provision. Migration cannot proceed to tickets until the user migration is complete and validated.

  5. Ticket migration with conversation preservation

    We migrate Freshservice Tickets to Zendesk Tickets using the Zendesk tickets or tickets/import API, with requester_id and assignee_id resolved from the user mapping completed in the previous step.

    What this step covers

    Conversation threads (public replies and internal notes) migrate as Zendesk comments with the public/private flag preserved. Freshservice Change, Problem, and Release records migrate as tagged Zendesk tickets with custom fields preserving the original ITIL classification. SLA assignments are set at the ticket level during import. Attachments are re-hosted from Freshservice CDN URLs to Zendesk's attachments API, with inline image URLs rewritten in the comment body.

  6. Delta migration and cutover

    We freeze Freshservice write access during the cutover window, run a final delta migration of any records created or modified since the bulk migration began, then enable Zendesk as the system of record.

    What this step covers

    We deliver a written inventory of all Freshservice automations, SLA escalation rules, and Service Catalog items with recommended Zendesk equivalents for the customer's admin to rebuild. We support a one-week hypercare window where we resolve any reconciliation issues raised by the support team. We do not rebuild Freshservice automations or SLA escalation rules as Zendesk triggers or macros within the migration scope.

Freshservice Zendesk
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · ZendeskRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
7-12 weeksLarge or heavily customised accounts

A quote scales with ticket volume, asset count, and whether the customer uses Freshservice Forest or Enterprise Custom Objects that require re-modeling in Zendesk. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Freshservice to Zendesk →

Why teams move from Freshservice to Zendesk

  • ITSM licensing cost at scale drives teams to Zendesk's per-agent model. Freshservice Forest and Enterprise pricing ($119 and ~$129 per agent per month) plus the Freddy AI paid add-on pushes the monthly cost above what Zendesk Suite Team or Growth delivers at a lower per-seat rate for teams that primarily need ticket management and reporting without the full ITIL stack. Reddit reviewers comparing the two platforms cite the pricing delta as the primary driver when their ITSM requirements are lighter than what Freshservice's modules enforce.
  • Zendesk's omnichannel support ecosystem is broader than Freshservice's integration marketplace. Reviewers who moved to Zendesk cite access to over 1,000 apps in the Zendesk Marketplace and native channel integrations (WhatsApp, Facebook Messenger, Twitter/X, voice, chat) as a reason for switching, particularly for organizations supporting external customers across multiple channels rather than internal IT requesters. Freshservice's integrations are solid for ITSM-native tools but thinner for CX channels.
  • Dashboard performance under large ticket volumes pushes IT teams toward Zendesk. Multiple G2 and Capterra reviewers of Freshservice note that dashboard load times degrade when handling tens of thousands of tickets, requiring BI tool exports for meaningful cross-ticket views. Zendesk Explore provides built-in analytics across tickets, CSAT, and agent performance that some teams find more responsive at scale without requiring a separate reporting platform.
  • Freddy AI became a paid add-on on all Freshservice tiers, which felt like a feature removal for teams who expected it included. This pricing change surfaces consistently in negative Freshservice reviews as a bait-and-switch perception. Teams evaluating Zendesk Advanced AI as an alternative find the pricing comparison more transparent on Zendesk's add-on model, even though both platforms charge separately for AI capabilities.
  • Zendesk's support for multi-brand and multi-language customer-facing portals is more mature than Freshservice's equivalent. Organizations supporting multiple product lines or subsidiaries under a single account find Zendesk's brand settings and help center localization more granular out of the box. Freshservice's portal capabilities serve internal IT requesters well but offer less flexibility for external customer-facing deployments.

Questions, answered

Freshservice to Zendesk migration questions

How long does a Freshservice to Zendesk migration take?

Most Freshservice to Zendesk migrations land between three and five weeks for accounts under 30,000 tickets, 500 assets, and no Forest-tier Custom Objects. Migrations with large engagement histories (over 200,000 comment records), multi-level CMDB asset hierarchies, Change and Problem records requiring custom field reconstruction, or Forest-tier Custom Objects requiring schema redesign move to seven to twelve weeks. The primary timeline drivers are Freshservice API rate limits (which throttle export throughput), the volume of attachments requiring re-hosting, and the size of the user and organization dataset that must land before ticket import begins.

Do Freshservice automations, SLA escalation rules, and Service Catalog items migrate to Zendesk?

No. Freshservice automations, escalation rules, and Service Catalog items are workflow objects that do not migrate as working code to Zendesk because the underlying rule engines are structurally different. Zendesk uses macros, triggers, and SLA policies in a different configuration model from Freshservice's workflow automation builder. We deliver a written inventory of every active Freshservice automation and escalation rule with its trigger conditions, actions, and a recommended Zendesk equivalent (trigger, macro, or SLA policy). The customer's Zendesk admin rebuilds them post-migration. Service Catalog items do not migrate; Zendesk's Request Management is a separate product tier.

What happens to Freshservice Changes and Problems during migration?

Zendesk has no native ITIL Change or Problem management objects. We map Freshservice Changes to Zendesk Tickets with custom fields preserving the original change type (Normal, Standard, Emergency) and risk level. Problems map to Zendesk Tickets with a custom field referencing related incident ticket IDs. The migration report lists every Change and Problem record with its original Freshservice ID, type, and status so the customer's Zendesk admin can assess whether Zendesk's Change Management product tier (a separate license) is needed or whether tagged tickets provide sufficient audit trail for their use case.

Can Freshservice Custom Objects be migrated to Zendesk?

Freshservice Custom Objects (Forest and Enterprise plans) store structured data beyond standard fields but cannot define native associations to Tickets, Assets, or Changes in Freshservice itself. Zendesk has no custom object data model, so we migrate Custom Object records as Zendesk ticket custom fields with the original Freshservice record ID stored as a text reference. The association gap — where a Custom Object record references a Ticket or Asset — is stored as a text field rather than a native lookup, and this gap is documented in the migration report. If the customer requires a more relational structure post-migration, a separate database or a Zendesk partner-built app would be needed.

Do historical ticket comments and attachments migrate completely?

Yes. We migrate Freshservice ticket conversation threads as Zendesk comments with the public/private flag preserved. HTML content is sanitized during import. Inline images are downloaded from Freshservice's CDN and re-uploaded to Zendesk's attachments API, with URLs rewritten in the comment body so images display correctly in Zendesk. Files exceeding Zendesk's 25 MB attachment limit are flagged and a link to the original file or an archive location is stored in a custom ticket field. Total attachment volume is the primary driver of migration time beyond the ticket count itself.

What happens to Freshservice Freddy AI data after migration?

Freddy AI in Freshservice generates triage suggestions, automated responses, and resolution predictions. Zendesk has its own Advanced AI product with a different model and training data. Freddy AI outputs are not portable to Zendesk Advanced AI because the AI-generated suggestions are tied to Freshservice's conversation context and Freddy's proprietary model. We do not migrate Freddy AI artifacts. Customers who rely on Freddy AI for triage or automation should evaluate Zendesk Advanced AI ($50/agent/month add-on) during the migration planning phase. The customer's existing Freddy AI configuration (what triggers it, what actions it takes) is documented in the migration inventory for reference when rebuilding automation logic in Zendesk.

How do we handle Freshservice's asset discovery data in Zendesk?

Freshservice's automated network and endpoint discovery populates the CMDB with hardware, software, and network configuration items that are associated with tickets and users. Zendesk's asset management (available on Enterprise Suite) provides an asset inventory but does not include automated discovery. We migrate Freshservice asset records as Zendesk assets or as tagged custom fields on related tickets, depending on the destination Zendesk plan tier. The asset-to-ticket linkage is preserved as a custom field reference. Customers relying on automated discovery should plan to run a fresh discovery scan in Zendesk's asset management workspace post-migration to rebuild the real-time CMDB.

Get a quote

Moving from Freshservice to Zendesk?

Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.

Get a quote