Migrate from Listrak to Freshsales

Listrak contacts migrate to Freshsales contacts with email as the dedupe key. We preserve the original opt-in date in a custom date field listrak_opt_in_date__c, and channel subscription status (email subscribed/unsubscribed) maps to Freshsales's email_status field. Any Listrak contact with a matching email in Freshsales is flagged as a potential duplicate for admin review before final insert. Custom contact properties migrate to Freshsales custom fields, with type mapping (text stays text, date stays date, numeric stays numeric) verified before load.

Listrak company records (if present) migrate to Freshsales Account. The company name becomes the Account Name, and domain data becomes the Website field. Account is created before Contact import so the lookup relationship resolves at insert time. Any Listrak company without a company_name field is held for manual review to prevent blank Account records.

Listrak mobile subscribers migrate to Freshsales Contacts with the mobile_number stored in Freshsales's phone field and the original opt-in date preserved in the custom listrak_opt_in_date__c field. We validate that the phone field format matches Freshsales's expected format before insert. The listrak_sms_consent__c flag migrates as a custom checkbox. Opted-out mobile subscribers are excluded from this mapping and loaded into the suppression list instead.

Listrak suppression and unsubscribe lists load into Freshsales's Do Not Contact list before any active contact import. This sequencing is mandatory to prevent Freshsales from sending to contacts that are opted-out in Listrak. We load suppression records by email address first, then by phone number for SMS suppressions. Any record that appears in both the active contact export and the suppression export is flagged and excluded from the active load to maintain compliance integrity.

Listrak behavioral segments (defined by email opens, clicks, cart events, purchase history) map to Freshsales contact lists. Since Freshsales lists are static and Listrak segments are dynamic, we capture the segment membership snapshot at migration time and load each segment as a Freshsales list. Listrak's segment filter criteria are documented in the handoff document for the customer to recreate as Freshsales filters post-migration. Segments with complex behavioral logic that cannot be replicated in Freshsales are noted for review.

Listrak email engagement events (opens, clicks, unsubscribes) migrate to Freshsales Activity records linked to the parent Contact. Open events become Note records with the timestamp and engagement type preserved in a custom field. Click events follow the same pattern. We preserve the engagement timestamp as the Activity Date so the contact timeline reflects the original behavior sequence. Historical campaign send data migrates as Notes attached to the contact.

Listrak SMS engagement events (replies, opt-outs, keywords) migrate to Freshsales Activity records with the engagement type preserved in a custom field. SMS opt-out events feed the suppression list load. Keyword responses are logged as Notes tied to the contact record. We exclude any SMS events associated with suppressed contacts to prevent re-activation in Freshsales.

Listrak custom contact properties migrate to Freshsales custom fields. We audit which custom fields appear in Listrak's API versus only in the UI before migration; UI-only fields require manual export or a support ticket to Listrak to surface. Field types are mapped to Freshsales equivalents: text to Text, date to Date, numeric to Number, dropdown to Picklist. Custom fields are provisioned in Freshsales before data load to avoid schema mismatch errors.