CRM migration
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
Source
Salesforce Sales Cloud
Destination
Compatibility
11 of 14
objects map 1:1 between Zendesk Sell and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
4-6 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Salesforce Sales Cloud
Lead
1:1Sell 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
Salesforce Sales Cloud
Contact
1:1Sell 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
Salesforce Sales Cloud
Account
1:1Sell 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
Salesforce Sales Cloud
Opportunity
1:1Sell 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
Salesforce Sales Cloud
Record Type
lossyEach 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
Salesforce Sales Cloud
Stage Name (Sales Process)
lossySell 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
Salesforce Sales Cloud
OpportunityLineItem
1:1Sell 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
Salesforce Sales Cloud
Task
1:1Sell 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
Salesforce Sales Cloud
Note
1:1Sell 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
Salesforce Sales Cloud
User
1:1Sell 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
Salesforce Sales Cloud
Task (TaskSubtype = Call) + ContentDocument
1:1Sell 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
Salesforce Sales Cloud
Custom Field
1:1Sell 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
Salesforce Sales Cloud
Multi-Select Picklist or Topic
lossySell 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
Salesforce Sales Cloud
ContentDocument + ContentVersion
1:1Sell 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.
| Zendesk Sell | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline | Record Typelossy | Fully supported | |
| Stage | Stage Name (Sales Process)lossy | Fully supported | |
| Line Item | OpportunityLineItem1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Call Record | Task (TaskSubtype = Call) + ContentDocument1:1 | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported | |
| Tag | Multi-Select Picklist or Topiclossy | Fully supported | |
| Document | ContentDocument + ContentVersion1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Sell sunset creates a hard deadline for data migration
Sell API rate limits are low for large-volume exports
Custom field IDs differ from field keys in API calls
Sequences and cadence state cannot be migrated
Job queue limit of 30 concurrent background jobs
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Zendesk Sell
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Zendesk Sell and Salesforce Sales Cloud.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
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
Zendesk Sell exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Zendesk Sell to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Zendesk Sell
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.