Migration guides

Zendesk to Freshdesk Migration: Triggers, Views and Ticket History

Zendesk to Freshdesk migration: which automation rule type each trigger becomes, how views are rebuilt, and what Freshdesk's API lets ticket history keep.

Ayush BothraFounding Member, MigrateX

Published 8 min read

Two taped printouts, a Zendesk record and a Freshdesk record, joined by a hand-drawn arrow, for a Zendesk to Freshdesk migration of triggers, views and ticket history
On this page

In a Zendesk to Freshdesk migration, triggers, automations and views are configuration: each is read from Zendesk's API, reviewed and rebuilt in Freshdesk, not copied. Ticket history is data and moves, with every reply and internal note in order. What Freshdesk does not document is a way to set a ticket's original created date through its API, so that is proven on a sample.

This guide is for the support operations lead or Freshdesk admin who will own the rules after cutover. The object mapping, Zendesk's export limits and Freshdesk's 20 MB attachment cap are on the Zendesk to Freshdesk migration page.

Which Freshdesk automation rule does each Zendesk trigger become?

It depends on when the trigger fires. Freshdesk has three automation rule types, Ticket Creation, Ticket Updates and Hourly Triggers, and Zendesk's two rule kinds split across them: a trigger "performed when a ticket is created or updated", an automation checked "every hour".

In ZendeskIn FreshdeskStatusVendor fact behind it
Trigger with a "ticket is created" conditionTicket Creation ruleRebuilt as configurationFreshdesk runs either the first matching creation rule or all of them, a setting you choose
Trigger on updates (status change, new comment, reassignment)Ticket Updates ruleRebuilt as configurationOnly Ticket Updates rules have events, such as who acted and which field changed
Automation (time-based)Hourly Triggers ruleRebuilt, sometimes redesignedFreshdesk Hourly Triggers only match tickets updated in the last 30 days
Macro that sets fieldsScenario automationRebuilt as configurationFreshdesk's API only lists scenarios, so they are created in the admin screen
Macro that inserts reply textCanned response, or a scenario "Set Reply as" actionRebuilt as configurationCanned responses can be created in bulk through Freshdesk's API
SLA policiesSLA policiesRebuilt as configurationFreshdesk has create and update endpoints for SLA policies
Trigger and automation run countsNo equivalentNot movedKept in the inventory file as evidence for keep or drop

Zendesk stores each trigger as data, so the inventory is exact. Its Triggers API returns conditions as all and any lists of field, operator and value, and on Support Professional or Suite Growth and above it adds how often each trigger ran in the past 30 days. A trigger with zero runs is the first candidate to drop.

Freshdesk's Automations API takes a new rule at /api/v2/automations/[automation_type_id]/rules, with type 1 for Ticket Creation, 4 for Ticket Updates and 3 for Hourly Triggers. The same call takes an active flag, so rules are created switched off, and each one also has its own toggle in Freshdesk's admin screen. None fires on loaded history.

The 30-day limit is the row to read twice. A Zendesk automation that closes tickets pending for 60 days, for example, cannot be copied as is, because Freshdesk's hourly rules ignore tickets idle that long. Such rules are flagged at mapping and redesigned with you.

Do Zendesk views move to Freshdesk?

Not as data. Zendesk's Views API describes a view as "one or more conditions that define a collection of tickets", while a Freshdesk custom view is a saved set of ticket filters, available from the Growth plan. Freshdesk's API offers only fixed list filters, such as new_and_my_open and deleted, so each view is rebuilt in the Freshdesk interface from a list we hand over.

Zendesk view conditionFreshdesk filterStatusVendor fact behind it
Status, priority, type, group, assigneeStatus, Priority, Type, Groups, AgentsRebuilt as configurationAll are in Freshdesk's Filters panel
Requester or organizationContacts, CompaniesRebuilt as configurationFiltered by name or email
Drop-down custom fieldDropdown or dependent fieldRebuilt as configurationFreshdesk filters on dropdown and dependent custom fields
Multi-select custom fieldNo equivalent field typeRedesignedFreshdesk's 8 custom field types include no multi-select
Text, regex or lookup fieldNo custom field filterRedesignedFreshdesk lists only dropdown and dependent custom fields as filters
Personal and shared viewsPersonal and shared viewsRebuilt as configurationFreshdesk roles decide who manages shared views

Fields come before views. Freshdesk's Growth plan caps custom ticket fields per type, for example 80 dropdowns and 10 date fields, and Pro or Enterprise raises that on request, so a large Zendesk field list is trimmed before views are built on it. Freshdesk's field article also warns that changing a dropdown choice in use sets that field to null on existing tickets, so choices are fixed before the load.

What can Freshdesk's API keep from Zendesk ticket history?

