Customer support migration

Zendesk → Freshdesk

Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Zendesk to Freshdesk with a reversible cutover, explicit exception ledger, and evidence-backed verification.

Typical timeline15–45 business days70–180 hours active work

Statusneeds review

Source profileZendesk documentation reviewed 2026-07-20

Destination profileFreshdesk documentation reviewed 2026-07-20

Documentation date2026-07-20

Review window2026-07-202026-10-20

Evidence2 sources

This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.

Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Zendesk

Reasons to stay

Mature ticketing, omnichannel support, help centers, routing, SLAs, and ecosystem depth serve complex teams
Tickets, customer context, knowledge, automation, and service reporting share one operating system

Reasons to leave

Customization, administration, licensing, and source-specific ticket semantics make migrations demanding
Conversation visibility, routing logic, SLAs, and reporting history are hard to reproduce exactly

New platform

Freshdesk

What gets better

Accessible omnichannel ticketing and automation provide strong value for growing support teams
Tickets, customer context, knowledge, automation, and service reporting share one operating system

What gets worse

Advanced reporting, customization, and ecosystem depth can lag enterprise-focused competitors
Conversation visibility, routing logic, SLAs, and reporting history are hard to reproduce exactly

Best of the move

Freshdesk: Accessible omnichannel ticketing and automation provide strong value for growing support teams. This removes a major source-side concern: Customization, administration, licensing, and source-specific ticket semantics make migrations demanding.

Worst of the move

What you lose: Mature ticketing, omnichannel support, help centers, routing, SLAs, and ecosystem depth serve complex teams. What you inherit: Advanced reporting, customization, and ecosystem depth can lag enterprise-focused competitors.

Jump to a section

01At a glance

Know the shape of the move.

Transfer outcome10 features audited

Clean0

Partial6

Manual3

Lost1

Mapping route8 of 9 fields have a destination path

SourceZendesk9 mapped fields

Automatic0

Transform6

Manual2

Unsupported1

DestinationFreshdesk8 supported paths

This timeline assumes

Up to 500 agents, one million tickets, 250 automations, and 500 GB of attachments
Administrators control both Zendesk and Freshdesk, including billing, identity, APIs, integrations, and export permissions.
Zendesk remains intact and recoverable until Freshdesk completes one representative operating cycle.
A production-shaped pilot includes every object type, access class, edge case, and failure path.
The migration team preserves stable source identifiers and records durable evidence for every blocking check.

02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

Item	Outcome	Impact	What happens	Mitigation
Customers, contacts, and organizations	partial	critical	Identity keys, merged profiles, organization membership, custom attributes, and consent do not share one model. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Map customers, contacts, and organizations explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Tickets and conversations	partial	critical	Ticket states, conversation parts, channel semantics, requester identity, and threading require transformation. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Map tickets and conversations explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Public replies and private notes	partial	critical	Comment visibility and author attribution can flatten or expose internal material. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Map public replies and private notes explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Attachments and inline media	partial	high	Exports can preserve attachment metadata while binaries, inline images, or authenticated URLs remain behind. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Map attachments and inline media explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Agents, teams, roles, and permissions	manual	critical	Agent accounts, restricted groups, custom roles, and licensing must be provisioned deliberately. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Inventory and rebuild agents, teams, roles, and permissions, then test normal, edge, failure, and rollback behavior.
Custom fields, forms, tags, and statuses	partial	high	Field types, option values, required rules, lifecycle states, and tag behavior differ. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Map custom fields, forms, tags, and statuses explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Macros, triggers, routing, and SLAs	manual	critical	Automation syntax, business hours, escalation clocks, assignment rules, and SLA calculations are runtime configuration. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Inventory and rebuild macros, triggers, routing, and slas, then test normal, edge, failure, and rollback behavior.
Help center articles and categories	partial	high	Knowledge hierarchy, locales, URLs, votes, and author metadata have separate import constraints. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Map help center articles and categories explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Reports, CSAT, and SLA history	lost	high	Imported records do not recreate destination-native metrics, historical SLA calculations, or reporting baselines. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Archive reports, csat, and sla history as dated source evidence and define the new destination baseline.
Email channels, apps, bots, and webhooks	manual	critical	Inbound addresses, sender authentication, marketplace apps, bots, API clients, and callbacks remain source-bound. A successful bulk job therefore does not prove semantic parity between Zendesk and Freshdesk.	Inventory and rebuild email channels, apps, bots, and webhooks, then test normal, edge, failure, and rollback behavior.

03Field and feature mapping

Where each thing goes.

