Skip to content
Get a quote

Zendesk to Freshdesk migration

We migrate Tickets, Users, Organizations, and Knowledge Base articles from Zendesk into Freshdesk with Organizations mapped to Companies, Help Center structure preserved through the Freshdesk content API, and every custom field created in Freshdesk before import begins.

Short answer

FlitStack AI migrates companies, contacts, agents, tickets and product or manual recreations from Zendesk to Freshdesk, 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: 1-2 weeks.

By

Source Zendesk
DestinationFreshdesk
CompanyContactAgentTicketProduct or manual recreation
Mapped field by field · sample run · one-click rollback

What moves from Zendesk to Freshdesk?

Moving from Zendesk to Freshdesk is a data consolidation that requires careful object mapping and schema pre-creation.

Read the full summary

Zendesk Organizations map to Freshdesk Companies, Zendesk Users to Freshdesk Contacts and Agents, and Zendesk Brands require either a Product mapping or manual recreation in Freshdesk's multi-brand tools. We pull ticket histories directly from Zendesk's API on any plan tier, bypassing the plan-gated export UI, and reconstruct Help Center articles with section hierarchy in Freshdesk's Knowledge Base. Triggers, Automations, SLA Policies, and Macros do not migrate as configuration code; we deliver a written inventory of each rule and its recommended Freshdesk automation equivalent for the customer's admin to rebuild. The Knowledge Base migration requires pre-creating categories and sections in Freshdesk before article import begins to avoid duplication issues reported by other migrators.

1:1

Organization → Company

Zendesk Organizations map to Freshdesk Companies.

How it maps

The organization domain_names array maps to Freshdesk Company domains for auto-association. organization_fields map to Freshdesk Company custom fields, which must be pre-created in Freshdesk before migration. We preserve the original Zendesk organization id as a read-only external ID field so that retries are idempotent and cross-validation during reconciliation is possible.

1:1

User (End-User / Requester) → Contact

Zendesk end-users (requesters) map to Freshdesk Contacts.

How it maps

Email is the dedupe key. We import name, email, phone, custom fields, language, and timezone. Role assignment (agent vs. end-user) is handled by mapping agents to Freshdesk Agents and requesters to Contacts. Any Zendesk user with agent role becomes a Freshdesk agent record during the parallel agent migration step.

1:1

Agent → Agent

Zendesk agents map to Freshdesk agents.

How it maps

We extract agent profiles including group membership and role (admin, agent, light agent). Roles map by function: Zendesk admin to Freshdesk Admin, Zendesk agent to Freshdesk Agent. Group memberships transfer to Freshdesk Groups. Agent status (active/inactive/deleted) maps to Freshdesk availability status with a reconciliation queue for any deleted source agents whose tickets need reassignment.

1:1

Ticket → Ticket

Zendesk Tickets map to Freshdesk Tickets.

How it maps

Every ticket's requester_id resolves to a Freshdesk Contact, assignee_id to a Freshdesk Agent, group_id to a Freshdesk Group, status to Freshdesk status, and priority to Freshdesk priority. Custom fields on tickets map to pre-created Freshdesk ticket custom fields. The full comment thread migrates with public/private visibility preserved as Freshdesk inbound/outbound notes. Attachments download from Zendesk and re-upload to Freshdesk with filenames and MIME types intact.

lookup

Brand → Product or manual recreation

Zendesk Brands (multi-brand routing, separate email addresses, and independent Help Centers) have no direct Freshdesk equivalent.

How it maps

Freshdesk Products can serve as a brand proxy if the team uses Product-based ticket routing, but multi-brand email routing requires recreating mailbox aliases in Freshdesk's Email Settings manually. We flag Brand as a manual-configuration item in the migration scope and document the source brand email addresses for the customer's admin to reconfigure in Freshdesk before cutover.

mapping

View → Custom View

Zendesk Views (saved ticket filters with conditions, columns, and sort order) map to Freshdesk Custom Views.

How it maps

