Skip to content
Get a quote

Zendesk Sell to Salesforce migration

We migrate Leads, Contacts, Deals, Tasks, and custom Fields from Zendesk Sell into Salesforce Sales Cloud, resolving Sell's pipeline-stage hierarchy against Salesforce's Sales Process model, handling the Lead versus Contact split, and preserving engagement history through the Bulk API before the August 31, 2027 Sell sunset date.

Short answer

FlitStack AI migrates leads, contacts, accounts, opportunities and record types from Zendesk Sell to Salesforce, 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: 4-6 weeks.

By

Source Zendesk Sell
DestinationSalesforce
LeadContactAccountOpportunityRecord Type
Mapped field by field · sample run · one-click rollback

What moves from Zendesk Sell to Salesforce?

Moving from Zendesk Sell to Salesforce Sales Cloud is an enterprise-grade migration driven by Sell's mandatory retirement on August 31, 2027.

Read the full summary

Zendesk Sell organizes revenue data around Leads, Contacts, Deals, and Pipelines with Stages as child objects, while Salesforce maps this to its Lead, Contact, Account, and Opportunity model. We resolve the Lead-versus-Contact split (Sell stores both in Contacts; Salesforce separates them), preserve pipeline and stage ordinality in Salesforce Record Types and Sales Processes, and use the Bulk API 2.0 to migrate activity history at scale. Sell Sequences, Line Items on Deals, and custom automation do not migrate as code; we deliver written inventories for the customer's admin to rebuild. Given the August 2027 deadline, we treat every Sell migration as time-bound and push customers toward a start window of 12 to 18 months before sunset to avoid last-minute data loss and constrained specialist availability.

1:1

Lead → Lead

Sell Leads migrate directly to Salesforce Lead.

How it maps

The lead_source, unqualified_reason, and custom Lead fields transfer as-is. Sell Lead status values map to Salesforce Lead Status picklist, which we configure during Salesforce setup. We resolve any Sell custom Lead fields to Salesforce custom Lead fields with equivalent types.

1:1

Contact → Contact

Sell Contacts migrate to Salesforce Contact.

How it maps

The is_organization flag that some Sell accounts use to designate company contacts requires resolution: if a Sell Contact has is_organization = true and no individual name, we treat it as a lead for Account creation rather than a Contact. All standard fields (name, email, phone, address) map to Salesforce Contact equivalents. We run duplicate detection on email during import.

1:1

Company → Account

Sell Company records map to Salesforce Account.

How it maps

The company domain becomes the Account Website field and serves as the dedupe key. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at Contact insert. Sell custom Company fields map to Salesforce custom Account fields.

1:1

Deal → Opportunity

Sell Deals map to Salesforce Opportunity.

How it maps

The Deal amount, loss_reason, deal_source, and stage history transfer. We resolve the associated Contact as the Opportunity's primary Contact role, and the associated Pipeline and Stage as the Salesforce Record Type and Sales Process stage value. Closed-Loss and Closed-Won dates from Sell map to Opportunity CloseDate and StageName.

configuration

Pipeline → Record Type

Each Sell Pipeline becomes a Salesforce Record Type on Opportunity.

How it maps

We pre-create Record Types during the schema phase so that stage mapping is scoped per pipeline context. If the customer uses more than five Sell Pipelines, we consolidate or split per the customer's input during scoping.

configuration

Stage → Stage Name (Sales Process)

Sell Stages are children of Pipelines with ordinal position, loss/win flags, and probability.

How it maps

We map these to Salesforce Sales Process stage values, preserving stage order and renaming to match Salesforce naming conventions. Stage probability percentages migrate as StageProbability values, rounded to the nearest integer.

What moves14 objects
Zendesk SellSalesforce
  • LeadLead1:1
  • ContactContact1:1
  • CompanyAccount1:1
  • DealOpportunity1:1
  • PipelineRecord Typetransformed
  • StageStage Nametransformed

+ 8 more in the mapping below

How Zendesk Sell and Salesforce 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.

