Migrate your Pipedrive data

Persons are the primary contact record in Pipedrive, holding name, email, phone, and address fields. They link to Organizations and can be attached to Deals. We migrate Persons 1:1 and re-link them to their Organizations and Deals in the destination.

Organizations are company-level records that can hold custom fields and link to multiple Persons. We map them to Accounts or Companies in the destination and preserve all person-organization relationships.

Deals are the core pipeline object, each tied to one Person, one Organization, and a Pipeline Stage. We preserve stage order, loss/reason flags, monetary value, and expected close dates. Stage names are remapped if the destination uses different terminology.

Leads are a separate pool from Deals introduced in Pipedrive's newer UX. Leads inherit all Deal custom fields. Where the destination has no separate Lead object, we merge Leads into Contacts and preserve Lead_Status as a custom property.

Activities encompass tasks, calls, meetings, and notes, each with a type, due date, assigned user, and optional deal/person link. We migrate activities as structured records with their metadata; note bodies migrate as text. Formatting differences between activity types require field-level mapping at migration time.

Products are standalone items with pricing, SKU, and unit information that can be attached to Deals via Deal-Product associations. We migrate Products and their associations, preserving quantity and pricing per deal.

Custom fields exist on Deals, Organizations, Persons, and Products. Pipedrive assigns each custom field a 40-character hash key that is unique per account — the same field name in two different accounts has different hash keys. We translate source hashes to destination-native field IDs during migration, preserving labels, types, and values.

Pipelines are containers for Deal stages and control visual layout. The pipeline definition itself is migrated; Deals are assigned to the matching pipeline in the destination by stage name. If the destination has no equivalent pipeline structure, we create one or map stages into an existing pipeline.

Stages define deal progression within a Pipeline, each with a name, position, and probability. We map stage names and probabilities and preserve deal stage history where available from the API.

Users are the team members who own records, activities, and deals. We map by email address and re-assign owner relationships in the destination. Role and permission structures are not migrated as they are destination-specific.

Tags are label strings applied to Persons, Organizations, Deals, and Products. We migrate tags as string arrays and apply them to the corresponding records in the destination by name match.

Notes are standalone content entries with optional person, organization, or deal attachments. We migrate note text and content, preserve the linked entity reference, and re-attach to the corresponding record in the destination.

Sequences are structured email cadence workflows with step timing, templates, and tracking. The Pipedrive API does not expose Sequences for read or write. We do not migrate Sequences and flag them during scoping so customers can export templates manually.

Automations are condition-based workflow triggers scoped to Pipedrive's event model. The automation definition — conditions, actions, and branching logic — is not fully exposed via the REST API. We do not migrate Automations and recommend rebuilding them in the destination using equivalent features.