Zendesk to Salesforce Service Cloud migration
We migrate Tickets, Users, Organizations, Attachments, and Knowledge Base articles from Zendesk into Salesforce Service Cloud Cases, Contacts, Accounts, and Articles — resolving Zendesk SLA policies against Salesforce Entitlements, extracting Help Center content through the API, and mapping agent roles to Service Cloud users before cutover.
FlitStack AI migrates cases, contacts, users, accounts and account + experience cloud sites from Zendesk to Salesforce Service Cloud, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5-7 weeks.

What moves from Zendesk to Salesforce Service Cloud?
Zendesk and Salesforce Service Cloud have fundamentally different data models despite both being enterprise helpdesk platforms.
Read the full summary
Zendesk Tickets are standalone records with a built-in requester-organization hierarchy; Salesforce Cases are linked to Contacts on Accounts, which changes how you think about customer relationships. We map Zendesk end-users to Contacts, Zendesk Organizations to Accounts, and Zendesk agents to Salesforce Users with their role and group assignments preserved. SLA Policies from Zendesk require a rebuild as Salesforce Entitlements and Milestones because there is no direct SLA object migration path. The Help Center has no native export feature — we extract all articles, sections, and translations through Zendesk's Help Center API and reconstruct the hierarchy in Salesforce's Knowledge Base. Triggers, Automations, Macros, Views, and SLA Policies do not migrate as code; we deliver a written inventory of every rule, template, and view so your admin team can rebuild them in Salesforce Flow and Omni-Channel.
Ticket → Case
Zendesk Tickets map directly to Salesforce Case records.
How it maps
The Zendesk ticket ID is stored in a custom field zendesk_id__c for cross-reference. Ticket Status (New, Open, Pending, Solved, Closed) maps to Salesforce Case Status values (New, Working, Escalated, Closed) — the customer configures the picklist mapping during scoping because Status semantics differ between the two platforms. Priority, requester, assignee, group, tags, and custom fields migrate directly. Each ticket comment thread migrates as an EmailMessage record linked to the Case for full conversation history.
End-User (Requester) → Contact
Zendesk end-users (requesters) map to Salesforce Contacts.
How it maps
We resolve each requester by email address as the dedupe key. The requester's organization membership in Zendesk is preserved as the Contact's AccountId lookup. Custom fields on the Zendesk user profile migrate to custom Contact fields. Role assignment (agent vs. end-user) is encoded in the Contact record; agents migrate separately as Users rather than Contacts.
Agent → User
Zendesk agents map to Salesforce Users.
How it maps
We resolve agents by email address against the destination org's User table and preserve the Zendesk role (admin, agent, light agent) as a custom field on the User record. Group memberships map to Salesforce Queues and Group membership. Agents without a matching Salesforce User are held in a reconciliation queue for the customer's admin to provision before the migration resumes.
Organization → Account
Zendesk Organizations map to Salesforce Accounts.
How it maps
The organization's domain names, details fields, and shared tags migrate to the Account record. Multiple Zendesk users can belong to one Organization — we preserve these memberships by setting AccountId on each Contact at import time. If the customer uses Zendesk's multi-brand feature with separate organizations per brand, each brand's organization maps to its own Account or a parent Account with child Accounts for subsidiaries.
Brand → Account + Experience Cloud Site
Zendesk Brands (available on Growth through Enterprise, capped at 5-300 depending on tier) represent separate support identities with their own email addresses and help centers.
How it maps
We map each Brand to an Account for ticket ownership and optionally provision a separate Experience Cloud site if the customer requires a distinct self-service portal per brand. Brand routing rules map to Salesforce Omni-Channel routing configurations that the admin sets up post-migration.
Attachment → ContentVersion + ContentDocumentLink
Ticket comment attachments and Help Center article attachments are downloaded from Zendesk via the API, preserved with their original filenames and MIME types, and uploaded to Salesforce as ContentVersion records.
How it maps
ContentDocumentLink records attach each file to the parent Case or Article record. Attachments larger than 25 MB require chunked upload via the Salesforce chunked upload endpoint.
- TicketCase1:1
- End-UserContact1:1
- AgentUser1:1
- OrganizationAccount1:1
- BrandAccounttransformed
- AttachmentContentVersion1:1
+ 6 more in the mapping below
How Zendesk and Salesforce Service Cloud differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Zendesk | Salesforce Service Cloud |
|---|---|---|
| Ticket model | Standalone Tickets with embedded requester and organization | Cases linked to Contacts on Accounts with a three-level hierarchy |
| SLA handling | Native SLA Policies with first-response and resolution targets per plan | Entitlements and Milestones with business hours and escalation rules rebuilt separately |
| User roles | Admin, Agent, Light Agent, Contributor roles scoped to Groups | Standard, CS Agent, and Custom profiles with Permission Sets and Queues |
| Knowledge base export | No native export — requires API scripting or a migration service | Articles organized by categories with Data Category visibility controls |
| Automation primitives | Triggers (event-driven) and Automations (hourly, 1,000 ticket cap) as first-class objects | Flow (record-triggered, scheduled, screen) and Omni-Channel routing rebuilt by admin |
| Multi-brand support | Up to 5 brands on Growth/Professional, up to 300 on Enterprise | Multiple Service Cloud instances or Experience Cloud sites for brand isolation |
| Reporting model | Plan-gated dashboards; Advanced Reporting on Professional and above | Native Salesforce Reports and Dashboards across all tiers with CRM Analytics add-on |
What to watch for in a Zendesk to Salesforce Service Cloud migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Zendesk ticket status semantics do not map directly to Salesforce case status
Zendesk ticket statuses (New, Open, Pending, Solved, Closed) have different implied behaviors than Salesforce Case statuses.
How we handle it
In Zendesk, Solved tickets remain editable; in Salesforce, Closed cases are locked by default unless the org has cases without edit after close enabled. We store the original Zendesk status in a custom field zendesk_status__c on the Case so the admin can design the Salesforce picklist values and validation rules around the actual business process rather than the platform defaults. Migrations that skip this step often result in cases being accidentally locked that should still be open.
SLA Policies do not migrate — they must be rebuilt as Entitlements
Zendesk SLA Policies are a first-class configuration object with first-response and resolution targets, business hours, and escalation actions.
How we handle it
Salesforce has no direct SLA object — support commitments are modeled as Entitlements (the support contract) and Milestones (individual time targets). We export the full SLA Policy definitions as a written specification document with targets, business hours, and escalation logic. The customer's Salesforce admin rebuilds them in Entitlement Management. SLA data attached to tickets does not migrate as actionable records.
Omni-Channel routing and active Triggers can block data load
If the destination Salesforce org has Omni-Channel routing enabled or active Flows and Validation Rules on Case, incoming data from the migration can trigger routing assignments, Flow logic, or validation failures that interrupt the load.
How we handle it
The Pandora migration case study (PR Newswire, April 2026) documents how Help Desk Migration resolved this by temporarily suspending backend rules, loading historical data, then re-enabling them. We perform the same check during scoping: we audit active Flows and Omni-Channel presence configurations and coordinate with the customer's admin to suspend them during the load window.
Zendesk Automations cap at 500 rules and process 1,000 tickets per hour
Zendesk Automations are time-based and run on a maximum of 1,000 tickets per batch with a 500-active-rule cap per account.
How we handle it
Accounts with heavy automation logic often exceed these limits, and rules beyond the cap are silently ignored. We audit the active automation count during discovery and flag any that reference fields or values that do not exist in Salesforce. Automations do not fire on closed tickets — a common misconception that leads to unexpected behavior in post-migration SLA compliance reporting. We document this behavior in the automation inventory handoff.
Help Center export requires paginated API extraction with no native bulk tool
Zendesk does not offer a bulk export for Help Center articles.
How we handle it
We iterate over the Help Center API endpoints for sections, categories, and articles, downloading HTML content, translations, and attachments per article. For accounts with thousands of articles across multiple locales, this requires hundreds of paginated API calls that must respect Zendesk's rate limits. If the Help Center uses Dynamic Content for multilingual variants, we extract each locale variant separately and map it to Salesforce's locale fields on the Knowledge Article. The customer must pre-create the ArticleType in Salesforce before articles can be imported.
How the migration runs
Discovery and scoping
We audit the Zendesk account across tier, active tickets, closed ticket volume, user count (agents vs. end-users), Organization count, Help Center article count and section hierarchy, active SLA Policies, Triggers, Automations, Macros, and Views.
What this step covers
We assess the destination Salesforce org: edition, existing objects, active Validation Rules, Omni-Channel configuration, and Knowledge Base setup. The discovery output is a written migration scope with object-level field mapping, a list of pre-requisites (ArticleType creation, User provisioning, custom field schema), and an estimated timeline.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using the customer's production-like data volume.
What this step covers
The customer's Service Cloud admin and support operations lead review record counts, spot-check 25-50 tickets and articles against the Zendesk source, validate SLA Policy translation documents, and sign off on the mapping before production migration begins. Schema corrections and field mapping adjustments happen in the Sandbox, not in production.
Data extraction from Zendesk
We pull data from Zendesk via authenticated API across all supported objects.
What this step covers
Ticket extraction uses paginated API requests with rate-limit handling and exponential backoff. The Help Center export iterates over sections, categories, and articles, downloading HTML content, translations, and attachments. Custom Objects are extracted separately if the account is on Enterprise plan. We produce a row-count manifest for each object before transformation begins.
Data transformation and schema mapping
We transform Zendesk data into Salesforce records in dependency order: Accounts (from Organizations), Contacts (from end-users with AccountId resolved), Users (from agents with role preserved), Cases (with zendesk_id__c and zendesk_status__c for audit), ArticleType creation and Knowledge Articles, Attachments as ContentVersion and ContentDocumentLink.
What this step covers
SLA Policies, Triggers, Automations, Macros, and Views are exported as structured JSON inventories and delivered as handoff documents — they are not executed in the destination org as part of the migration.
Production migration and cutover
We freeze Zendesk write access during the cutover window, run a final delta migration of any tickets or articles modified during the Sandbox validation period, load data into production in dependency order, and validate row counts match the Sandbox manifest.
What this step covers
We deliver the SLA Policy, Trigger, Automation, Macro, and View inventory documents to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the support team. We do not rebuild Zendesk Triggers, Automations, or SLA Policies as Salesforce Flow or Entitlement records inside the migration scope — that is a separate engagement for the admin team or a Salesforce implementation partner.
Post-migration handoff
We deliver a data reconciliation summary comparing source and destination record counts per object, a field-level mapping reference document, the automation and macro inventory for rebuild, and a knowledge base article category map showing the Zendesk section hierarchy mapped to Salesforce Data Categories.
What this step covers
We do not provide ongoing admin support, training, or workflow rebuild as part of standard migration scope.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with ticket volume, Help Center article count, custom field complexity, and whether the destination org requires Sandbox-first validation. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Zendesk to Salesforce Service Cloud →Why teams move from Zendesk to Salesforce Service Cloud
- Teams with existing Salesforce Sales Cloud or Marketing Cloud move to Service Cloud to unify their customer view. Agents who already work in Salesforce see the full account history, purchase data, and campaign interactions without switching between Zendesk and a separate CRM window. Reviewers on G2 and Reddit confirm that the unified 360-degree profile is the primary driver for B2B companies at mid-market and enterprise scale.
- Zendesk per-agent pricing with add-on costs for AI, advanced reporting, and high-volume API access makes the effective price 30-50% above the base per-seat rate at scale. Salesforce Service Cloud pricing bundles omnichannel routing and basic analytics into Professional and Enterprise tiers without treating AI features as separate line items, making the per-agent cost more predictable for teams above 50 seats.
- Zendesk's automation engine — Triggers, Automations, and SLA Policies — is purpose-built for ticketing but lacks the extensibility of Salesforce Flow. Enterprise teams cited inability to automate across Sales and Service objects, integrate with ERP or contract management systems, or build multi-step approvals as the reason they moved to Service Cloud where Flow connects to any Salesforce object or external API.
- Zendesk's reporting is plan-gated — Team plan has basic dashboards, Professional unlocks Advanced Reporting, and Enterprise adds sandbox and custom reports. Salesforce provides native Reports and Dashboards across all paid tiers with CRM Analytics (Tableau) available as an add-on. Enterprise teams cited Zendesk's inability to produce cross-channel analytics that combine email, chat, phone, and case resolution data as a reason for switching.
- Zendesk's data export restrictions on Team and Essential tiers force teams to use API scripting or a migration service to extract their own data. This creates a lock-in effect that becomes expensive to break when data volume grows. Salesforce's Data Loader and Bulk API 2.0 are available on all editions without plan-gating, giving customers direct access to their data at any time.
Questions, answered
Zendesk to Salesforce Service Cloud migration questions
How long does a Zendesk to Salesforce Service Cloud migration take?
Most migrations land between five and seven weeks for accounts under 50,000 tickets, a single-brand Help Center, and no Enterprise-only features. Migrations with multi-brand Zendesk accounts, large Knowledge Base exports (over 5,000 articles), complex SLA Policy rebuild scope, or over 200,000 ticket records move to twelve to eighteen weeks. Salesforce recommends at least two dedicated Service Cloud admins for teams over 150 seats, which affects internal resource planning and go-live readiness.
What data does FlitStack AI migrate from Zendesk to Salesforce Service Cloud?
We migrate Tickets (Cases), End-Users (Contacts), Organizations (Accounts), Agents (Users with role mapping), Attachments (ContentVersion and ContentDocumentLink), Tags, Help Center Articles (Knowledge Base), Custom Objects (Enterprise tier), and historical timestamps. We preserve ticket comment threads as EmailMessage records, maintain organization memberships as Account lookups on Contacts, and store the original Zendesk ticket ID and status in custom fields for audit and reconciliation.
What does FlitStack AI NOT migrate from Zendesk to Salesforce Service Cloud?
We do not migrate Zendesk Triggers, Automations, SLA Policies, Macros, or Views as executable records. These are platform-specific configuration objects that have no direct equivalent in Salesforce. We deliver a written inventory of every active Trigger, Automation, SLA Policy, Macro, and View with its full definition, conditions, and actions — your admin team or a Salesforce implementation partner rebuilds them in Salesforce Flow and Entitlement Management. We also do not migrate Zendesk Sunshine Conversations history, third-party app data, or embedded widget configurations.
Can we migrate our Zendesk Help Center to Salesforce Knowledge Base?
Yes. We extract all Help Center articles, section hierarchy, categories, translations, and attachments via Zendesk's Help Center API. Articles are imported as Salesforce Knowledge articles of the appropriate ArticleType. The customer must pre-create the ArticleType in Salesforce before migration begins. Dynamic Content items (multilingual variants) are resolved to their default locale and mapped to Salesforce locale fields. We do not migrate Help Center branding themes, custom CSS, or embedded video configurations — these are rebuilt separately as part of the Salesforce Experience Cloud setup.
Do we lose historical ticket data when migrating from Zendesk?
No. We preserve the full ticket history including closed and resolved tickets. Each ticket's comments, attachments, status transitions, timestamps, assignee history, and tags migrate as structured records in Salesforce. The original Zendesk ticket ID is stored in a custom field for cross-reference. Zendesk does not natively export ticket thread history in a format Salesforce can ingest directly — we use the API to pull it in structured form rather than relying on a CSV export that would lose comment threading and attachment links.
How do we rebuild Zendesk SLA Policies in Salesforce Service Cloud?
Zendesk SLA Policies must be rebuilt as Salesforce Entitlements and Milestones because there is no direct migration path. We provide a written inventory of every Zendesk SLA Policy with its first-response target, resolution target, business hours, and escalation actions. Your Salesforce admin creates Entitlement records (representing the support contract or plan) and Milestones (representing individual time-bound commitments) in Setup under Entitlement Management. We do not configure Entitlements or Milestones as part of the data migration scope.
Can FlitStack AI migrate from multiple Zendesk brands to a single Salesforce org?
Yes. If the customer uses Zendesk's multi-brand feature (up to 5 brands on Growth/Professional, up to 300 on Enterprise), we map each brand's Organizations to separate Salesforce Accounts and optionally configure separate Experience Cloud sites per brand for self-service portals. Ticket routing by brand is documented for the admin to configure in Salesforce Omni-Channel post-migration. The brand-level email routing configurations (inbound email-to-case addresses per brand) require Salesforce admin setup of separate email services or Salesforce Inbox routing rules.
Related migrations
Salesforce implementation
Set up Salesforce Service Cloud and migrate into it as one engagement.
See the service → Freshdesk to Salesforce Service CloudMapping · history · rollback Zendesk to FreshdeskMapping · history · rollbackZendesk to HubSpot Service HubMapping · history · rollbackZendesk to IntercomMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
Get a quote
Moving from Zendesk to Salesforce Service Cloud?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce Service Cloud setup with you, then send a quote.
Get a quote