Migrate from Click to HighLevel

ClickDimensions does not store contacts independently — they live in the underlying Microsoft Dynamics 365 CRM. We extract contacts from the Dynamics instance using the Dynamics Web API, mapping FirstName, LastName, Email, Phone, CompanyName (to Account lookup), and Address fields to GoHighLevel Contact properties. Any ClickDimensions-specific consent flags, email engagement scores, or lead scoring attributes stored as Custom Fields on the Dynamics contact record are extracted separately and written to GoHighLevel Contact custom fields during the custom field mapping phase. We confirm the Dynamics environment and required OAuth credentials during scoping before any extraction begins.

Dynamics 365 Accounts (Companies) map to GoHighLevel Company records. The Dynamics AccountName becomes the Company name, Website maps from the Dynamics Website field, and Industry maps from the Dynamics Industry picklist. We create GoHighLevel Company records before Contact records so that the Contact-to-Company lookup is satisfied at the moment of Contact insert. Address, phone, and annual revenue fields migrate as standard Company properties where available in Dynamics.

Dynamics 365 Leads that have not been qualified or converted to Contacts in the source org are mapped to GoHighLevel Contacts with a lead source indicator in a custom field. Any ClickDimensions custom field annotations on the Dynamics Lead record (lead scoring, marketing consent, event attendance history) migrate to the corresponding GoHighLevel Contact custom fields. We use a lead_source__c custom field to flag records that originated as Dynamics Leads so that the customer's team can identify unqualified prospects requiring follow-up in GoHighLevel.

ClickDimensions Email Sends record campaign name, send date, recipient email, and delivery status against a Dynamics contact. We split this into two destination records: the campaign name and send metadata migrate to GoHighLevel Contact custom fields (e.g., last_email_campaign__c, last_email_send_date__c), and a Task activity record is created for each send event with the campaign name in the Subject and the send date as ActivityDate. Individual open and click engagement events are noted as additional Task records with a custom engagement_type__c field set to open or click.

ClickDimensions Event Registrations map to GoHighLevel pipeline Deals. We create a dedicated pipeline (e.g., Events Pipeline) with stage values such as Registered, Attended, No-Show, and Follow-Up based on the registration status in ClickDimensions. Registration date, session choices, and custom registration field answers migrate to custom fields on the Deal record. The Deal is linked to the Contact record via the GoHighLevel Contact lookup, preserving the event-to-attendee relationship.

ClickDimensions Web Tracking Events capture page visits, form submissions, and behavioral data against known contacts (identified by email) or anonymous visitors. Known-contact events map to GoHighLevel Contact custom fields (e.g., last_page_visited__c, landing_page_source__c) and Tags that segment contacts by behavior. Anonymous visitor data is optionally migrated as tags or contact properties if the customer has a use case; otherwise it is excluded from the migration scope and documented as a decision point during scoping.

Survey responses in ClickDimensions are linked to Contacts and store answer data in custom field structures. We extract each survey question and answer pair and map them to GoHighLevel Contact custom fields. For surveys with open-ended responses or long-form answers, we create a Note attached to the Contact record containing the full response text. Survey metadata (survey name, completion date, completion rate) migrates to contact-level custom fields or a dedicated tag on the Contact record.

ClickDimensions custom fields on contacts, tasks, and event registrations are audited during scoping. Free Forever plan customers are limited to 60 Custom Field write uses, which we check before the migration begins. If the plan is Free Forever and the custom field count approaches or exceeds 60, we prioritize active marketing fields, defer low-priority fields, and document the remainder for post-migration manual population. Paid plan customers have higher or unlimited custom field write access, and we map all active fields to GoHighLevel Contact or Opportunity custom fields using GoHighLevel's native custom field builder. Field type mapping (text, date, number, dropdown) is resolved during the scoping phase before schema creation in GoHighLevel.