DimensionZendesk SellSalesforce
Lead and Contact modelSell stores Leads and Contacts as separate objects with distinct sources, unqualified reasons, and pipeline assignmentsSalesforce separates Lead (unqualified) from Contact (qualified, attached to Account) with an explicit Convert action
Pipeline and stage hierarchySell Pipelines contain Stages as child objects with ordinal position, loss/win flags, and stage probabilitySalesforce Sales Processes contain Stage picklists; Record Types gate pipeline access; probability set per stage in setup
Deal structureSell Deals hold amount, loss reason, source, and associated Line Items as child recordsSalesforce Opportunity holds amount and stage; Line Items are OpportunityLineItem with PricebookEntry reference
Custom fieldsSell assigns numeric field IDs and separate field keys; bulk API requires field key not numeric IDSalesforce uses field API names with __c suffix on custom fields; type-mapped to Sell field types during import
Pricing modelSell Team at $19/user/month and Professional at $49/user/month, both per-user with seat capsSales Cloud Starter at $25/user, Professional at $100/user, Enterprise at $175/user; unlimited record types from Professional
Workflow automationSell Professional includes workflow automation builder gated behind the Professional tierSalesforce Flow (record-triggered, scheduled, screen) available from Professional; Process Builder deprecated
Activity historyEngagements (calls, emails, meetings, tasks, notes) stored as first-class objects linked to parent recordsTasks, Events, and EmailMessage as standard objects; call recordings as ContentDocument files

What to watch for in a Zendesk Sell to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Sell's August 31, 2027 sunset creates a hard data deletion deadline

Zendesk deletes all Sell data per its Service Data Deletion Policy upon subscription end or August 31, 2027, whichever comes first.

How we handle it

This is not a soft deadline. We treat every Sell migration as time-bound and schedule discovery calls with a migration-start target at least 9 months before the deadline. Organizations that begin planning in late 2026 face constrained specialist availability, rushed testing windows, and the risk of leaving historical deal data behind because there is no time to clean it before migration. We recommend starting 12 to 18 months before sunset.

high

Sell Lead and Contact objects do not map directly to Salesforce Lead and Contact

Sell stores Leads and Contacts as distinct objects with different schemas, while Salesforce separates Leads (unqualified prospects) from Contacts (qualified, attached to Accounts) with an explicit Convert action.

How we handle it

Sell Contacts that represent companies (is_organization = true) and Sell Contacts that represent individuals require different Salesforce destinations. We design the split rule during scoping using the customer's lead source and qualification criteria, and we preserve the original Sell Contact record type in a custom field for audit.

medium

Sell Sequences cannot be migrated to Salesforce

Sell Sequences store enrollment state, step history, reply tracking, and cadence timing tied to individual Contacts.

How we handle it

This automation data is not exportable as a discrete object and has no equivalent in Salesforce Sales Cloud, which uses Salesforce Flow for workflow and Sales Engagement (optional add-on) for cadence-based outreach. We export Sequence metadata (name, step count, cadence) as a reference document for the customer's admin to rebuild, but we do not migrate enrollment state or in-progress sequence positions.

medium

Sell custom field keys differ from numeric IDs and both are required for API calls

Sell assigns a numeric custom field ID and a separate custom field key (required for bulk API calls).

How we handle it

When bulk importing via the Sell API, the field key is required, not the numeric ID. We resolve both identifiers during the scoping phase and maintain a field-key lookup table for all custom fields before writing a single record to Salesforce. Migrations that skip this step silently fail on custom field population.

medium

Line Items on Sell Deals require Pricebook and Product2 provisioning in Salesforce

Sell Line Items attach to Deals and represent products or services with quantity and price.

How we handle it

Salesforce models Line Items as OpportunityLineItem requiring a PricebookEntry (which itself requires a Product2 and active Pricebook). We create Product2 records and Standard Pricebook entries before any Line Item migration begins. If the destination Salesforce org does not use the native Pricebook2 model, Line Items require a custom object or custom fields on Opportunity, which we configure during schema design.