Source	Destination	Method	Notes
Zendesk: Customers, contacts, and organizations	Freshdesk: approved customers, contacts, and organizations representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for customers, contacts, and organizations.
Zendesk: Tickets and conversations	Freshdesk: approved tickets and conversations representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for tickets and conversations.
Zendesk: Public replies and private notes	Freshdesk: approved public replies and private notes representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for public replies and private notes.
Zendesk: Attachments and inline media	Freshdesk: approved attachments and inline media representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for attachments and inline media.
Zendesk: Agents, teams, roles, and permissions	Freshdesk: approved agents, teams, roles, and permissions representation	manual	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for agents, teams, roles, and permissions.
Zendesk: Custom fields, forms, tags, and statuses	Freshdesk: approved custom fields, forms, tags, and statuses representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for custom fields, forms, tags, and statuses.
Zendesk: Macros, triggers, routing, and SLAs	Freshdesk: approved macros, triggers, routing, and slas representation	manual	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for macros, triggers, routing, and slas.
Zendesk: Help center articles and categories	Freshdesk: approved help center articles and categories representation	transform	Preserve source IDs, ownership, timestamps, access intent, and an explicit exception status for help center articles and categories.
Zendesk: Reports, CSAT, and SLA history	No destination	unsupported	Retain immutable source evidence; do not manufacture destination-native history.

04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Zendesk data, configuration, access, and operating evidence before any destination write.

Export every available Zendesk object and binary in scope, including customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media.
Capture configuration and runtime dependencies for agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories.
Record counts, sizes, owners, timestamps, access classes, financial totals where applicable, and known exceptions.
Hash immutable exports, record tool versions and commands, and transform working copies only.

Proof to capture: A signed manifest accounts for every scoped record class, configuration object, binary, count, total, exception, and hash.

Transformation · Version-controlled migration workbook, SQL, or typed transformation code

Identity, schema, and disposition registry

Preserve stable identity and make every mapping or exclusion reviewable.

Inventory source types, identifiers, owners, states, and access.
Define one approved destination representation or explicit archive decision.
Reject unmapped critical items and produce an exception ledger.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Official APIs, provider importers, checksums, and reconciliation scripts

Dependency-ordered migration package

Load prerequisite identities and configuration before dependent records and runtime actions.

Normalize encoding, timestamps, identifiers, nulls, and destination limits.
Run a representative pilot and retain request, response, and rejection evidence.
Reconcile the final delta before enabling destination production writers.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Import

A completed migration hides missing or altered customers, contacts, and organizations

criticalpossible likelihood

Headline counts look plausible while semantic, access, or relationship checks fail.

Consequence: The destination becomes authoritative with incomplete or misleading business data.
Mitigation: Reconcile by type, state, owner, access class, and representative record rather than total count alone.

Stop if: Any critical item lacks a verified destination, approved transformation, explicit exclusion, or recoverable archive.

Cutover

Zendesk and Freshdesk both perform production actions

criticalpossible likelihood

Users, schedules, webhooks, integrations, or traffic continue changing both systems.

Consequence: State diverges or customers receive duplicate, contradictory, or unsafe actions.
Mitigation: Freeze source writers and transfer one production owner at a time with an approved rollback.

Stop if: An unapproved source writer or destination duplicate action appears after the freeze.

Verification

Destination access or security is broader than approved

criticalpossible likelihood

A representative restricted user can read, change, export, or trigger an unauthorized item.

Consequence: Confidential, regulated, financial, or security-sensitive data is exposed or changed.
Mitigation: Apply least privilege before bulk loading and test every access class using ordinary identities.

Stop if: Any unauthorized read, write, export, administrative action, or secret access succeeds.

06Precise timeline

Do the work in this order.

Estimate forUp to 500 agents, one million tickets, 250 automations, and 500 GB of attachments

Total elapsed15–45 business days

Active work70–180 hours

BufferAdd time for large Zendesk exports, destination rate limits, unsupported features, identity exceptions, regulated data, or a strict downtime objective.

Days 1–4Inventory and decisions2–4 days

Days 3–8Backup and reconcile2–5 days

Days 6–20Map, transform, and pilot5–12 days

Days 18–35Bulk load, final delta, and switch2–8 days

Days 25–45Observe and close7–14 days

