Migrate from Pipedrive to Microsoft Dynamics 365 Sales

Pipedrive Persons map to Dynamics 365 Contacts if they are active in the sales pipeline; Persons flagged as unqualified prospects in a Pipedrive Lead pool map to Dynamics 365 Leads. We apply a qualification rule during scoping (based on deal association, last activity date, or owner assignment) to route each Person to Lead or Contact. Email address is the dedupe key; name, phone, address, and custom fields transfer with type-aware mapping. Organization linkage preserves as AccountId on Contact.

Pipedrive Organizations map 1:1 to Dynamics 365 Accounts. Organization name becomes Account Name; domain fields map to Website. We use Organization ID as the external key so that multiple Persons linked to the same Organization resolve to a single Account during import. Address fields map to the Account's address composite field per Dynamics 365 Dataverse conventions.

Pipedrive Deals map to Dynamics 365 Opportunities. The Pipedrive pipeline name maps to a Dynamics 365 Record Type or Business Process Flow; stage names map to Opportunity Stage values. Deal monetary value maps to Amount; expected close date maps to CloseDate. We preserve loss reason and win reason as custom fields if the Pipedrive account uses those properties.

Each Pipedrive pipeline stage becomes a Dynamics 365 Opportunity Stage within a Sales Process. We map stage probabilities from Pipedrive to StageProbability on the corresponding stage. The stage order is preserved by setting pipeline stage position to the Opportunity Stage's rank integer. If the destination org has existing stage values, we align by name match rather than position.

Pipedrive's separate Lead pool (distinct from Deals-attached Persons) migrates to Dynamics 365 Lead records. Lead title, company, email, phone, and status map to the corresponding Dynamics 365 fields. We preserve any Lead scoring or source attribution from Pipedrive custom fields as custom Lead fields in Dynamics 365.

Pipedrive Activities map to Dynamics 365 Task (for calls and tasks) and Event (for meetings). Activity type maps to TaskSubtype on Task. We resolve the parent record reference (person_id and org_id in Pipedrive) to the corresponding Dynamics 365 Contact or Account GUID at migration time. Activity due dates and completed timestamps map to ScheduledEnd and ActualEnd respectively.

Pipedrive Products map to Dynamics 365 Product2 records. SKU, name, pricing (unit_price), and currency map directly. We create a corresponding Pricebook2 entry during migration and attach it to the destination Opportunity via the standard pricebook relationship. If the customer uses multiple currencies, we map the Pipedrive currency code to the Dynamics 365 TransactionCurrency ISO code.

Pipedrive Deal-Product attachments (quantity and pricing per deal) map to Dynamics 365 OpportunityLineItem. We resolve the Pricebook2 reference, Product2 reference, and parent Opportunity GUID at migration time. UnitPrice, Quantity, and ManualDiscount migrate as-is. If Pipedrive tracks product-level discount reasons, we preserve those in a custom line-item field.

Pipedrive Owners map to Dynamics 365 User records by email address match. We extract every distinct owner_id referenced on Persons, Organizations, Deals, Activities, and Products and match against the destination User table. Owners without a matching Dynamics 365 User enter a reconciliation queue for the admin to provision before record import proceeds.

Pipedrive tags migrate as string arrays applied to the corresponding Dynamics 365 records. For deal-level tags, we create a multi-select picklist field on Opportunity. For person-level tags, we apply a TopicAssignment strategy. The customer selects tag strategy during scoping; tags that represent segmentation logic map to Dynamics 365 Customer Insights or Sales Insights data if the customer licenses those modules.

Pipedrive Notes (standalone content entries) map to Dynamics 365 Note records linked via Annotation object to the parent Contact, Account, or Opportunity. Note body migrates as plain text; any embedded link references preserve as-is. We set the Subject field to the first 200 characters of the note for quick scanning in the Dynamics 365 timeline.

Pipedrive custom fields exist on Deals, Organizations, Persons, and Products with account-specific hash keys. We resolve each hash to its human-readable label during export, then map the label to a matching Dynamics 365 custom field by label and data type (text, number, date, picklist, checkbox). Fields without a destination match enter a custom field creation queue for the Dynamics 365 admin to provision before migration.