Skip to content
DataGrine home

What is a helpdesk migration? What moves, what does not, and how it runs

A helpdesk migration moves your support data from one platform to another: companies, contacts, tickets or conversations with their replies and internal notes, tags, attachments and knowledge base articles, together with the relationships between them. The configuration around that data, such as triggers, macros, views and SLAs, does not migrate; it is rebuilt on the new platform.

By the DataGrine team · Updated · 3 min read

Key takeaways

  • Data migrates; configuration is rebuilt. Plan for both.
  • The relationships matter as much as the records: which ticket belongs to which company, who wrote which reply, and when.
  • There are three ways to do it: a built-in importer, a self-serve tool, or a managed migration.

What moves

ObjectWhat travels with it
CompaniesTheir fields, and the contacts and tickets attached to them
ContactsEmail, phone, external ID and custom fields, matched rather than merged blindly
Tickets or conversationsStatus, priority, assignee, team, custom fields, tags
Replies and internal notesIn order, with author and date, notes kept internal
AttachmentsAs files, on the message they belong to
Knowledge baseCategories, sections or collections, articles and translations

Three ways to migrate a helpdesk

RouteFitsWatch out for
The destination’s built-in importerSimple, one-off moves within its limitsWhat it leaves out. Intercom’s Zendesk importer, for example, is aimed at fewer than 150,000 tickets and does not bring tags or side conversations.
A self-serve migration toolTeams with time to map and test themselvesYou own the mapping, the testing and the failed records.
A managed migrationLarge or messy histories and fixed datesWho actually does the work. Ask for a written mapping and a sample run first.

How a migration runs

  1. 1.Connect both platforms with API credentials.
  2. 2.Map every field and every value, in writing.
  3. 3.Run a sample of your own records and check it in the destination.
  4. 4.Run the full migration while the team keeps working.
  5. 5.Cut over with a delta run that carries only what changed since.
  6. 6.Reconcile record counts on both sides.

On DataGrine you can run these steps self-serve on the platform, or have the migration team handle them end to end, with 24/7 support either way. Each stage is covered in the helpdesk migration checklist. The same process runs whichever pair you are moving between, including Zendesk to Freshdesk, Freshdesk to Zendesk, Salesforce Service Cloud to Intercom and HubSpot to Intercom.

Questions

Asked about this, often.

Is a helpdesk migration the same as an export and import?

Not quite. An export file is a snapshot, and few helpdesks import another vendor’s export format. A migration reads from one platform’s API and writes to the other’s, keeping the links between companies, contacts and tickets, and can run again at cut-over to catch what changed.

Can you migrate between any two helpdesks?

Generally yes, as long as both have an API that exposes the data. See the [platforms DataGrine migrates](/supported-products).

Do triggers, macros and views migrate?

No. They are configuration rather than data, so they are listed before the migration and rebuilt on the new platform.

Let’s move your data forward.

Tell us where you are moving from and to. Run it yourself on the DataGrine platform or let our migration team handle it end to end, with 24/7 support either way.

  • A written mapping document before anything moves
  • A sample migration you review before the live run
  • Delta sync at cut-over and rollback per run
  • 24/7 premium support until you sign off