Freshdesk to Zendesk migration

Configuration such as automations, macros and views is not data, so it is set up again in Zendesk. Anything with no equivalent in Zendesk is listed in the written mapping, and you choose what happens to it before anything moves.

Yes. Run it self-serve on the DataGrine platform, or let our migration team handle it end to end. Either way you get 24/7 premium support until the migration is signed off.

No. We only read from Freshdesk, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

No. Zendesk's help article on migrating data into Zendesk points to CSV import for users and organizations, the API, Marketplace apps or professional services; there is no built-in Freshdesk importer. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Freshdesk: 100 calls a minute on Growth, 400 on Pro and 700 on Enterprise, 50 on trial accounts, shared by every integration on the account; ticket list calls are capped at 40, 100 and 200 a minute respectively. Runs are paced to stay inside that limit, which is why large accounts move in a full run first and a delta at cut-over.

Dependent dropdowns need a decision between conditional fields and flattened lists before the mapping is signed off. Freshdesk's shared API allowance sets how fast history can be read, and View a Ticket returns only ten conversation entries. Imported tickets do not count in Zendesk metrics or SLAs, so historical reporting must be planned separately.

It depends on how many records move and whether you run the migration yourself or have the DataGrine team run it. You get a quote once the records in scope are counted, before anything moves.