Skip to content
Get a quote

Freshdesk to Zendesk migration

We migrate Tickets, Contacts, Companies, Agents, and SLA Policies from Freshdesk into Zendesk with the API rate-limit ceiling on the source side identified before extraction begins, multi-channel conversation history normalized to Zendesk channel types, and every Freshdesk custom field mapped to its typed Zendesk equivalent before any record touches the destination.

Short answer

FlitStack AI migrates tickets, users, organizations, agents and comments from Freshdesk 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 Freshdesk
DestinationZendesk
TicketUserOrganizationAgentComment
Mapped field by field · sample run · one-click rollback

What moves from Freshdesk to Zendesk?

Moving from Freshdesk to Zendesk is an API orchestration problem with a strict load order.

Read the full summary

Zendesk's import API requires that requester Users exist before Ticket records can reference them, and ticket forms (Freshdesk's Ticket Types) must be pre-created in Zendesk before import begins. We extract Freshdesk data in dependency order—Contacts first, then Companies, then Agents and Groups, then Tickets with their full conversation threads—resolving Freshdesk's per-plan API rate limits (0 on Free, 200/min on Growth, 700/min on Enterprise) before we begin any pull. Multi-channel source types from phone, Twitter, Facebook, and forwarded email normalize to Zendesk's channel model during transformation. Freshdesk SLA Policies migrate as Zendesk Service Level Agreements on Enterprise and higher tiers; Pro-plan customers receive a written map of their SLA configuration for manual recreation. We do not migrate automations, macros, or forum structures as code; these appear in a delivered configuration inventory for the customer's admin to rebuild in Zendesk Admin Center.

1:1

Ticket → Ticket

Freshdesk Tickets map to Zendesk Tickets with full conversation history.

How it maps

The Freshdesk status Open and Pending map directly to Zendesk Open and Pending. Freshdesk Resolved maps to Zendesk Solved (terminology difference, not a schema gap). Freshdesk Closed maps to Zendesk Closed. Ticket priority, type, group, and agent assignments migrate directly. We use Zendesk's /imports/tickets endpoint to preserve created_at, updated_at, and closed_at timestamps on historical records.

1:1

Contact (Requester) → User (End User)

Freshdesk Contacts (called Requesters) map to Zendesk End Users.

How it maps

Email is required for all Zendesk requesters; we flag any Freshdesk Contact without an email address during scoping and either create placeholder records or exclude per the customer's data-quality policy. Custom contact fields migrate as Zendesk user fields after the destination fields are pre-created in Zendesk Admin.

1:1

Company → Organization

Freshdesk Companies map to Zendesk Organizations.

How it maps

The domain field on Freshdesk Company populates Zendesk's domain for auto-linking. Organizations must exist before Contacts that reference them can be imported, so we load Organizations first. Multiple company memberships per contact (available in Freshdesk Pro and Enterprise) map to Zendesk's multi-organization membership model.

1:1

Agent → Agent

Freshdesk Agents map to Zendesk Agents.

How it maps

We extract agent records with their group assignments and role definitions. Agents who are also ticket requesters are flagged during scoping to prevent circular references (an agent cannot be both the assignee and the requester on the same ticket). Agent groups migrate as Zendesk Groups, and roles are mapped to Zendesk's Agent roles and permissions.

1:1

Conversation (Public Reply) → Comment

Freshdesk public conversation threads migrate as Zendesk Ticket Comments.

How it maps

Each comment carries its author, timestamp, and body. Public vs private distinction is preserved via Zendesk's is_public flag on the Comment API payload. Inline images attached to conversations migrate as Zendesk inline attachments under the 50 MB per-attachment limit.

1:1

Conversation (Private Note) → Comment (Internal)

Freshdesk private notes migrate as Zendesk internal comments with is_public=false.

How it maps

Author attribution is preserved by resolving the Freshdesk agent ID to the Zendesk Agent record. Private notes are visible only to Zendesk agents, matching Freshdesk's permission model.

