Migrate from Lead Liaison to Twenty CRM

Lead Liaison Prospect records map directly to Twenty CRM Person. We extract all standard contact fields (name, email, phone, address) plus custom properties stored on the Prospect record. Lead Liaison's lifecycle stage and source attribution properties map to custom fields on the Person record. A dedupe key is constructed from the email address; any duplicates found in Twenty are flagged for customer resolution before final import.

Lead Liaison Company profiles map to Twenty CRM Organization. Org-type classification, industry, website, and employee count migrate to corresponding Organization fields. Company records are imported before Person records so that the Person-to-Organization link is satisfied at insert time. Website domain from Lead Liaison becomes the Organization's website field for dedupe validation.

If Lead Liaison's bundled OneFocus CRM is used for deal management, Deals map to Twenty CRM Opportunity. Deal stage names map to a custom Opportunity status field (Twenty does not have a native pipeline stage object), and the deal amount, close date, and probability migrate as typed fields. The Opportunity is linked to the resolved Organization and Person records from the prior mapping phases.

Lead Liaison's custom activity tracking allows arbitrary event types (button clicks, link clicks, phone calls, orders, and any custom-defined event). These user-defined schemas have no standardized field names across customers. During scoping, we request a full list of active custom activity types, map each to either Twenty's Activity object (for time-stamped engagement events) or a Twenty Custom Object (for entity-like records with structured properties), and flag any types that cannot be represented natively for customer decision before migration begins.

Lead scoring values are stored as Prospect properties in Lead Liaison and export as numeric scores. We migrate the score value to a custom number field (e.g., lead_score__c) on the corresponding Person record. The scoring model itself (point allocations and weighted criteria) is not separately exposed in the Lead Liaison API and cannot be migrated; we document the original scoring logic as a written summary for the customer to recreate in Twenty or an external scoring tool.

Lead Liaison's ProspectVision module produces a chronological log of page views, company identification, and engagement depth per Prospect. We export visit records as a flattened engagement history attached to the corresponding Person record in Twenty. Each visit becomes an Activity record with the page URL, visit timestamp, and engagement depth preserved. Note that Twenty has no native website visitor identification feature, so this behavioral context is available for historical reference but does not produce live alerts in Twenty.

Automated buy signals are behavioral triggers attached to Prospects in Lead Liaison. We export signal type, trigger date, and associated Prospect. The signal type and trigger timestamp migrate to a custom field or tag on the Person record in Twenty. The underlying rule configuration that generated the signal is not exposed in the Lead Liaison API and is not migratable; we deliver a written description of the signal rules for the customer to implement as filters or workflows in Twenty or n8n.

Lead Liaison's flat tagging system applies labels to Prospects and other objects. We export all tag definitions and the Prospect-to-tag assignments. Tags migrate as flat labels on the Person record in Twenty. Twenty's tagging model is simpler than Lead Liaison's multi-object tagging; if tags were applied to Company or Deal records in Lead Liaison, those tags are migrated as custom fields or noted as scope gaps for the customer to address in Twenty's tagging UI.

Lead Liaison list membership defines audience targeting for campaigns and automations. We export list definitions and all Prospect-to-list assignments. Static lists become Twenty Collections (or groups of tagged Persons). Dynamic segments cannot be migrated as active filters because Twenty does not have a native dynamic segmentation engine; we document the segment criteria for manual rebuild or for implementation in an automation layer like n8n.

Form definitions and all submission records are available via the Lead Liaison API. We transfer form schemas and submission data including field responses, submission timestamps, and referring pages. Custom form field values become structured fields on an Activity record attached to the Person who submitted the form. Form builder configuration (field labels, conditional logic) is documented separately as a written handoff for the customer to recreate in Twenty or a form tool like Typeform.

Lead Liaison User records include name, email, role, and ownership assignments. We export all active users and map them to Twenty Workspace Users. Inactive or archived users are exported with a status flag for the customer to decide whether to provision them in Twenty. Owner assignments on Prospects, Companies, and Deals resolve via email match against the Twenty User table.