Migrate from Click to Pipedrive

ClickDimensions does not store contacts independently — all contact records live in the underlying Microsoft Dynamics 365 instance. We extract contacts from Dynamics 365 first using the Dynamics API or Dataverse, then map them to Pipedrive Person records. The Dynamics contactid becomes the dedupe key during import, and the original Dynamics contact ID is preserved in a custom field crm_contact_id__c on the Pipedrive Person for audit and future cross-reference.

Account records are stored in Dynamics 365 and linked to Contacts via the parentcustomerid relationship. We extract Accounts from Dynamics first (before any Contact import) and map them to Pipedrive Organization records. The Dynamics accountid is preserved in a custom field crm_account_id__c on the Organization. Organization is created before Person import so that the AccountId lookup on Person is satisfied at insert time.

Leads are standard Dynamics 365 CRM records that can receive ClickDimensions marketing annotations. We extract Leads from Dynamics and migrate them to Pipedrive Lead records. Any ClickDimensions lead-scoring attributes or custom field data annotated on the Lead in Dynamics migrate as custom fields on the Pipedrive Lead object.

Dynamics 365 Opportunities map to Pipedrive Deals. The Dynamics processid maps to a Pipedrive Pipeline (one per Dynamics business process or sales process). Dynamics stagecode maps to Pipedrive Stage within that Pipeline. Close date, estimated value, and probability migrate to the corresponding Pipedrive Deal fields. Owner is resolved by email match to the Pipedrive User table.

ClickDimensions Email Send records are marketing activity entries linked to CRM contacts. There is no native Pipedrive equivalent for email campaign send history. We map each Email Send to a Pipedrive Note attached to the corresponding Person (resolved via the Dynamics contact lookup), with campaign name, send date, send status, and open rate stored as custom fields on the Note. Email send records without a resolvable Contact reference are held in a reconciliation queue for the customer's admin to resolve.

ClickDimensions Event Registration records are tied to CRM contacts via the eventid and contactid cross-references. We map registrations to Pipedrive Notes on the linked Person, with event name, registration date, registration status, session choices, and custom registration fields stored as custom fields on the Note. Multi-session events with separate registration records per session are consolidated into a single Note per contact per event with session data as a multi-value custom field.

ClickDimensions captures web behavioral events (page views, form submissions, content downloads) tied to known contacts via email address matching. We map these to Pipedrive Activity records (Activity type: Task with a custom activity type field set to WebTracking) on the linked Person. Anonymous visitor events without a resolvable contact are optionally migrated as Organization-level Activities or omitted based on the customer's scoping decision.

ClickDimensions Survey Responses store answer data in custom field structures linked to contacts. We map each response to a Pipedrive Note on the Person, with survey name and response date as header fields and individual question-answer pairs mapped to custom fields on the Note. Survey questions that represent multi-select answers are stored as semicolon-delimited strings or multi-select custom fields where Pipedrive field types permit.

ClickDimensions custom fields on tasks and entities carry marketing-specific attributes that extend Dynamics CRM records. We pre-create matching custom fields in Pipedrive on the Person, Organization, Deal, and Lead objects during schema design. ClickDimensions Free Forever plan customers are scoped for API usage within the 60-use limit; for migrations exceeding this, we coordinate with the customer to upgrade the plan or use manual UI-based field population for overflow records.

Products in Dynamics 365 (or those managed through ClickDimensions product references) map to Pipedrive Product records. ProductCode from Dynamics maps to the Pipedrive Product code field. Price book entries in Dynamics map to the Pipedrive Price field on the Product.

Dynamics 365 activities (tasks, phone calls, appointments, emails) that are standard CRM records map to Pipedrive Activities. Call activities from Dynamics map to Pipedrive Activities with the activity type set to Call. Appointment activities map to Meetings. Task activities map directly to Pipedrive Task activities. Each activity is linked to its parent Person or Organization via the WhoId and OrganizationId references resolved during migration.

Dynamics 365 users who own records are mapped to Pipedrive User records by email address match. Any Dynamics user without a matching Pipedrive User is placed in a reconciliation queue; the customer provisions the missing Pipedrive Users before migration of owner-dependent records (Deals, Activities) proceeds. Inactive Dynamics users are mapped to inactive Pipedrive users to preserve historical assignment.