Migrate from eTrigue to Salesforce Sales Cloud

eTrigue Prospects map to Salesforce Contact as the primary target for known buyers and to Salesforce Lead for early-stage prospects. We apply a split rule based on the customer's eTrigue lifecycle data (or the presence of a closed Won campaign response) to determine which records convert directly to Contact versus landing as Lead first. Email address is the dedupe key. Standard fields (FirstName, LastName, Email, Phone, Company) map to typed Salesforce equivalents.

eTrigue custom fields (Boolean, Text, Date, Number) defined under Settings > Prospect Fields map to Salesforce custom fields on Contact with equivalent data types. Boolean fields in eTrigue store a true/false value with custom labels per value; we map the raw boolean to a Salesforce Checkbox and preserve the label mapping in a data dictionary for the customer's admin. Custom field API names use the __c suffix per Salesforce convention.

eTrigue exports the Status field as numeric codes (e.g., 1 = Active, 2 = Opt-Out). We detect these during data profiling, decode them against the documented eTrigue mapping, and set Salesforce HasOptedOutOfEmail to true for Opt-Out records. Active status records receive a custom field etrigue_status_code__c preserving the original numeric value for audit. Skipping this step silently marks Opt-Out contacts as active in Salesforce.

eTrigue's Lead Score is a composite of Campaign_Score, Activity_Score, Source_Score, Relationship_Score, and Buy_Time_Score, each stored as a separate numeric property on the Prospect record. We create five custom Number fields on Contact (etrigue_campaign_score__c, etrigue_activity_score__c, etrigue_source_score__c, etrigue_relationship_score__c, etrigue_buy_time_score__c) and export all five values independently. The customer's admin rebuilds the composite logic as a Salesforce Flow or formula field post-migration; we flag the original composite calculation rule in the scoring inventory document.

eTrigue's 3D Lead Scoring model enriches standard scoring with content-type engagement weighting and produces a single composite value. We export the 3D score as a numeric value and store it in a custom field etrigue_3d_score__c on Contact. Salesforce has no native equivalent for this model; we document the 3D scoring components and recommended Flow rebuild approach in the scoring inventory so the admin can recreate the weighting logic in Salesforce Flow or an AppExchange scoring tool.

eTrigue Campaigns map directly to Salesforce Campaign. Campaign Name, Start Date, End Date, and Status migrate to CampaignName, StartDate, EndDate, and Status. Campaign response data (who responded and when) maps to Salesforce CampaignMember records linked to the Contact or Lead. We use the CampaignMember object to reconstruct which Prospects responded to which campaigns, preserving the campaign attribution timeline.

Each eTrigue Prospect has an Activity History recording page views, email opens, form submissions, and campaign responses with timestamps. We export this as a structured log and map page views and email interactions to Salesforce Task records (with a custom activity_type__c field), form submissions to Event records, and campaign responses to CampaignMember with Status mapped from eTrigue's response type. Timestamps preserve the original eTrigue activity date for timeline ordering.

eTrigue email send records (campaign name, send date, open rate, click rate per contact) map to Salesforce CampaignMember with a custom field etrigue_email_sent_date__c and open/click tracking flags. We do not recreate the email content itself in Salesforce; email templates and body content are documented separately for rebuild in Salesforce Marketing Cloud Account Engagement (Pardot) or Marketing Cloud.

eTrigue landing pages host progressive forms with field definitions (field name, type, required/optional). We export the form field schema and map it to Salesforce Web-to-Lead form configuration or a custom form handler. We document the form field mapping, required fields, and any conditional logic so the admin can configure the equivalent Web-to-Lead or Experience Cloud form. Styling and page layout are not migratable and require rebuild.

eTrigue's Scheduled Exports use saved search criteria to segment Prospects (e.g., by score threshold, campaign response, or custom field value). We document every active scheduled export's criteria as a written segmentation rule. These rules translate into Salesforce Report filters, List Views, or Campaign segmentation logic. The customer's admin rebuilds these as Salesforce Report filters or a complementary segmentation tool.

eTrigue uses Content Types internally to classify prospect engagement with different content categories. We export these as tag values and map them to Salesforce multi-select picklist fields on Contact. For content-taxonomy use cases, we map to Salesforce Topics with TopicAssignment records linked to the Contact. The customer chooses the tagging strategy during scoping based on how the tags are used in reporting.

eTrigue Lead Accelerator customers store partner organization names and partner-specific campaign attribution in custom Prospect fields rather than a dedicated Partner object. We map partner organization names to Salesforce Account (using the partner name as Account Name with a custom Account Type = Partner), and partner-specific scoring rules to custom fields on Contact. We flag any partner-specific scoring logic requiring Flow rebuild in the scoring inventory document.