Skip to content

Migration guide · Customer Service

Zendesk or Freshdesk to Salesforce Service Cloud migration

Zendesk / FreshdeskSalesforce Service Cloud

Short answer

Migrating from Zendesk or Freshdesk to Salesforce Service Cloud moves tickets, comments, users, organizations and knowledge articles into Salesforce cases, contacts, accounts and Knowledge, so service teams work on the same platform as sales and operations.

Why firms make this move

Firms that already run Salesforce often consolidate their help desk into Service Cloud to give agents the full client relationship, use the same automation and reporting, and remove an integration. The work covers ticket history, routing, SLAs (entitlements), macros and the customer-facing help centre.

What moves

  • Tickets with comments and attachments
  • Users and organizations
  • Knowledge articles
  • Macros as quick text or actions
  • Fields, statuses and tags

How the data maps

FromTo
TicketCase
CommentCase comment or email message
UserContact
OrganizationAccount
ArticleKnowledge article
SLA policyEntitlement and milestone

See the field-by-field map ↓

What to watch out for

  • Ticket history volume and attachment storage
  • Rebuilding routing, SLAs and macros
  • Help centre URLs and redirects
  • Integrations that created tickets

How Vantage Point runs the migration

  1. Inventory and design case processes
  2. Map fields and statuses
  3. Migrate history, attachments and articles
  4. Rebuild routing, entitlements and automation
  5. Redirect help centre URLs
  6. Go live and hypercare

Typical timeline

Typically 6 to 10 weeks.

Frequently asked questions

Does ticket history migrate?

Yes, including comments and, where needed, attachments.

Can we use Omni-Channel routing?

Yes. Routing is rebuilt with Omni-Channel and queues to match your team structure.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Zendesk or Freshdesk to Salesforce Service Cloud: field by field

10 mappings we start from on this migration, 7 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Ticketsubject / description CaseSubject / Description req direct
Ticketstatus / priority CaseStatus / Priority req picklist map
Ticketrequester CaseContactId req lookup
OrganizationOrganization AccountName direct
Ticketassignee / group CaseOwnerId (user or queue) lookup
Ticket commentPublic / private comments CaseComment / EmailMessage— manual review Private comments become internal comments.
Tickettags / custom fields CaseCustom fields picklist map
MacroMacros Quick text / macros— rebuild
Help Center articleArticles Knowledge article— direct
SLA policyTargets Entitlements & milestones— rebuild

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.