Zendesk to Gorgias migration

Configuration such as automations, macros and views is not data, so it is set up again in Gorgias. Anything with no equivalent in Gorgias 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 Zendesk, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

Yes. Gorgias's Historical Imports (all Helpdesk plans, admins only) bring tickets, macros, users, tags and ticket fields from Zendesk: up to two years of recent data, at about 720 tickets an hour, with continuous sync afterwards. It does not bring ticket attachments or rating information, splits tickets over 250 comments, keeps only open and closed statuses, and allows one import per Zendesk domain. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Zendesk Support API: 200 requests a minute on Team, 400 on Professional, 700 on Enterprise and 2,500 on Enterprise Plus or with the High Volume add-on; incremental export endpoints are limited to 10 requests a minute (30 with High Volume). 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.

History older than two years, attachments and ratings need a second pass through the Gorgias API, with every message given a sent date so nothing is emailed. Pending work has to stay findable once it lands as closed, through the pending tag and a view. Gorgias's API allows 40 requests per 20 seconds for an API key integration, so any API pass on a large history is long and paced.

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.