1
Days 1–4 · inventory
Inventory and decisions
8–16 hours active2–4 days elapsedOwner, legal, security, and finance review waiting
- Inventory Zendesk data, configuration, identities, integrations, limits, and billing.
- Approve scope, owners, mappings, exclusions, acceptance thresholds, and rollback authority.
Depends on: Zendesk and Freshdesk administrator access
Stop / go checkpoint
Export?
Go when: Every critical item and production action has an owner and disposition.
Stop when: Authority, retention, billing, access, or system ownership is unclear.
2
Days 3–8 · backup
Backup and reconcile
8–20 hours active2–5 days elapsedProvider export processing waiting
- Create immutable data, configuration, binary, and audit exports.
- Reconcile source counts, totals, sizes, access classes, and hashes.
Depends on: Approved inventory and retention location
Stop / go checkpoint
Transform?
Go when: The signed source manifest and exports agree.
Stop when: Any critical dataset, binary, configuration, or recovery path is absent.
3
Days 6–20 · pilot
Map, transform, and pilot
25–70 hours active5–12 days elapsedDestination processing and owner review waiting
- Configure Freshdesk and transform a production-shaped pilot.
- Test normal records, every feature class, edge cases, permissions, failures, and rollback.
Depends on: Verified source backup and approved mapping registry
Stop / go checkpoint
Scale?
Go when: Every pilot mapping and blocking verification check passes.
Stop when: Any critical invariant, access boundary, or production action lacks a safe destination.
4
Days 18–35 · cutover
Bulk load, final delta, and switch
20–55 hours active2–8 days elapsedImports, propagation, indexing, or synchronization waiting
- Freeze production writes and automated actions in Zendesk.
- Apply and reconcile the final delta, switch ownership to Freshdesk, and run all blocking checks.
Depends on: Passed pilot, stakeholder go decision, and rehearsed rollback
Stop / go checkpoint
Open production?
Go when: Freshdesk is the sole production owner and every critical exception is resolved.
Stop when: A source writer remains active, a blocking check fails, or rollback is unavailable.
5
Days 25–45 · observe
Observe and close
9–19 hours active7–14 days elapsedRepresentative operating-cycle evidence waiting
- Monitor correctness, access, failures, latency, delivery, cost, and user outcomes.
- Sign the verification report and close rollback only after stable evidence.
Depends on: Verified cutover
Stop / go checkpoint
Close rollback?
Go when: No trigger occurs during the approved observation period.
Stop when: Data, access, delivery, routing, cost, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Freshdesk the only production system without losing the final Zendesk delta.

Recommended window: A low-volume weekday morning with platform, data, security, networking, finance, and business owners available.

Freeze user, integration, schedule, and API writes in Zendesk.
Capture and reconcile the final source delta against the last verified checkpoint.
Apply the approved delta and configuration changes to Freshdesk.
Switch traffic, domains, integrations, credentials, automation, and user entry points in dependency order.
Run every blocking verification check and keep the source intact.

Proof to capture: Freshdesk alone owns production, totals reconcile, exceptions are signed, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Zendesk without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, keys, or retention settings are changed.

Stop new user, integration, schedule, and API writes in Freshdesk.
Restore prior Zendesk traffic, domains, credentials, automation, and integration ownership.
Export and classify the Freshdesk post-cutover delta.
Apply safe destination-era changes back to Zendesk without duplicating actions.
Run the same blocking checks against the restored source.

Proof to capture: Zendesk again owns production with current data and no duplicate destination action.

Rollback immediately when

Unexplained critical count, value, relationship, or checksum variance
Missing, corrupted, or exposed critical data
Duplicate production action or unresolved split-brain state
Failed access, security, delivery, routing, performance, or integration check
A critical feature has no safe destination replacement or rollback path

08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

ID	Check	Method	Expected result	Evidence
`V-01`Blocking	Customers, contacts, and organizations reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for customers, contacts, and organizations.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Customers, contacts, and organizations ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-02`Blocking	Tickets and conversations reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for tickets and conversations.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Tickets and conversations ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-03`Blocking	Public replies and private notes reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for public replies and private notes.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Public replies and private notes ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-04`Blocking	Attachments and inline media reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for attachments and inline media.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Attachments and inline media ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-05`Blocking	Agents, teams, roles, and permissions reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for agents, teams, roles, and permissions.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Agents, teams, roles, and permissions ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-06`	Custom fields, forms, tags, and statuses reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for custom fields, forms, tags, and statuses.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Custom fields, forms, tags, and statuses ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-07`Blocking	Macros, triggers, routing, and SLAs reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for macros, triggers, routing, and slas.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Macros, triggers, routing, and SLAs ledger with counts, exceptions, sample IDs, and owner sign-off.
`V-08`	Help center articles and categories reconciliation	Compare source inventory, transformed output, destination results, and a stratified sample for help center articles and categories.	Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.	Help center articles and categories ledger with counts, exceptions, sample IDs, and owner sign-off.

09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check and exception.

Create final Zendesk exports and archive verification, access, financial, and rollback evidence.
Revoke temporary credentials, API keys, webhooks, elevated roles, and migration network access.
Remove obsolete jobs, embeds, domains, integrations, collectors, routes, and DNS records.
Keep the source intact and read-only through the approved legal and operational retention window.
Cancel paid plans only after billing, legal, security, evidence, and recovery review.
Schedule the next Freshdesk backup, restore test, access review, and migration-playbook review.

Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

Zendesk: official portability and migration documentationAccessed 2026-07-20
Freshdesk: official portability and migration documentationAccessed 2026-07-20

Know the shape of the move.

This timeline assumes

What survives the move.

Where each thing goes.

Make the move recoverable.

Create the source-of-truth backup

Identity, schema, and disposition registry

Dependency-ordered migration package

The things most likely to hurt.

A completed migration hides missing or altered customers, contacts, and organizations

Zendesk and Freshdesk both perform production actions

Destination access or security is broader than approved

Do the work in this order.

Inventory and decisions

Export?

Backup and reconcile

Transform?

Map, transform, and pilot

Scale?

Bulk load, final delta, and switch

Open production?

Observe and close

Close rollback?

Cut over with a way back.

Cutover

Rollback

Prove the migration worked.

Remove the scaffolding safely.

Verify against the primary material.