What moves12 objects
FreshdeskZendesk
  • TicketTicket1:1
  • ContactUser1:1
  • CompanyOrganization1:1
  • AgentAgent1:1
  • ConversationComment1:1
  • ConversationComment1:1

+ 6 more in the mapping below

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

DimensionFreshdeskZendesk
Ticket TypesTicket Types as named categories (Question, Bug, Feature Request)Ticket Forms with conditional field visibility and agent workspace routing
Status terminologyOpen, Pending, Resolved, ClosedOpen, Pending, Solved, Closed (Solved not Resolved)
CompaniesCompanies as standalone linked objectOrganizations with domain-based auto-linking and multiple organizational memberships
Channel modelMulti-channel with siloed source types (phone, email, chat, Twitter, Facebook, forum)Unified agent workspace with channel context preserved in ticket metadata
Custom objectsAPI-accessible custom objects on Pro/Enterprise; in-product objects are isolatedCustom Objects with their own API, agent workspace display, and trigger/automation integration
SLA policiesAvailable on Pro and Enterprise; multiple SLA policies with per-plan limitsEnterprise Suite and above; Service Level Agreements tied to business hours and agents
API rate limitsAccount-wide per-minute limits: 0 on Free, 200 on Growth, 400 on Pro, 700 on EnterpriseHigher throughput on Enterprise import API; standard API at 700 requests per minute

What to watch for in a Freshdesk 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

Freshdesk free plan has zero API access

Freshdesk's free plan explicitly allows 0 API calls per minute and blocks all programmatic access.

How we handle it

Any migration tooling that uses the Freshdesk REST API will fail immediately for free-plan accounts. We require at minimum the Growth plan ($15/agent/month) before we begin extraction. If the customer is on the free plan, we advise upgrading early in the project to avoid timeline delays; the upgrade itself can take 24-48 hours for the API access to activate after plan change.

high

Ticket Types require pre-created Zendesk Ticket Forms

Freshdesk Ticket Types (Question, Bug, Feature Request, and any custom types) have a different structure from Zendesk Ticket Forms.

How we handle it

Zendesk Ticket Forms must be created in Admin Center before ticket import begins, and each form controls which custom fields and status options are visible to agents. If ticket forms are not pre-created, importing a Freshdesk ticket with type=bug against a Zendesk instance with no matching form will either reject the record or default it to the default form, losing the type context.

medium

Multi-channel source types normalize during transformation

Freshdesk tickets can originate from phone, forwarded email, tweet, Facebook, forum, or survey in addition to standard email and chat.

How we handle it

Zendesk's channel model supports email, chat, voice, and social (Twitter, Facebook) natively. Non-standard source types (forum, survey, forwarded email) are normalized to a default channel value during transformation, and the original source type is preserved in a ticket comment for auditability. Teams that rely on source-type reporting in Freshdesk dashboards should note this normalization in their post-migration validation checklist.

medium

Freshdesk dependent fields lack a Zendesk native equivalent

Freshdesk supports conditional field visibility (dependent fields) where one dropdown controls what options appear in another field.

How we handle it

Zendesk's custom field model does not include native dependent fields in the same way. We document every Freshdesk dependent field relationship during scoping and recommend rebuilding the logic in Zendesk using Conditional Fields or, for complex hierarchies, a post-migration configuration engagement. Fields that cannot be rebuilt natively are migrated as-is but display as static dropdowns in Zendesk.

medium

Large attachment volumes extend migration time significantly

Freshdesk supports attachments up to 20 MB per file; Zendesk supports up to 50 MB per file.

How we handle it

Attachments are not bulk-exported efficiently by the Freshdesk API at high volume. We chunk attachment extraction, stream-upload to Zendesk, and run attachment migration in parallel with record migration. For accounts with thousands of tickets containing attachments, the attachment phase can extend the overall timeline by one to two weeks. We scope this separately during discovery.

