Migrate from Click to Freshsales

ClickDimensions does not store contacts independently — it extends Microsoft Dynamics 365 contacts with marketing attributes (consent flags, email engagement scores, custom field data). We migrate contacts from the underlying Dynamics 365 instance, not from ClickDimensions directly. The Dynamics contact ID becomes the dedupe key during Freshsales import. Email address is used as the primary match field if a Freshsales contact already exists. ClickDimensions marketing annotations (consent status, engagement scores) map to Freshsales custom fields on the Contact record.

Accounts in Dynamics 365 map to Freshsales Organizations. The account name, website, industry, address, and phone fields migrate directly. Freshsales Organization is created before any Contact import so that the organization lookup is satisfied at the moment of Contact insert. The contact-to-account relationship in Dynamics maps to Freshsales Contact-Organization linkage via the organization_id field.

Leads from Dynamics 365 map directly to Freshsales Lead records. Lead status, source, rating, and custom fields migrate. Any ClickDimensions marketing annotations on Dynamics Leads (lead scores, campaign responses) migrate to Freshsales custom Lead fields. We preserve the original Dynamics Lead ID in a reference field for audit and reconciliation purposes.

ClickDimensions email send records (campaign name, send date, status, recipient count) map to Freshsales Contact records with an associated Activity Task documenting the send. Individual open and click events are mapped to Freshsales custom contact activities where the destination plan supports custom activity types; otherwise they are preserved as notes on the Contact. The parent contact is resolved via the Dynamics contact ID lookup before import.

ClickDimensions event registration records are linked to CRM contacts via the Dynamics contact ID. Registration status, session choices, and custom registration fields map to Freshsales Contact custom fields (event_name__c, registration_status__c, session_choice__c). We extract registration data via the ClickDimensions API, resolve the parent contact, and append event history as structured custom field data on the Freshsales Contact record.

ClickDimensions web tracking captures behavioral events (page views, form submissions) tied to known contacts by email address. Known-contact events migrate to Freshsales Contact records as Activity tasks with a descriptive body (page URL, timestamp, event type). Anonymous visitor events are optionally migrated if the customer requests them; otherwise they are logged as a separate data artifact for the admin to handle manually.

Survey responses in ClickDimensions are linked to contacts and include answer data in custom field structures. We extract response records via the API, resolve the parent contact, and map survey questions to Freshsales Contact custom fields. If survey answers exceed a reasonable number of custom fields per contact, we create a Survey_Response__c custom object with a lookup to Contact and store question-answer pairs as field-value records.

ClickDimensions custom field definitions on tasks and other entities are mapped to Freshsales Contact custom fields. We check the destination Freshsales plan tier during scoping to confirm custom field availability (all plans support custom fields). ClickDimensions Free Forever plan limits Custom Field writes to 60 uses per workspace — we verify the plan tier and either use the API within the limit or fall back to manual UI-based population for overflow records before migration begins.

Dynamics 365 Opportunities map to Freshsales Deals. The opportunity name, amount, close date, stage, and probability migrate. Dynamics opportunity products and line items map to Freshsales Deal Line Items. The deal owner maps from the Dynamics user to a Freshsales User via email match. Any ClickDimensions marketing influence data attached to the opportunity is preserved as custom fields on the Freshsales Deal.