Predicting the exact duration of your data migration is complex due to various factors impacting speed.
The migration involves two main steps: reading and writing. Reading retrieves records from the source help desk, while writing transfers them to the target help desk.
Factors affecting migration time include:
The duration required to complete each step is contingent upon various factors, including:
- Record Volume: The more records, the longer the migration.
- Attachments: Large or numerous attachments can extend retrieval.
- API Limits: Source and target help desks impose limits on requests.
- API Architecture: Some platforms require multiple requests per record.
Here's how each aspect relates to your migration process
Records: The quantity of records impacts migration time. More records mean longer durations, although high API limits can mitigate this.
Attachments: Attachment presence and size influence migration time, with larger or numerous attachments extending the process. Estimating accurately is challenging without prior knowledge of attachment quantity.
API Limits and Specifications: API limits determine the maximum requests allowed within a timeframe, varying by platform and subscription tier. Understanding API architecture nuances is vital for optimizing migration strategies.
In this hypothetical scenario, let's consider migrating from Zendesk to Freshdesk. Below is a summary of each API's functionality and the corresponding number of calls needed for effective data migration:
| Reading data | Writing data | ||
| Zendesk entities | API calls used | Freshdesk entities | API calls used |
| Groups |
Count - 1 call Fetch - 1 call per 100 groups |
Groups |
Search - 1 call per 100 groups Create - 1 call per group |
| Staff |
Count - 1 call Fetch - 1 call per 100 staff members + 1 call to get relations for each staff. |
Staff |
Search - 1 call per 100 staff members Create - 1 request to check if there’s a contact with the same email as the agent has. If there isn’t, then 1 request to create a contact + 1 request to update is as agent |
| Companies |
Count - 1 call Fetch - 1 call per 100 companies |
Companies |
Search - 1 call per 100 companies Create - 1 call per company |
| Contacts |
Count - 1 call Fetch 1 call per 100 contacts |
Contacts |
Search - 1 request per 100 contacts. If the same Zendesk contact is found on Freshdesk then +1 call to assign it to a company. If not, then we create a contact. Create - 1 request per contact |
| Tickets |
Count - 1 call Fetch - 1 call per 100 tickets + 1 call for each ticket to assign the relations |
Tickets | Create - 1 call per ticket + 1 call per reply |
| Knowledge base articles |
Count - 1 call Fetch - 1 call per 100 articles + additional requests to retrieve attachments |
Knowledge base articles | Create - 1 call per article |
| Categories |
Count - 1 call Fetch - 1 call per 100 category |
Categories |
Search - 1 call per 100 categories Create - 1 call per category |
| Folders |
Count - 1 call Fetch - 1 call per 100 folder |
Folders |
Search - 1 call per 100 folders Create - 1 call per folder |
Count - getting the total amount of records
Search - means that Migration Wizard checks records for duplicates before creating new ones. Only true if you already have records in the target help desk.
Fetch - retrieving records.
Create - creating a record in the target help desk.
Target Help Desk Considerations:
- Empty Target Help Desk: Migrating to a clean target help desk usually takes less time.
- Existing Data: If your target help desk already has tickets, contacts, or other data, the Migration Wizard will allocate additional time to verify and prevent duplication.
What you can do to fix it?
- Request API Limit Increase: Contact the new platform provider to request a temporary increase in API limits. This can speed up the migration process significantly. Make sure to address this well in advance of the migration date to prevent delays.
- Calculate Migration Duration: Gather information about API limits for both the source and target help desks. This will help you estimate the time needed for the migration process accurately.
Comments
0 comments
Please sign in to leave a comment.