Zendesk to JSM migration limit size

Hi

Plan is move 150+ k tickets into JSM. What could be best way to sync them into JSM from Zendesk?

Urmo

Hi @urmo

When doing this type of ticket movements we suggest building the config to start and test with some tickets first, to make sure that everything you will need on the remote side is there. Sometimes is easy to miss a custom field or to make sure that a ticket can be created on a specific status.

Once you done the POC with a couple of test ticket, you will need to start doing the bulk movement.

For that Exalate has a built in tool that its called Bulk Exalate, meaning that you will create a trigger on Exalate that matches all the issues you want to Exalate and then click on Bulk Exalate on the trigger, there is no need for the trigger to be ON to start a bulk Exalate.

I do want to comment on a limitation with the Zendesk API, they do not allow to search for more than 1000 issues at the time. If the trigger you created finds more than 1000 issues, Zendesk will return an error and the it will not execute.

So you will need to make sure that the triggers are not for more than 1000 issues at the time, a good approach would be to create triggers for a specific type/group and then a specific month.
Ex: support_type:agent updated>=“2026-02-01” updated<="2026-02-28
Making sure that the search does not return over 1000 issues.

Let me know if you have any follow up questions.

Best
Kevin