How the migration runs

  1. Discovery and Sell sunset timeline review

    We audit the source Zendesk Sell portal across tier (Team at $19/user or Professional at $49/user), active pipelines and stages, record volume by object, custom fields (with ID and field key resolution), active Sequences, and engagement history volume.

    What this step covers

    We cross-reference this against the customer's Salesforce edition target (Professional at $100/user for most migrations; Enterprise at $175/user if custom objects or advanced Flow are required) and confirm the August 31, 2027 sunset timeline as the hard constraint that drives scheduling. The discovery output is a written migration scope, Salesforce edition recommendation, and a project timeline anchored to the sunset date.

  2. Lead-Contact split rule design and schema configuration

    We design the destination Salesforce schema before any data moves.

    What this step covers

    This includes provisioning custom fields (mapped from Sell custom field keys), Salesforce Record Types (one per Sell Pipeline), Sales Processes (stage values per Record Type), and the Lead-Contact split rule based on the customer's Sell lead qualification criteria. If the customer uses Sell Company records as organizations, we pre-create the Account hierarchy. Schema deploys into a Salesforce Sandbox via metadata API for validation before production.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox using production-like data volume.

    What this step covers

    The customer's Salesforce admin or RevOps lead reconciles record counts (Leads in, Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 25 to 50 random records against the Sell source, and validates that pipeline and stage assignments match. Any mapping corrections, custom field type mismatches, or Record Type configuration issues surface here, not in production.

  4. Owner reconciliation and User provisioning

    We extract every distinct Sell User referenced on Leads, Contacts, Deals, Tasks, and Engagements and match by email against the destination Salesforce org's User table.

    What this step covers

    Any Sell User without a matching Salesforce User goes to a reconciliation queue. The customer's admin provisions missing Users (active or inactive depending on whether the rep is still employed) before record migration resumes. OwnerId references are required on most Salesforce standard objects, so this step gates the data migration.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Sell Companies), Contacts (with AccountId resolved), Leads (with the split rule applied), Opportunities (with AccountId, OwnerId, RecordTypeId, and StageName resolved), Tasks and Events (via Bulk API 2.0 for large volumes), Call records with recording files, Notes, Tags, and Line Items (with PricebookEntry and Product2 resolved).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We use rate-limit-aware polling against the Sell Core API (36,000 requests per hour) with batch chunking and exponential backoff on 429 responses.

  6. Cutover, delta sync, and Sequence handoff

    We freeze Sell writes during cutover, run a final delta migration of records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We deliver the Sell Sequences metadata document (step count, cadence, enrolled contacts) to the customer's admin for rebuild in Salesforce Sales Engagement or Flow. We support a one-week hypercare window for reconciliation issues. We do not rebuild Sell Sequences, automations, or workflows as Salesforce Flow inside the migration scope; that is a separate engagement or internal admin task.

Zendesk Sell Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-6 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

A quote scales with record volume, pipeline complexity, and custom object count. Given the August 31, 2027 sunset, Sell customers who begin migration in 2025 or early 2026 secure better scheduling availability and more time for data cleanup before cutover. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Zendesk Sell to Salesforce →

Why teams move from Zendesk Sell to Salesforce

  • Zendesk Sell's retirement on August 31, 2027 makes migration mandatory rather than discretionary. Zendesk deletes all Sell data per its Service Data Deletion Policy upon subscription end or the sunset date, whichever comes first. Organizations that wait until Q1 2027 risk rushed migrations, data loss, and constrained specialist availability. Starting 12 to 18 months before the deadline gives teams enough time for discovery, sandbox testing, data cleanup, Salesforce configuration, and user training without competing against a surge of last-minute movers.
  • Salesforce holds approximately 20.7 percent of the global CRM market and is trusted by over 150,000 businesses globally, making it the natural enterprise destination for Sell customers who have outgrown the SMB tier. Salesforce's unified platform covers sales, service, marketing, analytics, and commerce, giving growing companies a single system of record that Sell no longer provides as Zendesk winds down the product.
  • Sell's pipeline and stage model requires explicit reimplementation in Salesforce. Sell Pipelines are custom workflow containers with Stages as children; Salesforce maps this to Record Types and Sales Processes that whitelist stage values per pipeline context. Organizations with multiple Sell pipelines need to rebuild that hierarchy in Salesforce before any Deal migration begins, which is both a configuration task and an opportunity to optimize sales stages for growth.
  • Salesforce Einstein provides AI recommendations on deal prediction, best outreach timing, and revenue forecasting that exceed what Zendesk Sell offers at its tier. For teams that have grown beyond Sell's reporting capabilities, Salesforce's AI-driven insights represent a substantive upgrade in sales intelligence that justifies the migration effort and licensing cost.
  • Sell's per-user pricing with no unlimited-seat option inflates cost as teams grow, while Salesforce's Professional tier at $100 per user supports unlimited record types, custom objects, and sales processes without the per-feature gating Sell applies across Team and Professional. For teams with multiple pipelines, advanced reporting needs, or complex data models, Salesforce's pricing structure provides better long-term predictability even at a higher per-seat rate.