How the migration runs

  1. Discovery and plan-tier scoping

    We audit the source Freshdesk account: plan tier (Free/Growth/Pro/Enterprise determines API access and rate limits), ticket volume and age distribution, custom fields for tickets and contacts, SLA policy definitions, knowledge base structure (categories, sections, articles, translations), and product inventory.

    What this step covers

    We also inventory automations and macros for the delivered configuration inventory. The discovery output is a written migration scope and a migration sequence that respects Freshdesk's per-plan rate limits.

  2. Destination schema preparation

    We create the Zendesk environment before any data import.

    What this step covers

    This includes provisioning Zendesk Agents and Groups (matched to Freshdesk agents and groups by email), creating Ticket Forms to match Freshdesk Ticket Types, defining custom ticket fields and user fields to match Freshdesk custom fields, setting up SLA policies (Enterprise and above), and configuring business hours. Schema is built in a Zendesk Sandbox or staging environment first for validation before production migration.

  3. User and Organization load (pre-ticket dependency)

    Zendesk's import API requires that all requester Users exist before Tickets that reference them can be imported.

    What this step covers

    We load Freshdesk Contacts as Zendesk End Users and Freshdesk Companies as Zendesk Organizations in the first data phase. Any Freshdesk Contact without an email address is flagged for the customer's admin to resolve before the contact phase completes. Agent records (Users with agent role) load in the same phase.

  4. Ticket and conversation migration with timestamp preservation

    We use Zendesk's /imports/tickets endpoint for historical ticket import, which preserves created_at, updated_at, and closed_at timestamps without triggering automations or sending notifications to customers.

    What this step covers

    Public replies and private notes load as Comments and internal Comments respectively. We run Freshdesk API queries against the customer's rate limit ceiling (200/min Growth, 400/min Pro, 700/min Enterprise) with exponential backoff on 429 responses and batch chunking to avoid timeouts.

  5. Knowledge base and attachment migration

    KB articles, categories, and sections export from Freshdesk and import to Zendesk Help Center.

    What this step covers

    Multi-language articles are imported with their locale tags. Attachments migrate in parallel as a separate pass, with inline images re-attached to their originating comments. Large attachment volumes are staged and processed in chunks to manage memory and bandwidth.

  6. Delta sync and cutover

    We freeze Freshdesk writes during the final delta migration window, extract any records created or modified since the initial migration pass, apply them to Zendesk, then switch the customer's routing and email MX records to Zendesk as the system of record.

    What this step covers

    We deliver the automation and macro inventory (not migrated) to the customer's admin. We support a one-week post-cutover reconciliation window to resolve any record mismatches identified by the support team.

Freshdesk 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
6-10 weeksLarge or heavily customised accounts

A quote scales with ticket volume, attachment size, and custom field complexity. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Freshdesk to Zendesk →

Why teams move from Freshdesk to Zendesk

  • Zendesk offers enterprise-grade capabilities that Freshdesk's feature set does not support at scale. Zendesk's unified agent workspace, advanced AI (Zendesk AI with autonomous resolution and real-time guidance), and deeper customization options appeal to teams that have outgrown Freshdesk's simpler workflow model. Reviews on G2 and Reddit cite Zendesk's Explore reporting, multi-brand management, and the ability to handle complex routing as the key differentiators driving the switch.
  • Zendesk's app marketplace has over 1,500 integrations versus Freshdesk's approximately 1,000. Teams needing native ERP connectors, advanced CRM integrations, or specialized workflow tools move to Zendesk because the integrations are available on the Zendesk Marketplace without requiring third-party middleware or Zapier workarounds.
  • Freshdesk's AI features (Freddy AI Agent at $49 per 100 sessions) carry unpredictable per-session billing that grows at volume. Zendesk AI's licensing model (bundled at higher tiers with per-agent pricing) provides more predictable cost management for teams running high ticket volumes. Reviewers on Capterra and G2 cite AI billing unpredictability as a consistent frustration with Freshdesk.
  • Zendesk handles complex multi-brand, multi-region, and multi-team deployments with built-in features that require marketplace apps or workarounds in Freshdesk. Organizations managing separate support operations for different product lines, subsidiaries, or customer segments move to Zendesk for its native multi-brand capabilities without paying for multiple Freshdesk instances.
  • Performance issues during high-volume periods—delayed ticket loading, occasional dropped chats—drive teams to seek a more stable platform. While Freshdesk's per-agent pricing is attractive, the operational cost of degraded performance during peak support periods outweighs the price savings for teams with strict SLA requirements.

