Kayako 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 Kayako, 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 (including the Ticket Import API), Marketplace apps or professional services; there is no built-in Kayako importer. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Kayako documents that it may enable per-minute rate limits on some actions and answers HTTP 429 with a Retry-After header when one is reached; it publishes no fixed numbers, so the read is paced on the responses it gives. 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.

Posts come back newest first with several channels mixed together, so every case is read in full and reordered before it moves. Customers with several identities have to be merged into one Zendesk user before their tickets are imported. This playbook follows Kayako's current v1 API, so the Kayako product and API version an account runs on is confirmed before the mapping starts.

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.