
ZendeskSalesforce Service Cloud
Zendesk to Salesforce Service Cloud migration
Migration specialists move your tickets, public replies and internal notes into Salesforce Service Cloud, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 14 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Zendesk to Salesforce Service Cloud at a glance
A Zendesk to Salesforce Service Cloud migration turns tickets into Cases, end users into Contacts and organizations into Accounts. The hard part is history: each public reply becomes an EmailMessage and each internal note an internal feed item, with original dates and authors. Zendesk stays live until the final delta sync, which copies anything changed during the run.
- Objects mapped
- 14
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- Support teams moving onto Salesforce Service Cloud because the rest of the company already runs on Salesforce.
- What does not move
- Triggers, automations, macros, views and SLA policies are configuration. We list each one for your admin to rebuild as flows, macros and entitlement processes.
- What sets the scope
- Ticket and comment volume, attachment count (Salesforce loads 200,000 file versions a day), Help Center size, brands, and the rules in your Salesforce org that must pause.
What moves
What moves from Zendesk to Salesforce Service Cloud
Tickets become Cases, end users Contacts, organizations Accounts and groups queues, with public replies as email messages, internal notes as internal feed items and attachments as Files.
- 14 included
| Zendesk | maps to | Salesforce Service Cloud | Status |
|---|---|---|---|
| Organizations | AccountsThe Zendesk organization ID goes in an external ID field; domains are kept in a text field. | Included | |
| End users | ContactsLoaded before Cases and linked to their Account, so every Case gets its ContactId and SuppliedEmail. | Included | |
| Agents | UsersMatched to existing Users by email. Agents who left become inactive Users, so their tickets keep an owner. | Included | |
| Groups | QueuesCreated as queues, at most 18 per Bulk API call, and linked to the Case object. | Included | |
| Tickets | CasesSubject, description, status, priority, channel (Case Origin) and owner (a user or a queue). Upserted on the Zendesk ticket ID. | Included | |
| Public replies | Email messagesEmailMessage on the Case, in order, with the original MessageDate and Incoming set for customer messages. | Included | |
| Internal notes | Chatter feed items (internal)FeedItem with Visibility InternalUsers and the original author and date. CaseComment with IsPublished false on request. | Included | |
| Side conversations | Chatter feed items (internal)Zendesk stores side conversation messages as events, not comments, so they are read separately and posted as internal feed items with participants and times. | Included | |
| Attachments and inline images | Files (ContentVersion)Published to the Case with FirstPublishLocationId; files on internal notes stay internal. | Included | |
| Ticket custom fields | Case custom fieldsDrop-downs become picklists and multi-selects become multi-select picklists, with every value added before the load. | Included | |
| Ticket forms | Case record typesOne record type per form, so each keeps its own page layout and picklist values. | Included | |
| Tags | Multi-select picklist or text fieldYour choice on the scoping call: a picklist for tags you report on, a text field for the rest. | Included | |
| Help Center categories and sections | Data categoriesOne category group, with sections as data categories (100 by default). | Included | |
| Help Center articles | Knowledge articlesPublished articles land published, drafts as drafts, translations as article translations. Needs Lightning Knowledge. | Included |
- OrganizationsAccounts
The Zendesk organization ID goes in an external ID field; domains are kept in a text field.
- End usersContacts
Loaded before Cases and linked to their Account, so every Case gets its ContactId and SuppliedEmail.
- AgentsUsers
Matched to existing Users by email. Agents who left become inactive Users, so their tickets keep an owner.
- GroupsQueues
Created as queues, at most 18 per Bulk API call, and linked to the Case object.
- TicketsCases
Subject, description, status, priority, channel (Case Origin) and owner (a user or a queue). Upserted on the Zendesk ticket ID.
- Public repliesEmail messages
EmailMessage on the Case, in order, with the original MessageDate and Incoming set for customer messages.
- Internal notesChatter feed items (internal)
FeedItem with Visibility InternalUsers and the original author and date. CaseComment with IsPublished false on request.
- Side conversationsChatter feed items (internal)
Zendesk stores side conversation messages as events, not comments, so they are read separately and posted as internal feed items with participants and times.
- Attachments and inline imagesFiles (ContentVersion)
Published to the Case with FirstPublishLocationId; files on internal notes stay internal.
- Ticket custom fieldsCase custom fields
Drop-downs become picklists and multi-selects become multi-select picklists, with every value added before the load.
- Ticket formsCase record types
One record type per form, so each keeps its own page layout and picklist values.
- TagsMulti-select picklist or text field
Your choice on the scoping call: a picklist for tags you report on, a text field for the rest.
- Help Center categories and sectionsData categories
One category group, with sections as data categories (100 by default).
- Help Center articlesKnowledge articles
Published articles land published, drafts as drafts, translations as article translations. Needs Lightning Knowledge.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Zendesk to Salesforce Service Cloud as-is
Triggers, macros, SLA policies and ticket audits are configuration or history that Salesforce cannot import as records, so they are rebuilt or stay in your Zendesk export.
- Satisfaction ratingsOn request
- In Salesforce Service Cloud: Custom object on CaseScore, comment and date per ticket, kept for reporting.
- On request
- BrandsOn request
- In Salesforce Service Cloud: Case field or record typeAgreed on the scoping call for multi-brand Zendesk accounts.
- On request
- Triggers and automationsNot migrated
- In Salesforce Service Cloud: Flows and assignment rulesConfiguration, rebuilt by your admin or partner from the list we hand over.
- Not migrated
- MacrosNot migrated
- In Salesforce Service Cloud: Salesforce macros or Quick TextEach macro is documented with its actions so it can be rebuilt.
- Not migrated
- SLA policiesNot migrated
- In Salesforce Service Cloud: Entitlement processes and milestonesSalesforce's SlaProcess object supports query and describe, not create, so entitlement processes are set up in Setup.
- Not migrated
- Ticket auditsNot migrated
- In Salesforce Service Cloud: Case HistorySalesforce history objects are read-only through the API. The final state of each ticket moves; the change log stays in your Zendesk export.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Zendesk to Salesforce Service Cloud migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree where comments land, which brands, date ranges and Help Center sections move, and how users who sit in several Zendesk organizations map to Accounts.
Connect Zendesk and a sandbox
You0.5 dayYou approve an OAuth client in Zendesk and create a Salesforce integration user with API access and the two audit field permissions. The first loads go into a sandbox, not production.
Field, picklist and rule review
Both1 dayTicket fields to Case fields, statuses to Case Status values, groups to queues, forms to record types. Your admin marks the validation rules, duplicate rules and flows to pause.
Migration
Day 3-7
Free sample in the sandbox
MigrateX1 day100 of your records, picked for the longest threads, largest files and most internal notes, loaded into the sandbox end to end.
You review the sample
You1 dayYour team opens the Cases as a support rep and as a portal user, and checks email order, internal notes, owners and dates.
Full load into production
MigrateX2-3 daysAccounts, Contacts, Users and queues first, then Cases upserted on the Zendesk ticket ID, then emails, feed items and files, paced to your org's API allocation.
Delta sync
MigrateX0.5 dayTickets changed in Zendesk since the full load are upserted on the same external ID, so nothing is created twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayTickets against Cases per status, queue and year, comments against emails and feed items, attachments against files, plus every note that was split.
Spot checks and sign-off
You1-2 daysYour leads check a random sample, the paused rules go back on, and Zendesk stays read-only with a rollback plan ready until you sign off.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 4 solved
- 3 handled
- 01SolvedMost critical
Every Zendesk comment needs one of three Salesforce homes
The problem
Zendesk keeps a ticket's public replies and internal notes in one comment list. Salesforce has three places for them: CaseComment caps each body at 4,000 bytes and only IsPublished can change after insert; EmailMessage needs Email-to-Case or Enhanced Email and cannot be edited once it is not a draft, apart from IsExternallyVisible and custom fields; FeedItem accepts only a short list of HTML tags.
How we handle it
Public replies become EmailMessage records on the Case, with the original MessageDate and Incoming set for customer messages. Internal notes become internal feed items. If your reports already use case comments, notes go to CaseComment instead and anything over 4,000 bytes is split into numbered parts. You see the result on the free sample first.
Source: Salesforce developer documentation, checked 14 Nov 2026
- 02Solved
Internal notes can surface in your customer portal
The problem
In Salesforce, IsExternallyVisible on EmailMessage defaults to true, and a FeedItem with Visibility AllUsers can be seen by external users. A Zendesk internal note loaded with the defaults can end up in front of a customer.
How we handle it
We set visibility on every record instead of trusting defaults: internal notes go in as InternalUsers feed items, and files attached to them get an internal ContentDocumentLink. Your team checks the sample logged in as a portal user before the full load.
Source: Salesforce developer documentation, checked 14 Nov 2026
- 03Solved
Original dates and authors have to be set on insert, or never
The problem
Salesforce lets an integration user set CreatedDate, CreatedById, LastModifiedDate and LastModifiedById only when a record is created, and only with the Set Audit Fields upon Record Creation and Update Records with Inactive Owners permissions. A Case loaded without them shows the migration date for ever.
How we handle it
Both permissions go on the integration user before the sample run. Feed items keep their original author and date through the Insert System Field Values for Chatter Feeds permission, and agents who have left are created as inactive Users so their history keeps a real owner.
Source: Salesforce Help, checked 14 Nov 2026
- 04Handled
Validation, duplicate and auto-response rules reject API loads
The problem
Salesforce validation rules apply to records created through the API, a duplicate rule set to block stops a Contact from being inserted, and with an active auto-response rule a Case created through the API must carry SuppliedEmail. A live org usually has all three.
How we handle it
Your admin and our engineer list every validation rule, duplicate rule, flow, assignment rule and auto-response rule on Case, Contact and Account during scoping. We agree which ones pause for the load, set SuppliedEmail from the requester, and switch them back on after the delta sync.
Source: Salesforce Help, checked 14 Nov 2026
- 05Handled
Files load against a daily cap of 200,000 versions
The problem
Salesforce Enterprise, Unlimited and Performance orgs can publish at most 200,000 new ContentVersion records in 24 hours. An account with 600,000 Zendesk attachments needs at least three days of file loading on its own.
How we handle it
We count attachments by ticket during export, start the file pass early, and run it beside the Case load. Each file is created with FirstPublishLocationId set to its Case, so it is shared with the record in the same transaction.
Source: Salesforce developer documentation, checked 14 Nov 2026
- 06Handled
Help Center sections meet the 100 data category default
The problem
Lightning Knowledge is available in Essentials and Unlimited editions with Service Cloud, and for an additional cost in Professional, Enterprise, Performance and Developer editions. Salesforce sets a default maximum of 100 data categories, which a Help Center with many sections can exceed.
How we handle it
We check your Knowledge licence and count Help Center categories and sections on the scoping call. Sections map to data categories; where there are more than 100, we either group them or you ask Salesforce support to raise the limit before the article load.
Source: Salesforce Help, checked 14 Nov 2026
- 07Solved
Zendesk API tokens stop working on 30 April 2027
The problem
Zendesk will permanently deactivate API tokens on 30 April 2027, and since 27 October 2026 existing accounts can no longer create new ones. An export built on a token can stop halfway through a long project.
How we handle it
MigrateX connects to Zendesk with OAuth, so the export and the final delta sync do not depend on API tokens.
Source: Zendesk developer documentation, checked 14 Nov 2026
Technical profile
What makes this route technical
Zendesk paces the export at 10 incremental export calls a minute, and Salesforce paces the load through your org's daily API allocation and its rules for comments, files and audit fields.
- Exporting from Zendesk: 10 export calls a minute
- Zendesk's incremental export endpoints accept 10 requests a minute (30 with the High Volume API add-on) and return up to 1,000 tickets a page. Ticket events only flag that a comment exists unless the comment_events sideload is requested.
Source: Zendesk developer documentation, checked 14 Nov 2026
- Exporting from Zendesk: comments come 100 at a time
- The Zendesk ticket comments endpoint returns at most 100 comments a page, and each comment's public flag is false for an internal note. Long threads take several calls per ticket.
Source: Zendesk developer documentation, checked 14 Nov 2026
- Exporting from Zendesk: archived tickets hide from list calls
- Zendesk archives a ticket 120 days after it is closed, and the Listing Tickets, Count Tickets and Listing Ticket Audits endpoints do not return archived tickets. A full inventory has to come from the incremental export.
Source: Zendesk Help Center, checked 14 Nov 2026
- Exporting from Zendesk: side conversations are not comments
- Zendesk side conversations need the Collaboration add-on, and their messages are recorded as events on the side conversation, not as ticket comments. A comments-only export leaves them behind.
Source: Zendesk developer documentation, checked 14 Nov 2026
- Importing into Salesforce: Bulk API 2.0 allowances
- Salesforce allows 150,000,000 records a rolling 24 hours through Bulk API 2.0 and 15,000 batches a rolling 24 hours, shared with the original Bulk API. A job takes up to 150 MB, and Salesforce advises uploading no more than 100 MB because base64 adds about 50%.
Source: Salesforce developer documentation, checked 14 Nov 2026
- Importing into Salesforce: the daily API allocation is per org
- An Enterprise Edition org gets 100,000 API calls a rolling 24 hours plus 1,000 per Salesforce licence, and Bulk API calls count towards it. The migration shares that allocation with every integration already running in the org.
Source: Salesforce developer documentation, checked 14 Nov 2026
- Importing into Salesforce: the Data Import Wizard cannot load Cases
- Salesforce's Data Import Wizard handles accounts, contacts, leads, solutions, campaign members and custom objects, up to 50,000 records. Cases are not on that list. Data Loader can load Cases, for 5,000 to 5 million records, on Enterprise, Unlimited, Performance and Developer editions.
Source: Salesforce Help, checked 14 Nov 2026
- Importing into Salesforce: 18 queues per Bulk API call
- In Salesforce a queue is a Group record whose Type is Queue, and the Bulk API cannot insert or update more than 18 queues at once. Zendesk groups are created as queues in small batches before any Case is loaded.
Source: Salesforce developer documentation, checked 14 Nov 2026
Facts checked 14 Nov 2026 against Zendesk and Salesforce documentation. Each fact links its source.
Zendesk to Salesforce Service Cloud questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
What moves from Zendesk to Salesforce Service Cloud?
Tickets move as Cases, end users as Contacts, organizations as Accounts, agents as Users and groups as queues. Public replies arrive as email messages, internal notes as internal feed items, attachments as Files, custom fields as Case fields and Help Center articles as Knowledge articles. Side conversations come over as internal feed items.
How long does a Zendesk to Salesforce Service Cloud migration take?
Our default plan is about 10 business days end to end. On this route the export is paced by Zendesk's 10 incremental export calls a minute and its per-ticket comment calls, and the load by your org's daily API allocation and the 200,000 file versions Salesforce accepts in 24 hours. The free sample shows the real pace.
Where do Zendesk comments go in Salesforce?
Public replies become EmailMessage records on the Case, so they read as the email thread your customer saw. Internal notes become feed items visible to internal users only. If your team reports on case comments, notes can go to CaseComment instead, split at Salesforce's 4,000-byte limit. We agree the rule with you before the sample.
Do original ticket dates, authors and assignees carry over?
Yes, when the integration user has Set Audit Fields upon Record Creation and Update Records with Inactive Owners before the first insert. Salesforce accepts original CreatedDate and CreatedById only when a record is created. Agents who have left are created as inactive Users, so their old Cases keep a named owner.
Will the migration email our customers or fire Salesforce automation?
Not if the rules are paused. Your admin and our engineer list the auto-response rules, assignment rules, flows and email alerts on Case before the load and switch them off for the production run. On the sandbox sample we confirm that no customer receives an email, and everything goes back on after the delta sync.
Do macros, triggers and SLA policies move to Service Cloud?
No, they are rebuilt. Triggers and automations become flows or assignment rules, macros become Salesforce macros or Quick Text, and SLA policies become entitlement processes with milestones, which the Salesforce API cannot create. We hand your admin a list of every rule in scope, with what it does today.
Does the Zendesk Help Center move to Salesforce Knowledge?
Yes, if your org has Lightning Knowledge. Lightning Knowledge is available in Essentials and Unlimited editions with Service Cloud, and for an additional cost in Professional, Enterprise, Performance and Developer editions. Articles keep their published or draft state and their translations, and Help Center sections become data categories. Article URLs change, so we hand over a map of old to new addresses for redirects.
Are side conversations and satisfaction ratings kept?
Side conversations are kept as internal feed items on the Case, with participants and times, because Zendesk stores their messages as events rather than comments. Satisfaction ratings can move on request into a custom object linked to each Case, so past scores stay available for reporting.
What does a Zendesk to Salesforce Service Cloud migration cost?
The price is set by what moves: tickets and the comments and attachments on them, the size of your Help Center, the number of brands and forms, and how many Salesforce rules need mapping. You get a fixed quote within 24 hours of the scoping call, after a free sample migration of 100 of your records.
How it compares
Four ways to run Zendesk to Salesforce Service Cloud
The same data, moved four different ways. This is what changes between them.
Object coverage (cases, emails, comments, files, Knowledge)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Linked records, files and knowledge often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Public replies vs internal notes
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Attachments
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the Salesforce Service Cloud cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a Zendesk to Salesforce Service Cloud migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your Salesforce Service Cloud move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.




