Migrate from eTrigue to HighLevel

eTrigue Prospects map 1:1 to GoHighLevel Contacts. Standard fields (First Name, Last Name, Email, Phone, Company, Address) transfer directly. We use email as the dedupe key during import to prevent duplicate contact creation. Any Prospect records missing an email address are held in a reconciliation queue; GoHighLevel requires an email for Contact creation via its API.

eTrigue stores Lead Score as five separate numeric properties: Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score. We create five custom numeric fields on the GoHighLevel Contact object (etrigue_campaign_score__c, etrigue_activity_score__c, etrigue_source_score__c, etrigue_relationship_score__c, etrigue_buy_time_score__c) and populate each from the corresponding source field. The customer decides during scoping whether to also create a composite etrigue_total_score__c field or apply their own scoring formula in GoHighLevel's Automation builder.

The 3D Lead Scoring model enriches standard scoring with content-type engagement weighting. We export the 3D score as a single composite numeric value and map it to a custom field etrigue_3d_score__c on the GoHighLevel Contact. GoHighLevel does not have a native equivalent 3D scoring model; the customer rebuilds the content-type weighting logic as an Automation using contact field triggers.

eTrigue's Status field exports as numeric codes (1 = Active, 2 = Opt-Out, and others documented in eTrigue support). We decode these codes during data transformation before loading into GoHighLevel and map them to GoHighLevel's contact subscription status fields (subscribed = Active, unsubscribed = Opt-Out). Without this decoding step, all migrated contacts would appear as numeric status codes rather than readable subscription states.

eTrigue campaign response data (email opens, click-throughs, form submissions, page views) is exported from Activity History as structured rows tied to a Prospect ID and timestamp. We map this to GoHighLevel Contact Tags (e.g., tag per campaign name or response type) and create an Opportunity-level note capturing the campaign response timeline as a text block for sales visibility. GoHighLevel's native Campaigns feature can also be used if the customer chooses to configure it.

eTrigue Lead Accelerator customers store partner organization names and partner-specific attribution in custom Prospect fields rather than a native Partner object. We map these to GoHighLevel Companies (for partner-level accounts) or a Custom Object named Partner__c if the customer wants a separate partner entity with a Contact lookup relationship. Which approach is used depends on whether contacts from multiple partners need to associate to the same partner organization.

eTrigue supports Boolean, Text, and other custom field types defined under Settings > Prospect Settings > Prospect Fields. Boolean fields store true/false with custom value labels. We create matching GoHighLevel Contact custom fields with equivalent types and map values field-by-field. GoHighLevel custom fields must be created before data import; we handle schema creation via the GoHighLevel API before loading.

eTrigue Content Types classify prospect engagement with content categories. We export these as tag values and map them directly to GoHighLevel Tags on the Contact record. Tags migrate as a comma-separated list that GoHighLevel splits and assigns to each Contact during import. The customer selects which Content Types to migrate during scoping to avoid over-tagging.