Migrate from Lead Liaison to Freshsales

Lead Liaison Prospects with a linked Company record map to Freshsales Contact tied to an Account. Prospects without a company association or without a clear buying signal map to Freshsales Lead for the sales team to qualify and convert. We compute the split using Lead Liaison properties including lifecycle_stage, hs_lead_status, and engagement_score, then preserve the original Prospect record ID in a custom field ll_prospect_id__c for deduplication and audit. If the customer's sales process treats all Prospects as Contacts in Freshsales, we apply a bulk-to-Contact migration and skip the Lead step.

Lead Liaison Company records map to Freshsales Account. Company domain from Lead Liaison becomes the Account Website field and serves as the dedupe key during import. Org-type classification and industry data transfer to Freshsales Account standard fields; any additional company properties store in custom fields provisioned before the Account import phase. We create Accounts before any Contact import so that the AccountId Lookup is satisfied at Contact insert time.

Lead Liaison list membership defines audience targeting for campaigns and automations. We export all list definitions and Prospect-to-List assignments, then recreate them in Freshsales as either native Tags (flat labels) or a multi-select picklist field list_name__c on the Contact or Lead object. The customer chooses the strategy during scoping. Dynamic segments with filter-based criteria do not migrate; we document the filter logic for manual rebuild in Freshsales.

Lead Liaison Form definitions and all submission records are available via API. We transfer form schemas and submission data including field responses, submission timestamps, and referring page URLs as a structured Note body attached to the corresponding Contact or Lead in Freshsales. Custom form field labels that have no equivalent in Freshsales store in a custom field form_responses__c as a JSON blob. Note that Freshsales Forms is a separate product (Freshmarketer) and form rebuilds are scoped as a separate task.

Lead Liaison Tags are a flat labeling system applied to Prospects and other objects. We export all tag definitions and prospect-to-tag assignments. Tags map directly to Freshsales native Tags, which apply to Contacts, Accounts, Deals, and Leads. Tags used for segmentation intent are preserved alongside list membership for double-layer audience targeting in the new platform.

Lead Liaison User records include name, email, role, and ownership assignments. We extract all active users and map them by email to Freshsales Owner fields on Contacts, Accounts, Deals, and Activity records. Inactive or archived Lead Liaison users are flagged in the migration report for the customer's admin to provision as inactive Freshsales Users or reassign to an active owner.

Lead Liaison lead scoring values are stored as Prospect properties and exported as numeric scores. We transfer the score to a custom numeric field ll_lead_score__c on Contact or Lead. The scoring model itself (point allocations and weighted criteria) is not separately exposed in the API and does not migrate; we document the model's structure from a screen share or configuration export if available so that the customer can rebuild it in Freshsales AI Scoring or a custom formula field.

Lead Liaison's API allows tracking custom activities such as button clicks, link clicks, phone calls, orders, and any user-defined event. We export all custom activity records with type, timestamp, and associated Prospect. Each custom activity type is mapped to a Freshsales Activity record with the activity type set to Custom, or to a Note if the event is informational rather than a tracked interaction. The customer selects the preferred treatment during scoping. Custom activity schemas that cannot be represented natively store as JSON in a custom field ll_custom_activity__c.

Automation logic including triggers, conditions, time-delay configurations, and A/B split logic is stored in a proprietary format not fully exposed via API. We export automation definitions as a structured summary document including trigger types, step counts, associated assets, and a recommended Freshsales Workflow equivalent. The customer's admin rebuilds automations in Freshsales Workflow Builder (available from Growth tier). Automation rebuild is outside migration scope and is scoped as a separate consulting task.

Automated buy signals in Lead Liaison are behavioral triggers attached to Prospects. We export signal type, trigger date, and associated Prospect. Signal types transfer to a custom multi-select picklist ll_buy_signal__c on Contact or Lead. The underlying rule configuration is not exposed in the API; we document the signal generation logic separately for the customer to rebuild in Freshsales using Workflow triggers or territory rules.