Zendesk® to Salesforce Service Cloud (Agentforce) Migration

Zendesk® to Salesforce Service Cloud (Agentforce) Migration

Move tickets, customers, organizations, and KB articles from Zendesk® to Salesforce Service Cloud — or directly into Salesforce Agentforce — with our automated Migration Wizard.

No downtime. No CSV juggling.

Pandora — the world's largest jewelry brand — moved 1.2 million records from Zendesk® to Salesforce Agentforce in 4 weeks using Help Desk Migration. Run a free demo migration today and see your own data move before you commit to a paid plan.

G2 Leader
60k+ Migrations
SOC 2 Certified
Fast Setup

Book a Migration Consult →

No credit card required Fast setup

Interactive Migration Calculator

Adjust sliders to estimate your migration time and cost savings

2,000
1K 500K
10-15 mins Estimated Migration Time
85% Time Savings vs Alternatives
$3,777 Savings vs In-house Development

Estimates based on 60,000+ successful migrations. Actual results may vary.

Trusted by support teams who've outgrown Zendesk®

From 8-agent SaaS teams to Pandora-scale enterprises, more than 38,000 companies have used Help Desk Migration to consolidate, replatform, or modernize their support stack — including teams moving from Zendesk® to Salesforce Service Cloud and now, Agentforce.

Why teams move from Zendesk® to Salesforce Service Cloud (or Agentforce)

Why teams move

Zendesk® is excellent at email-and-form support. Where it starts to bend is when your business outgrows pure ticketing — when sales, marketing, billing, and field ops all need to see the same customer record, and when 'a faster macro' stops being enough.

The four reasons we most often hear from teams replatforming:

Service Cloud unifies tickets with the Salesforce Account/Contact/Opportunity records sales already lives in. No more cross-tool lookups.

Salesforce's autonomous AI agent layer is built natively on top of Service Cloud. If your roadmap includes deflection, agent assist, or autonomous resolution, you'll want your support data in the same place the AI lives.

Salesforce objects, validation rules, flows, and Lightning pages let ops teams model complex workflows that would require Zendesk® app development or external automation.

Sales, service, marketing, and analytics consolidated under the Salesforce umbrella — simpler procurement, simpler renewals, simpler license management.

Case Study

Pandora migrated 1.2M Zendesk® records to Salesforce Agentforce in 4 weeks

Pandora — the Danish jewelry house with 6,800 stores in 100+ countries and the world's largest jewelry brand by volume — partnered with Help Desk Migration in early 2026 to move its global customer-support stack off Zendesk® and into Salesforce Agentforce.

Zendesk® → Salesforce Agentforce | Retail & E-Commerce

us.pandora.net
USA
Location
1982
Founded
37,000
Employees

Data Migrated
Tickets
Customers
Organizations
CSAT records
Migration Summary

Records migrated:
1.2 million tickets, customers, organizations, and CSAT records.

Timeline:
4 weeks from kickoff to production cutover.

Source:
Zendesk® Support (multibrand, multilingual).

Destination:
Salesforce Agentforce (Service Cloud + Agentforce for Service).

Downtime:
Zero — Pandora ran Delta migration to keep both systems in sync until cutover.

Key technical move:
Validation rules and triggers temporarily suspended during legacy data load to prevent failed inserts on historical records that don't satisfy current business logic.

Read the full Pandora case study →

Join Pandora and 60,000+ other teams.

No credit card required

What records can you migrate from Zendesk® to Salesforce?

The Migration Wizard maps Zendesk® objects to Salesforce Service Cloud (and Agentforce) objects automatically. Below is the standard map — every field is editable inside the Wizard before you run a demo.