The filter conditions transfer as Freshdesk filter criteria. We export view definitions as structured data and recreate them in Freshdesk. Column selection and sort order transfer where the target system supports equivalent column configuration. If a Zendesk view references a field that has no Freshdesk equivalent, we substitute the closest match and flag it for admin review.

What moves12 objects
ZendeskFreshdesk
  • OrganizationCompany1:1
  • UserContact1:1
  • AgentAgent1:1
  • TicketTicket1:1
  • BrandProduct or manual recreationtransformed
  • ViewCustom Viewtransformed

+ 6 more in the mapping below

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

DimensionZendeskFreshdesk
Organization modelOrganizations with domain names, custom fields, and multi-user membershipCompanies with domain associations and contact relationships
Multi-brand supportUp to 300 brands with independent routing and email on EnterpriseProducts used for brand separation; no native multi-brand equivalent
Help Center structureCategories and Sections within multiple Help Centers (Growth+)Categories and Articles within a single or multiple portals
Automation primitivesTriggers (event-driven), Automations (time-based), Macros, and SLA PoliciesScenario Automations combining event, time, and conditions; canned responses; SLA policies
Custom field scopeTicket, User, Organization, and Brand custom fields across all tiersTicket, Contact, and Company custom fields; Product custom fields on higher tiers
AI pricing model$50/agent/month add-on for all agents; resolution-based AI Agent pricingFreddy AI Copilot at $29/agent/month for select agents; session-based AI Agent pricing
Per-agent cost$49-$169/agent/month depending on tier, with aggressive feature gating$29-$79/agent/month with more features included at lower tiers

What to watch for in a Zendesk to Freshdesk migration

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

high

Knowledge Base migration can duplicate articles if categories are not pre-created

A Freshworks community post documents a case where migrating the Knowledge Base from Zendesk to Freshdesk resulted in 800 articles instead of 200 because categories and sections did not exist in Freshdesk at import time.

How we handle it

Freshdesk's import process appears to create new category nodes on each pass, multiplying the article count. We avoid this by pre-creating the Freshdesk category and section structure before any article import begins. We validate article counts after import and rerun with a clean KB if duplication occurs.

high

Custom fields must exist in Freshdesk before ticket import

Freshdesk does not auto-create custom fields during ticket import.

How we handle it

If a Zendesk ticket custom field has no corresponding Freshdesk field, the field value is silently dropped. We audit all Zendesk ticket fields, organization fields, and user fields during discovery, then create matching custom fields in Freshdesk with correct types (dropdown, text, date, number, checkbox) before any record migration begins. This is a pre-migration configuration step, not a migration step.

medium

Zendesk Automations and Triggers do not have Freshdesk equivalents as automation code

Zendesk Triggers and Automations use an event-condition-action model that differs architecturally from Freshdesk Scenario Automations.

How we handle it

Freshdesk Scenario Automations combine time-based and event-based logic in a single construct rather than maintaining separate primitives. Complex Zendesk automations with multiple nested conditions may require decomposition into multiple Freshdesk Scenarios or manual simplification. We export full trigger and automation definitions and deliver a written rebuild guide; the admin configures the Freshdesk equivalents post-migration.

medium

Multi-brand Zendesk accounts require manual Freshdesk mailbox configuration

Zendesk Brands provide independent email routing, Help Centers, and agent routing per brand under a single account.

How we handle it

Freshdesk does not have an equivalent multi-brand abstraction. Teams with multiple Zendesk brands must recreate separate mailbox aliases and routing rules in Freshdesk manually before cutover, or consolidate brands into a single Freshdesk account. We flag Brand as a manual-configuration item and document the source brand email addresses and routing rules for the customer's admin to reconfigure.

