Zendesk to Salesforce Data Migration
A Zendesk to Salesforce data migration isn't an export problem in either direction. The hard part is the fortnight when both systems are live.
Decide the scope before the mapping
The instinct is to move everything. Resist it, because history is the most expensive and least used part of any helpdesk migration.
Three scopes, in increasing order of pain:
Agree the scope with the people who will actually be asked for old records. Legal and finance, usually, not support.
Zendesk to Salesforce data migration: what maps cleanly
| Zendesk | Salesforce Service Cloud | Notes |
|---|---|---|
| Ticket | Case | The core mapping. Status and priority values need translating. |
| End user | Contact | Straightforward, subject to matching on email. |
| Organization | Account | Usually clean for B2B, meaningless for consumer desks. |
| Ticket comments | Case comments or feed items | Public and internal must stay distinguishable. |
| Attachments | Files linked to the case | Volume here drives migration time more than anything. |
| Custom fields | Custom fields on Case | One to one only if types line up. Drop lists need care. |
| Help centre articles | Knowledge articles | Content moves, theming and structure do not. |
What doesn't map at all
This is the list nobody sends you at the start of the project.
closed_by_merge tag mean nothing on the other side, so merged pairs land as an odd closed record unless you handle them.The parallel period is the risk
Almost nobody cuts over instantly. There's a window, days or weeks, when both systems can receive work, and that window is where the damage happens.
A customer replies to an old Zendesk notification while your new address routes to Salesforce. Now the same conversation exists as an open ticket in one system and a new case in the other. Two agents, two answers, one confused customer. This is the single most common failure of a helpdesk migration and it's entirely predictable.
Three controls, all boring, all effective. Freeze new ticket creation in the source system on a stated date and forward its inbound mail to the new one. Run a delta migration for everything created or updated after the initial export. And before go live, deduplicate the source, because every duplicate you migrate becomes two cases you now maintain in a system where merging works differently.
How to actually move the data
Three routes, and the choice is mostly about volume and how weird your data is.
Whichever you pick, test on a subset into a sandbox and have real agents open twenty migrated cases and tell you what looks wrong. They will find things no mapping document catches. See Zendesk migration for the platform agnostic checklist and Zendesk vs Salesforce if the decision itself is still open.
Cutover week, in order
The plan that works is dull and specific. Write it down and give each line an owner.
Then leave the old system dormant for a quarter before you cancel it. The licence is cheaper than the panic.
Frequently asked questions
Is this the same as a Service Cloud migration?
Yes. A Zendesk Service Cloud migration is this migration under Salesforce's product name, since Service Cloud is the support half of Salesforce.
How long does a Zendesk to Salesforce data migration take?
Data movement is days. The project is weeks to months, because rebuilding automations, SLAs and reporting is the real work, not the export.
Do ticket IDs survive the migration?
No. Salesforce assigns its own case numbers. Store the original Zendesk ID in a custom field so customers quoting old numbers can still be found.
Can we migrate from Salesforce to Zendesk instead?
Yes, the same mapping runs in reverse and the same gaps apply. Automation, SLA and reporting logic still has to be rebuilt by hand.
What causes duplicate cases during a migration?
The parallel period. Customers reply to old notifications while new mail routes elsewhere, so one conversation becomes a ticket and a case.
Should we migrate closed tickets?
A rolling window of twelve to twenty four months suits most teams. Full history is worth it only when regulation requires it, and an archive often serves better.
Migrate a clean queue
Duplicates you migrate become duplicates you maintain. Ticket Merger clears them out of Zendesk before the export, and keeps the new queue clean after.
Start free trial14-day free trial. No credit card required.