Migrate from Dynamics 365 Marketing to Pipedrive

Dynamics 365 Contact records map to Pipedrive Person records. Standard fields (full name, email, phone, address) migrate directly. The Dynamics Contact-to-Account relationship maps to a Pipedrive Organization linkage using the Account name as the Organization dedupe key. If the source Contact has no associated Account, the Person is created standalone. We preserve the original Dynamics contactid as a custom field dynamics_contact_id__c for audit and future reference. Note that Pipedrive does not distinguish between a marketing-qualified contact and a transactional contact; we do not apply a separate label during import unless the customer requests a Person label strategy.

Dynamics 365 Lead records map to Pipedrive Person records with the Lead lifecycle status preserved in a custom text field dynamics_lead_status__c. The Dynamics Lead_Status field (New, Contacted, Qualified, Unqualified) migrates as-is. Lead scores and lead sources migrate to custom fields lead_score__c and lead_source__c if the Advanced tier Custom Objects API is available; otherwise they are documented in the migration inventory for manual re-entry. Leads that were already converted to Contacts in Dynamics are not re-imported as separate Person records to avoid duplication.

Dynamics 365 Account records map to Pipedrive Organization records using the Account name as the Organization dedupe key. Industry, website, address, phone, and employee count fields migrate to their Pipedrive Organization equivalents. Account hierarchies in Dynamics (parent-account relationships) cannot be natively represented in Pipedrive's flat Organization model; we document the hierarchy in a written inventory for the customer's admin to recreate as Organization links or a custom field. Account ownership (ownerid) maps to the Pipedrive user by email match.

Dynamics 365 Opportunity records map to Pipedrive Deals. The opportunity name, estimated close date (estimatedclosedate), amount (estimatedvalue), and pipeline stage (stageid) map to the Deal title, close date, value, and pipeline stage respectively. Dynamics Opportunity stages map to Pipedrive pipeline stages during schema design; we create a Pipedrive pipeline per Dynamics sales process or record type. Lost reasons from Dynamics close_stage field migrate as a custom field lost_reason__c on the Deal. The Opportunity-to-Account and Opportunity-to-Contact relationships resolve to the target Organization and Person records during migration.

Dynamics 365 Product records (productid, name, productnumber, standardcost, price) map to Pipedrive Products. We create Pipedrive Products during migration and associate them with Deals as line items. ProductCode from Dynamics (hs_sku equivalent) migrates as the Pipedrive Product code field. Note that Pipedrive's product pricing is managed within the Product record and attached to Deals; there is no separate Pricebook equivalent.

Dynamics 365 ActivityPointer records (Email, Task, PhoneCall, Appointment) migrate as Pipedrive Activities. Each Dynamics activity type maps to the corresponding Pipedrive Activity type (email, task, call, meeting). The regardingobjectid lookup links to the migrated Person or Organization by resolving the original Dynamics record ID to the newly assigned Pipedrive ID. Subject, description, and timestamps (actualend, actualstart) migrate directly. We handle activity migration in a separate pass after Person and Organization records exist in Pipedrive to satisfy the relationship lookups.

Dynamics 365 Annotations (notes with file attachments) migrate as Pipedrive Notes with attached files. We export Annotations in a separate pass after the parent Person, Organization, or Deal exists. The annotation's objectid and objecttypecode resolve to the target Pipedrive record. File content (documentbody) migrates as a Pipedrive file attachment linked to the Note. Rich-text note body preserves formatting where the Dynamics note uses HTML; plain text is used as fallback.

Dataverse custom entities exported via the managed solution schema map to Pipedrive Custom Objects. The customer must provide the solution ZIP or Configuration Migration Tool schema file before we can define the destination Custom Object structure. Custom fields are created in Pipedrive via the /v1/itemSchemas API (not the standard /dealFields endpoint, which does not cover Custom Objects). If the destination Pipedrive account is on the Essential or Advanced lower tiers, Custom Objects may not be available; in that case we document the custom entity fields and advise on which Pipedrive tier is required for migration.

Dynamics 365 Campaign records have no direct Pipedrive equivalent. We handle Campaign membership by labeling the associated Person records with a Campaign-derived label in Pipedrive (e.g., a label named after the Campaign). The Campaign name and description are documented in the migration inventory, and the campaign association for each Person is preserved via the Pipedrive label. Campaign Activities (msdyn_campaignactivity) that represent specific outreach actions are documented as Activity records with type=campaign_activity and the original campaign name in the subject.

Dynamics 365 Marketing Lists contain member records (Contacts or Leads) and are associated with Campaigns. We export the Marketing List membership, creating Pipedrive Lists (accessible via the Pipedrive API) that contain the Person records in each list. The list name maps from the Marketing List's msdyn_name. List membership is recreated by resolving the Dynamics contact or lead IDs to the migrated Pipedrive Person records. If Pipedrive Lists are not available on the customer's current tier, we document the list membership as a custom Person field multi-select for manual reassignment.

Dynamics 365 Owner records (systemuser) map to Pipedrive Users by email address match. We extract all distinct ownerid values from Contacts, Accounts, Opportunities, and Activities. Any owner without a matching Pipedrive User is placed in a reconciliation queue for the customer's admin to provision before record migration resumes. Inactive Dynamics users map to inactive Pipedrive Users if the historical owner assignment must be preserved; otherwise the admin can reassign records to active users during the migration window.

Marketing email templates stored in the msdynmkt_email Dataverse table have no direct Pipedrive equivalent because Pipedrive does not include native marketing email send capabilities. We export the email template content (subject, HTML body, sender address) and deliver it as a written inventory document. The customer's admin or a marketing implementation partner uses this inventory to rebuild templates in their chosen marketing automation tool (Mailchimp, ActiveCampaign, HubSpot Marketing, or similar). We do not migrate email templates as functional records.