CRM migration

Migrate from Zendesk Sell to Freshsales

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

Zendesk Sell logo

Zendesk Sell

Source

Freshsales

Destination

Freshsales logo

Compatibility

63%

5 of 8

objects map 1:1 between Zendesk Sell and Freshsales.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Zendesk Sell objects map to Freshsales

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

maps to

Freshsales

Person (Lead subtype)

1:many
Fully supported

Zendesk 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

maps to

Freshsales

Person (Contact subtype)

1:many
Fully supported

Sell 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

maps to

Freshsales

Account

1:1
Fully supported

Sell 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

maps to

Freshsales

Deal

1:1
Fully supported

Sell 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

maps to

Freshsales

Deal Pipeline + Stage (inline)

lossy
Fully supported

Sell 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

maps to

Freshsales

Activity (Task subtype)

1:1
Fully supported

Sell 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

maps to

Freshsales

Activity (Call subtype)

1:1
Fully supported

Sell 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

maps to

Freshsales

Note

1:1
Fully supported

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

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Sell sunset deadline creates time-bound migration windows

    Zendesk formally retired Sell on August 31, 2027, and deletes all data per its Service Data Deletion Policy upon subscription end or the sunset date, whichever comes first. 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 contact FlitStack AI in Q4 2026 or Q1 2027 face constrained specialist availability and compressed timelines that increase cost and risk data loss. We strongly encourage customers to begin planning before Q3 2026 to secure an orderly migration window.

  • Freshsales does not have a native custom objects API at Growth tier

    Sell supports custom objects with configurable fields and relationships at Professional tier ($49 per user). Freshsales Growth tier ($15 per user) does not expose a custom objects API equivalent; deal fields and products are configurable but true custom object creation with independent schemas is limited to higher tiers or requires Freshsales's Products module as a workaround. We inventory all Sell custom objects during scoping and either map them to Freshsales custom fields, use the Products module, or flag them as requiring schema redesign before migration. If the customer's data model depends on standalone custom objects, the migration scope expands accordingly.

  • Sequences and engagement cadence state cannot migrate

    Sell Sequences store enrollment state, step timing, reply tracking, and cadence metadata tied to individual Contacts. This automation data is not exportable as a discrete object via the Sell Core API and has no equivalent in Freshsales's standard CRM feature set. We export Sequence metadata (name, step count, cadence) as a reference document and flag that sales reps must rebuild active sequences in Freshsales's Workflows or a dedicated sales engagement tool. We do not migrate enrollment state or paused-sequence resume points because the destination cadence model differs structurally from Sell's.

Migration approach

Six steps for a successful Zendesk Sell to Freshsales data migration

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

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

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

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

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

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.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

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

  • 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 Freshsales 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 Freshsales data migrations

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

Can't find your answer?

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 consultation

Migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Deals with no custom objects and a clean pipeline structure. Migrations with multiple Sell Pipelines, large engagement histories (over 200,000 activity records), or Sell custom objects requiring Freshsales field remapping move to seven to ten weeks because of schema reconciliation and parent-record dependency ordering. The August 31, 2027 Sell sunset deadline means customers who begin before Q3 2026 can secure orderly migration windows; those waiting until 2027 face constrained specialist availability.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Zendesk Sell.
Land in Freshsales, 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