Migrate from Click to Salesforce Sales Cloud

ClickDimensions does not store contacts independently — it extends Microsoft Dynamics 365 contact records with marketing attributes. We pull the base Contact records from the Dynamics 365 instance, preserving FirstName, LastName, Email, Phone, and the contact's Account link. ClickDimensions-specific fields (email consent flags, engagement scores, lifecycle stage annotations) migrate as custom fields on the Salesforce Contact record. The AccountId lookup on Contact is resolved from the Account records imported in the same phase.

ClickDimensions links marketing activity to Accounts primarily through the contact-to-account relationship. We extract Account records from the Dynamics 365 instance and import them into Salesforce as Account. The Account Name, Website, Industry, and Billing Address fields migrate directly. Account must be imported before Contact so that the AccountId foreign key is available at Contact insert time.

Dynamics 365 Lead records with ClickDimensions marketing annotations (lead scoring, source attribution, campaign responses) migrate to Salesforce Lead. The Dynamics leadscore and rating fields map to Salesforce LeadScore and Rating. Any ClickDimensions custom fields on Leads migrate to custom Lead fields. Leads are imported after Accounts and before Contacts to maintain referential integrity.

ClickDimensions Email Send records (send date, campaign name, recipient count, delivery status) map to Salesforce Campaign. Individual send recipients link as CampaignMember records attached to the corresponding Contact or Lead. Email engagement events (opens, clicks) from ClickDimensions migrate as Campaign Member Status updates (Sent, Opened, Clicked) and as Activity records (Tasks) with engagement timestamps. Open and click counts aggregate on the Campaign for reporting.

ClickDimensions Event entities store registration records linked to CRM contacts and accounts. Registration status, session choices, and custom registration fields migrate to Salesforce Campaign (of type Event) with CampaignMember records for each registrant. Custom registration fields (e.g., dietary restrictions, session preferences) become custom fields on Campaign or CampaignMember depending on whether the data is attendee-level or event-level. The Event start and end date from ClickDimensions map to Salesforce Campaign StartDate and EndDate.

ClickDimensions captures web behavioral events tied to known contacts (via email) or anonymous visitors. Known-contact events migrate to Salesforce Task records linked to the Contact, with the event type (page view, form submission, resource download) as Task Subject and a custom Task field for event detail. Anonymous visitor data is optionally migrated to a custom WebActivity__c object keyed by session ID if the customer requires the raw behavioral data for reporting. The ActivityDate on Task preserves the original event timestamp for timeline ordering.

ClickDimensions Survey Responses are linked to contacts and include answer data in custom field structures. We extract response records and map survey questions to fields on a Salesforce custom object SurveyResponse__c with a Lookup to Contact. Survey answers that are multi-select or free-text become Textarea fields; single-select answers become Picklist fields. Response status (completed, partial, abandoned) from ClickDimensions becomes a Status__c picklist on the custom object. We pre-create the custom object schema in Salesforce before migration.

Dynamics 365 Opportunities map to Salesforce Opportunity. The Dynamics opportunity amount, close date, and stage map to Salesforce Amount, CloseDate, and StageName. Stage probability percentages migrate to Salesforce StageProbability fields. The Opportunity's AccountId and OwnerId are resolved from the Account and User lookups imported earlier in the migration sequence.

ClickDimensions creates activity records in Dynamics 365 for email engagement, form submissions, and other interactions. These are standard CRM Activity objects in Dynamics and migrate cleanly to Salesforce Task and Event. Email engagements migrate as EmailMessage records (the content) linked to a Task (the timeline entry). Form submission events migrate as Task records with a custom form_name__c field. The WhoId on Task points to the Contact or Lead; the WhatId points to the related Opportunity, Account, or Campaign.

ClickDimensions supports custom fields on tasks via its API. Free Forever plans limit Custom Field writes to 60 uses per workspace, so we check the customer's plan tier during scoping. On Free Forever plans we use the API within the 60-use limit and fall back to manual UI-based field population for overflow records. On paid plans we map all custom task fields to Salesforce custom Task fields without limitation. The custom field API name from ClickDimensions becomes the Salesforce custom field API name with __c suffix.

ClickDimensions user records for the Dynamics instance (sales reps, marketers) map to Salesforce User records. We resolve owners by email match against the destination Salesforce org's User table. Any owner without a matching User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId must be resolved before Opportunities, Contacts, Leads, and Tasks can be imported.

If the Dynamics 365 instance contains product catalog data used in Quotes or Opportunities, we extract Products and Price List entries and map them to Salesforce Product2 and PricebookEntry. The product code from Dynamics becomes the Product2 ProductCode; the price list value becomes the Standard Pricebook entry. Products must be imported before Line Items.