Freshdesk to Zendesk Migration, and Back

In a Freshdesk to Zendesk migration the tickets move easily. Everything that made your helpdesk work has to be rebuilt, and that's the part that overruns.

Start free trial All Zendesk guides

Freshdesk to Zendesk migration: what moves and what doesn't

Moves with tooling: tickets, conversations, attachments, contacts, companies, knowledge base articles. Both vendors have importers and there's a healthy ecosystem of migration services.

Has to be rebuilt by hand: triggers and automations, macros or scenarios, views, SLA policies, business hours, ticket forms and custom fields, routing rules, integrations, and the reports everyone relies on.

That second list is the project. Anyone who quotes you a migration timeline based on data volume has not built the second list.

A realistic sequence

Audit first. List every automation, view and macro and mark it keep, change or drop. Teams routinely find a third is dead weight.

Rebuild in the new system before touching data. This is where the time goes.

Import historical data and check a sample properly, including attachments and threading order.

Run parallel for a week on one channel.

Cut over, keep the old system readable for a quarter.

Clean before you move

A migration is the one moment when everybody accepts a data cleanup, so use it.

Merge duplicate contacts before you export, because importing them creates two records in the new system and splits every future ticket. And measure your duplicate ticket rate while you're in there. Migrating a queue that runs a tenth duplicates means paying to import work that should never have existed, then paying seats to handle it again.

FAQ

Frequently asked questions

Is a help desk migration different in each direction?

The shape is the same either way. Whether you migrate from Zendesk or into it, tickets and contacts move with tooling, and automations, macros, views and SLA policies get rebuilt by hand.

How long does a Freshdesk to Zendesk migration take?

Data, days. Configuration and testing, usually four to eight weeks for an established setup. Plan for the second number.

Will we lose ticket history?

No, if you plan the import. Check threading order and attachments on a sample before you trust the whole set.

Should we migrate to fix ticket volume?

No. Volume follows your customers and your product. Removing duplicates reduces it, and that needs no migration.