Salesforce Service CloudZendesk

Salesforce Service Cloud to Zendesk migration

Migration specialists move your cases, email messages and case comments into Zendesk, check a sample with you first, and count every record on both sides.

Scope my migration

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
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Salesforce Service Cloud to Zendesk at a glance

Moving from Salesforce Service Cloud to Zendesk means turning each Case, and the emails, case comments and Chatter posts around it, into one Zendesk ticket thread. We import tickets with their original created and solved dates, carry files Case by Case, and move Knowledge into the Help Center. Salesforce keeps running until cutover, and a final delta sync 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 leaving Salesforce Service Cloud for Zendesk, whether the CRM stays in Salesforce or the whole company moves.
What does not move
Entitlement processes, flows, assignment rules, Omni-Channel routing and macros are configuration. We document each one so it can be set up again in Zendesk.
What sets the scope
Case count, emails and feed posts per Case, file volume, Knowledge languages, and how many queues and record types need a home in Zendesk.

What moves

What moves from Salesforce Service Cloud to Zendesk

Cases become tickets with their emails, case comments and Chatter posts merged into one thread, Accounts become organizations, Contacts end users, queues groups and Knowledge articles Help Center articles.

  • 14 included
Salesforce Service CloudZendesk
  • AccountsOrganizations

    Account names must be unique in Zendesk; duplicates are renamed by a rule you approve. The Account ID goes in external_id.

  • ContactsEnd users

    Linked to their organization. Contacts without an email still import, matched on the Contact ID.

  • Users who work CasesAgents

    Only Users who own or work Cases in scope become agents.

  • QueuesGroups

    Every agent also gets a default group, because Zendesk needs one for any assigned ticket.

  • CasesTickets

    Imported with the original created, updated and solved dates. The Case Number is kept in a custom field and as the external ID.

  • Case Status valuesTicket statuses

    Each value maps to new, open, pending, on-hold, solved or closed, or to a custom ticket status.

  • Record typesTicket forms

    One form per record type, with the fields that record type used.

  • Email messagesPublic comments

    Incoming emails are authored by the end user, outgoing ones by the agent, in date order.

  • Case commentsPublic comments or internal notes

    Published comments stay public; unpublished ones become internal notes.

  • Chatter feed posts on CasesInternal notes

    Text posts with their author and date. Posts visible to all users can be made public on request.

  • Files and attachmentsTicket attachments

    The latest version of each file linked to the Case, attached to the comment it belongs to.

  • Case custom fields and picklistsCustom ticket fields

    Picklists become drop-downs or multi-selects; shared values are prefixed so tags stay unique.

  • Knowledge articlesHelp Center articles

    Latest published version with translations per locale; draft-only articles become drafts.

  • Data categoriesCategories and sections

    The top two levels of a category group become Help Center categories and sections.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Salesforce Service Cloud to Zendesk as-is

Entitlement processes, flows, routing and macros are configuration, and Case History is read-only in Salesforce, so they are rebuilt in Zendesk or moved as notes on request.

