Migrate from OPEX 365 CRM to Pipedrive

OPEX 365 CRM Account maps to Pipedrive Organization as a direct equivalent, capturing company-level records and business details. Dynamics parent-account hierarchies map to Pipedrive's one-level org linking — circular references are flagged during the pre-migration audit. Multi-currency accounts require currency-field consolidation in Pipedrive's single-currency field, with exchange rates preserved as a custom field reference where applicable. The pre-migration audit also validates website URLs, industry codes, and employee count fields against Pipedrive's pick-list constraints before migration. Owner assignment follows the standard email-matching logic used across all entity types.

OPEX 365 CRM Contact maps to Pipedrive Person directly on all standard fields: name, email, phone, job title, address. Dynamics Contacts without a primary AccountId are attached to a placeholder Organization record to prevent orphaned Person entries. Owner resolution runs by email match against Pipedrive users.

OPEX 365 CRM Opportunity maps to Pipedrive Deal. Each Dynamics sales pipeline maps to a Pipedrive Pipeline; stage names translate via value-by-value mapping defined in the field mapping workbook. Dynamics Opportunity fields — amount, probability, estimated close date — map to Pipedrive Deal fields directly.

OPEX 365 CRM Lead maps to Pipedrive Lead as a near-equivalent. Pipedrive Leads are pre-qualification records that route to Persons upon conversion; Dynamics Leads that have already advanced to Opportunity stage are mapped to Deals instead to preserve the deal history.

OPEX 365 CRM's unified ActivityPointer entity merges phone calls, emails, tasks, and appointments into a single object type. These merge into Pipedrive Activity records with a type field differentiating call, email, task, or meeting. The original timestamps, owners, and regarding links to Account or Contact are preserved as Pipedrive activity fields.

OPEX 365 CRM Product records map to Pipedrive Products with name, code, unit price, and description transferred directly. Product bundles and pricing lists from Dynamics are not a native Pipedrive construct — if used, they are flattened into individual product entries with pricing notes carried in a custom field.

OPEX 365 CRM custom entities built on Dataverse have no native equivalent in Pipedrive, which lacks a custom object model. We surface each custom entity's key fields as custom fields on the nearest Pipedrive object (Person, Organization, or Deal). N:N relationship data between custom entities is preserved as pipe-delimited IDs in a custom field for reference.

OPEX 365 CRM Opportunity Products link Products to Opportunities with quantity and pricing. Pipedrive Deals support Products on each deal record; we migrate the linked products with quantities and prices as deal-line items. Bundle products from Dynamics are expanded to individual line items in Pipedrive.

OPEX 365 CRM Notes (Annotation records) with body text migrate to Pipedrive Activity records of type 'note' linked to the parent Person, Organization, or Deal. File attachments are downloaded and re-uploaded to Pipedrive's file storage against the matching record. Large files above Pipedrive's storage limits are flagged for manual re-upload.

OPEX 365 CRM owners (SystemUser records) are matched to Pipedrive users by email address. Unmatched owners are flagged before migration — teams either invite the user to Pipedrive first or assign their records to a fallback user. This owner resolution step runs before any record data is written to Pipedrive.