There is no native migration path from Zendesk Sell to Pipedrive. Zendesk Sell uses a single Contact object for both individuals and organizations, distinguished only by an is_organization boolean flag. Pipedrive requires separate Person and Organization entities with explicit linking via org_id. The structural gap extends to activities and products: Zendesk Sell maintains distinct objects for Tasks, Calls, and an Order/Line Item chain for deal products, while Pipedrive unifies tasks and calls under a single Activities entity and attaches products directly to deals. Every migration requires API-driven extraction with contact splitting by boolean flag, pipeline and stage recreation with ID crosswalks, custom field structure recreation using Pipedrive's hash-based keys, and Order/Line Item flattening into direct product-on-deal associations.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
A note on Pipedrive API versions
Pipedrive is in the process of rolling out a v2 API alongside its existing v1. Throughout this guide, we reference v2 endpoints where they are available (e.g., POST /api/v2/deals, POST /api/v2/organizations) and fall back to v1 for endpoints that have not yet been migrated (e.g., POST /v1/leads, POST /v1/notes, POST /v1/files). Check the Pipedrive API changelog for the latest availability.
Watch for custom field type incompatibilities
Not all Zendesk Sell custom field types have a direct equivalent in Pipedrive. For example, if Zendesk has a field type that Pipedrive doesn't support, you'll need to choose the closest available type and potentially transform the data. Review the field types on both sides before creating them in Pipedrive, and document any lossy conversions.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Agree scope, pipeline design and success criteria before touching data.
Objective A scope covering every object in the revenue model, with sales leadership signed up to the pipeline design.
Keep these open
-
Inventory every object in Zendesk Sell
Count accounts, contacts, leads, deals or opportunities, activities, notes, emails, files, products and quotes. Activity and email history is usually the largest object by an order of magnitude and the one people forget to size.
Data Profiler Get real record counts instead of estimating from memory -
Map the current pipeline and agree the target model
Document every pipeline, stage, probability and required field, then agree the Pipedrive model with sales leadership. Migrating a broken pipeline faithfully is a wasted opportunity; redesigning it mid-migration is a wasted migration.
Stage changes alter historical conversion rates. Agree how you will restate reporting before you change the model.
-
Catalogue integrations and automation
List every system touching Zendesk Sell: marketing automation, quoting, billing, ERP, data enrichment, dialler, BI. Each is a separate cutover task with its own owner, and each can silently write bad data into your new CRM.
-
Capture the reporting that must survive
Interview the people who actually live in the dashboards — forecast, pipeline coverage, rep activity, cohort conversion. Every one of these needs the underlying fields to migrate, which frequently expands the scope.
-
Build the business case and pick the go-live date
Model licence delta, implementation effort and productivity dip. Then choose the date deliberately: mid-quarter is disruptive, quarter-end is worse. Most teams land on the first week of a new quarter.
COI & ROI Calculator Build the 36-month business case you will need for sign-off
Don't move on until
- Object counts confirmed for accounts, contacts, deals and activities
- Target pipeline and stage model agreed with sales leadership
- Reporting requirements captured from the people who use the reports
02 Data Audit CRM data is usually dirtier than anyone expects. Find out how dirty.
Objective A profiled export with duplicates, ownership gaps and relationship integrity all quantified and triaged.
Keep these open
-
Export and profile every object
Profile null rates, distinct values and type consistency across all objects. Pay attention to fields sales reps were supposed to fill in: an 80% null rate on a field your forecast depends on is a business finding, not a data one.
Data Profiler Profile the Zendesk Sell export for nulls, outliers and type drift -
Quantify duplicates and agree the merge policy
Measure duplicate accounts (same company, different spellings and suffixes) and contacts (same email, or same person at a renamed company). Agree survivorship rules before merging: which record wins, which fields, and what happens to the activity history on the loser.
Merging before you have agreed survivorship rules destroys history irreversibly. Decide first, merge second.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Verify relationship integrity
Check every deal has a valid account, every contact a valid account, every activity a valid parent. Referential breaks are the defect that turns a clean-looking load into a CRM where the pipeline report does not tie to the account list.
-
Resolve ownership and the user map
Build the Zendesk Sell user → Pipedrive user map, including leavers. Every record needs a valid owner: records assigned to deactivated users either fail to load or land unassigned, and unassigned pipeline is pipeline nobody works.
Records owned by deactivated users are a top cause of load failures. Decide the reassignment target before you start.
-
Scan for PII and regional compliance
CRMs hold marketing consent, lawful basis and unsubscribe state. Confirm these fields migrate intact and that consent provenance survives — losing consent records is a regulatory problem, not a data-quality one.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Clean, normalise and archive the pre-state
Normalise country and state values, phone formats, currencies and casing, and standardise all timestamps to UTC. Keep an untouched copy of the raw export — it is your only reference if a mapping decision turns out wrong.
Zendesk Sell → Pipedrive specifics
- Zendesk Sell
- uses cursor-based pagination. Each response includes a links.next_page URL. Keep fetching until next_page is null.
- Pipedrive
- also uses cursor-based pagination. Look for additional_data.next_cursor (v2) or additional_data.pagination.next_start (v1) in responses.
Don't move on until
- Duplicate rate quantified per object with a merge policy agreed
- Every record has a valid owner mapped to a target user
- Relationship integrity verified — no orphaned deals or contacts
03 Field Mapping Map objects, relationships and picklists — in that order.
Objective A signed mapping spec that covers objects, relationships, picklist values and currency handling.
Keep these open
-
Map objects and their relationships first
Establish how Zendesk Sell objects correspond to Pipedrive objects before any field work. Leads-versus-contacts, accounts-versus-organisations and deal hierarchies differ structurally between CRMs, and a field map built on the wrong object model has to be redone.
Schema Mapper Opens pre-loaded with the Zendesk Sell → Pipedrive field pair -
Generate and then hand-review the field map
Auto-match both schemas, then review every row. Look hardest at anything named "type", "source", "stage" or "status", where names match and meanings do not.
-
Map every picklist value, including retired ones
Enumerate all values on both sides — deal stages, lead sources, industries, statuses — and map each explicitly, including values no longer offered but still present on old records. Unmapped values either fail the row or land as blanks that quietly break segmentation.
Historical records often carry picklist values that were retired years ago and no longer appear in the UI.
-
Decide currency, amount and date handling
If you sell in multiple currencies, confirm how Pipedrive stores amounts, exchange rates and dated conversion rates. Recalculating historical deal values at today's rate silently rewrites your revenue history.
Multi-currency deals re-converted at current rates will not tie to your historical reporting or your finance system.
-
Determine the load order
Sequence the load so parents exist before children: users, then accounts, then contacts, then deals, then activities and notes. Keep source IDs in custom fields so relationships can be rebuilt by lookup rather than guesswork.
-
Freeze the spec and sign off
Version-control the mapping, walk RevOps and sales leadership through the decisions that change reporting, and get written sign-off before the pilot.
Don't move on until
- Object and relationship model mapped and reviewed
- Every picklist value explicitly mapped, including dead values
- Load order determined so parents always exist before children
04 Test Migration Pilot with related records, not a flat sample.
Objective A pilot load whose relationships, ownership and roll-up reporting all verify against source.
Keep these open
-
Configure the Pipedrive sandbox to match the agreed model
Build the pipelines, stages, custom fields, record types and user roles first. Load into a default configuration and you will only discover the configuration defects at full scale.
-
Select a connected pilot slice
Take complete account trees — 50-100 accounts with all their contacts, deals, activities and files — rather than a flat random sample. Relationship defects are the whole point of a CRM pilot and a flat sample cannot expose them.
-
Run the load in dependency order with full logging
Load users, accounts, contacts, deals, then activities, logging every request against its source ID. Note which failures are transient (rate limits, timeouts) and which are structural (validation, missing parent).
-
Verify relationships and roll-ups
Confirm every deal sits on the right account with the right owner and stage, and that pipeline totals per account and per rep match Zendesk Sell exactly. Roll-up mismatches almost always mean a relationship or currency defect upstream.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Measure throughput and project the full load
Record actual records-per-hour under Pipedrive's API limits and extrapolate, remembering activity history usually dominates volume. If the projection exceeds your window, split the load or trim activity scope now.
-
Let reps work the pilot data
Put two or three reps in the sandbox against their own accounts. They spot missing context, wrong owners and unusable notes far faster than any reconciliation script, and their buy-in is what makes adoption work.
Don't move on until
- Relationships intact across the whole pilot slice
- Pipeline roll-ups match source for the pilot accounts
- Reps have worked pilot records and confirmed they are usable
05 Cutover Switch the revenue system with the pipeline intact.
Objective All in-scope CRM data live in Pipedrive, integrations repointed, and reps selling on day one.
Keep these open
-
Pre-load history ahead of the freeze
Load closed deals, historical activities and inactive accounts while Zendesk Sell stays live. Only open pipeline and the final delta need to move inside the window.
-
Publish the cutover runbook
A timed sequence with owners and abort criteria: freeze, final export, delta load, integration switch, smoke test, go/no-go, rep enablement. Pick a window that avoids quarter-end and month-end close.
-
Freeze Zendesk Sell and take the final delta
Set Zendesk Sell read-only and export everything changed since the pre-load. Reps updating deals during an unenforced freeze is the classic way to lose the most recent — and most valuable — pipeline changes.
A rep who updates a deal in the old CRM during the freeze will lose that update permanently.
-
Load the delta and reconcile the pipeline
Run the delta, then verify open pipeline value and count per rep against Zendesk Sell before anything else. If the pipeline number is wrong on day one, reps stop trusting the system and never fully come back.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint every integration and verify with real records
Switch marketing automation, quoting, billing, enrichment, dialler and BI connections, then push a live record through each path. An unrepointed integration writing into the old CRM causes divergence that gets harder to reconcile every day.
Two-way integrations left pointing at the old CRM will keep writing there. Disable them before you switch, not after.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Go/no-go, then enable the reps
Call the decision explicitly against the exit criteria. Run enablement on real data with their own accounts on screen, and keep Zendesk Sell read-only rather than cancelled until validation closes.
Don't move on until
- Historical load complete and reconciled before the freeze
- All integrations repointed and verified end to end
- Reps logged in with pipeline visible and correct
06 Validation Prove the revenue numbers tie out, then close the project.
Objective Reconciled data, forecast parity with pre-migration reporting, and signed acceptance.
Keep these open
-
Reconcile every object
Compare counts and values across accounts, contacts, deals, activities and files, plus field-level spot checks on a random sample. Produce a single report suitable for audit and for finance.
Migration Validation Tool Reconcile Zendesk Sell and Pipedrive record-for-record -
Tie the pipeline and forecast to baseline
Rebuild forecast, pipeline coverage and win-rate reporting and compare to pre-migration figures. Every variance needs an explanation — most trace back to stage or currency mapping decisions made in Field Mapping.
Stage-model changes will legitimately shift historical conversion rates. Restate the baseline rather than chasing the difference as a defect.
-
Verify ownership, visibility and permissions
Confirm every record has the right owner and that sharing rules, territories and role hierarchy give each rep exactly the visibility intended. Over-broad visibility in a CRM is a data-protection issue as much as a config one.
-
Re-profile for field completeness
Compare loaded null rates against the source profile per field. A field that arrived empty while counts matched is the failure counts alone cannot detect.
Data Profiler Prove field completeness held up through the load -
Test automation and integration write-back
Fire every workflow, assignment rule, sequence and notification, and confirm each integration writes correctly in both directions. Automation is rebuilt rather than migrated, so it is unproven until observed.
-
Sign off and schedule decommission
Get written acceptance against the Discovery criteria, keep Zendesk Sell read-only for 30-90 days with a final archive export taken, then diarise cancellation so the contract does not auto-renew.
Don't move on until
- Full reconciliation report complete across all objects
- Forecast and pipeline reports tie to pre-migration baselines
- Acceptance signed and Zendesk Sell decommission scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Zendesk Sell Pipedrive
| Zendesk Sell field | Pipedrive field | Notes |
|---|---|---|
| Contact (is_organization: true) | Organization | Zendesk uses a single Contact object for both people and companies. You'll need to filter these based on the is_organization flag. |
| Contact (is_organization: false) | Person | A Zendesk Contact can be linked to an organization via contact_id, which maps to a Pipedrive Person's org_id. |
| Lead | Lead | Pipedrive keeps leads in a separate "Leads Inbox" before they are converted into deals. Zendesk Leads map directly to this concept |
| Deal | Deal | This is a straightforward mapping. Both platforms track ongoing transactions through pipelines and stages |
| Pipelines & Stages | Pipelines & Stages | The concepts are parallel. You will need to recreate the pipeline and stage structure in Pipedrive first. |
| Task | Activity (type task) | Zendesk Tasks map to Pipedrive Activities. Pipedrive uses different ActivityTypes (e.g., call, meeting, task) |
| Call | Activity (type call) & CallLog | Zendesk Calls should be migrated as call type Activities in Pipedrive. They can also be added as CallLogs (specific type of activity that stores call details) in Pipedrive |
| Notes | Notes | Notes can be attached to leads, contacts, and deals in Zendesk and to leads, deals, persons, and organizations in Pipedrive |
| Document | File | Documents attached to Zendesk resources can be migrated to Pipedrive as files attached to the corresponding items |
| Product | Product | Both platforms have a product catalog. Pipedrive allows products to be attached directly to deals |
| Order & Line Item | Product on a Deal | Zendesk uses an Order object with Line Items to link products to a deal. In Pipedrive, you'll add products directly to a deal, specifying quantity and price |
| User | User | Represents the accounts for your team members |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts (organizations) → Organizations | medium | Filter by is_organization flag; must migrate before persons to establish org_id linking |
| Contacts (persons) → Persons | medium | contact_id linking to parent org must be resolved to Pipedrive org_id via crosswalk map |
| Leads → Leads | low | Direct mapping; API-created leads show source as "API" in Pipedrive |
| Deals → Deals | medium | Requires correct pipeline, stage, owner, and contact ID resolution from multiple crosswalk maps |
| Tasks → Activities (task) | low | Straightforward type mapping with subject, due date, and status preservation |
| Calls → Activities (call) + CallLogs | medium | Dual creation needed — Activity for the timeline entry plus CallLog for detailed call metadata |
| Notes → Notes | low | Direct mapping with resource type and ID translation via crosswalk |
| Documents → Files | high | Per-file download from Zendesk and re-upload to Pipedrive; rate limits apply to both sides |
| Products → Products | low | Direct catalog migration with ID mapping for subsequent deal-product linking |
| Orders/Line Items → Products on Deals | medium | Structural transformation from Order model to direct product attachment with quantity and price |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Contact Object Splitting
Zendesk's single Contact must be filtered by the is_organization flag and routed to either Pipedrive Organizations or Persons, with org linking preserved.
Activity Type Unification
Zendesk's separate Task and Call objects must be unified into Pipedrive Activities with appropriate type classification and optional CallLog creation for detailed call data.
Order/Line Item Conversion
Zendesk's Order object with Line Items must be flattened into Pipedrive's direct product-on-deal model with quantity and price specified per attachment.
Custom Field Recreation
Custom field structures must be recreated in Pipedrive before data migration since Pipedrive uses hash-based keys that cannot be predetermined.
Document Migration
Zendesk documents must be downloaded via the provided download_url and re-uploaded to Pipedrive's Files API with correct entity associations.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
Duplicate contacts
If your Zendesk data has contacts with the same email address, Pipedrive may reject or merge them depending on your duplicate detection settings. Audit for duplicates before you start.
Orphaned notes and activities
If a parent record (deal, person, org) fails to migrate, any notes or activities linked to it will have nowhere to land. Always validate that parent records exist before migrating child data.
Currency and deal values
If your Zendesk Sell instance uses multiple currencies, confirm that Pipedrive has the same currencies enabled. Deal values will import as numbers — the currency association must be set explicitly.
Timezone shifts on activity dates
Zendesk Sell and Pipedrive may store and display datetimes in different timezones. Verify that due_date and completed_at values on activities land on the correct dates after migration.
The is_organization split
The most common migration bug: forgetting to filter on is_organization and creating all Zendesk Contacts as Persons. Always migrate Organizations first, then Persons, so the org_id links resolve correctly.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.