Migrate from Lead Liaison to Nutshell

Lead Liaison Prospects map directly to Nutshell People. The API exposes all standard contact fields (name, email, phone, address) plus custom properties. We map each Lead Liaison custom property to a Nutshell custom field (text, number, date, or dropdown depending on type) that we create in the destination Nutshell account before import. The Prospect's lifecycle stage property migrates as a dropdown custom field on Person. Email opt-out status maps to the standard Nutshell unsubscribe field.

Lead Liaison Company records map to Nutshell Account. The company domain_name becomes the Account's website field and is used as the dedupe key during import. Industry, org-type classification, and number of employees map to Nutshell custom fields that we create pre-import. Accounts are imported before People so that the Person-to-Account relationship is satisfied at the moment of Person insert.

Lead Liaison's deal management (available via the bundled OneFocus CRM or API-accessible deal records) maps to Nutshell Leads and Opportunities. If Lead Liaison deal records exist, we split them by stage: early-stage unqualified deals map to Nutshell Lead; qualified deals with an associated Account map to Nutshell Opportunity. Pipeline stage names map to Nutshell pipeline stage values that we configure pre-migration. The customer defines the stage mapping during scoping based on their existing Lead Liaison pipeline configuration.

Lead Liaison list membership (Prospect-to-List assignments) migrates as Nutshell Tags applied to the corresponding Person records. We export all list definitions and the full set of member assignments, then apply tags during Person import. If the customer used dynamic lists (automatically updated based on criteria), we document the criteria and recommend Nutshell's reporting filters or a manual rebuild of equivalent dynamic segments.

Lead Liaison Tags are a flat labeling system applied to Prospects and other objects. Tags migrate as Nutshell Tags on the corresponding Person records. Tag names are preserved verbatim. If the same tag is applied across multiple object types in Lead Liaison, we apply it to the corresponding Nutshell object type for each record.

Lead Liaison's custom activity types (button clicks, phone calls, orders, or any user-defined event) have no standard Nutshell equivalent. We extract all active custom activity type definitions during scoping, then map each type to either a Nutshell Activity (for behavioral events like calls or meetings) or a custom field on Person (for transactional events like orders or form completions). The customer selects the mapping strategy during scoping. Any custom activity types that cannot be represented natively are flagged as scope gaps for customer decision before import.

Lead Liaison email campaign metadata (name, status, associated lists, send date) transfers to Nutshell Campaign records. Email content and HTML templates require manual re-creation in Nutshell's email editor because Nutshell uses a different template format. We extract the full HTML content and inline assets and provide them to the customer for use during the manual rebuild. Campaign performance metrics (open rates, click rates) are not reliably available via the Lead Liaison API and are flagged as scope gaps; we recommend exporting UI reports before migration kickoff.

ProspectVision visitor identification data (page views, company identification events, engagement depth per prospect) has no native equivalent in Nutshell. We export the visit history as a flattened chronological log and attach it as a multi-line Note or Activity record to the corresponding Person. The note preserves page URL, company identified, and engagement depth indicator per visit. This is a best-effort representation; the full ProspectVision behavioral timeline is not queryable as structured data in Nutshell.

Lead Liaison's GoExhibit! event lead capture records (badge scans, trade-show submissions, post-event follow-up status) migrate as Nutshell Activity records attached to the corresponding Person. Form field responses that do not map to standard Person fields become custom fields on Person that we create pre-import. Event name and date are preserved as metadata fields. If the customer used badge scanning with custom fields, we flag the full schema during scoping for explicit mapping.

Lead Liaison User records (name, email, role, ownership assignments) map to Nutshell Users. We resolve by email match. Any Lead Liaison Owner referenced on a Prospect or Company record without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or archived Lead Liaison users are noted for customer review and mapped to inactive Nutshell Users if required for historical ownership continuity.