Migrate from Salesforce Sales Cloud to Pipedrive

Salesforce Account maps directly to Pipedrive Organization. The Account Name becomes the Organization name, Industry maps to a Pipedrive custom field (since Pipedrive does not have a native Industry taxonomy), and Annual Revenue maps to a numeric custom field. Parent-Account hierarchies in Salesforce (where an Account has a Parent Account) map to Pipedrive Organization parent links; we import Organizations in breadth-first order so that parent Organizations exist before their children are linked.

Salesforce Contacts present the most significant schema challenge in this migration. In Salesforce, Contacts live under Accounts via a many-to-many junction (Account Contact Relation), meaning one Contact can be linked to multiple Accounts with roles. In Pipedrive, a Person record links to one Organization via a single field. We resolve this by mapping the primary Account-Contact relationship (the junction with the IsPrimary flag or the first-created relationship) to the Pipedrive Person-Organization link, and storing all secondary Account IDs and roles as a multi-value custom field on the Person record. Contacts that have not been converted in Salesforce remain as Contact records and map to Pipedrive Person records.

Salesforce Lead maps to Pipedrive Lead without structural transformation. Lead Status maps to Pipedrive's Lead status values. Any custom Lead fields migrate as custom fields on the Pipedrive Lead. Note that Salesforce Leads can exist simultaneously with Salesforce Contacts representing the same real-world person; during migration, we flag any Salesforce Lead and Contact sharing the same email address and present the customer with options: import both as separate records, deduplicate by converting the Lead to a Person, or archive the Lead.

Salesforce Opportunity maps to Pipedrive Deal. StageName maps to a Pipedrive Pipeline stage, with the stage probability migrated as a custom field since Pipedrive Deal stages do not carry native probability by default. Amount maps to Deal value. CloseDate maps to the Pipedrive close date. The Opportunity AccountId resolves to the Pipedrive Organization ID via the Account-Organization mapping. OwnerId resolves to the Pipedrive user ID via email matching.

Salesforce Campaigns have no native Pipedrive equivalent. Campaign membership (which Contacts and Leads are members of which Campaigns) is migrated as a multi-select custom field on the relevant Pipedrive Person or Organization record. Campaign attributes (Budget, Status, Type, StartDate, EndDate) are stored as custom fields on an Organization-level Campaign record or consolidated into a reference table for reporting purposes. The customer chooses the strategy during scoping based on how Campaign data is used.

Salesforce Products map to Pipedrive Products with the Product Code, Name, Description, and Family preserved. Standard Pricebook entries are created as Pipedrive Product prices. Products are imported before any Deal that references them so that the Product ID is resolved at Deal-line-item creation time.

Salesforce Tasks map to Pipedrive Activities with Activity type = task. Subject maps to the Activity subject. Status maps to Done flag (completed vs open). Priority, ActivityDate, and Description transfer directly. The WhatId (related Opportunity, Account, Case) resolves to the corresponding Pipedrive Deal or Organization ID; the WhoId (related Contact, Lead) resolves to the corresponding Pipedrive Person or Lead ID. Salesforce Task attachments do not migrate via API and must be re-uploaded manually post-migration or stored in a shared file repository.

Salesforce Events map to Pipedrive Activities with Activity type = meeting for standard Events and type = call for Events with ShowAs = Busy and DurationInMinutes under 60. StartDateTime and EndDateTime map to the Pipedrive Activity start and end timestamps. Location maps to the Pipedrive Activity location field. Event attendees (EventRelation records) are not natively supported by Pipedrive's API and are stored as a custom field on the Activity record listing the attendee email addresses.

Salesforce Notes migrate to Pipedrive Notes attached to the parent record (Person, Organization, or Deal). Body content transfers as text. Salesforce ContentNote (Lightning notes with rich text) content migrates as plain text since Pipedrive Notes do not support rich text natively. Notes are imported after the parent Person and Organization records exist to satisfy the attachment relationship.

Salesforce Contracts have no direct Pipedrive equivalent. Contract fields (Status, StartDate, EndDate, ContractTerm, TotalAmount) migrate as custom fields on the associated Pipedrive Deal or Organization. Contract PDFs are not transferable via Pipedrive's API and must be re-uploaded manually as Files attached to the Deal or Organization post-migration.

Salesforce Cases map to Pipedrive Helpdesk (available on Advanced and above plans) if the destination Pipedrive account has Helpdesk enabled. Case fields (Status, Priority, Origin, Subject, Description) map to Helpdesk ticket attributes. Pipedrive accounts without Helpdesk (Lite, Essential, Professional plans) cannot receive Case data natively; Cases are either archived with a custom field reference for manual post-migration recreation or imported as custom fields on the associated Organization record.

Salesforce Users map to Pipedrive users by email address match. We extract every distinct Salesforce User referenced as an Owner on any record, match by email against the Pipedrive destination account, and flag any Users without a matching Pipedrive account for the customer's admin to provision before production migration begins. Inactive Salesforce Users who own historical records are migrated as inactive Pipedrive users so that ownership attribution is preserved.