Case History (field history)On request
In Zendesk: Internal noteSalesforce history objects can be read but not created. On request, each Case's change log is written as one internal note on the ticket.
Milestone resultsOn request
In Zendesk: Custom ticket fieldsMet or missed per milestone, for reporting on old tickets.
Entitlement processes and milestonesNot migrated
In Zendesk: SLA policiesConfiguration, set up again in Zendesk. Entitlement Management is in Professional, Enterprise, Performance and Unlimited with Service Cloud, so we list what yours does today.
Flows, assignment rules and Omni-Channel routingNot migrated
In Zendesk: Triggers, automations and routingRebuilt in Zendesk from the list we hand over, rule by rule.
Macros and Quick TextNot migrated
In Zendesk: MacrosDocumented with their actions and text so your team can rebuild the ones still in use.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Salesforce Service Cloud to Zendesk migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We agree which Cases move (all, or open plus a date range), how queues and record types map to groups and forms, and which Knowledge articles and languages come across.

    • Read-only Salesforce access

      You0.5 day

      You create a Salesforce integration user with API access and read permission on Cases, emails, feeds, files and Knowledge, and a Zendesk admin connection for the Ticket Import API.

    • Mapping and duplicate review

      Both1 day

      We send the field, status and owner mapping, plus the list of duplicate Account names and agents without a group. You approve or change it.

  2. Migration

    Day 3-7

    • Free sample migration

      MigrateX1 day

      100 of your records, picked for Cases that mix emails, case comments, feed posts and files, imported into Zendesk with their original dates.

    • You review the sample

      You1 day

      Your agents open the tickets and check thread order, internal notes, attachments and requesters before anything else moves.

    • Full import

      MigrateX2-3 days

      Organizations, end users, agents and groups first, then tickets through the Ticket Import API, Case by Case with their files, paced to your Salesforce allocation and Zendesk plan.

    • Delta sync

      MigrateX0.5 day

      Cases created or changed in Salesforce since the full import are brought across, matched on the Case ID kept on each ticket.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Cases against tickets per status, group and year, emails and comments against ticket comments, files against attachments, and every renamed organization.

    • Spot checks and sign-off

      You1-2 days

      Your leads check a random sample. Salesforce stays as it was, with a rollback plan ready, until you sign off and switch intake to Zendesk.

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

  • 3 solved
  • 4 handled
  1. 01SolvedMost critical

    One Salesforce case conversation lives in up to three objects

    The problem

    On a Salesforce Case, emails sit in EmailMessage, case comments in CaseComment and Chatter posts in FeedItem, each with its own visibility setting. Zendesk expects one ordered comment list per ticket, and the weekly Data Export cuts Chatter posts at 1,000 characters.

    How we handle it

    We read all three through the API, merge them by timestamp into one Zendesk comment list, and keep each one's visibility: emails become public comments, unpublished case comments and internal feed posts become internal notes. You check the order on the free sample.

    Source: Salesforce developer documentation, checked 14 Nov 2026

  2. 02Solved

    Zendesk will not assign a ticket to an agent without a group

    The problem

    In Salesforce a Case can be owned by a User with no queue at all. In Zendesk, a ticket can never be assigned to an agent without also being assigned to a group, so a user-owned Case has nowhere to land as it is.

    How we handle it

    Each queue becomes a group, and every agent gets a default group agreed with you, so user-owned Cases arrive assigned to the right agent and group. Cases owned by people who have left go to a group with no assignee.

    Source: Zendesk developer documentation, checked 14 Nov 2026

  3. 03Handled

    Zendesk organization names must be unique; Salesforce Account names need not be

    The problem

    Zendesk requires a unique name for each organization. A Salesforce org with two Accounts called Acme Ltd, one per region, cannot load them as two organizations under the same name.

    How we handle it

    We find duplicate Account names during export and agree a rule with you, such as adding the billing country or a parent Account name. The Salesforce Account ID goes in external_id, so later imports and syncs still match.

    Source: Zendesk developer documentation, checked 14 Nov 2026

  4. 04Handled

    Imported tickets carry no Zendesk metrics or SLAs, and triggers do not run

    The problem

    Zendesk does not support its metrics or SLAs on imported tickets, and triggers do not run on them. Your Salesforce entitlement and milestone history cannot become Zendesk SLA results.

    How we handle it

    Closed Cases import as closed with their original dates, and we tag every imported ticket. Milestone results you report on, such as first response met or missed, move into custom ticket fields, so old performance stays visible next to new Zendesk SLAs.

    Source: Zendesk developer documentation, checked 14 Nov 2026

  5. 05Handled

    Picklists become drop-down fields, and their tags cannot repeat

    The problem

    A Zendesk drop-down field stores each option as a tag, and tags cannot be reused across custom ticket fields. Salesforce picklists on different Case fields often share values such as Other or Billing.

    How we handle it

    We map every Case picklist to a Zendesk drop-down or multi-select field and prefix shared values with the field name, so each tag stays unique and reports still group cleanly. Record types become ticket forms with the fields each one used.

    Source: Zendesk developer documentation, checked 14 Nov 2026

  6. 06Solved

    Zendesk upload tokens expire after 60 minutes

    The problem

    A file reaches a Zendesk comment through an upload token, and the token is valid for 60 minutes. Uploading every Salesforce file first and attaching them later leaves expired tokens and comments without their files.

    How we handle it

    Each Case is processed as one unit: its files are downloaded from Salesforce and uploaded to Zendesk just before the comments that carry them are imported, and the reconciliation report counts files per ticket against the Case.

    Source: Zendesk developer documentation, checked 14 Nov 2026

  7. 07Handled

    Salesforce keeps every article version; the Help Center keeps one per language

    The problem

    Salesforce Knowledge stores draft, published and archived versions of each article, with archived versions in the article's __kav object. A Zendesk Help Center article has one current body per locale, and its draft flag can only be set when the article is created.

    How we handle it

    We move the latest published version of each article with its translations, and create articles that only exist as drafts as Help Center drafts. Archived versions stay in Salesforce or move as a text record on request. Data categories become Help Center categories and sections.

    Source: Salesforce developer documentation, checked 14 Nov 2026

Technical profile

What makes this route technical

Salesforce paces the export through your org's daily API allocation, and Zendesk paces the import through your plan's per-minute limit and the rules of its Ticket Import API.

Exporting from Salesforce: the export shares your org's API allocation
Salesforce gives an Enterprise Edition org 100,000 API calls a rolling 24 hours plus 1,000 per Salesforce licence, and 5,000 per licence on Unlimited and Performance. Bulk API calls count towards the same allocation as your live integrations.

Source: Salesforce developer documentation, checked 14 Nov 2026

