Migrate from Loyalistic to Freshsales

Loyalistic Contacts map to Freshsales Leads if the contact is unqualified or has no associated deal history, and to Freshsales Contact if the contact has a closed-won deal, survey response, or campaign engagement record. We apply this split at migration time using the Loyalistic contact's status property and deal association count. The original Loyalistic contact ID is preserved in a custom field loyalistic_id__c on both the Lead and Contact for cross-reference. Email is the dedupe key on import.

Loyalistic Customer Profile enrichment data (company name, domain, industry, employee count, revenue range) maps to Freshsales Account fields. We separate company-level data from contact-level profile fields, placing enrichment provenance metadata in a custom field profile_source__c on the Account. If the Loyalistic contact has no associated Customer Profile, we create an Account using the contact's company name field as a fallback.

Loyalistic segment membership (which contacts belong to which behavioural or demographic groups) is a membership list export. We export each segment name and its member contact IDs, then apply the segment names as Tags in Freshsales using the Freshsales Tags API. Segment rule logic does not migrate; the static membership list is what transfers. The customer's admin recreates segment logic as Freshsales Workflow conditions or Freddy AI filter criteria post-migration.

Loyalistic Survey definitions and response records attach to contacts. We extract each survey question as a custom field name on the Freshsales Contact object, and the response value as the field value. Survey branching logic requires manual reconstruction in Freshsales Forms or via a custom object if the Enterprise tier is licensed. We deliver a written survey-field inventory mapping each Loyalistic survey question to its Freshsales custom field API name and field type.

Loyalistic Campaign records (title, status, timing, budget) map to Freshsales Account with a campaign_type__c custom field set to Campaign. Engagement events (opens, clicks, sends) associated with a campaign migrate as Activity records on the related Account. Campaign-level metrics (open rate, click rate) are stored as custom numeric fields on the Account. Campaign automation sequences do not migrate.

Loyalistic custom properties on Contact are identified through field-level sampling during discovery. Each custom property is typed (text, number, date, checkbox, dropdown) and mapped to an equivalent Freshsales custom field on the Contact or Lead object. Field mapping is explicit before migration; no unmapped custom properties are dropped silently. Multi-select Loyalistic properties map to Freshsales multi-select picklist fields.

Loyalistic tags are flat labels applied to contacts for grouping. They migrate directly to Freshsales tags using a 1:1 name mapping. Tags are applied to the migrated Lead or Contact record based on the Loyalistic contact-to-tag association. Tag names are normalised (trimmed, lowercased) before import to prevent casing-variant duplicates.

Loyalistic engagement events (opens, clicks, conversions, form submissions) are extracted as individual activity records and attached to the migrated contact in Freshsales. Opens and clicks become Task records with type=Email; conversions become Task records with a custom conversion_event__c field; form submissions become Task records with a custom form_name__c field. Activity timestamp is preserved from the Loyalistic event date. We use Freshsales Bulk API with chunking for engagement histories exceeding 10,000 records.