Freshdesk to Zoho Desk migration

Configuration such as automations, macros and views is not data, so it is set up again in Zoho Desk. Anything with no equivalent in Zoho Desk 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.

Yes. Zoho Desk's Zwitch migrates Freshdesk companies, users, tickets with threads, comments and attachments, and Solutions, from Freshdesk backup files plus the Freshdesk API. Zoho documents that it runs in two phases roughly two weeks apart and might take a minimum of two weeks, migrates into one department per pass, skips deleted contacts and their tickets, and needs agent emails to match exactly. 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.

Zwitch might take at least two weeks across two phases, so the cut-over date is planned around it. Agent emails must match exactly and every agent needs access to the target department before the run. Zoho advises disabling any Zoho CRM or Salesforce integration during the migration to avoid duplicate contacts and accounts.

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.