Exporting from Salesforce: Bulk API 2.0 query allowance
Bulk API 2.0 runs up to 10,000 query jobs and returns up to 1 TB of results in a rolling 24 hours, so case, email and comment tables are exported in bulk rather than record by record.

Source: Salesforce developer documentation, checked 14 Nov 2026

Why the Salesforce Data Export Service is not enough
The Data Export Service runs weekly on Enterprise, Performance and Unlimited and monthly on other editions. It writes zip files of about 512 MB that are deleted 48 hours after the email, and it cuts Chatter posts and comments at 1,000 characters.

Source: Salesforce Help, checked 14 Nov 2026

Exporting from Salesforce: files are found through their links
A Salesforce file reaches a Case through a ContentDocumentLink, and a query on ContentDocumentLink must filter on Id, ContentDocumentId or LinkedEntityId. Files are listed per Case, then downloaded one by one.

Source: Salesforce developer documentation, checked 14 Nov 2026

Importing into Zendesk: the Ticket Import API keeps dates
Zendesk's Ticket Import API can set created_at, updated_at and solved_at, takes up to 100 tickets per bulk request, and sends no notifications to people copied on the imported tickets. Only admins can call it.

Source: Zendesk developer documentation, checked 14 Nov 2026

Importing into Zendesk: request limits by Suite plan
Zendesk allows 200 Support API requests a minute on Suite Team, 400 on Growth and Professional, 700 on Enterprise and 2,500 on Enterprise Plus. It also caps an account at 30 queued or running background jobs, which bulk imports use.

Source: Zendesk developer documentation, checked 14 Nov 2026

Importing into Zendesk: people and organizations in batches of 100
Zendesk's create_many endpoints take up to 100 users or 100 organizations per request. A user needs a name but not an email, and external_id holds the Salesforce Contact ID for matching.

Source: Zendesk developer documentation, checked 14 Nov 2026

Facts checked 14 Nov 2026 against Salesforce and Zendesk documentation. Each fact links its source.

Salesforce Service Cloud to Zendesk questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How do I get cases out of Salesforce with their emails and files?

Through the API, not the weekly export. MigrateX reads each Case with its EmailMessage, CaseComment and FeedItem records and the files linked to it, then imports them into Zendesk as one ticket. Salesforce's Data Export Service writes zip files that are deleted after 48 hours and cuts Chatter posts at 1,000 characters.

How long does a Salesforce Service Cloud to Zendesk migration take?

Plan for about 10 business days end to end. The export draws on your org's daily API allocation, shared with your live integrations, and the import is paced by your Zendesk plan's per-minute limit and its 30 background jobs. The free sample shows how fast your own Cases move before a cutover date is set.

Are original created dates and case numbers kept in Zendesk?

Yes. Zendesk's Ticket Import API sets created_at, updated_at and solved_at, so each ticket keeps the dates it had as a Case. The Salesforce Case Number also goes into a custom field and the external ID, so agents can still search for a case by its old number.

Do Salesforce Knowledge articles move to the Zendesk Help Center?

Yes. The latest published version of each Knowledge article moves with its translations, and data categories become Help Center categories and sections. Salesforce also keeps archived versions; those stay behind unless you ask for them as a record. Articles that were only ever drafts are created as Help Center drafts.

What happens to entitlements, milestones and SLA history?

Entitlement processes are configuration, so your team sets up Zendesk SLA policies in their place. Zendesk does not run metrics or SLAs on imported tickets, so old results cannot become Zendesk SLA data. On request, MigrateX copies each milestone's met or missed result into custom ticket fields for reporting.

Will Zendesk triggers email customers about imported tickets?

No. Zendesk does not run triggers on tickets created through the Ticket Import API and sends no notifications to people copied on them. Triggers do run on later updates, so we import closed Cases as closed and bring open Cases across close to cutover, when your agents take them over.

Do Chatter feed posts and internal case comments stay private?

Yes. Feed posts on a Case and case comments that were never published become internal notes in Zendesk, visible to agents only. Emails and published case comments become public comments. Your team checks this on the free sample, logged in as an end user, before the full import starts.

Can we keep Salesforce as our CRM and move only support to Zendesk?

Yes. A scoped migration moves Cases and their history, and copies the Accounts and Contacts those Cases need as Zendesk organizations and end users. Salesforce keeps every CRM record. Each Zendesk record carries its Salesforce ID, so an integration you add later can match the two systems.

What does a Salesforce Service Cloud to Zendesk migration cost?

It depends on the number of Cases and how much hangs off each one: emails, case comments, feed posts and files. Knowledge languages and the queues and record types to map add scope. MigrateX migrates 100 of your records as a free sample, and the fixed quote follows within 24 hours.

How it compares

Four ways to run Salesforce Service Cloud to Zendesk

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 Zendesk 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 Salesforce Service Cloud to Zendesk migration

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    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 Zendesk move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.