Order, authors and privacy are documented; original dates are not. Zendesk lists a ticket's comments oldest first, 100 to a page, each with a public flag. Freshdesk's Create a Note endpoint takes a user_id for "the agent/user who is adding the note", a private flag and an incoming flag for entries that came from outside.

Zendesk historyHow it lands in FreshdeskWhat Freshdesk documents
Agent's public replyReply or public note by that agentA reply's user_id is documented as an agent ID
Customer's replyPublic note, incoming true, by that contactA note's user_id can be an agent or a user
Internal notePrivate noteNotes are private by default
Ticket created and solved datesConfirmed on your free sampleCreate a Ticket lists no created_at parameter
Each comment's original timeConfirmed on your free sampleReply and note parameters list no created date
AttachmentsOn the matching reply or note20 MB in total per ticket, across all its entries
Notifications during the loadSwitched off account-wide firstA disabled notification stops that email "across your account"

Speed is set by plan. Freshdesk's rate-limit article allows ticket creation at 50 a minute on Growth, 160 on Pro and 280 on Enterprise, and the Free plan's limit is 0 calls. Every reply and note is a further call, so a long thread costs more than a short one.

Zendesk's archive is the other trap. Zendesk archives tickets 120 days after they close, and seven ticket endpoints, Listing Tickets among them, skip archived tickets. The incremental export returns them, and ticket audits for an archived ticket need the per-ticket endpoint.

What should the Freshdesk admin check on the sample?

Check what agents will see on their first morning. Include tickets closed more than 120 days ago, a thread of twenty or more entries, and one ticket with large attachments.

  1. Dates. Compare the created and resolved dates, and the time on each entry, with Zendesk.
  2. Authors. Each customer entry shows the contact; each agent entry shows the agent.
  3. Privacy. Log in as a customer and confirm no internal note is visible.
  4. Queues. Open each rebuilt view and compare its ticket count with the Zendesk view.
  5. Rules. Switch on one rebuilt rule at a time against a test ticket before cutover.
  6. Silence. No customer or agent received an email during the load.

Anything that reads wrong is fixed in the mapping and the sample runs again. Our guide to exporting tickets from Zendesk compares export routes, and the Zendesk and Freshdesk pages list what each platform holds.

Facts checked November 17, 2026 from Zendesk Triggers API, Zendesk Automations API, Zendesk Views API, Zendesk Macros API, Zendesk Ticket Fields API, Zendesk Ticket Comments API, Zendesk Incremental Exports API, Zendesk help: About ticket archiving, Zendesk Ticket Audits API, Freshdesk API, Freshdesk help: Overview of Automation Rules, Freshdesk help: Understand the Ticket List View, Freshdesk help: Understand and Customize Ticket Fields, Freshdesk help: Perform Macro Actions with Scenarios, Freshdesk help: Configuring email notifications and Freshdesk help: API rate limits. No vendor paid for this article. How we research

Zendesk to Freshdesk migration FAQ

How many Zendesk triggers usually need rebuilding?

Fewer than you have. Zendesk's Triggers API reports how often each trigger ran in the past hour, day, week and 30 days on Support Professional or Suite Growth and above. Triggers that never run are listed for you to drop, and the rest are rebuilt as Freshdesk Ticket Creation or Ticket Updates rules.

What happens to Zendesk multi-select fields in Freshdesk?

They need a decision. Freshdesk's custom ticket fields come in eight types, and none is a multi-select. The usual options are tags, one checkbox per option, or a text field holding the values; which one fits depends on how your views and reports filter on that field, and it is agreed at mapping.

Will tickets we deleted in Zendesk reappear in Freshdesk?

They should not. Zendesk's Incremental Exports documentation says "by default, deletions will appear in the ticket stream", so a load that took everything in the stream would bring them back. Deleted tickets are filtered out before the load; pick one you know was deleted and check it is absent from the sample.

Can the record of who changed a Zendesk ticket move too?

It can be read. Zendesk keeps field changes in ticket audits, on their own endpoint, per ticket. Whether that trail goes into Freshdesk as a private note on each ticket or stays beside it as an archive file is decided with you at mapping, because it adds a call per ticket.

When should rebuilt rules and views go live?

At cutover. Views can be built and shared while history loads, since they only filter. Rules stay switched off until the load ends, then go on one at a time, so no rule acts on a three-year-old ticket and agents start their first Freshdesk day with the queues they know.

Send your trigger count, get 100 records in Freshdesk

Send us your Zendesk ticket count and roughly how many triggers, automations and views your team uses. MigrateX, an AI migration platform that is SOC 2 Type II, GDPR and HIPAA compliant, returns 100 of your records in Freshdesk at no cost and a fixed quote within 24 hours. Talk to us. Moving the other way? Read Freshdesk to Zendesk: custom fields, macros and history.

Written by

Ayush Bothra

Founding 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.