How the migration runs

  1. Discovery and plan-tier audit

    We audit the source Zendesk account across plan tier (Team/Growth/Professional/Enterprise), active agent count, ticket volume, organization count, Help Center section and article count, active Triggers and Automations count, and SLA Policy definitions.

    What this step covers

    We confirm whether the account is on Team or Essential tier (requiring API-based export rather than native export UI) and note any Custom Objects on Enterprise plans. The discovery output is a written migration scope including record counts per object, custom field inventory, and a pre-migration checklist for Freshdesk configuration.

  2. Freshdesk environment pre-configuration

    Before any data migration begins, we configure the Freshdesk destination environment to match the source schema.

    What this step covers

    This includes creating Agents and Groups, defining Ticket Status and Priority values matching the Zendesk taxonomy, creating all ticket custom fields with correct types, creating Company custom fields matching Zendesk Organization Fields, creating Contact custom fields matching Zendesk User Fields, and pre-creating Knowledge Base Categories and Sections matching the Zendesk Help Center hierarchy. We do not begin record migration until this schema exists in Freshdesk.

  3. Demo migration and reconciliation

    We run a demo migration using a representative sample of tickets (typically 20-50 records per object type) into a Freshdesk sandbox or the production environment.

    What this step covers

    The customer's support operations lead spot-checks records against the Zendesk source, validates custom field values, confirms status mapping, and reviews the Knowledge Base article structure. Mapping corrections are documented and applied before the full migration begins. This step catches the Knowledge Base duplication issue and custom field drop scenarios before they affect production data.

  4. Record migration in dependency order

    We run production migration in the order that respects foreign-key dependencies: Companies (from Zendesk Organizations) first, then Contacts (from Zendesk Users with agent vs. requester split applied), then Agents, then Ticket custom fields (validated against pre-created schema), then Tickets with full comment history and attachments, then Tags, then SLA Policies, then Knowledge Base Articles with section hierarchy and translations.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins.

  5. Delta migration and cutover

    We freeze Zendesk writes during a defined cutover window, migrate any tickets created or modified since the last batch, then switch the team to Freshdesk as the system of record.

    What this step covers

    We deliver the Trigger and Automation inventory document to the customer's admin team for post-migration rebuild. We do not rebuild Zendesk Triggers, Automations, Macros, or SLA Policies as Freshdesk configuration code; that work is documented for the customer's admin or a Freshdesk implementation partner.

  6. Validation and post-migration handoff

    We run a final reconciliation comparing migrated record counts in Freshdesk against exported record counts from Zendesk.

    What this step covers

    We validate a random sample of 25-50 tickets for field-level accuracy, attachment presence, and timestamp fidelity. We deliver the automation rebuild guide and a runbook for the admin team covering Freshdesk configuration for multi-brand email routing if applicable. We offer a one-week hypercare window for reconciliation issues raised during the first week of live Freshdesk operation.

Zendesk Freshdesk
  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 · FreshdeskRollback 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

1-2 weeksTypical, smaller accounts
4-8 weeksLarge or heavily customised accounts

A quote scales with ticket volume, contact count, and knowledge base article size. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Zendesk to Freshdesk →

Why teams move from Zendesk to Freshdesk

  • Per-agent pricing climbs steeply on Zendesk Suite. Reviewers on G2 and Capterra cite sticker shock when adding omnichannel features or AI add-ons, with effective costs 30-50 percent above the base per-agent price. Freshdesk's pricing includes more features at lower tiers, with Freddy AI Copilot available at $29/agent/month for select agents rather than forcing an all-or-nothing add-on purchase. Teams with 10-50 agents consistently report halving their monthly platform spend by switching.
  • Zendesk's plan-gated export tools force teams on Team or Essential tiers to use API scripting to extract their own data. A Quora answer and multiple migration-service landing pages confirm that Freshdesk's built-in import tool expects Professional-tier Zendesk exports, which means non-Enterprise accounts must pull data via API before migration can begin. Freshdesk's own migration app and third-party tools lower this barrier for teams leaving Zendesk.
  • Setup complexity drives smaller teams to Freshdesk for faster time-to-value. G2 reviewers note that Zendesk's configuration layers, plan-gated features, and steep learning curve frustrate teams without dedicated admins. Freshdesk's shallower onboarding curve and more opinionated defaults let smaller support teams get to first response faster, which G2 reviewers cite as a primary switching reason for teams under 30 agents.
  • AI costs behave more predictably on Freshdesk. Zendesk's AI Copilot at $50/agent/month for every agent and resolution-based AI Agent pricing means costs rise as the AI improves at resolving tickets. Freshdesk's Freddy AI Copilot can be assigned to specific agents rather than the entire team, and AI Agent sessions are priced per 100 sessions at a fixed rate. Teams evaluating total AI cost of ownership consistently find Freshdesk more controllable at scale.
  • Knowledge base functionality is more integrated in Freshdesk at lower tiers. Zendesk separates Help Center management from core ticketing with its own permission model and versioning, while Freshdesk's Knowledge Base sits closer to the support workflow. Teams migrating from Zendesk Suite Team or Suite Growth cite the consolidation of KB and ticket context as a simplification rather than a downgrade.

