CRM migration

Migrate from Zendesk Sell to Salesforce Sales Cloud

Field-level mapping, validation, and rollback between Zendesk Sell and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.

Zendesk Sell logo

Zendesk Sell

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

79%

11 of 14

objects map 1:1 between Zendesk Sell and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Zendesk Sell to Salesforce Sales Cloud is an enterprise-grade migration driven by Sell's mandatory retirement on August 31, 2027. 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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Zendesk Sell logo

Zendesk Sell

What's pushing teams away

  • Zendesk officially announced Sell's retirement on August 31, 2027, with data deletion per Zendesk's Service Data Deletion Policy upon subscription end or sunset date, whichever comes first.
  • Pricing tiers gate features aggressively: advanced workflows move from Team to Professional, and reporting depth varies significantly across plans with no transparency in published docs.
  • Customers report the platform does not accommodate SaaS business models well and lacks advanced reporting capabilities that growing companies require.
  • Per-user pricing compounds with seat creep as teams add power users, temp licenses, and partner access, making total cost unpredictable.
  • Support-only billing and multiple login charges frustrate teams that feel they already pay for the service and should receive unlimited user seats on paid tiers.

Choosing

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How Zendesk Sell objects map to Salesforce Sales Cloud

Each row shows how a Zendesk Sell object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Zendesk Sell

Lead

maps to

Salesforce Sales Cloud

Lead

1:1
Fully supported

Sell Leads migrate directly to Salesforce Lead. 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.

Zendesk Sell

Contact

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

Sell Contacts migrate to Salesforce Contact. 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.

Zendesk Sell

Company

maps to

Salesforce Sales Cloud

Account

1:1
Fully supported

Sell Company records map to Salesforce Account. 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.

Zendesk Sell

Deal

maps to

Salesforce Sales Cloud

Opportunity

1:1
Fully supported

Sell Deals map to Salesforce Opportunity. 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.

Zendesk Sell

Pipeline

maps to

Salesforce Sales Cloud

Record Type

lossy
Fully supported

Each Sell Pipeline becomes a Salesforce Record Type on Opportunity. 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.

Zendesk Sell

Stage

maps to

Salesforce Sales Cloud

Stage Name (Sales Process)

lossy
Fully supported

Sell Stages are children of Pipelines with ordinal position, loss/win flags, and probability. 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.

Zendesk Sell

Line Item

maps to

Salesforce Sales Cloud

OpportunityLineItem

1:1
Fully supported

Sell Line Items attach to Deals and carry product name, quantity, and price. Salesforce models this as OpportunityLineItem linked to a PricebookEntry and Opportunity. We create Product2 records and Standard Pricebook entries during the schema phase, then link Line Items during migration. If the destination org does not use Salesforce CPQ, Line Items map to custom fields on Opportunity or a custom Line Item object.

Zendesk Sell

Task

maps to

Salesforce Sales Cloud

Task

1:1
Fully supported

Sell Tasks with due dates, assignees, completion status, and descriptions migrate to Salesforce Task. Notes attached to Tasks in Sell migrate as Salesforce Note records linked via ContentDocumentLink to the parent Task. Task assignment resolves via email match from Sell Owner to Salesforce User.

Zendesk Sell

Note

maps to

Salesforce Sales Cloud

Note

1:1
Fully supported

Sell Notes are free-text records attached to Contacts, Deals, Leads, or Companies. We migrate Notes with parent reference intact so conversation context links to the correct Salesforce record (Lead, Contact, Account, or Opportunity). Rich text and embedded images in Sell Notes migrate as Salesforce Note with content preserved.

Zendesk Sell

User

maps to

Salesforce Sales Cloud

User

1:1
Fully supported

Sell Users (sales reps, admins) export with email, role, and territory. We match Users by email to the destination Salesforce org. Any Sell User without a matching Salesforce User goes to a reconciliation queue for admin provisioning before record import resumes.

Zendesk Sell

Call Record

maps to

Salesforce Sales Cloud

