How to speed up the Full Data Migration

Full Data Migration is a comprehensive process that cannot be completed swiftly; it requires careful consideration due to the substantial volume of data involved.

Over time, as you utilize your current help desk platform, your data accumulates significantly. Therefore, when transitioning to a new help desk, the goal is to preserve all data comprehensively, not just individual records.

The duration of Full Data Migration can vary significantly, ranging from a few hours to up to a week. However, migration speed depends on various factors, including:

1. The number and size of attachments.
2. API limits on both source and target platforms.
3. API specifications.
4. Characteristics of your target help desk.
5. The processing speed of data by server infrastructure.

To speed up Full Data Migration, several strategies can be employed. For example, consider migrating open and closed tickets separately or excluding historical data. However, such measures may offer only marginal improvements, and you may still experience wait times during the migration process.

A highly recommended step is to increase API limits on both source and target platforms. Contact the support teams of both solutions well in advance of migration to request temporary increases in API limits.

Additionally, you can opt for an automated approach by selecting the "Skip attachments" option. This simplifies the migration process by focusing solely on transferring core customer data, which can be selected during the Demo Migration at the "Select Object" step.

The automated option is available if your source platform is: Zendesk, Freshdesk, Freshservice, Jira Service Management, Help Scout, Gorgias, Zoho Desk, Reamaze, Intercom, Kayako, ServiceNow, HubSpot Service Hub, or TenderSupport. Other platforms are also supported.