Migrate from Leadfwd to Mailchimp

Leadfwd Contacts map 1:1 to Mailchimp Audience Members using email address as the primary dedupe key. We extract Contacts from Salesforce (the only available export path due to Leadfwd's absence of a public API), deduplicate by Email, and load into the target Mailchimp Audience via the Mailchimp Marketing API. Standard Contact fields (FirstName, LastName, Email, Phone, Title) map to Mailchimp merge fields FNAME, LNAME, EMAIL, PHONE, COMPANY. Any custom Contact fields require field-by-field mapping with attention to Mailchimp's 255-character merge field limit.

Leadfwd Leads map to Mailchimp Audience Members. Leadfwd treats Leads and Contacts as equivalent enrollment targets; we merge Lead records into the same Audience as Contacts, using Email as the dedupe key so that a Lead and Contact sharing an email address collapses to a single Member record. The original Leadfwd Lead record type (Lead_Status) is preserved as a custom merge field for segmentation purposes.

Leadfwd Company records map to Mailchimp Companies if the destination Mailchimp account has the Companies feature enabled (available on Standard and Premium plans). We use Company Name as the match key and link Members to their parent Company via the companies relationship in Mailchimp's data model. If Mailchimp Companies is not enabled or not available on the destination plan, we map Company Name to a COMPANY merge field on the Member instead.

Active Sequence enrollment records (Contact in Sequence X at step Y on date Z) are exported as structured data but cannot resume in Mailchimp because Customer Journeys are trigger-based automations, not step-resumable cadences. We tag each affected Member in Mailchimp with a tag identifying the original Sequence name and last completed step, then flag every enrollment record as 'requires re-enrollment' in the handoff inventory. The customer's team uses the tag to identify contacts who need replaying through a new Customer Journey.

Leadfwd engagement events (opens, clicks, replies, bounces, meeting completions) are exported as timestamped records with channel metadata. We map them to Mailchimp as Member Tags with timestamps (e.g., tag 'EmailOpened_2025-11-15') and optionally as internal notes on the Member record. Deep engagement details such as which exact email variant was opened are not portable because Mailchimp's activity model does not store per-variant interaction history at the same granularity.

Icebreakers are personalized conversation openers generated per Contact using LinkedIn profile data. We export the generated text and source LinkedIn URL as an internal note on the Mailchimp Member record or as a custom merge field. The AI personalization variants are Leadfwd-specific and do not carry semantic value in Mailchimp's text-based email editor; the customer decides whether to carry the text forward as a note for their team to reference manually.

Leadfwd Tasks linked to Sequence steps (manual sales actions, follow-up reminders) are exported with status, due date, and assignee. We map them to Mailchimp Notes on the corresponding Member record with the task title and due date preserved as note content. Automated Task logic does not transfer; Mailchimp does not have a native task management layer for sales follow-ups.

Custom fields on Leadfwd Contacts and Companies sync through the Salesforce API pipeline and are extracted from Salesforce. We map them to Mailchimp merge fields field-by-field. Any field exceeding 255 characters is truncated to 255 characters during import; we flag these fields during scoping so the customer can decide whether to split the data across multiple fields or accept truncation. Fields referencing Leadfwd-specific picklist values (e.g., Sequence enrollment status) require manual value remapping to Mailchimp-compatible options.