Task (TaskSubtype = Call) + ContentDocument

1:1
Fully supported

Sell call logs, call outcomes, and call duration migrate to Salesforce Task with TaskSubtype = Call and disposition stored in a custom field. Call recording audio files migrate as ContentDocument records linked to the Task via ContentDocumentLink, requiring separate file transfer and storage consideration in Salesforce.

Zendesk Sell

Custom Field

maps to

Salesforce Sales Cloud

Custom Field

1:1
Fully supported

Sell custom fields exist on Leads, Contacts, Deals, and other objects. We resolve the Sell numeric custom field ID and the separate field key (required for bulk API calls) during scoping and maintain a lookup table. Custom field values map to Salesforce custom fields with equivalent types (text, number, date, picklist, checkbox). Multi-select picklist values in Sell map to Salesforce multi-select picklist; we flag any multi-select Sell field that cannot map directly.

Zendesk Sell

Tag

maps to

Salesforce Sales Cloud

Multi-Select Picklist or Topic

lossy
Fully supported

Sell Tags are labels applied to Contacts, Deals, and Leads for segmentation. We migrate Tags as-is and note that Salesforce handles tag-based filtering differently. The customer chooses during scoping whether tags become Salesforce multi-select picklist fields on the target object or Topic assignments with TopicAssignment records.

Zendesk Sell

Document

maps to

Salesforce Sales Cloud

ContentDocument + ContentVersion

1:1
Fully supported

Sell Documents attach to records as file references. We migrate document metadata (name, description, file type) and URL pointers where available. File binary content migrates as Salesforce ContentVersion with ContentDocumentLink to the parent record. Large file migration is flagged as a separate step requiring Salesforce file storage planning.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Zendesk Sell logo

Zendesk Sell gotchas

High

Sell sunset creates a hard deadline for data migration

Medium

Sell API rate limits are low for large-volume exports

Medium

Custom field IDs differ from field keys in API calls

Medium

Sequences and cadence state cannot be migrated

Low

Job queue limit of 30 concurrent background jobs

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • 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. 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.

  • 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. 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.

  • Sell Sequences cannot be migrated to Salesforce

    Sell Sequences store enrollment state, step history, reply tracking, and cadence timing tied to individual Contacts. 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.

  • 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). 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.

  • 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. 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.

Migration approach

Six steps for a successful Zendesk Sell to Salesforce Sales Cloud data migration

  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. 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. 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. 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. 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). 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. 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.

Platform deep dives

Context on both ends of the pair

Zendesk Sell logo

Zendesk Sell

Source

Strengths

  • Native click-to-dial and call recording built into every tier without add-on cost.
  • Multichannel unified inbox consolidating email, chat, voice, and social tickets in one place.
  • Conversational UI reduces training friction for sales reps new to CRM tools.
  • Deep Zendesk Support integration for companies running both Sell and Support.
  • Mobile-first design with geolocation and full CRM functionality on iOS and Android.

Weaknesses

  • Sell is being retired August 31, 2027, with no new development expected and data deletion on sunset.
  • Feature gating across tiers forces upgrades for basic workflow automation and reporting depth.
  • Per-user pricing with no unlimited seat option on paid plans inflates cost as teams grow.
  • Advanced SaaS metrics, custom reporting, and product-led growth features are limited compared to purpose-built sales platforms.
  • Export and migration tooling is CSV-heavy with limited bulk API automation outside the developer API.
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Zendesk Sell and Salesforce Sales Cloud.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Zendesk Sell: Sell Core API: 36,000 requests/hour (10 req/token/sec); Zendesk Support varies by plan tier from 20 req/min (Team) to 700 req/min (Enterprise).

  • Data volume sensitivity

    A

    Zendesk Sell exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Zendesk Sell to Salesforce Sales Cloud migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Zendesk Sell to Salesforce Sales Cloud data migrations

Answers to the questions buyers ask most during Zendesk Sell to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Zendesk Sell to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

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.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Zendesk Sell.
Land in Salesforce Sales Cloud, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day