Migrate from Lead Liaison to Mailchimp

Lead Liaison Prospects map to Mailchimp Contacts. The email address is the primary dedupe key. Standard contact fields (first name, last name, phone, address) map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). Custom Prospect properties migrate as Mailchimp custom merge fields; the customer's admin creates these in Mailchimp's Audience settings before import. Prospects without email addresses are excluded from the primary import and listed separately for manual review.

Lead Liaison Company records do not have a native Mailchimp equivalent because Mailchimp does not maintain a separate Account object. Company name maps to a COMPANY merge field in Mailchimp. If the customer also uses a CRM integration with Mailchimp (e.g., Salesforce, HubSpot), Company records can be maintained there and linked via the CRM integration rather than within Mailchimp itself. Org-type classification and industry data from Lead Liaison become custom merge fields or Notes on the Contact.

Lead Liaison Lists define audience membership for campaigns and automations. Each distinct List becomes a separate Mailchimp Audience. We export list definitions and all Prospect-to-List assignments, then recreate each list as a static Mailchimp audience or as tagged segments within a unified audience depending on the customer's preference. Multi-list structures with overlapping contacts require deduplication at the email address level before import.

Lead Liaison's dynamic segments (based on prospect properties, engagement behavior, or buy signals) do not have a direct Mailchimp equivalent. We export the segment criteria as a structured definition document. Static segments recreate as tagged groups in Mailchimp. Dynamic segments require manual rebuild in Mailchimp using its segment builder with the original criteria documented as a handoff asset.

Lead Liaison tags apply as flat labels to Prospects. We export all tag definitions and prospect-to-tag assignments and recreate them as Mailchimp Tags on the corresponding Contacts. Tags transfer cleanly and do not require schema transformation; the tag name and contact association map directly.

Lead Liaison campaign metadata (name, status, associated lists, send date) transfers as a campaign record in Mailchimp. The HTML email content and inline assets extract from Lead Liaison and are uploaded to Mailchimp as saved templates or applied directly to campaigns. Campaign performance metrics (open rates, click rates, conversion attribution) are UI-visible but not reliably available via the Lead Liaison API in bulk, so these do not transfer. We flag this gap in the migration report and recommend exporting UI reports before kickoff.

Lead Liaison automation logic (triggers, conditions, A/B splits, time delays) is stored in a proprietary format not exposed via the public API. We export what is available: automation names, associated campaigns, trigger types, and step counts. The full rule builder configuration including conditional branches and delay logic cannot be extracted programmatically. We deliver a structured automation summary document for the customer to use as a rebuild reference in Mailchimp's Customer Journey builder. This is a manual rebuild task scoped separately from the data migration.

Lead Liaison form definitions and all historical submission records (field responses, submission timestamps, referring pages) export via the API. We transfer submission data as Contact records with custom field values reflecting the form responses. Form schemas (field structure, conditional logic, styling) require manual rebuild in Mailchimp's signup form builder. Custom form field definitions from Lead Liaison map to Mailchimp merge fields created in advance of the data import.

Lead scoring values export as numeric properties on Prospects. Mailchimp does not have a native lead scoring model. We transfer the score as a numeric merge field (LEADSCORE) on the Contact record. If the score value range is categorical (e.g., Hot, Warm, Cold), we map it to a Mailchimp Tag applied at import time. The scoring model itself (point allocations, weighted criteria) is not exposed in the Lead Liaison API and cannot migrate.

Lead Liaison buy signals (behavioral triggers such as page visit depth, content downloads, or demo requests) export as signal type and trigger date per Prospect. Mailchimp has no native buy signal object. We convert each signal type to a descriptive Tag on the Contact (e.g., 'signal: high_intent_page', 'signal: demo_requested') with the trigger date preserved in the Contact's last activity or a custom date merge field. The underlying rule configuration that generated the signal is not exportable and is documented for manual rebuild if needed.

Lead Liaison's API supports arbitrary custom activity types (button clicks, phone calls, orders, or any user-defined event). Each distinct custom activity type maps to a corresponding Mailchimp Tag or a custom merge field depending on the activity data type. We request a complete list of active custom activity types during discovery, map each to a Mailchimp-native representation, and flag any activity types that cannot be represented (e.g., multi-event sequences) for the customer to decide whether to flatten or drop.

Lead Liaison User records (name, email, role, ownership) export for mapping context but do not create Mailchimp accounts. The customer provisions Mailchimp user seats independently. We map Lead Liaison ownership assignments (which user owns which Prospects) to Mailchimp Notes or Tags on the Contact record to preserve the original assignment context.