Freshdesk to Zendesk Migration: Custom Fields, Macros and History
Freshdesk to Zendesk migration: each field type mapped, canned responses and scenarios rebuilt as macros, and what ticket history keeps on import.
Published 8 min read

On this page
- Which Freshdesk custom field types have a Zendesk equivalent?
- How do canned responses and scenario automations become Zendesk macros?
- What does Zendesk's Ticket Import API keep from Freshdesk history?
- What should the Zendesk admin check on the sample?
- Freshdesk to Zendesk migration FAQ
- Try it on 100 of your own Freshdesk records
In a Freshdesk to Zendesk migration, custom fields are recreated in Zendesk type by type before any ticket loads, and their values then move as data. Canned responses and scenario automations are rebuilt as Zendesk macros. Ticket history moves through Zendesk's Ticket Import API, which keeps original dates, comment authors and the line between public replies and private notes.
This guide is for the Zendesk admin or support lead who owns the move and signs off the field and macro mapping. The full object list and Freshdesk's export limits are on the Freshdesk to Zendesk migration page; this post goes deeper on the three parts in its title.
Which Freshdesk custom field types have a Zendesk equivalent?
Seven of the eight do. Freshdesk's ticket fields article lists eight custom types (single-line text, multi-line text, checkbox, dropdown, dependent field, date, number and decimal), and Zendesk's Ticket Fields API has a direct type for each one except the dependent field.
| Freshdesk field type | Zendesk field type | Status | Vendor fact behind it |
|---|---|---|---|
| Single-line text | Text | Moves as data | Zendesk text fields hold up to 65,536 characters |
| Multi-line text | Multi-line (textarea) | Moves as data | Same 65,536-character limit |
| Checkbox | Checkbox | Moves as data | Zendesk can add a tag to the ticket when the box is checked |
| Dropdown | Drop-down (tagger) | Field rebuilt, values move | Up to 2,000 values per Zendesk drop-down |
| Dependent field (3 levels) | Nested drop-down, or conditional fields | Rebuilt as configuration, values move | Zendesk nests options with a double colon (::); conditional fields need Suite Growth or above, or Support Enterprise |
| Date | Date | Moves as data | Zendesk's API shows dates as 2021-04-16 |
| Number | Numeric (integer) | Moves as data | Zendesk sets no length limit on ticket number fields |
| Decimal | Decimal | Moves as data | Direct match |
Every field is configuration first and data second. Zendesk's API says a field's type is editable "only on creation", so a wrong type means deleting the field and starting again. That is why the field list is signed off before the first load, not after it.
Three Zendesk rules shape the build:
- Values are written by field ID. Freshdesk's API keys custom field values by field name; Zendesk's Tickets API takes
custom_fieldsas "a field ID and its value". Each Freshdesk field name is mapped to its new Zendesk field ID. - Drop-down tags must be unique. Zendesk's help centre says a tag duplicated on a ticket makes the fields that use it uneditable until the duplicate is removed, so option tags are generated per field.
- There is a ceiling. Zendesk's Ticket Fields API recommends at most 400 ticket fields per account, or per ticket form. On Pro and Enterprise, Freshdesk raises the single-line text limit alone to 400 on request, so the inventory, with keep, merge or drop marks, comes first.
Company and contact fields follow the same pattern into Zendesk organization and user fields. Freshdesk ticket, contact and company IDs go into external_id, which Zendesk documents on tickets, users and organizations alike.
How do canned responses and scenario automations become Zendesk macros?
They are rebuilt, because they are configuration. A Freshdesk canned response is a reply template; a scenario automation is a set of ticket updates run in one click, which Freshdesk itself calls "a macro command". A Zendesk macro covers both: it is a list of actions, and the reply text is one of them, the comment_value action.
| In Freshdesk | In Zendesk | Status | Vendor fact behind it |
|---|---|---|---|
| Canned response (title, text, folder) | Macro with a comment_value action | Rebuilt as configuration | Zendesk allows up to 5,000 shared macros per account |
| Canned response attachments | Files on the macro comment | Rebuilt, file by file | A Zendesk macro comment holds up to five attachments |
| Scenario automation (status, priority, type, tag, assignment) | Macro with field actions | Rebuilt as configuration | Freshdesk's API only lists scenarios, so they are read, then recreated |
| Scenario "Set Reply as" action | comment_value in the same macro | Rebuilt as configuration | Freshdesk prefills the reply and waits for the agent to send it |
| Personal canned responses and scenarios | Personal macros | Rebuilt per agent, on request | Zendesk admins can list every macro, personal ones included |
| Ticket Creation and Ticket Updates rules | Ticket triggers | Rebuilt as configuration | A Zendesk trigger runs when a ticket is created or updated; 7,000 active triggers at most |
| Hourly Triggers rules | Automations | Rebuilt as configuration | Zendesk checks automation conditions every hour |
Freshdesk's admin-only Canned Responses API returns responses folder by folder, and Zendesk creates macros at POST /api/v2/macros, so the text moves without retyping. What does not move is judgement: which responses your agents still use. Each one is listed with its folder and visibility, and you mark it keep or drop.
The Hourly Triggers row needs the most care. Zendesk's Automations API refuses a new automation unless it has a condition that is true only once, or an action that cancels one of its conditions, such as adding a tag the rule then checks for. Any Freshdesk hourly rule without that guard gains one when it is rebuilt.
What does Zendesk's Ticket Import API keep from Freshdesk history?
Dates, authors and privacy. Zendesk's Ticket Import API documentation says "you can set the following time stamps on the tickets: solved_at, updated_at, and created_at", and its example sets an author_id, a created_at and a public flag on each comment.
| Freshdesk history | How it lands in Zendesk | What Zendesk documents |
|---|---|---|
| Ticket created, updated and resolved dates | created_at, updated_at, solved_at | Settable on import; dates before 1970 are rounded up to 1970 |
| Agent reply | Public comment, author is the agent | Each comment carries its own author and date |
| Customer reply | Public comment, author is the end user | The same; the user is created before the ticket |
| Private note | Comment with public set to false | "false if an internal note" |
| Attachment on a reply | Upload token passed in that comment | "You upload the files then supply the token in the comment parameters" |
| Freshdesk ticket number | external_id on the ticket | Zendesk assigns its own ticket ID |
| SLA timers and response metrics | Not kept | "Zendesk metrics and SLAs are not supported for imported tickets" |
Freshdesk replies and notes come from each ticket's conversations endpoint, so every comment is placed in order with its own date. Imported tickets that are not closed stay outside your new triggers until they are next updated, and Zendesk recommends tagging imported tickets so reports can leave them out.
What should the Zendesk admin check on the sample?
Check the fields and macros as hard as the tickets. Pick sample tickets that use your dependent field, your busiest dropdowns and a long thread with attachments.
- Open five tickets and compare every custom field value with Freshdesk, including all three levels of the dependent field.
- Run three rebuilt macros on a test ticket and confirm the reply text, placeholders and field changes.
- Search for a Freshdesk ticket number and confirm Zendesk finds the ticket through
external_id. - Read a long thread: comment order, the author on each comment, private notes still private.
- Confirm the created and solved dates are the Freshdesk ones, not the import date.
If a value is wrong, the mapping is fixed and the sample runs again before the full load. Platform details are on the Freshdesk and Zendesk pages, and the wider test plan is in the test migration checklist.
Facts checked November 17, 2026 from Zendesk Ticket Import API, Zendesk Ticket Fields API, Zendesk Tickets API, Zendesk Users API, Zendesk Organizations API, Zendesk Macros API, Zendesk Triggers API, Zendesk Automations API, Zendesk Ticket Comments API, Zendesk Satisfaction Ratings API, Zendesk help: About custom fields and custom field types, Zendesk help: Adding custom ticket fields to your tickets and forms, Zendesk help: Creating conditional ticket fields, Zendesk help: Creating macros for repetitive ticket responses and actions, Zendesk help: Creating ticket triggers for automatic ticket updates and notifications, Freshdesk API, Freshdesk help: Understand and Customize Ticket Fields, Freshdesk help: Perform Macro Actions with Scenarios and Freshdesk help: Overview of Automation Rules. No vendor paid for this article. How we research
Freshdesk to Zendesk migration FAQ
Can a three-level Freshdesk dependent field keep all its levels in Zendesk?
Yes, in one of two ways. A single Zendesk drop-down can nest options with a double colon, such as Hardware::Laptop::Battery, which keeps all three levels in one value. Or each level becomes its own field, shown by conditional rules, which needs Suite Growth or above, or Support Enterprise. The choice is made at mapping.
Do Freshdesk ticket numbers stay the same in Zendesk?
No. Zendesk assigns ticket IDs itself, so the numbers change. The Freshdesk number is written to the ticket's external_id, and contact and company IDs go to the same field on Zendesk users and organizations, so a number a customer quotes from an old email still finds the right ticket.
Can Freshdesk satisfaction ratings be imported into Zendesk?
Not as Zendesk ratings. Zendesk's Satisfaction Ratings API says only the end user listed as the requester can create one, so a migration cannot create them for your customers. The Freshdesk score and comment are kept on the ticket as a custom field or a tag instead, where reports can still use them.
Do we need to ask Zendesk for anything before the import?
Yes, one thing. Zendesk's Users API says bulk user imports are off by default, and the account owner or an admin has to ask Zendesk Customer Support to enable them. Ask early: contacts and companies load before tickets, because every comment needs its author to exist first.
Will customers get emails from Zendesk while history loads?
They should not. Zendesk's Ticket Import documentation says no notifications go to users CC'd on imported tickets, and users can be created with skip_verify_email set to true so no verification email goes out. Notifications do start on later updates, so checking for stray emails is part of the sample.
Is there a limit on how long a ticket thread can be in Zendesk?
Yes. Zendesk's Ticket Comments API allows up to 5,000 comments on one ticket, public and private together. Threads that long are rare; if one of yours comes close, it is raised at mapping, before any load.
Try it on 100 of your own Freshdesk records
MigrateX is an AI migration platform with engineers reviewing every mapping, and it is SOC 2 Type II, GDPR and HIPAA compliant. Send us your rough ticket count, your custom field list and how many canned responses and scenarios you use. You get 100 of your records in Zendesk, free, and a fixed quote within 24 hours. Book a scoping call, or read the opposite route in Zendesk to Freshdesk: triggers, views and history.
Written by
Ayush BothraFounding 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.


