Migrate from Zendesk Sell to Pipedrive

Sell Leads map directly to Pipedrive Leads. 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.

Sell's separate Lead and Contact objects both map to Pipedrive's single Persons object. 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.

Sell Companies map 1:1 to Pipedrive Organizations. 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.

Sell Deals map 1:1 to Pipedrive Deals. 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.

Sell Pipelines and their child Stages are recreated in Pipedrive as Pipelines with ordered Stages inside. 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.

Sell Tasks with due dates, assignees, and completion status map to Pipedrive Activities with type = 'task'. 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.

Sell call logs (call outcome, duration, recording URL) map to Pipedrive Activities with type = 'call'. The call disposition maps to a custom Activity field; call duration maps to a numeric custom field. Call recording audio files require separate file storage transfer and are linked to the Activity via a custom field holding the recording URL. We flag large call recording libraries as a separate file-migration step and advise on Pipedrive's storage limits per plan.

Sell meeting records map to Pipedrive Activities with type = 'meeting'. Title, start and end timestamps, location, and attendee list migrate. Pipedrive does not support a native attendee list as a standard field; we map attendee emails to a custom Activity field or Note for reference. Meeting notes attached in Sell migrate as Pipedrive Notes linked to the Activity.

Sell Notes attached to Contacts, Deals, Leads, or Companies migrate as Pipedrive Notes linked to the corresponding Person, Deal, Lead, or Organization. Note body text transfers as-is. Parent record reference is preserved by resolving the Sell parent ID to the Pipedrive record ID at migration time.

Sell custom fields on Leads, Contacts, Deals, and Companies map to Pipedrive custom fields of equivalent type. Sell's numeric custom field IDs must be resolved to field keys during scoping; Pipedrive uses field IDs differently. We build a field-key lookup table during discovery, pre-create custom fields in Pipedrive via the API before import begins, and then map values using the correct destination field identifiers. Picklist values, multi-select values, and date formats are normalized to match Pipedrive's accepted formats.

Sell Tags applied to Contacts, Deals, and Leads migrate to Pipedrive Labels. Tag-to-Label is a direct string mapping preserved at record level. Pipedrive Labels are entity-scoped (Person, Deal, Lead, Organization) matching Sell's tagging model. We note that Pipedrive does not support cross-entity tagging from a single label; multi-entity tag use cases are preserved per entity type.

Sell Products with SKU, name, price, and description map to Pipedrive Products. Products must exist in Pipedrive before Deal-Product associations can be created. We import Products first in the sequence, then associate them to Deals using the product_id reference resolved from the Pipedrive Product import.