Questions, answered

Zendesk Sell to Salesforce migration questions

How long does a Zendesk Sell to Salesforce migration take?

Most migrations land between four and six weeks for accounts under 25,000 Contacts and 5,000 Deals with one or two Sell pipelines and no complex custom objects. Migrations with multiple Sell pipelines, Line Items on Deals, large engagement histories (over 500,000 activity records), or multi-org Salesforce destinations move to ten to sixteen weeks. Given the August 31, 2027 Sell sunset, we strongly recommend beginning discovery 12 to 18 months before that date to avoid competing with a surge of last-minute migrators.

Do Zendesk Sell Sequences, workflows, and automations migrate to Salesforce?

No. Sell Sequences store enrollment state, step history, and reply tracking that are not exportable as discrete objects and have no direct Salesforce equivalent (Sales Cloud uses Salesforce Flow for workflow and Sales Engagement as a separate licensed add-on for cadence-based sequences). Sell workflows built in the Professional tier automation builder do not migrate to Salesforce Flow because the two automation models have different triggers, actions, and limits. We deliver a written inventory of every active Sequence and workflow with its configuration and a recommended Salesforce equivalent, and the customer's admin rebuilds them post-migration.

Can we keep Zendesk Support while moving Sell data to Salesforce?

Yes. Many Sell customers use Zendesk Support for their service desk and plan to move that to Salesforce Service Cloud separately or continue it with Zendesk Suite. Sell migration to Salesforce Sales Cloud does not require moving Zendesk Support. If the customer also moves to Salesforce Service Cloud, we handle the Case migration alongside the Sell CRM migration, with Sell Tickets mapped to Salesforce Cases and Sell Users mapped to Salesforce Users. Zendesk Suite licensing then becomes a separate decision for the customer's finance and IT teams.

Do we lose historical deal and activity data during migration?

No. We migrate Deals, Tasks, Notes, Call records, and custom field data through Salesforce's Bulk API 2.0 with parent-record resolution (ContactId, AccountId, OpportunityId, WhoId, WhatId). Call recording files migrate as ContentDocument records linked to the parent Task. Sell Line Items migrate as OpportunityLineItem records with PricebookEntry and Product2 resolved. The only data that does not migrate is Sell Sequences (enrollment state and cadence timing) and any workflows or automations built in the Sell Professional automation builder, which we document for rebuild.

How does the Sell Lead versus Contact split work in this migration?

Sell stores Leads and Contacts as separate objects with distinct schemas. We migrate Sell Leads directly to Salesforce Lead. Sell Contacts migrate to Salesforce Contact, but we apply a split rule: if a Sell Contact has is_organization = true (indicating it represents a company rather than an individual), we create a Salesforce Account from it first and then link the Contact to that Account. All Sell Contacts also get a custom field preserving the original Sell Contact ID for audit and reconciliation. This split ensures that Salesforce reporting on Lead conversion and Account attribution reflects the customer's original data.

What happens to our Sell data after the August 31, 2027 sunset?

Zendesk deletes all Sell data per its Service Data Deletion Policy upon subscription end or August 31, 2027, whichever comes first. There is no grace period or data export window after the sunset date. Organizations that have not completed migration by that date lose access to Sell and their data is permanently deleted. We strongly encourage customers to begin migration planning at least 12 months before the deadline to allow time for vendor evaluation, internal approvals, sandbox testing, data cleanup, Salesforce configuration, and user training without rushing.

Can FlitStack AI also migrate Zendesk Support tickets to Salesforce Service Cloud alongside this migration?

Yes. If the customer moves both Sell (sales CRM) and Support (service desk) to Salesforce, we handle both migrations as a combined scope. Sell Leads, Contacts, Deals, and activity history migrate to Salesforce Sales Cloud; Zendesk Support Tickets migrate to Salesforce Cases with status, priority, and SLA mapping preserved. Ticket comments migrate as EmailMessage records linked to the Case. We do not migrate Zendesk Help Center articles, macros, or automations as code; we deliver written inventories for the customer's admin to rebuild in Service Cloud. The combined scope is scoped and priced separately from the Sell migration.

Get a quote

Moving from Zendesk Sell to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote