Why teams leave Dynamics 365
Dynamics 365 Sales is usually a decision made above the sales team. It arrives with the Microsoft agreement, gets customised by a partner, and then the partner leaves. Two years later the sales team works around it in Outlook and Excel, and the licence renewal lands on someone's desk.
The complaints are always the same. Forms with forty fields. Business Process Flows that force steps nobody follows. Reports that need a Power BI specialist. Pipedrive wins these teams because a rep can learn it in an afternoon.
Stay honest about the reverse case. If your quoting, service and finance processes are deep in the Dynamics stack, moving only sales creates an integration bill. Read our Salesforce guide for the same trade-off in a different suite.
What carries over and what does not
The core sales records move. Accounts, contacts, leads, opportunities, activities and notes all have direct Pipedrive equivalents. Attachments stored as annotations can be exported and re-uploaded to the matching records.
The platform layer does not move. Custom entities, Business Process Flows, Power Automate flows, security roles, business units, forms and views all stay behind. So do audit logs. Server-side sync with Exchange is replaced by Pipedrive's own email sync, which each user connects personally.
Field mapping: Dynamics entities to Pipedrive
| Dynamics 365 | Pipedrive | Notes |
|---|---|---|
| Account | Organization | Join child records on the account GUID. |
| Contact | Person | Match on primary email, keep the GUID as a field. |
| Opportunity | Deal | Map statecode and statuscode to open, won, lost. |
| Lead | Leads inbox | Only unqualified leads. Qualified ones already became opportunities. |
| Appointment, phone call, task | Activities | Export each activity type separately. |
| Email activities | Email sync | History stays in Exchange, resyncs after cutover. |
| Annotations (notes and files) | Notes and files | Attachments are base64 in the export, decode first. |
| Custom entities | Fields, pipelines or external tools | Decide per entity, do not force a mapping. |
Pitfalls specific to Dynamics
Option sets are stored as integers. An export without the label mapping gives you columns of numbers. Pull the labels from the solution metadata first and translate every column before import. This one mistake causes more Dynamics migration rework than everything else combined.
Advanced Find is not an export tool. It caps columns, hides some system fields and pages large sets. Use it for spot checks, not for the real extraction. Power Query against Dataverse, or the API, gives you complete tables with GUIDs intact.
Ownership does not translate one to one. Dynamics spreads records across business units and teams with cascading security roles. Pipedrive uses owners plus visibility groups, which is flatter. Design the visibility model fresh instead of copying the old org chart.
Watch the integrations. Dynamics rarely runs alone. ERP links, marketing tools and Power BI datasets all point at Dataverse. List every consumer of CRM data before cutover, because each one needs a new source.
The step plan
1. Inventory the customisation
List custom entities, custom fields with real data, Business Process Flows and Power Automate flows. Mark each as rebuild, replace or retire. This list is the project.
2. Extract with GUIDs and labels
Export each entity as a full table, keep every GUID column, and translate option sets to labels. Store the raw files untouched and clean in copies.
3. Clean and deduplicate
Merge duplicate accounts on domain, contacts on email. Normalise countries and currencies. Dynamics instances that lived through several partners always carry duplicates.
4. Build Pipedrive and run a test import
Pipelines, stages, fields, users and visibility groups first. Then fifty accounts, their contacts and ten opportunities. Verify by hand before the full run.
5. Import, reconcile, cut over
Import in order: organizations, people, deals, activities, notes. Reconcile record counts and open value per stage. Announce one cutover date and freeze Dynamics edits from that moment.
6. Rewire the integrations
Point ERP links, marketing tools and reporting at the Pipedrive API. Rebuild the surviving flows as Pipedrive automations where they fit.
Timeline and cost band
Six to ten weeks is realistic for a sales team of ten to fifty. Budget €8,000 to €25,000 with a partner, which sits at the top of the market band for good reason. Extraction depth, custom entities and integration rework set the price, not the user count. The cost page breaks down how to read a quote, and how to choose a partner covers the questions that expose whether a partner has actually done Dataverse extractions before.
Questions
Can we get our data out of Dynamics 365 ourselves?
Yes, but not in one click. Advanced Find exports work per view and hide some columns. For a full export you pull entities through Power Query, the Dataverse API or a partner tool, then join the files on GUIDs.
What happens to our custom entities?
Pipedrive has no custom objects. Each custom entity becomes fields on a deal, person or organization, a separate pipeline, or an external tool. Some are best archived as a read-only spreadsheet.
Do option set values export as readable text?
Not by default. Dynamics stores option sets as integers. You need the label mapping from the solution metadata, or your CSV is full of numbers like 100000002. Export the labels before you start.
How long does a Dynamics to Pipedrive migration take?
Six to ten weeks for a typical sales team. Extraction and relinking take longer than in any other migration we run, because the data model is deeper and the GUID joins must be exact.
What replaces our Power Automate flows?
Pipedrive automations cover the sales-side flows like stage changes, task creation and notifications. Flows that touch other Microsoft systems move to Make or keep running in Power Automate against the Pipedrive API.