Migrate from eTrigue to Freshsales

eTrigue Prospects map directly to Freshsales Contacts. Standard fields (First Name, Last Name, Email, Phone, Company) migrate cleanly via CSV export. The Prospect record ID is preserved in a custom field etrigue_prospect_id__c for audit and cross-referencing. We deduplicate by email address during import to avoid creating duplicate Contact records.

The Company name stored on each eTrigue Prospect maps to a Freshsales Account. Accounts are created first so that the Contact-to-Account Lookup relationship is satisfied at import time. If multiple Prospects share the same Company name, they link to a single Account, which is the expected behavior in Freshsales.

eTrigue Campaigns become Freshsales Campaigns with campaign response data migrated as Campaign Member records. Each Prospect with a campaign attribution history gets a corresponding Campaign Member entry linked to the Campaign and the Contact. Campaign response timestamps (first response, last response, total responses) map to Freshsales Campaign Member fields. If eTrigue has campaign stage values (Registered, Attended, Converted), these map to custom Campaign Member status values.

eTrigue Activity History records (page views, email opens, form submissions, campaign responses with timestamps) migrate as Freshsales Tasks with Activity Type set to the corresponding engagement category. Each Task is linked to the migrated Contact via WhoId. Timestamps are preserved from the source record to maintain the chronological activity timeline. Page views and email opens without a specific action are logged as Note-type Tasks with descriptive body text.

The eTrigue composite Lead Score has five sub-components: Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score, each stored as a separate numeric field on the Prospect. We create five matching custom numeric fields on the Freshsales Contact record and migrate each score individually. Freshsales' native Freddy AI scoring is separate from these values; the customer can use the migrated scores as baseline reference data or configure Freddy rules that incorporate them. We do not merge the five components into a single composite score because each component carries independent signal.

eTrigue Boolean fields (true/false with custom labels per value) map to Freshsales checkbox fields. Text fields map to text fields. Numeric custom fields map to Freshsales numeric fields with type preservation. We handle the mapping during data profiling before import so that field types are pre-created in Freshsales rather than discovered during load. The total count of custom fields and their types is gathered during discovery to scope the custom field creation effort.

Customers using eTrigue Lead Accelerator for channel partner programs store partner organization names and partner-specific attribution in custom Prospect fields. We identify these fields during discovery, map the partner organization name to the Freshsales Account Name, and create additional custom fields on Account (e.g., partner_tier__c, partner_program__c, partner_campaign_id__c) to preserve attribution metadata. Partner-specific scoring rules are flagged in the deliverable for manual recreation in Freshsales if required.

eTrigue Content Types and Tags used to classify prospect engagement with content categories migrate to Freshsales Labels applied to each Contact. If a Prospect has multiple tags, they map to multiple Freshsales Labels on the Contact record. We export the tag list first to ensure the label taxonomy is created in Freshsales before import.