Migrate from Lead Liaison to monday CRM

Lead Liaison Prospect records map directly to Monday.com CRM Contacts. Standard contact fields (name, email, phone, title, address) transfer cleanly. Custom prospect properties map to Monday.com custom fields on the Contact record. Any prospect scoring value stored as a numeric property transfers to a number column in Monday.com CRM. We preserve the original Lead Liaison prospect ID in a custom field (ll_prospect_id__c) for reconciliation and audit trail. Duplicate detection uses email as the primary dedupe key during import.

Lead Liaison Company profiles map to Monday.com Work Items on a dedicated Accounts board. The org-type classification, industry data, and website URL transfer as text or dropdown columns. We recommend creating the Accounts board before contact import so that the board relationship can be established during data load. Company records serve as the parent entity for matching Contacts by domain where a Company-C prospect relationship exists in Lead Liaison.

Form definitions transfer as a schema summary document listing field names and types. Form submission records (field responses, submission timestamps, referring pages) transfer as Contact records with custom fields capturing each form response. If multiple forms exist, we append a form_name column to identify the source. Form submission count and last submission date can be stored as numeric and date columns on the Contact record. Monday.com does not have a native form builder equivalent to Lead Liaison's form module; replacement forms require separate configuration.

Lead Liaison's flat tagging system applies directly to Monday.com CRM's built-in Tags field on Contacts. We export all distinct tag values and prospect-to-tag assignments, then map each assignment to the Contact record during import. Tags used for segmentation in Lead Liaison campaigns become labels that the customer can use for filtering views in Monday.com CRM boards.

Lead Liaison buy signals (behavioral triggers attached to prospects including signal type and trigger date) transfer as custom fields on the Contact record. We create a text column for signal_type and a date column for signal_date. The underlying rule configuration that generated the buy signal is not exposed via API and does not migrate; we document the signal types in scope for the customer to manually reconfigure if needed. If a prospect has multiple signals, we store the most recent in the primary signal fields and append older signals to a notes column.

Lead Liaison visitor tracking produces chronological visit records (page views, company identification, engagement depth) attached to prospects. We flatten the visit timeline into a text-formatted engagement log attached to the Contact record as a long-text column. Each entry includes the page URL, visit timestamp, and engagement depth indicator. This approach preserves the data in a readable format without requiring a separate board structure. Full granular visit records exceed Monday.com's column-based data model and are not practical to represent as separate board items.

Lead scoring values stored as prospect properties in Lead Liaison export as numeric values mapped to a number column on the Monday.com CRM Contact record. The scoring model itself (point allocations and weighted criteria) is not exposed via API and does not migrate; we document the scoring model in the automation inventory for the customer to rebuild using Monday.com's native formulas or third-party scoring tools if Enterprise-tier lead scoring is adopted.

Lead Liaison custom activity types (button clicks, phone calls, orders, and user-defined events) require schema alignment before migration. We request a list of all active custom activity types during discovery, then create corresponding custom fields on the Contact record or a separate Activities board depending on volume and relationship requirements. Each custom activity type maps to a typed column (date, number, text, or status) on the destination structure. Activity records transfer with type, timestamp, and associated prospect reference. Any custom activity types that cannot be represented natively in Monday.com CRM are flagged for customer decision before migration begins.

Lead Liaison user records (name, email, role, ownership assignments) map to Monday.com CRM Users. We extract all active users and map them by email match. Owner assignments on Prospects, Companies, and Deals transfer to the Owner column in Monday.com CRM. Inactive or archived Lead Liaison users are flagged in the migration report for the customer to handle (reactivate, reassign, or leave unlinked) before cutover.

If the Lead Liaison OneFocus CRM bundle is used for deal management, pipeline stage definitions and deal assignments transfer to Monday.com CRM as items on a Deals board. Stage names map to Monday.com Status column values, and deal properties (amount, close date, probability) map to corresponding number and date columns. We recommend setting up the Deals board structure before migration so that stage mapping is consistent across all imported records.