Migrate from Lead Liaison to Microsoft Dynamics 365 Sales

Lead Liaison Prospects with no lifecycle stage or with early-stage values (e.g., visitor, raw lead) map to Microsoft Microsoft Dynamics 365 Sales Lead. Prospects with later stages (e.g., marketing qualified, sales accepted, customer) map to Dynamics 365 Contact attached to an Account. We define the split rule during scoping using Lead Liaison's lifecycle_stage property and any custom stage fields, preserve the original Lead Liaison stage value in a custom field ll_original_stage__c on both Lead and Contact, and run the split as the first transform before any records are inserted into Dynamics 365.

Lead Liaison Company records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The company domain name becomes the Account Website field and serves as the dedupe key during import. Account is created before any Contact import so that the CustomerId or parent Account reference is satisfied at Contact insert. Industry classification from Lead Liaison maps to the Account Industry picklist with manual mapping for any non-standard values.

If the customer uses Lead Liaison's bundled OneFocus CRM, Deal records map to Microsoft Dynamics 365 Sales Opportunity. Deal stage names map to Opportunity StageName via a configured stage mapping table. Deal amount, close date, and owner transfer directly. Custom OneFocus pipeline fields map to custom Opportunity fields that we provision in the destination org before migration. Closed-won and closed-lost reasons from OneFocus map to custom Opportunity fields for loss reason and win reason.

Lead Liaison Lists and segment membership map to Microsoft Dynamics 365 Sales Marketing Lists (associated to either a Campaign or a static list of Leads and Contacts). Static list membership is preserved as a list of target record IDs. Dynamic segments that rely on Lead Liaison's behavioral scoring cannot be replicated natively in Microsoft Dynamics 365 Sales and are documented as a scope gap requiring manual list recreation using Dynamics 365 Marketing or a Power Automate flow.

Lead Liaison Tags are a flat labeling system applied to Prospects and Companies. Tags stored as multi-checkbox custom properties on the Prospect map to a multi-select picklist field on the Dynamics 365 Lead or Contact. Tags used for behavioral classification that exceed picklist length limits are migrated as Notes on the record with a tag_reference label for retrieval.

Lead Liaison's user-defined custom activity types have no standardized schema and vary by customer. During scoping we request a complete list of active custom activity types, map each to either a Dynamics 365 Activity (Task, PhoneCall, or Appointment for time-stamped events) or a custom entity for non-standard event types, and flag any types that cannot be represented natively for customer decision before migration begins. Custom field schemas from Lead Liaison are provisioned in Dynamics 365 before any records are inserted.

Lead Liaison's visitor tracking produces chronological visit records with company identification, page URLs, and engagement depth. These records have no direct Microsoft Dynamics 365 Sales equivalent. We export the full visit timeline, flatten it to a chronological Note on the Prospect record (now Lead or Contact), or create a custom activity log entity in Dynamics 365 if the customer requires queryable visit history. The customer selects the representation strategy during scoping. Buy signal triggers (signal type and trigger date) map to a custom field on the Lead or Contact for sales-rep visibility.

Lead Liaison's numeric lead scoring values are stored as Prospect properties and export as integer fields. We map these to a custom field ll_lead_score__c on the Dynamics 365 Lead or Contact. The scoring model itself (point allocations and weighted criteria) is not exposed in the Lead Liaison API and cannot be migrated; we document the scoring model if the customer can provide it from the Lead Liaison UI for manual rebuild in Microsoft Dynamics 365 Sales or Power Automate.

Form definitions and submission records export from Lead Liaison with field responses, submission timestamps, and referring page URLs. We map form submissions to Notes on the associated Lead or Contact, or to a custom FormSubmission entity if the customer requires queryable submission history. Form field names that differ from standard CRM fields require custom field creation in Dynamics 365 before migration.

Email campaign metadata (name, status, associated lists, send date) migrates to Microsoft Dynamics 365 Sales Campaign. Campaign content, HTML templates, and inline assets are exported as separate files. Campaign performance metrics (open rates, click rates, bounce rates) are UI-visible in Lead Liaison but not reliably retrievable via the public API in bulk; these are flagged as scope gaps and the customer is advised to export UI reports before migration kickoff.

Lead Liaison User records map to Microsoft Dynamics 365 Sales User by email match. We export all active users and map them to OwnerId fields on migrated records. Users without a matching Dynamics 365 User record are held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or archived Lead Liaison users are noted in the migration report for customer review.