Migrate from Leadfox to Mailchimp

Leadfox Contact records map directly to Mailchimp Members within a single Audience. We use email address as the dedupe key. Standard fields (first name, last name, email, phone) map to Mailchimp's corresponding merge fields. Leadfox computed properties like lifecycle status migrate as custom merge fields with TEXT type. Contacts are imported in a single pass to maintain one Member record per email address, avoiding Mailchimp's per-audience counting model.

Leadfox unlimited custom fields per Contact map to Mailchimp Merge Fields on the destination Audience. We enforce Mailchimp's 255-character limit on TEXT-type merge fields at transform time: any Leadfox field with a value exceeding 255 characters is truncated and flagged in the migration report with the record ID and field name so the customer's admin can review. DATE, NUMBER, and ADDRESS field types map to their Mailchimp equivalents. Dropdown fields in Leadfox map to MAILCHIMP_TYPE.dropdown_merge with permitted values set at Audience creation time.

Leadfox Tags applied at the Contact level map directly to Mailchimp Tags on each Member. We export tag assignments as a separate CSV keyed on contact email and apply them in a post-import batch using Mailchimp's Tags API endpoint. Tag names are preserved verbatim unless they exceed Mailchimp's 30-character tag name limit, in which case they are truncated and flagged for admin review.

Leadfox dynamic Segments are evaluated at migration time to produce a snapshot list of Member email addresses. This snapshot migrates as a Mailchimp Static List. Dynamic Segment definitions that rely on ongoing behavioral criteria (email opens, page visits, form submissions) cannot be reproduced as live Mailchimp Segments without rebuilding the filter logic in Mailchimp's Segment builder. We deliver a segment definition map pairing each Leadfox Segment name with its filter criteria so the customer's admin can recreate the dynamic logic in Mailchimp.

Leadfox Content Studio templates with dynamic personalization tokens export as HTML with a token-to-merge-field map. We reconstruct each template in Mailchimp's template editor using the exported HTML, then reconnect the merge tags to the corresponding Mailchimp merge fields using the token map. Images hosted on Leadfox's CDN are downloaded and re-uploaded to Mailchimp's built-in content storage during template reconstruction. Complex templates with conditional content blocks may require manual reassembly.

Leadfox automation sequences — triggers, time delays, conditional branches, goal steps — are stored in a proprietary format. We do not migrate automation logic as executable code. We deliver a written automation inventory that documents each Leadfox sequence as a step-by-step action map: trigger type, conditions, delays, and actions in the order they execute. The customer's team or a Mailchimp partner uses this guide to rebuild sequences in Mailchimp's Customer Journeys. Complex multi-branch workflows with goal tracking almost always require manual reconstruction.

Leadfox CAN-SPAM compliance data — unsubscribe status and per-contact suppression flags — exports as a suppress file. We apply this file to the destination Mailchimp Audience before any re-engagement campaigns send. Unsubscribed contacts are set to unsubscribed status in Mailchimp; bounced contacts are added to the Global Suppression List. This preserves deliverability standing during and after cutover.

Leadfox behavioral lead scores (numeric values computed from page visits, email opens, form submissions) migrate as a static numeric merge field on each Member record. The scoring rule logic — which behaviors contribute, what thresholds apply — is not exported. Teams relying on lead scoring use the exported historical score values as a baseline to design new scoring criteria in Mailchimp's integration ecosystem (e.g., through a third-party scoring tool linked via Zapier).