Questions, answered

Freshdesk to Zendesk migration questions

How long does a Freshdesk to Zendesk migration take?

Most migrations land between three and five weeks for accounts under 20,000 tickets with no knowledge base articles and no SLA policies to recreate. Migrations with knowledge base articles, SLA policy recreation scope, large attachment volumes, or multi-language KB translations move to six to ten weeks. The Freshdesk plan tier also affects speed: Growth at 200 API calls per minute takes longer than Enterprise at 700 calls per minute for the same ticket volume.

Do Freshdesk automations, macros, and SLA policies migrate to Zendesk?

No. Automations (Freshdesk's workflow rules) and macros (canned responses) are configuration objects that do not have direct Zendesk equivalents because the trigger and action models differ. We do not migrate them as code. We deliver a written inventory of every Freshdesk automation and macro with its trigger conditions, actions, and recommended Zendesk Trigger or Macro equivalent for the customer's admin to rebuild in Zendesk Admin Center. SLA policies on Pro plans (not available on Zendesk Pro) receive a written map for manual recreation; SLA policies on Zendesk Enterprise migrate as Zendesk SLAs if the destination suite tier supports them.

What happens to Freshdesk's Freddy AI data after migration?

Freddy AI generates session logs, suggestion history, and bot training data that are stored within Freshdesk's proprietary AI layer and are not accessible via the Freshdesk REST API. These do not migrate because Zendesk AI uses a different training model. We do not transfer Freddy AI bots, training corpora, or AI-generated response templates. The customer's admin builds new Zendesk AI bots using Zendesk's own AI tools post-migration.

Can we migrate only recent tickets and archive old ones?

Yes. We support time-range filtering during ticket extraction, allowing customers to migrate only tickets created after a specified date (for example, the last 12 months) and archive older tickets. Archived tickets are not deleted but remain in Freshdesk as a reference dataset. This is useful for customers who want to limit migration scope to reduce cost or timeline while preserving historical records in Freshdesk for compliance.

How do you handle Freshdesk's API rate limits during migration?

Freshdesk enforces account-wide rate limits per plan tier that apply across all endpoints. The Tickets List endpoint has a tighter sub-limit (20/min on Growth) than the total account limit (200/min). We pre-map each migration to the customer's plan tier, throttle our API queries to the tightest sub-limit, use exponential backoff on 429 responses, and batch records into chunks to maximize throughput within the allowed limit. We do not request rate limit increases from Freshdesk as part of standard scope.

What about Freshdesk's forums and community discussions?

Freshdesk Forums (community discussions with categories, topics, and posts) do not have a native Zendesk equivalent in the standard Support Suite. We do not migrate forums as data objects. We deliver a written record of the forum structure (categories, topics, post counts, and links to posts if accessible via API) for the customer's admin to evaluate whether Zendesk Community (a separate product with its own licensing) or a third-party forum platform is the appropriate destination.

Do you migrate Freshdesk Products to Zendesk Assets?

Freshdesk Products (used to associate items with tickets and track customer assets) migrate to Zendesk Assets only if the destination Zendesk instance includes the Asset Management module (Enterprise Suite and above). If the destination Zendesk does not include Asset Management, we migrate product associations as a custom ticket field that preserves the product name and ID from Freshdesk. The customer decides during scoping which approach applies to their Zendesk edition.

Get a quote

Moving from Freshdesk 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