Migrate from Salesforce Field Service to Pipedrive

Salesforce Contact maps directly to Pipedrive Person. Name, email, phone, job title, and address fields map field-for-field. The primary AccountId on the Salesforce Contact resolves to the Organization lookup on the Pipedrive Person. Contacts without a primary account attach to a default organization.

Salesforce Account maps to Pipedrive Organization. Standard fields including Name, Website, Industry, Phone, and BillingAddress map directly to their Pipedrive equivalents. The Parent Account hierarchy in Salesforce translates to Pipedrive's parent Organization relationship, preserving the corporate structure. For multi-address accounts in Salesforce, only the primary billing address is retained in Pipedrive as the Organization's single address field. Account team members and account history do not migrate as discrete objects.

Salesforce Lead maps to a Pipedrive Person with Lead context. Status, Lead Source, Industry, Number of Employees, and Annual Revenue fields map to their Pipedrive equivalents. Salesforce Lead conversion — which creates Account + Contact + Opportunity — is unnecessary in Pipedrive since one Person object holds both lead and customer records.

Salesforce Opportunity maps to Pipedrive Deal. Deal Name, Amount, Stage, Close Date, Owner, and Description map directly. Probability and Forecast Category are preserved as Pipedrive custom fields since Pipedrive's pipeline view uses stage percentages differently. Multiple Salesforce opportunities for one Account collapse to one Pipedrive Deal per business transaction.

Salesforce Tasks representing calls, emails, and to-dos map to Pipedrive Activities with Type values of 'Call', 'Email', or 'Task'. The Subject, Status, Priority, ActivityDate, and Description fields transfer directly field-for-field. Owner resolution uses email matching against Pipedrive users to assign the correct owner. Completed tasks preserve their original completion timestamp in Pipedrive rather than recording the migration date as the completion time.

Salesforce Events for meetings and site visits map to Pipedrive Activities with Type = 'Meeting'. The Subject, Start DateTime, End DateTime, Location, and Description fields transfer directly. For Salesforce Events that lack an end time value, Pipedrive applies a default 60-minute duration to the resulting Activity. Recurring events in Salesforce are not supported in Pipedrive and must be created as individual Activity records.

Salesforce Notes attach to the corresponding Person, Organization, or Deal record in Pipedrive. The Title, Body content, and CreatedDate timestamp all transfer directly. Rich-text formatting applied in Salesforce Notes is preserved through the migration process. Notes originally attached to WorkOrder or ServiceAppointment records are migrated to the linked Person or Deal note stream to maintain contextual information accessibility.

Salesforce Files attached to Contact, Account, WorkOrder, or ServiceAppointment re-upload to Pipedrive as file attachments on the equivalent Person, Organization, or Deal. File size limit is 50MB per file in Pipedrive — Salesforce files exceeding this are chunked or flagged for manual review. Original file names and creation dates are preserved.

Salesforce WorkOrder has no direct Pipedrive equivalent. We decompose it: the service subject and description become a Pipedrive Deal; WorkOrder status, priority, and scheduled date migrate as custom fields on that Deal; and the original WorkOrder number is stored as Source_System_ID__c for traceability. Line items map to Pipedrive Product links on the Deal.

Salesforce ServiceAppointment maps to a Pipedrive Activity with Type = 'Visit' or 'Task'. Arrival window, actual start/end times, and service address migrate as Pipedrive custom fields on the Activity. Status (None, Scheduled, Dispatched, In Progress, Completed, Canceled) maps value-by-value to a Pipedrive custom pick-list. Parent WorkOrder reference is stored as a custom text field.

Salesforce ServiceResource records resolve to Pipedrive Users by email matching. Active resources with a Salesforce UserId map 1:1 to Pipedrive users who own the migrated Activities. Unmatched resources are flagged before migration so your team can create Pipedrive users or assign records to a fallback owner.

Salesforce custom objects and their fields have no Pipedrive custom object equivalent. Each custom object's fields are created as custom fields on the Pipedrive entity they relate to (Person, Organization, or Deal). Many-to-many relationships between Salesforce custom objects map to Pipedrive's tag system or custom multi-select fields.