---
title: "Zendesk Sell to Pipedrive Migration | FlitStack AI"
description: "Migrate Zendesk Sell to Pipedrive with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/zendesk-sell/to/pipedrive"
---

# Zendesk Sell to Pipedrive migration

We migrate Leads, Contacts, Companies, Deals, and Activities from Zendesk Sell into Pipedrive with the Sell Lead-versus-Contact consolidation resolved before import, custom fields mapped via a field-key lookup table built during discovery, and the August 31, 2027 data-deletion deadline factored into the project schedule from day one.

Short answer

FlitStack AI migrates leads, persons, organizations, deals and pipeline + stages from Zendesk Sell to Pipedrive, 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: 2-4 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/zendesk-sell/to/pipedrive#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Zendesk Sell ![](https://flitstack.ai/platforms-trim/zendesk-sell.webp)

Destination Pipedrive ![](https://flitstack.ai/platforms-trim/pipedrive.webp)

Lead Person Organization Deal Pipeline + Stage

Mapped field by field · sample run · one-click rollback

## What moves from Zendesk Sell to Pipedrive?

Moving from Zendesk Sell to Pipedrive is driven by Zendesk's official retirement of Sell on August 31, 2027, with data deletion per the Zendesk Service Data Deletion Policy.

Read the full summary

The two platforms share a similar sales-first object model — Leads map to Leads, Contacts map to Persons, Companies map to Organizations, Deals map to Deals — but Sell separates Leads from Contacts while Pipedrive consolidates all people into a single Persons object, requiring a consolidation step during import. We sequence the migration around Sell's parent-to-child dependency: Pipelines and Stages are configured in Pipedrive first, then Companies, then Contacts with their Company link resolved, then Deals with their Contact and Company lookups satisfied, then Activities (calls, tasks, meetings, notes). Custom fields and tags migrate with field-key resolution during scoping. Sell Sequences, email cadences, and workflow automations do not migrate; we deliver a written inventory of active sequences and workflows for the customer's admin to rebuild in Pipedrive's automation engine. We do not migrate reports or dashboards as configuration; we export them as reference documents for manual rebuild.

1:1

### Lead → Lead

Sell Leads map directly to Pipedrive Leads.

How it maps

We preserve all standard Lead fields (name, email, phone, source, status) and custom Lead Fields via a field-key lookup table resolved during discovery. Unconverted Sell Leads land as Pipedrive Leads with their original lead\_source and any custom qualification fields carried over. Pipedrive's Lead status values are mapped to the closest Sell status equivalents; the customer selects the target Lead status during scoping.

1:N merge

### Contact → Person

Sell's separate Lead and Contact objects both map to Pipedrive's single Persons object.

How it maps

We run a consolidation step during data transform: Sell Contacts with no corresponding Sell Lead convert directly to Pipedrive Persons. Sell Leads that were never converted into Contacts convert to Pipedrive Persons with a custom field sell\_original\_type\_\_c = 'Lead' preserved for reporting. Sell Contacts that originated from a Lead conversion map as Persons with that field = 'Contact'. This prevents data duplication and preserves the source record type for audit.

1:1

### Company → Organization

Sell Companies map 1:1 to Pipedrive Organizations.

How it maps

The domain field in Sell becomes the Organization's website URL. Organization is created before any Person import so that the Pipedrive Organization-ID lookup is satisfied at the moment of Person insert. We preserve industry, employee count, and address fields as standard or custom fields based on the customer's field inventory.

1:1

### Deal → Deal

Sell Deals map 1:1 to Pipedrive Deals.

How it maps

The Sell dealstage property maps to a Pipedrive Stage that belongs to a specific Pipeline; we resolve the pipeline and stage by name during import. Loss reasons from Sell become a custom field on Pipedrive Deal. Deal value, expected close date, and custom Deal Fields migrate directly. Pipedrive Deal status (open, won, lost) maps from Sell's stage-level win/loss flags.

configuration

### Pipeline + Stage → Pipeline + Stage

Sell Pipelines and their child Stages are recreated in Pipedrive as Pipelines with ordered Stages inside.

How it maps

Each Sell pipeline becomes a Pipedrive Pipeline; stage order and names transfer. Sell stage-level loss/win flags map to Pipedrive Stage status (won/lost/open). Pipedrive's stage probability percentages are set to match Sell's where defined, or to sensible defaults where Sell has no probability data. We configure this before any Deal import so that stage assignment is valid at insert time.

1:1

### Task → Activity

Sell Tasks with due dates, assignees, and completion status map to Pipedrive Activities with type = 'task'.

How it maps

The original Sell task subject becomes the Activity subject, due date and assignee migrate, and completion status maps to completed = true/false. Activity timestamp preserves the original Sell created date for timeline ordering.

******What moves 12 objects

Zendesk Sell Pipedrive

- Lead Lead 1:1
- Contact Person merged
- Company Organization 1:1
- Deal Deal 1:1
- Pipeline Pipeline transformed
- Task Activity 1:1

\+ 6 more in the mapping below

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

| Dimension         | Zendesk Sell                                                                      | Pipedrive                                                                                     |
| ----------------- | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| People model      | Separate Lead and Contact objects; Leads qualify into Contacts                    | Single Persons object consolidating all people records                                        |
| Pipeline model    | Custom pipelines with Stages as child containers; Team tier limited to 1 pipeline | Unlimited pipelines from all paid tiers; stages are pipeline-scoped fields                    |
| Activities        | Tasks, Calls (with recording metadata), Meetings, Notes as separate object types  | Activities object grouping calls, meetings, and tasks under one type with Activity type field |
| Products in deals | Line Items as separate objects attached to Deals                                  | Products linked to Deals via Deal-Product association with quantity and price fields          |
| Automation scope  | Sequences with enrollment state; Workflows; Triggers                              | Automation rules, Smart Campaigns, and sequence rebuilds; enrollment state not migratable     |
| Pricing structure | Per-user: $19 Team (3-user cap), $49 Professional                                 | Per-user: Essential through Advanced tiers, different feature gates per tier                  |
| Reporting         | Built-in deal and activity reports; Advanced Reporting add-on on Professional     | Visual pipeline reports, revenue goals, and performance tracking built in                     |

## What to watch for in a Zendesk Sell to Pipedrive migration

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

high

### Sell sunset creates a hard data-deletion deadline

Zendesk retired Sell on August 31, 2027.

How we handle it

All Sell data is deleted per the Zendesk Service Data Deletion Policy on subscription end or the sunset date, whichever arrives first. Organizations that delay migration planning until 2027 face rushed migrations, specialist availability constraints, and potential data loss. We schedule discovery calls with a migration-start target no later than 9 months before the deadline and advise customers to begin migration planning 12-18 months ahead to allow time for data cleanup, testing, and team training without last-minute pressure.

high

### Lead and Contact consolidation requires design before import

Sell separates Leads from Contacts; Pipedrive consolidates all people into a single Persons object.

How we handle it

The migration must decide how to handle Sell Leads that were never converted to Contacts. We map converted Sell Leads to Persons with sell\_original\_type\_\_c = 'Contact' and unconverted Sell Leads to Persons with sell\_original\_type\_\_c = 'Lead', preserving the distinction for reporting. Migrations that skip this consolidation step either duplicate records (if every Lead and Contact is imported as a separate Person) or lose the Lead/Contact provenance. We define the consolidation rule during discovery and apply it as the first transform step.

medium

### Custom field IDs require a field-key lookup table before migration

Sell assigns a numeric custom field ID and a separate custom field key to all custom fields.

How we handle it

When writing to Pipedrive's API, the destination custom field identifier must be known and correctly referenced. We resolve both Sell identifiers during the scoping phase, pre-create equivalent custom fields in Pipedrive via the API, and maintain a field-key lookup table mapping Sell field keys to Pipedrive field IDs before writing a single record. Without this resolution step, custom field values either fail to write or write to the wrong fields.

medium

### Sequences and cadence state cannot migrate

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

How we handle it

This automation data is not exportable as a discrete object and has no equivalent structure in Pipedrive. We export Sequence metadata (names, step counts, cadence patterns) as a reference document and flag active sequences that reps must rebuild in Pipedrive's automation tools. We do not attempt to migrate enrollment state because paused or in-progress sequences would carry incorrect resume points. Call recording audio files similarly require separate file storage transfer and are linked to Activities via a custom URL field rather than migrated as native Pipedrive attachments.

low

### Sell API rate limits and job queue constraints affect export throughput

The Sell Core API permits 36,000 requests per hour (10 requests per token per second) per token, with a maximum of 30 queued or running background jobs for bulk update endpoints.

How we handle it

We implement rate-limit-aware polling using X-RateLimit-Remaining headers and pause between chunks to avoid hitting the ceiling. We monitor the zendesk-ratelimit-inflight-jobs header during export and throttle batch submissions accordingly. For organizations with hundreds of thousands of records, this adds processing time but prevents 429 errors and TooManyJobs failures that would otherwise require retry logic.

## How the migration runs

1. ### Discovery and scoping

   We audit the source Sell account across tier (Team or Professional), object counts (Leads, Contacts, Companies, Deals, Tasks, Notes, custom fields, tags), pipeline count, stage names, and active sequences.

   What this step covers

   We extract a representative data sample via the Sell Core API to verify field coverage and data quality. We also inventory Sell's user list for Owner mapping and flag any deal-currency or multi-currency considerations. The discovery output is a written migration scope with record counts per object, custom field inventory, pipeline-stage mapping, and a migration-start recommendation tied to the August 31, 2027 deadline.

2. ### Pipedrive setup and schema pre-creation

   We create Pipelines and Stages in Pipedrive matching the Sell pipeline-stage structure before any data import begins.

   What this step covers

   We pre-create custom fields via the Pipedrive API using the field-key lookup table from scoping, matching Sell field types to Pipedrive field types (text, numeric, date, picklist, multi-select). We configure user provisioning: Sell Owners map to Pipedrive Users by email match, with missing users flagged for the customer's admin to provision before the production migration phase begins.

3. ### Sample migration and reconciliation

   We run a sample migration of 50-100 records per object type into a staging environment, verifying that Pipedrive record counts, field mapping, and relationship resolution (Company on Person, Contact on Deal) match the source Sell data.

   What this step covers

   The customer spot-checks 25 random records against Sell, confirms that custom fields populated correctly, and signs off the mapping before full production migration begins. Any field-type corrections or pipeline adjustments happen at this stage, not during production cutover.

4. ### Production migration in dependency order

   We run production migration in record-dependency order: Pipelines and Stages (configured, not imported), Products (required for Deal-Product associations), Organizations (from Sell Companies), Leads (pre-convert map), Contacts and Deals (with CompanyId and PersonId lookups resolved), then Activities (calls, tasks, meetings, notes) via Pipedrive's API with rate-limit handling.

   What this step covers

   Each phase emits a row-count reconciliation report. Custom field values are written using the resolved field-key lookup table to prevent mismapped writes.

5. ### Cutover and delta sync

   We freeze Sell to read-only during the cutover window.

   What this step covers

   We run a final delta migration capturing any records modified or created in Sell during the migration window. The customer switches to Pipedrive as the system of record. We validate record counts, spot-check relationship integrity (Deals linked to Persons, Persons linked to Organizations), and deliver the migration summary report. A one-week hypercare window covers any reconciliation issues raised by the sales team.

6. ### Automation inventory handoff

   We deliver a written inventory of all active Sell Sequences (name, step count, cadence type) and Sell Workflows (trigger, conditions, actions) for the customer's admin to rebuild in Pipedrive's automation tools.

   What this step covers

   We do not rebuild Sell automations as Pipedrive automation rules; that is outside standard migration scope. Reports and dashboards do not migrate as configuration; we export them as reference documents for manual rebuild in Pipedrive's reporting interface. Post-migration admin training or workflow rebuild consulting is a separate engagement.

![](https://flitstack.ai/platforms/zendesk-sell.svg) Zendesk Sell ![](https://flitstack.ai/platforms/pipedrive.svg) Pipedrive

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Pipedrive Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**2-4 weeks** Typical, smaller accounts

**6-10 weeks** Large or heavily customised accounts

A quote scales with total record count and the number of custom fields, pipelines, and activity records requiring migration. Sell's August 31, 2027 sunset means we treat every Sell migration as time-bound, prioritizing early-start customers for specialist availability in the 12-18 months before the deadline. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Zendesk Sell to Pipedrive →](https://flitstack.ai/contact)

## Why teams move from Zendesk Sell to Pipedrive

- Zendesk formally retired Sell on August 31, 2027, with all data deleted per the Zendesk Service Data Deletion Policy on subscription end or sunset date, whichever arrives first. There is no extension. Organizations relying on Sell have a hard deadline to migrate, and waiting until Q1 2027 creates last-minute data-loss risk, constrained specialist availability, and rushed cutovers. Teams that begin migration planning 12-18 months before sunset complete with lower risk and more scheduling flexibility.
- Sell's Team tier caps at 3 paid users and permits only one custom pipeline, while Pipedrive's Essential tier supports unlimited pipelines and more flexible user scaling. Growing sales teams hit Sell's ceiling without upgrading to the $49/user Professional tier, whereas Pipedrive's tier model scales more granularly. Reviewers on GetApp (4.5 stars for Pipedrive vs 4.3 for Sell) and Gartner Peer Insights cite pipeline flexibility and per-seat pricing predictability as key differentiators.
- Pipedrive is a sales-first CRM with a visual pipeline interface built specifically for sales teams, while Zendesk Sell is one product in Zendesk's broader customer service and support suite. Organizations that selected Sell primarily for its sales capabilities but now face migration find that Pipedrive offers equivalent or deeper sales-specific features — visual pipelines, deal tracking, activity management, and revenue reporting — without the Zendesk ecosystem dependency and sunset risk.
- Zendesk officially partners with Pipedrive as the recommended migration path for Sell customers. Pipedrive maintains an official Zendesk Sell migration guide in its Knowledge Base covering Leads, Contacts, Deals, Companies, Tasks, Notes, Tags, and custom fields. This official endorsement means the target platform is pre-validated for Sell data, reducing migration uncertainty and providing a supported fallback path if custom tooling encounters edge cases.
- Organizations report that Sell's reporting depth and SaaS-specific metrics are limited compared to purpose-built sales CRMs. Pipedrive's reporting engine, revenue goals, and performance tracking are designed for sales operations teams that need pipeline forecasting, rep performance, and deal-loss analysis without exporting to a BI tool. For teams that outgrew Sell's reporting, Pipedrive offers a more capable analytics layer at a comparable per-seat price point.

Questions, answered

## Zendesk Sell to Pipedrive migration questions

How long does a Zendesk Sell to Pipedrive migration take?

Most migrations land between two and four weeks for accounts with under 10,000 total records and limited custom fields. Migrations with over 20,000 records, multiple Sell pipelines, extensive custom fields, or large activity histories (call logs, tasks, meeting records) move to six to ten weeks because of API batch chunking, parent-record lookup resolution, and the delta-sync step at cutover. Sell's August 31, 2027 sunset means we treat every Sell migration as time-bound and schedule discovery with a migration-start target at least 9 months before the deadline.

What data migrates from Zendesk Sell to Pipedrive?

We migrate Leads, Contacts, Companies, Deals, Tasks, Notes, Tags/Labels, Custom Fields, Products, and Deal-Product associations. Activity history (calls, meetings, tasks) migrates with parent-record references preserved. Call recording metadata (duration, outcome, recording URL) transfers; audio file storage requires a separate file-transfer step outside the standard migration scope. Custom field values migrate with the field-key lookup table resolved before import.

What does not migrate from Zendesk Sell to Pipedrive?

Sell Sequences and email cadence automation do not migrate because enrollment state is not exportable and Pipedrive uses a different automation model. We export Sequence metadata as a reference document. Sell Workflows and Triggers do not migrate; we deliver a written inventory for the customer's admin to rebuild in Pipedrive's automation rules. Reports and dashboards do not migrate as configuration; we export them as reference documents for manual rebuild. File attachments and document URLs migrate as metadata references only; actual file storage transfer is a separate step.

Can we migrate Sell's Leads and Contacts into Pipedrive without duplicating records?

Yes. Sell's separate Lead and Contact objects both map to Pipedrive's Persons object. We apply a consolidation rule during data transform: Sell Contacts convert to Pipedrive Persons directly. Sell Leads that were never converted to Contacts convert to Pipedrive Persons with a custom field sell\_original\_type\_\_c = 'Lead' preserved for reporting. This prevents duplication and retains the source record type for audit and segmentation in Pipedrive.

Does Pipedrive have an official migration tool for Zendesk Sell?

Pipedrive maintains an official Zendesk Sell migration guide in its Knowledge Base covering Leads, Contacts, Deals, Companies, Tasks, Notes, Tags, and custom fields. Pipedrive's native import tools support CSV-based uploads for these objects. However, native tools do not handle relationship resolution between records, custom field ID mapping, or large-volume API-based migration with rate-limit handling. Our migration service uses Pipedrive's API directly with dependency sequencing, field-key resolution, and batch chunking to handle migration complexity that exceeds CSV tooling capacity.

When should we start our Zendesk Sell to Pipedrive migration?

Immediately if you have not started. Zendesk retired Sell on August 31, 2027 and all data is deleted per the Zendesk Service Data Deletion Policy on subscription end or the sunset date, whichever arrives first. We recommend beginning migration planning at least 12-18 months before the deadline. Organizations that start 12-18 months ahead complete with time for data cleanup, test migrations, team training, and pipeline rebuild. Waiting until Q1 2027 creates competition for specialist availability and risks a rushed cutover with data integrity gaps.

Do you migrate Sell's custom objects and integrations?

Sell's custom objects (custom entity types beyond the standard objects) migrate if they have a defined schema and API access. We map them to Pipedrive custom fields or Pipedrive's custom object structure where supported by the customer's Pipedrive plan. Third-party integrations connected to Sell via Zapier or native apps do not migrate as configuration; we document the integration list during scoping so the customer's admin can re-establish connections in Pipedrive post-migration. Salesforce integrations, accounting software connections, and other downstream tools that pull data from Sell require re-configuration in Pipedrive as a separate step.

## Related migrations

[![](https://flitstack.ai/platforms-trim/pipedrive.webp) Migrate to **Pipedrive** Every source we move into Pipedrive, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/pipedrive)

### [Pipedrive implementation](https://flitstack.ai/services/pipedrive-implementation)

[Set up Pipedrive and migrate into it as one engagement.](https://flitstack.ai/services/pipedrive-implementation)

[See the service →](https://flitstack.ai/services/pipedrive-implementation) [**Mailchimp to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mailchimp/to/pipedrive) [**Salesforce to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/pipedrive) [**HoneyBook to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/pipedrive) [**HubSpot to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/pipedrive) [**ChartMogul to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/chartmogul/to/pipedrive) [**SmartDesk to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/smartdesk/to/pipedrive) [**Zendesk Sell to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/hubspot) [**Zendesk Sell to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/dynamics-365-sales) [**Zendesk Sell to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/odoo-crm)

## Sources: official documentation

1. [Importing data into Pipedrive with spreadsheets — Knowledge Base](https://support.pipedrive.com/en/article/importing-data-into-pipedrive-with-spreadsheets)
2. [Updating Pipedrive data with a spreadsheet — Knowledge Base](https://support.pipedrive.com/en/article/updating-pipedrive-data-with-a-spreadsheet)
3. [5 Simple CRM Data Migration Methods — Pipedrive Blog](https://www.pipedrive.com/en/blog/crm-data-migration)
4. [Option fields and label-vs-ID matching — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/option-fields)
5. [Import fields — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/import-fields)
6. [Importing: errors and skip files — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/importing-errors-and-skip-files)
7. [Custom field types — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/custom-field-types)

Get a quote

## Moving from Zendesk Sell to Pipedrive?

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

[Get a quote](https://flitstack.ai/contact)
