How long will it take to migrate my data?
Predicting the exact time it will take to migrate your data is quite difficult. That's because there are many factors that influence the speed of migration.
The procedure of migrating data between help desks boils down to two steps: reading and writing. The Migration Wizard first retrieves (reads) all records you told it to migrate from the source help desk. And then moves them over (writes) to the source help desk.
The time it will take to complete each step depends on the following factors:
- The total number of records you’re migrating.
- The number and size of attachments.
- API limits of the source and target help desk.
- Specifications of the API.
- Your target help desk.
Here’s what each of the above has to do with your migration.
The more records you have in your source, the longer it might take to migrate them. However, if you have high API limits, then this shouldn’t be much of an issue.
The more and larger the attachments, the longer it will take to retrieve them. Unfortunately, there is no way to find out how many attachments there is in the source help desk to estimate how much time it will take to migrate them.
3. API limits
An API limit is the number of requests that can be done within a certain time frame. For instance, the Essential plan on Zendesk allows 10 requests per minute. That means that you can migrate roughly 10 records per minute.
Each help desk platform allows different API limits. Moreover, the limits you get depend on your pricing plan. You can contact your help desk providers on both ends and ask to temporarily increase the limits to speed up the migration.
4. API specifications
Some platforms allow fetching a ticket with all comments using just one API request. Other platforms, however, need to send separate requests to fetch each record. That means one call to fetch a ticket, another call to fetch its comment and so on.
This depends solely on how the help desk vendor developed the API.
5. Your target help desk
If you’re migrating to a clean target help desk, then it will take less time. If you already have some tickets, contacts, etc. in your target help desk, the Migration Wizard will take its time to double-check them to avoid duplicates.
What you can do
To get an approximate duration of your data migration you can try to calculate it based on the API limits. Let's assume that you have 1500 records and 10 API requests per minute on your source help desk.
10 API requests per minute * 60 minutes = 600 requests which means you can read roughly 600 records per hour.
1500 total records divided by 600 records per hour equals 2.5 hours to read all your tickets. Remember, that it might take longer due to the factors mentioned above. But this way you will know what to expect.
Hopefully, this article answered your question. If not, feel free to contact us.