CRM migration
Field-level mapping, validation, and rollback between Zendesk Sell and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Zendesk Sell
Source
Freshsales
Destination
Compatibility
5 of 8
objects map 1:1 between Zendesk Sell and Freshsales.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Zendesk Sell to Freshsales is driven by Sell's August 31, 2027 sunset date, which triggers automatic data deletion under Zendesk's Service Data Deletion Policy. Freshsales is Freshworks' own CRM offering and shares the same parent company ecosystem, which simplifies both data migration tooling and long-term unified-stack administration. The structural migration differences center on three axes: Sell maintains a separate Lead object alongside Contacts, while Freshsales uses a unified Person model that merges both into a single record; Sell exposes Pipelines and Stages as distinct custom workflow containers, while Freshsales configures pipeline stages inline within the Deals object; and Sell logs calls and meetings as separate engagement objects, while Freshsales records them as Activities with subtype differentiation. We resolve these three schema deltas during scoping, migrate Deals with stage history intact, and deliver a written Sequence and workflow rebuild inventory for the customer's admin team to act on post-migration. Workflows, Sequences, Line Items, and custom Sell Objects do not migrate as code; we document them for manual rebuild.
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 Freshsales, 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
Freshsales
Person (Lead subtype)
1:manyZendesk Sell Leads are unqualified prospects with their own pipeline, sources, and unqualified-reason fields. Freshsales uses a unified Person object where Leads and Contacts merge into a single record with a Person Type property distinguishing lead from contact. We map Sell Lead fields (name, email, phone, source, owner) to Freshsales Person fields and set the person_type field to Lead. The original Sell lead_source is preserved in a custom Freshsales field sell_lead_source__c for segmentation. If the customer used Sell's Lead scoring, we map it to Freshsales's built-in contact scoring or a custom numeric field.
Zendesk Sell
Contact
Freshsales
Person (Contact subtype)
1:manySell Contacts map directly to Freshsales Person records with person_type set to Contact. We resolve the Sell contact-to-owner relationship to the Freshsales Owner field and map custom Contact Fields to Freshsales custom fields, maintaining the field-key lookup table built during scoping. The Freshsales Dedupe settings are configured to match on email as the primary key before import begins.
Zendesk Sell
Company
Freshsales
Account
1:1Sell Companies map to Freshsales Accounts. The company domain becomes the Account Website field and serves as the dedupe key during import. Account is created before Person import so that the account_id lookup is satisfied at the moment of Person insert. Territory and industry fields map directly between platforms.
Zendesk Sell
Deal
Freshsales
Deal
1:1Sell Deals map to Freshsales Deals with deal value, stage, probability, expected close date, and owner preserved. Loss reason and deal source custom fields migrate to Freshsales equivalent custom fields. The deal's closing flag and pipeline assignment transfer as metadata rather than a separate object because Freshsales handles pipeline configuration inline within the Deals module rather than as a standalone container.
Zendesk Sell
Pipeline + Stage
Freshsales
Deal Pipeline + Stage (inline)
lossySell Pipelines and their child Stages are separate objects. Freshsales handles pipeline and stage configuration within the Deals module settings. We map each Sell Pipeline to a Freshsales Pipeline and each Sell Stage to a Freshsales Stage, preserving ordinal position, stage type (open, won, lost), and probability. Stage naming conventions are normalized to match Freshsales defaults during import. If the customer has multiple Sell Pipelines, we configure corresponding Freshsales Pipelines before migration.
Zendesk Sell
Task
Freshsales
Activity (Task subtype)
1:1Sell Tasks migrate to Freshsales Activities with activity_type set to Task. Due date, assignee, priority, completion status, and notes transfer directly. Tasks attached to Contacts or Deals resolve their Freshsales Person or Deal lookup at migration time using the email and deal-name dedupe keys established during scoping.
Zendesk Sell
Call Record
Freshsales
Activity (Call subtype)
1:1Sell call logs (call outcomes, duration, recording URL) migrate to Freshsales Activities with activity_type set to Call. Call disposition maps to a Freshsales custom field call_disposition__c. Call recordings are audio files that require separate file transfer; we migrate recording URLs as metadata and flag the audio file transfer as a separate step that requires the customer to provision file storage access in Freshsales.
Zendesk Sell
Note
Freshsales
Note
1:1Sell Notes attached to Contacts, Deals, Leads, or Companies migrate to Freshsales Notes linked via the target record's ID. We preserve the note body and creation timestamp, and map the note author to the Freshsales Owner or leave it as a system-generated migration entry if the Sell user has no matching Freshsales account.
| Zendesk Sell | Freshsales | Compatibility | |
|---|---|---|---|
| Lead | Person (Lead subtype)1:many | Fully supported | |
| Contact | Person (Contact subtype)1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline + Stage | Deal Pipeline + Stage (inline)lossy | Fully supported | |
| Task | Activity (Task subtype)1:1 | Fully supported | |
| Call Record | Activity (Call subtype)1:1 | Fully supported | |
| Note | Note1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discovery and scoping
We audit the source Zendesk Sell account across tier (Team at $19 or Professional at $49 per user), custom fields, custom objects, pipeline count, active Sequences, active Workflows, engagement volume (calls, emails, meetings, tasks), and document attachment count. We pair this with a Freshsales edition recommendation: Growth ($15 per user) for teams replacing Sell Team; Pro ($49 per user) for teams replacing Sell Professional and wanting Freddy AI; Enterprise ($69 per user) if territory management, custom roles, or advanced analytics are required. The discovery output is a written migration scope, a Sell-to-Freshsales object map, and a Sequence and Workflow rebuild inventory.
Schema design and mapping
We design the Freshsales destination schema before any data moves. This includes creating Freshsales Pipelines and Stages mapped from Sell Pipelines and Stages, provisioning custom fields matched to Sell custom fields using the field-key lookup table, configuring dedupe rules on Person (email primary) and Account (domain primary), and setting Owner assignment rules. If Sell custom objects are present, we map them to Freshsales custom fields or the Products module depending on the data model complexity and tier. Schema design is validated against the scoping output before the Sandbox migration begins.
Sandbox migration and reconciliation
We run a full migration into a Freshsales Sandbox using production-like data volume. The customer's RevOps lead reviews record counts (Persons in, Accounts in, Deals in, Activities in), spot-checks 20-30 random records against the Zendesk Sell source, and validates pipeline and stage assignment. Any mapping corrections are documented and applied before production migration. The Sandbox phase typically takes three to five business days and is included in the standard scoping timeline.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Sell Companies), Persons (Contacts with account_id resolved, then Leads), Deals (with account_id, owner_id, and pipeline resolved), Activities (Tasks, Calls, Meetings, Notes via Freshsales REST API with rate-limit handling and chunking). Each phase emits a row-count reconciliation report before the next phase begins. Sequence metadata, Workflow counts, and custom object inventory are delivered as reference documents at this stage rather than migrated as executable records.
Cutover and rebuild handoff
We freeze Zendesk Sell writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the Sequence and Workflow rebuild inventory to the customer's admin team. We support a five-business-day hypercare window where we resolve any reconciliation issues. We do not rebuild Sell Sequences or Workflows inside the migration scope; that is documented for the customer's admin team to rebuild in Freshsales Workflows or a third-party sales engagement tool.
Platform deep dives
Zendesk Sell
Source
Strengths
Weaknesses
Freshsales
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 Freshsales.
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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Zendesk Sell to Freshsales 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 Freshsales
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.