Migrate from Lead Liaison to Pipedrive

Lead Liaison Prospect records map directly to Pipedrive Person records. All standard contact fields (name, email, phone, title, address) transfer via Pipedrive's Person API endpoint. Custom Prospect fields map to Pipedrive custom fields on Person, which we pre-create before migration using Lead Liaison's field type definitions as the source of truth. The Prospect lifecycle stage property becomes a custom picklist field on Person since Pipedrive does not have a native lifecycle concept.

Lead Liaison Company records map to Pipedrive Organization records. The company name, website, industry, org type, and address fields transfer directly. We resolve the Person-to-Organization link during migration by matching the primary company on each Prospect to the corresponding Organization record using company name or domain as the dedupe key.

If the customer uses Lead Liaison's bundled OneFocus CRM, deal records migrate to Pipedrive Deals. The deal name, value, stage, owner, and expected close date transfer directly. Stage names map to Pipedrive pipeline stages which we configure before migration. Deal custom fields map to Pipedrive Deal custom fields. Deals without an associated Company map to Deals with no linked Organization, which is valid in Pipedrive.

Lead Liaison's pipeline stage definitions (from OneFocus CRM or the Lifecycle deal management module) map to Pipedrive pipeline stages. We configure Pipedrive pipelines and stages in the destination account before migration, matching stage names and ordering. Stage probability weights transfer as Pipedrive stage probability values rounded to the nearest integer.

Lead Liaison tags are a flat labeling system applied to Prospects. We export all tag definitions and Prospect-to-tag assignments. Tags with fewer than 50 unique values migrate to Pipedrive Person Labels. Tags with high cardinality or freeform values migrate to a multi-select picklist custom field on Person. The customer selects the preferred strategy during scoping.

Lead Liaison static lists and dynamic segments export as list definitions with all Prospect memberships. Static lists migrate to Pipedrive Lists with Person memberships restored at migration time. Dynamic segments require rebuild as Pipedrive Filtered Views (using the filter API) since Pipedrive does not have a native dynamic segment engine. We document each dynamic segment's criteria and recommend the equivalent Pipedrive filter configuration.

Lead Liaison form definitions and all submission records transfer. Each form submission becomes a Note on the associated Person record, containing the form name, submission timestamp, field responses, and referring page URL. Custom form field values that have no direct Pipedrive equivalent become key-value text in the Note body. We flag any form fields that represent a distinct data type (e.g., file upload) for customer decision on how to represent in Pipedrive.

Email campaign metadata (campaign name, status, associated lists, creation date) transfers to Pipedrive Campaign records or as Notes on the associated Person records. The email HTML content and template assets extract from Lead Liaison's API and are delivered as a structured asset file to the customer's admin for re-upload to their email tool of choice. Email open rates, click rates, and conversion attribution are not accessible via Lead Liaison's public API in bulk and are documented as a scope gap.

Lead scoring numeric values stored on Prospects transfer as a numeric custom field on Pipedrive Person. The scoring model itself (point allocations, weighted criteria, tier thresholds) is not exposed in Lead Liaison's API and is documented separately as a text description. Pipedrive does not have native lead scoring; teams needing automated scoring use the Smart BPM add-on or a third-party scoring integration post-migration.

Automated buy signals in Lead Liaison (behavioral triggers attached to Prospects) export with signal type, trigger date, and associated Prospect. We map each signal type to a Pipedrive Activity or Note entry on the Person record. The underlying rule configuration is not API-accessible, so only the outcome (signal occurred on date X for Prospect Y) migrates. We provide a signal type catalog so the customer can configure Pipedrive Activities or custom fields to represent active signal types going forward.

Lead Liaison's custom activity tracking lets teams define arbitrary event types (button clicks, link clicks, phone calls, orders, and any custom event). These user-defined activity schemas have no standardized field names across customers. Before migration, we request a full list of active custom activity types, map each to Pipedrive's Activity type field or to a custom field, and flag any types that cannot be represented natively. Activity timestamps and Person associations migrate directly.

Lead Liaison visitor tracking produces a chronological log of page views, company identification, and engagement depth per Prospect. We export visit records and flatten them into a Note on the Person record in Pipedrive, preserving the chronological order and timestamps. Visit records are too granular to map to individual Pipedrive Activity entries; a consolidated engagement summary note preserves the behavioral context without bloating the Pipedrive timeline. The first-source-channel attribution (original UTM source) migrates as a custom field on Person.

Lead Liaison user records (name, email, role, ownership assignments) export and map to Pipedrive Users. Owner assignments on Prospect, Company, and Deal records resolve by email match to Pipedrive User accounts. Any Lead Liaison user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Lead Liaison automation rules are not fully API-exportable; the rule builder including conditional branches, time-delay configurations, and A/B split logic is proprietary. We export automation metadata (trigger types, step counts, associated assets, and membership counts) as a structured summary document. Pipedrive workflow automation must be rebuilt manually in Pipedrive's workflow editor post-migration. We do not migrate automation logic as code and scope this as a separate consulting task if the customer requires assisted rebuild.