Migrate from Function 365 to Pipedrive

Dynamics 365 Contacts map directly to Pipedrive Persons. The primary email, phone, name fields, and address fields carry over as-is. Dynamics Contact's AccountId (lookup to Account) maps to Pipedrive Person's org_id (lookup to Organization). Multi-company contacts in Dynamics collapse to one primary Organization link in Pipedrive; secondary company associations are preserved as additional Organization links if the data model allows.

Dynamics Leads can route to either Pipedrive Leads (if the separate Leads feature is enabled) or Pipedrive Persons. The routing rule applies per record: Leads with a qualified status map to Person, unqualified or new Leads map to Pipedrive's Lead object. Lead address, company name, and phone fields map to the equivalent Pipedrive Lead or Person fields. Dynamics Lead source and rating (Active / Qualified) map to Pipedrive's lead_status custom field.

Dynamics 365 Accounts map to Pipedrive Organizations. Account name, website, address, industry, employee count, and annual revenue carry over. Parent account hierarchies (Account.ParentId) map to Pipedrive Organization's parent_org_id. Multi-site organizations from Dynamics with child accounts become sibling Organizations linked by the parent_org_id in Pipedrive.

Dynamics 365 Opportunities map to Pipedrive Deals. The deal name, estimated close date, actual close date, and amount fields carry over directly. The Dynamics Opportunity's StageName (opportunitystage) maps to Pipedrive's pipeline stage_id on the Deal. Dynamics EstimatedValue and DealCurrency map to Pipedrive's weighted_value and currency_id.

Each Dynamics 365 Sales Process (pipeline) becomes a Pipedrive Pipeline. Each Dynamics Opportunity Stage within that Sales Process maps to a Pipedrive Stage within the corresponding pipeline. Stage probability values from Dynamics re-enter as custom probability fields in Pipedrive since Pipedrive does not enforce stage probability natively — forecast category is the closest built-in field but requires manual mapping per stage.

Dynamics OpportunityContactRole records linking Contacts to Opportunities map to Pipedrive Deal-Person associations. In Pipedrive, each Deal can have multiple linked Persons with a visible role label. The primary contact on a Dynamics Opportunity maps to the first Deal Person link in Pipedrive. Role names (decision-maker, evaluator, etc.) are preserved as custom text labels in Pipedrive.

Dynamics 365 Task entities map to Pipedrive Activities of type 'task'. PhoneCall activities map to Pipedrive Activities of type 'call'. Email (emailactivity) maps to Pipedrive Activities of type 'email'. The Regarding (regardingobjectid) lookup in Dynamics becomes the linked deal_id, person_id, or org_id in Pipedrive. Original timestamps, duration (for calls), and subject line carry over. Dynamics activityparty records (attendees, recipients) map to Pipedrive's attendee list on the corresponding activity.

Dynamics 365 Appointment records map to Pipedrive Activities of type 'meeting'. Start time, end time, location, and subject carry over. Dynamics RequiredAttendees and OptionalAttendees activityparty records map to Pipedrive attendee user_ids on the meeting activity. Body/notes on the appointment become the Pipedrive meeting activity's note field.

Dynamics 365 Note (annotation) records with isdocument=false map to Pipedrive Activity of type 'note'. The notetext field becomes the Pipedrive note content. Dynamics Note's object references (objectid) map to Pipedrive's deal_id, person_id, or org_id depending on the parent entity. File attachments on Notes (annotationattachments) re-upload as Pipedrive Files linked to the same parent record.

Dynamics 365 Product records (productentitlement) map to Pipedrive Products. Product name, SKU, unit, price list entries, and description carry over. Pipedrive Products can be linked to Deals for line-item tracking. If Dynamics pricing is complex (volume discounts, tiered pricing), the pricing rules are noted as rebuild items in Pipedrive's Product Catalog settings post-migration.

Every Dynamics 365 custom field (created via Power Apps > Customizations or the X++ extension model) is evaluated for a Pipedrive equivalent. Text, number, date, and pick-list fields map directly. Option-set (pick-list) values in Dynamics require value-by-value mapping in Pipedrive because Pipedrive generates unique hash keys per field per account. Lookup fields (regardingobjectid) in Dynamics that point to custom entities become custom fields in Pipedrive unless a matching Pipedrive entity exists.

Dynamics 365 SystemUser records map to Pipedrive Users. OwnerId on any Dynamics entity (Contact, Account, Opportunity) resolves by email address match to a Pipedrive user. Unmatched owners are flagged before migration and assigned to a designated fallback Pipedrive user. Business unit hierarchy from Dynamics is not transferred — Pipedrive's visibility group model replaces it and must be configured post-migration.

Dynamics 365 transactioncurrency records (currency ISO codes and exchange rates) map to Pipedrive's currency configuration. The active exchange rate at time of migration is applied to deal amounts. Pipedrive stores deal amounts in the selected currency; multi-currency pipelines in Dynamics require explicit currency_id assignment per deal.

Email attachments stored in Dynamics 365 or Exchange Online mailboxes re-upload as Pipedrive Files linked to the corresponding email Activity or Contact Person. File size validation runs against Pipedrive plan limits (5GB/user on Lite, 100GB on Power, unlimited on Enterprise). Files exceeding limit are flagged for alternative storage and linked by URL reference.

Dynamics 365 workflows, Power Automate cloud flows, business rules, and real-time plugins do not migrate. These are destination-platform automation constructs. FlitStack exports the full workflow definition (trigger conditions, actions, branch logic) as a JSON reference file for your Pipedrive admin to rebuild using Pipedrive Automations. Power Automate flows that reference Dataverse tables will need equivalent Pipedrive Automations or Zapier/Make scenarios.