Migrate from Pipedrive to Salesforce Sales Cloud

Pipedrive Persons map to Salesforce Contact. Name, email, phone, address, and social link fields translate directly to Contact fields. We use email as the dedupe key during import. Custom fields on Person migrate to custom Contact fields of matching type (text, picklist, number, date). Tags on Person migrate to a multi-select picklist or to Salesforce Topics with TopicAssignment records per customer preference.

Pipedrive Organizations map to Salesforce Account. Name, address, phone, website, and industry fields translate directly. Custom fields on Organization migrate to custom Account fields. Account is created before Contact import so that the AccountId lookup is satisfied at Contact insert time. In Pipedrive, a Person can be linked to zero Organizations; we create a placeholder Account (named from the Person's email domain or a 'No Organization' flag) for any Contact without an Organization link so the AccountId foreign key is satisfied in Salesforce.

Pipedrive Deals map to Salesforce Opportunity. Each Deal is tied to one Person and one Organization in Pipedrive; we resolve both to ContactId and AccountId before inserting the Opportunity. Stage names from Pipedrive map to Salesforce StageName values defined in the destination Sales Process. Deal value (formatted currency) maps to Amount; expected close date maps to CloseDate. Loss reason flags migrate to a custom Opportunity field.

Pipedrive's separate Lead pool (introduced in Pipedrive's newer UX) maps directly to Salesforce Lead. Lead inherits all Deal custom fields in Pipedrive; we map these to Salesforce Lead custom fields. Pipedrive Leads that have not entered the deal flow remain in Salesforce as Lead records. Pipedrive Leads that have advanced into Deals map to Opportunity records per the Deal mapping logic.

Pipedrive Pipelines (named deal containers) map to Salesforce Record Types on Opportunity. Each Pipedrive Pipeline becomes a Record Type with its own Page Layout and Sales Process. Stage names within each Pipeline map to StageName values whitelisted in that Sales Process. Pipedrive does not expose pipelines as API objects; we extract pipeline definitions via the Pipelines and Stages API endpoints and translate them to the Salesforce metadata structure.

Pipedrive Stages define deal progression within a Pipeline, each with a name, position, and probability. We map stage names and probabilities to Salesforce StageName and StageProbability. If the destination org already has stage values, we match by name and flag any Pipedrive stages with no Salesforce equivalent for the admin to decide on.

Pipedrive Activities are a unified object with a type field distinguishing tasks, calls, meetings, and notes. We split by type: tasks map to Salesforce Task; calls map to Task with TaskSubtype=Call and call duration in CallDurationInSeconds; meetings map to Salesforce Event with StartDateTime and EndDateTime; standalone notes map to Salesforce Note attached via ContentDocumentLink. The linked Person and Deal in Pipedrive resolve to WhoId (Contact or Lead) and WhatId (Opportunity or Account) in Salesforce. Activity timestamps are preserved to maintain the timeline ordering.

Pipedrive Products (standalone items with SKU, pricing, and unit information) map to Salesforce Product2. Standard Pricebook entries are created during import. Pipedrive's product-variation model (size, color) translates to Salesforce product attributes if the customer uses Salesforce CPQ; otherwise, variants migrate as separate Product2 records.

Pipedrive Products attached to Deals via Deal-Product associations map to Salesforce OpportunityLineItem. We resolve Pricebook2, Product2, and Opportunity references at migration time. Quantity and pricing migrate directly. The customer must enable products on the Opportunity before this mapping applies; we flag this in the pre-flight checklist.

Pipedrive custom fields use a 40-character per-account hash as the API key. We read the hash-to-label mapping from the source account API response, resolve human-readable names, and map values to Salesforce custom fields by label and field type (text, number, date, picklist). Custom field type translation is validated during scoping: Pipedrive free-text fields that represent a closed vocabulary must become Salesforce picklists, which requires the customer to provide the value set before migration.

Pipedrive Users who own records map to Salesforce User records resolved by email address. We extract every distinct owner_id referenced on Persons, Organizations, Deals, Activities, and Products. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Pipedrive Tags are label strings applied across Persons, Organizations, Deals, and Products. We migrate tags as string arrays. In Salesforce, tags on Contacts and Accounts become a multi-select picklist field. Tags used for content or topic classification become Salesforce Topics with TopicAssignment records linked to the parent record. The customer chooses the strategy during scoping.