Zendesk to Front migration

Configuration such as automations, macros and views is not data, so it is set up again in Front. Anything with no equivalent in Front 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. Front's own Zendesk importer is free but not actively maintained. It brings inboxes (from Zendesk groups), contacts, conversations and messages, attachments, comments and assignments, mapping Pending, Hold, Solved and Closed tickets to archived conversations; it does not bring tags, teammates or rules, and Front recommends its migration partners for Zendesk moves. 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.

Private comments arrive through a separate endpoint that takes no date, so internal history needs its original time written in. Every Zendesk identity has to resolve to one Front contact with several handles rather than several contacts. Front's API allows 50 to 200 requests a minute by plan, per company, so on this route the destination sets the pace.

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.