Migrate from Microsoft Dynamics 365 Sales to Pipedrive

Dynamics 365 Accounts map directly to Pipedrive Organizations. We extract accountname, website, address fields, industry, numberofemployees, and the primarycontactid lookup, resolving the Contact reference to a Person record at migration time. Deduplication uses website domain as the matching key in Pipedrive. Account is created before any Contact or Deal import so that the Organization reference is satisfied at the moment of Person and Deal insert.

Dynamics 365 Contacts map to Pipedrive Persons, preserving firstname, lastname, emailaddress1, telephone1, and jobtitle. The parentcustomerid_account lookup resolves to the Organization record created in the Accounts phase. Contact ownership maps to the Pipedrive User by email match. Multiple Contacts with the same email are flagged as duplicates for admin resolution before final import.

Dynamics 365 Leads map to Pipedrive Leads, preserving leadscore, leadsource, and statecode (Qualified/Disqualified). Lead status maps to Pipedrive's Lead status field. If the Dynamics 365 Lead has already been qualified and converted to an Opportunity, we flag it for routing to a Deal rather than a Lead record at the destination. We do not migrate Lead-to-Contact-Opportunity convert history; this is a Dynamics 365-specific lifecycle event.

Dynamics 365 Opportunities map to Pipedrive Deals, preserving estimatedvalue, closeprobability, actualclosedate, and stageid (mapped to a Pipedrive pipeline stage). The parentaccountid lookup resolves to the Organization; the closeprobability percentage maps to Pipedrive's probability field. Loss reason and win reason from Dynamics custom fields migrate as custom Deal fields. Opportunity owner resolves to Pipedrive User by email match.

Dynamics 365 Business Process Flows have no direct Pipedrive equivalent. We capture the BPF stage name at the time of migration as a custom field on the Deal (e.g., bp_stage__c) and set the Deal's starting pipeline stage to the equivalent Pipedrive stage. The BPF stage history (timestamps and stage transitions) is not migratable; we document the BPF structure in the migration handoff so the customer's admin can design an equivalent stage-based pipeline in Pipedrive.

Dynamics 365 Territory management (Enterprise tier only) maps territory names and hierarchies to Pipedrive as a custom multi-select field on Deal or Organization, or as Pipedrive User team assignments if the migration scope includes territory-to-team mapping. We detect the territory schema during scoping and present two options: a geographic custom field or a team-based assignment model. Territory hierarchy depth beyond two levels requires simplification at the destination.

Dynamics 365 Quotes, Orders, and Invoices form a commercial document chain that does not map directly to Pipedrive's single Deal model. We consolidate closed-won Opportunities with Quotes into Pipedrive Deals that include product line items using the Products and Price Lists mapping. Open Quotes are flagged as Deals with a 'Quote Pending' stage. We do not migrate the full Quote, Order, and Invoice document chain as separate records; product and pricing information is preserved in the Deal's line items.

Dynamics 365 Products map to Pipedrive Products, preserving productname, productnumber (SKU), and unitprice. Price List entries with quantity-based discounts map to Pipedrive Product pricing tiers. We create Pipedrive Products before any Deal import so that Deals can reference them at insert time. Product bundles in Dynamics 365 become individual Pipedrive Products with a custom bundle_id field for grouping.

Dynamics 365 activity records (Task, Email, PhoneCall, Appointment) map to Pipedrive Activities attached to the corresponding Person, Organization, or Deal. We preserve the activity type, subject, description, date, and duration (for calls). The regardingobjectid lookup resolves to the parent Person (Contact) or Deal (Opportunity) by our pre-built lookup table. Activities without a resolvable parent are attached to the related Organization. Note: Pipedrive Activities do not support a universal WhatId equivalent; complex multi-entity activity attachments require simplification.

Dynamics 365 custom tables on Enterprise tier map to Pipedrive custom fields on the equivalent standard object (Deal, Person, Organization) if the table is a simple entity with a lookup to Account or Contact. Complex custom tables with multiple lookups or many-to-many relationships require pre-migration schema design in Pipedrive. If the source is on Professional tier with exactly 15 custom tables, we map each to a Pipedrive custom field; tables above the limit require Enterprise licensing at destination or schema consolidation before migration proceeds.

Dynamics 365 Users map to Pipedrive Users by email address. We extract the full user list during scoping, match by email, and create a reconciliation report for any Pipedrive User that does not yet exist. Inactive Dynamics 365 users are mapped to a designated 'Legacy Owner' placeholder in Pipedrive so that records with inactive owners are not orphaned. Active users without Pipedrive accounts require admin provisioning before record migration begins.

Dynamics 365 Notes (noted text annotations) map to Pipedrive Notes attached to Person, Organization, or Deal. We preserve the notetext content, createdon timestamp, and the modifiedby user reference as a custom field. SharePoint-attached documents from Dynamics 365 require separate extraction via SharePoint API; we download and re-upload as Pipedrive Files attached to the corresponding Organization or Deal.