Migrate your Lead Liaison data

Prospect records are the core object in Lead Liaison's CRM. The API exposes all standard contact fields plus custom properties. We map Prospects directly to Contacts in destination CRMs and preserve all custom property values as standard or custom fields depending on the target schema.

Company profiles are linked to Prospects and include org-type classification, industry data, and website information. We extract Company records independently and match them to corresponding Account objects in the destination.

Lead Liaison's list membership defines audience targeting for campaigns and automations. We export list definitions and all Prospect-to-List assignments, then recreate static lists or dynamic segments in the destination based on the target platform's list model.

Campaign metadata (name, status, associated lists) transfers cleanly. Email content, templates, and assets require special handling: we extract HTML content and inline assets, but campaign performance metrics are not reliably exportable via API and must be noted as scope limitations.

Automation logic (triggers, conditions, step sequences) is stored in a proprietary format. We export automation definitions as a structured summary including trigger types, step counts, and associated assets, but complex multi-branch workflows require manual rebuild or consulting assistance in the destination.

Form definitions and all submission records are available via API. We transfer form schemas and submission data including field responses, submission timestamps, and referring pages. Custom form fields that do not map directly to standard CRM fields are stored as custom properties.

Lead scoring values are stored as prospect properties and exported as numeric scores. The scoring model itself (point allocations, weighted criteria) is not separately exposed in the API, so we export the current score state and document it as a snapshot rather than a replicable scoring rule.

Automated buy signals are behavioral triggers attached to prospects. We export the signal type, trigger date, and associated prospect. The underlying rule configuration is not exposed in the API and must be manually reviewed if the destination supports equivalent buy-intent features.

Lead Liaison's API allows tracking custom activities (button clicks, link clicks, phone calls, orders, and virtually any custom event). We export all custom activity records with type, timestamp, and associated prospect ID. Mapping to the destination's activity or engagement object requires field-by-field alignment.

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 standard tagging fields in most destination CRMs.

User records include name, email, role, and ownership assignments. We export all active users and map them to Owner/User fields in the destination, noting any inactive or archived users for customer review before import.

Visitor tracking 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 prospect. The destination's ability to display this as a native timeline depends on its data model.

If the bundled OneFocus CRM is used for deal management, pipeline stage definitions and deal assignments export as Opportunity records. Stage names and custom pipeline fields require mapping to the destination's pipeline configuration.