Migrate from Dynamics 365 Field Service to Pipedrive

Dynamics 365 accounts map directly to Pipedrive organizations. Account name becomes Organization name. Parent account hierarchies in Dynamics map to Pipedrive's parent organization field. Multi-address accounts: we map the primary address and preserve additional addresses as custom fields on the organization record.

Dynamics contacts migrate to Pipedrive persons. The contact's primary account link resolves to the organization_id in Pipedrive. N:N contact-to-account relationships in Dynamics (contacts linked to multiple accounts) collapse to the primary account link in Pipedrive, with secondary account links preserved as custom organization fields or organization relationship notes.

Dynamics 365 Field Service work orders have no direct equivalent in Pipedrive. We convert each work order to a Pipedrive deal — the work order number becomes a custom field on the deal, work order status maps to a deal custom field with value translation, and the primary service type maps to a custom field. Work order subject or title becomes the deal name. The linked account resolves to the Pipedrive organization; the linked contact resolves to the deal's linked person.

Technician scheduling records (bookable resource bookings) associated with a work order migrate as Pipedrive activities attached to the deal. The booking start and end times become activity dates, the resource name becomes the activity subject, and any booking notes become activity details. This preserves scheduling intent without requiring Pipedrive's native scheduling capability.

Dynamics cases become Pipedrive activities of type task. Case number and case status (Active, Resolved, Cancelled) migrate as custom fields on the activity. Case subject becomes the activity subject. The case's regarding link (account or contact) resolves to the corresponding organization or person in Pipedrive. Entitlements and SLA data have no Pipedrive equivalent — we preserve them as custom fields on the activity for reference.

Dynamics opportunities map directly to Pipedrive deals. Opportunity name becomes deal name, estimated value maps to deal value (amount), close date maps to close date, and pipeline + stage map to Pipedrive pipeline and stage. Dynamics opportunity contact roles map to the deal's linked person in Pipedrive. Lost reason and forecast category map as custom fields.

Dynamics product catalog products map to Pipedrive products. Product name, SKU, unit price, and cost map directly. Product bundles and bill of materials collapse to simple Pipedrive product entries; bundle components are listed in a custom field. Inactive products are migrated but flagged in Pipedrive's product status field.

Dynamics email activities (from the Email activity entity) migrate to Pipedrive activities of type email. Subject, body (plain text), from, to, cc, and timestamps map directly. HTML email bodies are stripped to plain text for Pipedrive compatibility. Attachments are not carried over by default; file references are preserved in a custom field and re-uploaded if requested.

Dynamics phone call activities migrate to Pipedrive activities of type call. Subject, duration, direction (inbound/outbound), and call result map directly. Call notes from Dynamics become the activity details. Phone number from the call activity links to the related contact in Pipedrive.

Dynamics appointment activities migrate to Pipedrive activities of type meeting. Subject, start time, end time, location, and body map directly. Required and optional attendees are noted in the activity details. The regarding link resolves to the associated account or contact in Pipedrive.

Dynamics annotations (notes attached to any entity) migrate to Pipedrive notes. The note text maps to Pipedrive note content. The regarding link resolves to the corresponding person, organization, or deal in Pipedrive. Annotation attachments are handled separately as file re-uploads.

Dynamics systemuser records resolve to Pipedrive users by email address match. We export ownerid from Dynamics records and match against the email field on Pipedrive users. Unmatched owners are flagged before migration — your team either invites them to Pipedrive or assigns records to a fallback owner. Owner history is preserved in a custom field on migrated records.