Zendesk® Salesforce Service Cloud Salesforce Agentforce
Tickets Cases Cases
Ticket comments (public & internal) Case Comments / Feed Case Comments / Feed
Users (end-users) Contacts Contacts
Organizations Accounts Accounts
Agents Users Users (with Agentforce permission set)
Help Center articles Knowledge Articles Knowledge Articles
Help Center categories / sections Data Categories Data Categories
Side conversations EmailMessage / Case Feed EmailMessage / Case Feed
Attachments Files / ContentDocument Files / ContentDocument
Tags Topic / Tag Topic / Tag
Custom fields Custom fields (mapped per-object) Custom fields (mapped per-object)
CSAT ratings Custom object or Survey responses Custom object or Survey responses

Zendesk® to Salesforce Service Cloud migration in 6 steps

1. Connect your accounts

Link your Zendesk® and Salesforce Service Cloud instances to the Migration Wizard.

2. Map your data and fields

Choose the records you want to migrate. The Migration Wizard auto-maps standard fields — review them, edit any that need adjustment, and add custom field mappings for non-standard data.

3. Set up filters

Narrow what moves by Tags, Group, Channel, Status, Priority, Created date, Updated date, and custom fields.

4. Run a Free Demo

Help Desk Migration moves a slice of your data — typically 20 random tickets and their related records — into your Salesforce instance or sandbox. You review field-by-field results before you pay anything.

5. Schedule the Full Migration

You can choose a low-traffic window for the transfer. Your agents keep working in Zendesk® — nothing goes offline.

6. Run the Full Migration

The Wizard moves everything — tickets, contacts, accounts, knowledge base articles, and attachments — to Salesforce in the background.

What changes after you move to Salesforce Agentforce

Replatforming isn't the goal — what you do with the new platform is. Here's the operational arc we see in the first 90 days after a Zendesk-to-Agentforce migration.

