Migrate from Zendesk to Freshdesk

Zendesk Organizations map to Freshdesk Companies. 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.

Zendesk end-users (requesters) map to Freshdesk Contacts. 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.

Zendesk agents map to Freshdesk agents. 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.

Zendesk Tickets map to Freshdesk Tickets. 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.

Zendesk Brands (multi-brand routing, separate email addresses, and independent Help Centers) have no direct Freshdesk equivalent. 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.

Zendesk Views (saved ticket filters with conditions, columns, and sort order) map to Freshdesk Custom Views. 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.

Zendesk Macros (canned reply templates with variable substitution) map to Freshdesk Canned Responses. Macro actions and conditions transfer as available. Variable placeholders like {{ticket.requester.name}} map to Freshdesk's {{contact.name}} syntax. Complex macros with conditional branching may require simplification or manual recreation in Freshdesk depending on the target plan tier.

Zendesk Triggers (event-driven rules that fire immediately on ticket events) do not migrate as active automation code. We export every trigger definition including conditions, field references, and actions, then deliver a written inventory recommending the equivalent Freshdesk Scenario Automation configuration. Freshdesk's Scenario Automations combine event-based and time-based logic differently from Zendesk's separate Trigger and Automation split, so a trigger-and-automation pair in Zendesk may map to a single Scenario in Freshdesk. The admin rebuilds them post-migration.

Zendesk Automations (time-based rules that run hourly on up to 1,000 tickets) do not migrate as automation code. We document the automation definition including the time condition, target criteria, and actions, then recommend a Freshdesk Scenario Automation with time-based triggers. The 500-active-automation cap and 65KB size limit from Zendesk are noted as upper bounds on what the Freshdesk equivalent must handle. We do not rebuild automations in Freshdesk; the customer receives a written map for their admin to configure.

Zendesk SLA Policies (first-response and resolution targets per plan or ticket type) map to Freshdesk SLA Policies. SLA definitions migrate as structured records. First-response time targets map to Freshdesk first-response SLA; resolution time targets map to Freshdesk resolution SLA. The mapping assumes the customer has SLA Policies enabled on their Freshdesk plan tier.

Zendesk Tags (flat string labels on tickets, users, and organizations) map to Freshdesk Tags. We import all tag assignments across Tickets, Contacts, and Companies. Tag naming collisions are handled by appending a suffix if the same tag name exists with a different type in Freshdesk. Tags are used for filtering and reporting post-migration.

Zendesk Help Center articles map to Freshdesk Knowledge Base articles. Section hierarchy in Zendesk maps to Category and Folder structure in Freshdesk. Article HTML content, translations, and attachments transfer via the Freshdesk content API. We pre-create Freshdesk categories and sections before article import to avoid the duplication bug reported in Freshworks community forums where articles were copied four times during migration. Dynamic Content items (multilingual variants) map to Freshdesk article locale fields where supported.