Migrate from ActiveTrail to Salesforce Sales Cloud

ActiveTrail Contacts with no associated Account data (email-only subscribers, marketing leads) map to Salesforce Lead. Contacts with company name, industry, or deal association map to Salesforce Contact attached to a corresponding Account. We compute the split using the presence of a company identifier in ActiveTrail's custom fields and route accordingly. Original subscription status preserves in hs_email_optin__c custom field for audit.

ActiveTrail Contacts with a recognized company name trigger Account lookup or creation in Salesforce. Company domain from ActiveTrail's custom fields maps to Account Website, used as the dedupe key. Accounts are created before Contact import so that AccountId is satisfied at Contact insert time.

ActiveTrail behavioral tags are flat string labels on Contact records. We create a Salesforce Campaign per major tag category (product interest, engagement tier, source channel) and add the corresponding Contacts as CampaignMembers. This preserves the behavioral segmentation in a queryable, reportable structure without creating 500+ individual Salesforce campaigns.

ActiveTrail dynamic segments are filter-based contact groups with conditions on custom properties and engagement behavior. We export the segment definition as a written rule set and map each segment to a Salesforce Report with filters matching the ActiveTrail conditions, plus a corresponding Campaign for membership tracking. The segment rebuilding happens in Salesforce via Reports, Pardot Dynamic Lists, or Flow-based segmentation.

ActiveTrail Email Campaigns (metadata: name, subject, send date, audience size, status) map to Salesforce Campaign records. Campaign Type is set to Email. Historical open/click/reply counts from ActiveTrail append to the Salesforce Campaign's statistics as a one-time historical sync rather than live reporting. HTML template content migrates as Salesforce email templates linked to the Campaign.

ActiveTrail HTML email templates (inline CSS, images, text blocks) export from the template library and import as Salesforce EmailTemplate records. Inline image hosting references update to Salesforce's document URLs or a customer-designated CDN. AMPscript or ActiveTrail-specific merge tags convert to Salesforce merge field syntax during import.

ActiveTrail SMS Campaigns map to Salesforce Campaign with Type = SMS. The SMS message content and character count migrate as custom fields on a Campaign or as a custom SMS Log object. Phone number normalization (E.164 formatting) applies during migration. SMS reply engagement history migrates to CampaignMember with ActivityDate timestamps.

ActiveTrail open events per Contact per Campaign migrate as CampaignMember records with Status indicating engagement level (Sent, Opened, Clicked). The original open timestamp preserves in a custom field member_engagement_date__c. These records populate Campaign reporting history but do not appear as live Email Analytics in Salesforce.

ActiveTrail click events migrate as CampaignMember records with a click-specific engagement flag and the URL of the clicked link stored in a custom field. Multiple clicks per Contact per Campaign aggregate to a click_count__c integer on the CampaignMember.

ActiveTrail Contact Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Lead or Contact. Note body passes through as rich text. Timestamps preserve in ActivityDate for timeline ordering.

ActiveTrail automation journeys with triggers, conditions, delays, and channel actions are exported as written blueprints describing the workflow graph, not as migrated automation code. The blueprint includes trigger event, condition branches, delay timers, and recommended Salesforce Flow equivalents. The customer's admin or a Salesforce partner rebuilds each journey post-migration. Running state and enrolled contacts do not migrate.

ActiveTrail contact custom fields (text, number, date, dropdown, checkbox) map to Salesforce custom fields on the destination object (Lead or Contact). Field types are matched: dropdown to picklist (requires value mapping), text to text (255 or long text area), date to date, checkbox to checkbox. Picklist fields require a value mapping table for any ActiveTrail dropdown options. Custom fields are pre-created in the Salesforce org via metadata API before data migration begins.

ActiveTrail landing pages built in the native builder export as HTML or reconstruct in Salesforce Experience Cloud. Form fields embedded in landing pages map to Salesforce Web-to-Lead or Experience Cloud form builders. We document the field mapping and redirect logic so the customer's admin can rebuild in Experience Cloud or a third-party landing page tool.

ActiveTrail signup form field definitions export as written field maps with field types and validation rules. The form-to-list and form-to-automation connections are documented for rebuild in Salesforce Web-to-Lead (connected to Salesforce Campaign) or Experience Cloud forms. Form submissions already collected migrate as Contact records.