Days 1–30 — Stabilize

  • Confirm ticket routing, agent permissions, and queue logic match your Zendesk® setup.
  • Train agents on the Salesforce Lightning console layout (it's not Zendesk® — the console is denser but more powerful).
  • Verify SLA reporting against your Zendesk® historical baseline.

Days 31–60 — Customize

  • Build the Salesforce Flows and validation rules your Zendesk® macros and triggers used to handle.
  • Connect Service Cloud to your Salesforce Sales and Marketing Clouds — the customer-360 view you were paying for.
  • Index your knowledge base for Einstein / Agentforce semantic search.

Days 61–90 — Activate Agentforce

  • Spin up your first Agentforce agent on a narrow use case (password resets, order status).
  • Wire in deflection metrics — what % of conversations Agentforce handles end-to-end vs. escalates.
  • Compare cost-per-resolution against your old Zendesk® baseline.
Security and Compliance

Built for security, privacy, and compliance

Help Desk Migration is built for teams that take data residency and access controls seriously — the same teams that run regulated workloads on Zendesk® and Salesforce in the first place.

  • SOC 2 Type II certified
  • HIPAA compliant for healthcare migrations
  • GDPR and CCPA compliant — full DSAR support
  • ISO/IEC 27001 information security management
  • Two-factor authentication on every account
  • Data encrypted in transit (TLS 1.2+) and at rest (AES-256)
  • Migration data retained only as long as needed for the project, then purged
Help Desk Migration

Ready to leave Zendesk® for Salesforce Service Cloud?

The free Demo migration moves 20 real tickets from your live Zendesk® to Salesforce Service Cloud. No staging environment, no dummy data. Your actual records, in the right place, ready to inspect.

Schedule a migration consultation →

No credit card required SOC 2 certified 60,000+ migrations completed

FAQs: Zendesk® to Salesforce Service Cloud migration

For most teams, 1–4 weeks end to end — including the free demo, mapping review, full migration, delta sync, and post-go-live verification. Pandora's 1.2M-record migration to Agentforce ran 4 weeks. A 50K-record Zendesk-to-Service-Cloud migration typically completes in 1–2 weeks.

Migration speed is set by API rate limits. Zendesk® exports at 200 requests per minute on standard plans — roughly 8.5 hours for a baseline of 100,000 tickets — and up to 2,500 rpm with the High Volume API add-on, which cuts that same export to about 40 minutes. Salesforce Service Cloud is the limiting factor: it enforces a daily API quota (100,000 requests per day on the baseline allocation), which works out to about 69 requests per minute effective. At that rate, a baseline migration of roughly 100,000 tickets plus contacts and companies takes about 5–6 days to import; adding Salesforce API licenses raises the ceiling and can bring it closer to 3 days.

Yes. Agentforce runs on the same Service Cloud data model, so Zendesk® tickets, contacts, and knowledge articles land in the same Salesforce objects (Cases, Contacts, Knowledge Articles). The difference is that on Agentforce, your knowledge base is automatically indexed for semantic search by Einstein and made available to Agentforce agents.

Service Cloud is Salesforce's case-management platform — Cases, Knowledge, Lightning console, omnichannel routing. Agentforce is the autonomous AI agent layer that runs on top of Service Cloud, with two main SKUs: Agentforce for Service ($125/user/mo) and Agentforce 1 Service ($550/user/mo with full conversation data services). You don't migrate to one or the other — you migrate to Service Cloud and turn on Agentforce when you're ready.

Migration cost depends on record volume, customizations, and service tier. Self-service Wizard migrations for small teams can start in the low hundreds; enterprise migrations like Pandora's run in the tens of thousands. For reference, custom-built consulting migrations from Zendesk® to Salesforce typically quote $150K–$400K — the Wizard route is a fraction of that. Run a free demo first to scope your exact migration.

Validation rules written for clean go-forward data often fail on historical Zendesk® records (a required field today may not have existed in 2019). We work with your Salesforce admin to identify which rules and Apex triggers would block legacy data, temporarily suspend them during the load window, and re-enable them before go-live so your go-forward data quality stays enforced.

No. We use Delta migration — the full migration runs in the background while your agents keep working in Zendesk®. New tickets created during the migration window are picked up incrementally so Salesforce is current at cutover. Effective downtime is zero.

Yes. Zendesk® Chat transcripts map to Salesforce Live Chat Transcripts (Service Cloud) or Conversation / MessagingChannel records (Agentforce). Channels, agents, and timestamps are preserved.

Yes. By default, Salesforce sets CreatedDate to the import time. We use Salesforce's Audit Field permission set to preserve the original Zendesk® created_at timestamps on every migrated case — essential if you need historical SLA reporting or year-over-year analytics.

Custom Zendesk® fields are mapped to custom Salesforce fields inside the Wizard — you can edit every mapping before paying. Third-party integrations (Jira, Slack, Stripe) aren't migrated by the Wizard, but we'll list them during the audit so you can re-establish each one on the Salesforce side.

Yes. Multibrand maps to Salesforce business units or record types depending on your model; locale metadata on tickets and articles is preserved. Pandora ran Zendesk® across 100+ countries — that's the scale we built the multibrand pattern for.
Olha Butenets
AUTHOR

Olha Butenets

Head of Sales & Support

Olha is a distinguished help desk migration expert and an esteemed lead for our Sales and Support team. With over 4 years of experience and a track record of 2000+ successful migrations, she specializes in masterminding high-stakes enterprise data migrations while focusing on total data integrity and operational continuity.

More tips and tricks for your data movement

Curious about transferring help desk data and boosting your support services? Dive into our blog for smart tips and insights!

The Best Customer Service Software Solutions 2026

It makes typing a single query into the Google search engine to get ...

11 Best Spiceworks Alternatives & Competitors in 2026

On December 31, 2021, Spiceworks officially ended support for the Desktop version of ...

The 6 Great Help Desk Systems for Shopify

Can you recall the last time you received outstanding customer service? Can you ...

Zendesk® is a registered trademark of Zendesk, Inc. Help Desk Migration is not affiliated with, sponsored by, or endorsed by Zendesk, Inc.
We provide data migration services that work with Zendesk's platform.