Questions, answered

Zendesk to Freshdesk migration questions

How long does a Zendesk to Freshdesk migration take?

Small migrations under 10,000 tickets and 2,000 contacts typically complete in one to two weeks. Mid-size migrations with 10,000-50,000 tickets, multi-section Knowledge Bases, complex custom field mappings, and a need for delta migration during cutover extend to four to eight weeks. Large enterprise accounts with over 50,000 tickets or multiple Zendesk brands require additional configuration time for Freshdesk mailbox routing and brand consolidation, pushing timelines to eight or more weeks.

Do Zendesk Triggers, Automations, and SLA Policies migrate to Freshdesk?

SLA Policies migrate as configuration records. Triggers and Automations do not migrate as automation code because the two platforms use different automation primitives. Zendesk separates event-driven Triggers from time-based Automations; Freshdesk uses a combined Scenario Automation construct. We export full definitions of every active Trigger and Automation and deliver a written rebuild guide mapping each to the recommended Freshdesk Scenario configuration. Your admin rebuilds them in Freshdesk's Automation section post-migration. Macros migrate as Canned Responses with variable substitution adjusted from Zendesk to Freshdesk syntax.

Will our Help Center articles and Knowledge Base migrate correctly?

Yes, with a critical pre-configuration step. Freshdesk requires Categories and Sections to exist before article import; otherwise, the import process can create duplicate category nodes and multiply article counts. We pre-create the Knowledge Base structure in Freshdesk matching the Zendesk Help Center hierarchy before any article import begins. HTML content, attachments, translations, and section hierarchy transfer. Dynamic Content items (multilingual Zendesk variants) map to Freshdesk's locale fields. We validate article counts post-import and rerun the Knowledge Base migration with a clean target if duplication occurs.

Can we run both Zendesk and Freshdesk in parallel during migration?

Yes. We recommend a parallel-operation window where Zendesk remains active for new ticket creation while we migrate historical data into Freshdesk. During this window, new tickets accumulate in Zendesk. At cutover, we run a delta migration to capture those new tickets and their associated contacts, then switch the team to Freshdesk. This approach eliminates downtime and maintains business continuity throughout the migration.

What happens to our Zendesk custom fields during migration?

Custom fields on tickets, organizations, and users must be pre-created in Freshdesk before record migration begins. We audit all Zendesk custom fields during discovery, create matching Freshdesk fields with correct types (dropdown, text, date, number, checkbox), and validate the mapping before any records load. If a Zendesk custom field has no Freshdesk equivalent, we flag it during scoping and either create a new Freshdesk field or store the data as a tag or note on the ticket.

What data does not migrate from Zendesk to Freshdesk?

We do not migrate Triggers, Automations, Macros (as code), SLA Policies (as active rules beyond definitions), Reports, Dashboards, or Integrations as configuration. We deliver written inventories of Triggers, Automations, Macros, and SLA Policy definitions with Freshdesk equivalents for your admin to rebuild. Custom Objects from Zendesk Enterprise accounts migrate as records if the destination Freshdesk plan supports custom fields on the equivalent object. Brand routing configuration and multi-brand mailbox setup requires manual recreation in Freshdesk. Any third-party app integrations (Salesforce, Jira, Slack) are documented for reconfiguration in Freshdesk post-migration.

Get a quote

Moving from Zendesk to Freshdesk?

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

Get a quote