Migrate from Salesforce Marketing Cloud Account Engagement to HighLevel

Account Engagement Prospects map to GoHighLevel Contacts. Email address is the sole unique identifier in Account Engagement and serves as the primary dedupe key in GoHighLevel import. We use a three-pass matching strategy: exact email, normalized email (stripped of case and punctuation), then manual resolution queue for duplicates. The Pardot prospect_id is preserved in a custom GoHighLevel field pardot_prospect_id__c for audit and cross-reference.

Account Engagement Custom Fields are first-class objects in the Pardot v5 API with full CRUD support. We export field definitions (label, API name, type) and their values per Prospect. Custom field labels and types map to GoHighLevel custom field equivalents by type: text to text, number to number, date to date, dropdown to dropdown. Field-level validation rules in GoHighLevel are configured to match the source field constraints.

Account Engagement does not have a native Account object — Prospects are associated to Salesforce Accounts via the CRM sync. We extract Account names and domains from the Salesforce sync fields on Prospect records and create GoHighLevel Company records before Contact import so that the Company-Contact relationship is established at insert time. If no Account data is present on the Prospect, we create a Company using the Prospect's domain field or leave it unattached for manual resolution.

Account Engagement Campaigns track marketing initiative performance and link to Salesforce Campaigns. We export Campaign metadata (name, status, type, start and end dates) and Prospect-level activity data (opens, clicks, form submissions, page visits) as Engagement history on the corresponding GoHighLevel Contact. Campaign-level aggregate metrics are preserved in a Campaign summary note or custom field. If the customer uses Campaigns as a pipeline proxy, we map them to GoHighLevel Opportunities or a dedicated Pipeline.

Account Engagement Scoring Categories define named buckets for categorizing Prospect scores (e.g., behavioural score vs. demographic score). We export category definitions and their weight rules as GoHighLevel Custom Score Fields on Contact. Score values recalculate post-migration based on the same criteria re-implemented as GoHighLevel workflow actions or custom field formulas. We do not migrate the score calculation engine — we document the rules for the customer's team to implement as GoHighLevel automations.

Account Engagement Tags segment Prospects and attach to Custom Fields and Prospects via the API. We export tag definitions and their assignments per Prospect as GoHighLevel Contact Tags. Tags merge cleanly into GoHighLevel's tag model without transformation.

Static Lists in Account Engagement segment Prospects for targeted campaigns. We export list memberships as Contact records assigned to GoHighLevel Contact Lists. Dynamic Lists with rule-based criteria are not migratable as active lists — we deliver a written description of each Dynamic List's filter conditions so the customer's team can recreate them in GoHighLevel's segmentation builder.

Account Engagement Email Templates contain HTML content, dynamic content blocks, and Pardot double-brace merge fields (%%first_name%%). We export template HTML and rewrite merge field syntax to GoHighLevel-compatible tokens ({{contact.first_name}} or equivalent). Dynamic content blocks with conditional logic require manual review and reconstruction in GoHighLevel's template editor — these are flagged for marketer-level rebuild rather than automated import.

Account Engagement Users (Assigned Users / Owners) correspond to Salesforce Users responsible for Prospect records. We map Pardot user email to GoHighLevel User by email match. Any Pardot User without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before Contact import resumes.