Pipedrive to Dynamics 365 migration
We migrate Persons, Organizations, Deals, Activities, and Products from Pipedrive into Microsoft Microsoft Dynamics 365 Sales with stage names preserved, owner lookups resolved by email, and a Lead-versus-Deal routing decision made before any data moves. We flag Pipedrive Sequences and Automations as non-migratable and deliver a written inventory for your Dynamics admin to rebuild.
FlitStack AI migrates contacts, accounts, opportunities, opportunity stages and leads from Pipedrive to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Pipedrive to Dynamics 365?
Moving from Pipedrive to Microsoft Microsoft Dynamics 365 Sales is a migration from a person-centric, visual pipeline tool into a data model with separate Lead, Contact, Account, and Opportunity objects that require deliberate routing decisions at migration time.
Read the full summary
Pipedrive Persons map to either Dynamics 365 Leads or Contacts depending on qualification status; Pipedrive Organizations map to Accounts; Pipedrive Deals map to Opportunities with stage names and probabilities preserved. Activities (calls, tasks, meetings) migrate as structured records linked to the correct parent entity using the Dynamics 365 Dataverse API. Pipedrive's Sequences and Automations are not exposed via the REST API and do not migrate; we deliver a written automation inventory for your Dynamics admin to rebuild in Power Automate or Sales Insights rules. The migration uses Dynamics 365's data import APIs with parent-record resolution so that Contact-to-Account and Opportunity-to-Contact links are intact when the system goes live.
Person → Contact (or Lead)
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.
How it maps
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.
Organization → Account
Pipedrive Organizations map 1:1 to Dynamics 365 Accounts.
How it maps
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.
Deal → Opportunity
Pipedrive Deals map to Dynamics 365 Opportunities.
How it maps
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.
Pipeline Stage → Opportunity Stage
Each Pipedrive pipeline stage becomes a Dynamics 365 Opportunity Stage within a Sales Process.
How it maps
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.
Lead → Lead
Pipedrive's separate Lead pool (distinct from Deals-attached Persons) migrates to Dynamics 365 Lead records.
How it maps
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.
Activity (Call, Meeting, Task) → Task and Event
Pipedrive Activities map to Dynamics 365 Task (for calls and tasks) and Event (for meetings).
How it maps
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.
- PersonContactsplit
- OrganizationAccount1:1
- DealOpportunity1:1
- Pipeline StageOpportunity Stagetransformed
- LeadLead1:1
- ActivityTask and Event1:1
+ 6 more in the mapping below
How Pipedrive and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Pipedrive | Dynamics 365 |
|---|---|---|
| Contact model | Person-centric: one Person linked to one Organization per Deal | Separate Lead, Contact, and Account objects with explicit qualification and conversion flow |
| Pipeline visualization | Drag-and-drop Kanban board with visual stage columns | Sales process stages managed via Business Process Flows, not a Kanban-native view |
| Custom objects | Not available; four standard entity types only | Custom entities available from any paid tier via Dataverse without additional setup fees |
| Automation model | Workflow automations gated by tier (30, 60, 90) plus separate Sequences for email cadences | Power Automate for cross-entity flows; Sales Insight rules for engagement automation; no native cadence equivalent |
| Pricing structure | Per-seat with add-on cost escalation for LeadBooster, Advanced AI, and workflow caps | Per-user tiers from $70/user/mo with Power Platform included; clearer bundle at mid-market |
| Integration ecosystem | 400+ marketplace integrations via Zapier and native API | Native Microsoft 365 (Teams, Outlook, SharePoint) plus Dataverse connector for Power Platform |
| Reporting | Basic pipeline analytics on lower tiers; multi-touch attribution requires upgrade | Power BI embedded natively; advanced forecasting and territory management from Professional tier |
What to watch for in a Pipedrive to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Pipedrive API uses account-specific hash keys for custom fields
Pipedrive assigns each custom field a 40-character hash as its API key, and the same field name in two different Pipedrive accounts has different hash values.
How we handle it
We read the hash-to-label mapping from the source account, resolve human-readable field names, and map values to the correct Dynamics 365 custom field by label and type during import. If the Dynamics 365 destination does not yet have the corresponding custom field created, we flag it in the pre-flight report and hold the migration until the field is provisioned with the matching label and data type.
Dynamics 365 data import requires parent records first
Dynamics 365 enforces referential integrity on lookup fields.
How we handle it
Accounts must exist before Contacts can be imported with an AccountId; Contacts must exist before Opportunities can be imported with a primarycontactid. The Dynamics community forum details a recommended import order: Leads/Accounts first, then Contacts, then Opportunities, then Activities. We enforce this order in every migration. Skipping it results in orphaned records or silent failures on the WhatId and WhoId fields of Activity records.
Pipedrive Sequences and Automations are not exposed via REST API
Pipedrive Sequences (email cadence workflows) and Automations (condition-action workflows) are not readable or writable via the public REST API.
How we handle it
We do not migrate them. We flag both as non-migratable during scoping, recommend exporting sequence email templates manually for reference, and deliver a written automation inventory document listing every active Automation trigger, condition, and action with a recommended Dynamics 365 Power Automate or Sales Insight rules equivalent for the admin to rebuild.
Pipedrive token-based rate limits since December 2024
Pipedrive introduced per-token rate limits for API access on December 2, 2024, replacing the previous request-frequency model.
How we handle it
Bulk exports using the Pipedrive API must now account for per-token throttling. We monitor rate limit responses, implement exponential backoff with request queuing, and chunk exports to stay within token quotas. If the migration account has a high volume of activity records, we schedule exports outside business hours to avoid throttling contention.
Dynamics 365 Business Process Flows require stage sequencing
Microsoft Dynamics 365 Sales uses Business Process Flows (BPFs) to guide reps through stage progression.
How we handle it
Pipedrive has no BPF equivalent; its pipeline stages are purely visual Kanban columns. We map Pipedrive stage order to BPF stages during migration but cannot retroactively apply BPF progress to Deals that are already closed. Active Deals migrate with the BPF stage matching the Pipedrive stage; closed Deals retain their final stage name as a custom field but do not carry BPF navigation history.
How the migration runs
Discovery and scope definition
We audit the source Pipedrive account: record counts for Persons, Organizations, Deals, Leads, Activities, and Products; pipeline names and stage definitions; custom field hash-to-label mappings; active Owners list; and a count of any active Sequences or Automations.
What this step covers
We pair this with a Dynamics 365 environment review: existing Record Types, Sales Processes, and custom fields already provisioned. The discovery output is a written migration scope document, a field-mapping matrix, and a Microsoft Dynamics 365 Sales tier recommendation ($70/user/mo Professional vs $95/user/mo Enterprise) based on BPF complexity and custom object requirements.
Schema provisioning in Dynamics 365
We create any missing custom fields in Dynamics 365 to match Pipedrive custom field labels and data types.
What this step covers
We configure Record Types and Sales Processes corresponding to Pipedrive pipelines, set stage probabilities matching Pipedrive stage weights, and create the Product2 pricebook entries. Custom fields are deployed to a Dynamics 365 Sandbox first; the customer validates field placement on Page Layouts before production provisioning.
Owner reconciliation and User provisioning
We extract every distinct Pipedrive Owner (by email) referenced across Persons, Organizations, Deals, and Activities and match against the Dynamics 365 User table.
What this step covers
Owners without a matching User enter a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users (active or inactive depending on whether the original rep is still employed). Migration cannot proceed past this step because OwnerId references are required on most standard objects in Dynamics 365.
Sandbox migration and data reconciliation
We run a full migration into a Dynamics 365 Sandbox (Full Copy or Partial Copy) using production-equivalent data volumes.
What this step covers
The customer's RevOps lead spot-checks 25-50 random records against the Pipedrive source: field values, parent-child relationships, stage assignments, and owner links. We correct any mapping errors in the sandbox and obtain sign-off before production migration begins.
Production migration in dependency order
We run production migration in the correct referential-integrity order: Accounts (from Pipedrive Organizations), Leads and Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries, OpportunityLineItems, and Activity history (Tasks and Events via Dataverse API with parent-record lookup).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta sync, and automation inventory handoff
We freeze Pipedrive writes during cutover, run a final delta migration for any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record.
What this step covers
We deliver the Automation and Sequence inventory document to the customer's Dynamics 365 admin team with Power Automate or Sales Insight rules equivalents for each item. We support a one-week hypercare window for reconciliation issues. We do not rebuild Pipedrive Automations as Power Automate flows inside the migration scope; that is a separate engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, number of Pipedrive pipelines, and whether custom fields and products need type-aware mapping. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Pipedrive to Dynamics 365 →Why teams move from Pipedrive to Dynamics 365
- Teams needing custom data structures hit Pipedrive's ceiling. Pipedrive supports only four standard entity types (Person, Organization, Deal, Activity) with no custom objects, forcing teams with project-based billing, service contracts, or multi-line data models to store relationships in custom fields that cannot enforce referential integrity. Microsoft Dynamics 365 Sales on Dataverse allows unlimited custom entities from any paid tier without setup fees, eliminating the workaround pattern that accumulates in large Pipedrive accounts.
- Cost creep from add-ons and workflow caps pushes total cost above the headline price. LeadBooster, Advanced AI, and workflow automation tiers ($14 to $99/user/mo on paper) stack add-on costs that approach Microsoft Dynamics 365 Sales territory at scale. Microsoft bundles Power Automate, Power BI, and Teams integration into the base subscription, removing the per-feature add-on model that inflates Pipedrive invoices.
- Microsoft 365 ecosystem integration drives the switch for Teams-heavy organizations. Pipedrive requires Zapier or native connectors for Outlook and Teams, while Microsoft Dynamics 365 Sales is built on the same identity and data platform as Office 365, SharePoint, and Teams. Reviewers on MSDynamicsWorld cite tighter Teams meeting capture, Outlook email tracking, and SharePoint document management as operational wins that Pipedrive cannot match without third-party routing.
- Enterprise and mid-market teams require reporting depth beyond Pipedrive's pipeline view. Pipedrive's built-in analytics cover deal-stage summaries and rep activity but lack multi-touch attribution, territory-based forecasting, and cross-object drill-downs that Microsoft Dynamics 365 Sales delivers through Power BI integration and native forecasting models. Reviewers on Gartner Peer Insights note that advanced reporting requires the Enterprise tier on Pipedrive, while Microsoft Dynamics 365 Sales includes these capabilities from Professional upward.
- AI-powered sales assistance through Microsoft Copilot influences the switch decision. Microsoft Dynamics 365 Sales integrates Copilot natively across Outlook, Teams, and the CRM record, auto-generating deal summaries, meeting prep, and email drafts. Pipedrive's AI features are add-on priced and operate within the CRM only, without the cross-application intelligence that Copilot provides across the Microsoft 365 surface.
Questions, answered
Pipedrive to Dynamics 365 migration questions
How long does a Pipedrive to Microsoft Microsoft Dynamics 365 Sales migration take?
Small migrations under 15,000 Persons, 3,000 Deals, and a single pipeline complete in three to five weeks. Migrations with multiple Pipedrive pipelines, large activity histories (over 200,000 records), product attachments, or a Dynamics 365 environment with pre-existing data (requiring dedup logic) extend to eight to twelve weeks. Discovery and schema provisioning typically add two to three weeks before migration begins.
Do Pipedrive Sequences and Automations migrate to Dynamics 365?
No. Pipedrive Sequences and Automations are not exposed via the REST API, so we cannot read them for migration. We do not attempt to migrate them as code. We flag both as non-migratable during scoping and deliver a written automation inventory document listing every active Pipedrive Automation trigger, condition, and action with a recommended Dynamics 365 Power Automate or Sales Insight rules equivalent. The customer's Dynamics 365 admin or a Microsoft partner rebuilds them post-migration. Sequence email templates can be exported manually from Pipedrive for reference.
How do we handle Pipedrive Leads versus Deals in Dynamics 365?
Pipedrive has a separate Lead pool distinct from Deals-attached Persons. During migration, we apply a qualification rule (based on deal association, last activity, or owner assignment) to route each Pipedrive Lead to either a Dynamics 365 Lead record or a Contact record. We preserve the original Pipedrive Lead status as a custom field in Dynamics 365 for audit. If the destination org uses Business Process Flows, we configure a BPF that maps the Pipedrive stage order to BPF stage progression.
Can we keep Pipedrive's visual pipeline while switching to Dynamics 365?
Microsoft Dynamics 365 Sales does not have a native Kanban pipeline view equivalent to Pipedrive's drag-and-drop interface. Sales teams moving from Pipedrive typically use either the Dynamics 365 Opportunity list view with inline editing, a Power Apps canvas pipeline view built on Dataverse, or a third-party solution from the AppExchange. We flag pipeline UX as a change-management item during scoping and note that reps will require retraining on Dynamics 365's stage management model, which uses dropdown selection rather than drag-and-drop.
Do historical activity records (calls, emails, meetings, tasks) migrate?
Yes. We migrate the full activity history from Pipedrive as structured records linked to the correct parent Contact or Account in Dynamics 365. Calls land as Task records with TaskSubtype=Call; meetings land as Event records with start and end times preserved; tasks land as Task records; notes land as Annotation records. We resolve the parent record GUID (WhoId for Contact, WhatId for Account or Opportunity) at migration time using the email-to-contact lookup built during the Account and Contact import phase.
How does the migration handle Pipedrive's custom field hash keys?
Pipedrive assigns each custom field a 40-character hash as its API key that is unique per account. We read the hash-to-label mapping during the export phase, resolve every hash to its human-readable field name, and map values to the corresponding Dynamics 365 custom field by label and data type. If the Dynamics 365 destination does not yet have the matching custom field created, we hold those records and flag the missing field in the pre-flight report for the admin to provision. Fields without a Dynamics 365 equivalent are documented for post-migration cleanup.
What happens to Pipedrive Products and deal-product attachments?
Pipedrive Products migrate to Dynamics 365 Product2 records with Standard Price Book entries. Deal-Product associations migrate as OpportunityLineItem records linked to the parent Opportunity, preserving quantity, unit price, and any discount values. If the Dynamics 365 destination uses multiple pricebooks, we provision the source pricebook and link it to the destination Opportunity during import. Product-Currency mapping uses the ISO currency code from Pipedrive matched to Dynamics 365 TransactionCurrency.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Field Services Workflow and Logistics to Dynamics 365Mapping · history · rollbackActiveCampaign to Dynamics 365Mapping · history · rollbackCivicrm to Dynamics 365Mapping · history · rollbackZendesk Sell to Dynamics 365Mapping · history · rollbackBitrix24 to Dynamics 365Mapping · history · rollbackHubSpot to Dynamics 365Mapping · history · rollback Pipedrive to HubSpotMapping · history · rollbackPipedrive to SalesforceMapping · history · rollbackPipedrive to Odoo CRMMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Importing data into Pipedrive with spreadsheets — Knowledge Base
- Updating Pipedrive data with a spreadsheet — Knowledge Base
- 5 Simple CRM Data Migration Methods — Pipedrive Blog
Get a quote
Moving from Pipedrive to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote