Migrate from FunnelMaker to Mailchimp

FunnelMaker Contacts map directly to Mailchimp Audience members (subscribers). The FunnelMaker email address is the primary key used for Mailchimp subscriber lookup during import. All standard FunnelMaker contact fields (First Name, Last Name, Email, Phone, Address) map to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). User-defined contact fields from FunnelMaker create Mailchimp merge fields up to the 40-field per-Audience limit; fields exceeding this threshold are flagged during scoping for tag-based migration instead.

FunnelMaker Company records have no Mailchimp equivalent object. We flatten company-level data (company name, industry, website, employee count, custom fields) into merge fields on each Contact record. The company name becomes a standard merge field; industry and size data map to custom merge fields or tags. Where multiple Contacts share the same company in FunnelMaker, the company data is duplicated per contact in Mailchimp because Mailchimp does not support relational joins between records.

FunnelMaker Opportunities track deal stage, amount, probability, and owner assignment with no Mailchimp equivalent. We do not migrate Opportunity records. During scoping, we ask whether the customer wants a CSV export of Opportunity data (deal name, stage, amount, close date, owner) delivered as a standalone reference file for CRM reconstruction in a future platform, but this does not enter Mailchimp.

FunnelMaker Pipelines are customizable sales process stages with no Mailchimp analog. Mailchimp has no deal stage, probability, or weighted pipeline value. We document the pipeline stages as a reference handoff document if the customer plans to move to a CRM in the future, but no pipeline data enters Mailchimp.

FunnelMaker Tags and Groups segment contacts into lists and map directly to Mailchimp Tags. We extract every unique tag assignment per contact from FunnelMaker's tag export, then apply those tags to the corresponding Mailchimp subscriber during import. FunnelMaker Groups (hierarchical list segments) map to Mailchimp Tags with group path preserved (e.g., 'Industry:Healthcare' becomes a tag with the original hierarchy label). Mailchimp tags are applied after subscriber creation using batch operations.

FunnelMaker unlimited user-defined contact fields map to Mailchimp merge fields, subject to Mailchimp's 40-merge-field per-Audience limit. We inspect the FunnelMaker custom field schema during discovery, map field types (text, number, date, dropdown, checkbox) to Mailchimp merge field types (text, number, date, radio, checkbox), and flag any fields exceeding the merge field ceiling for tag-based migration. Mailchimp merge field names are normalized to uppercase alphanumeric strings (e.g., 'lifetime_value' becomes 'LTVALUE').

FunnelMaker drip campaigns (email sequences with time-based delays and contact segment triggers) are documented as automation sequences for manual rebuild in Mailchimp. We do not migrate drip campaign logic as automation code because FunnelMaker and Mailchimp use different trigger condition models. We deliver a written drip campaign inventory: campaign name, step count, trigger conditions, delay timing, and email content summary. The customer's marketing team rebuilds these in Mailchimp Customer Journeys or Classic Automation using the inventory as a blueprint.

FunnelMaker Workflows are automation rules that trigger CRM actions (task assignment, contact field updates, internal notifications) based on contact behavior. These have no direct Mailchimp equivalent because Mailchimp Customer Journeys are email-focused and cannot assign tasks or update CRM fields. We document the active workflow tree (trigger, conditions, each action step) as a written handoff for the customer's admin. CRM-action workflows (task creation, owner reassignment) must move to a separate task management tool post-migration.

FunnelMaker email engagement metadata (open date, click date, subject line, send date) migrates as contact activity records in Mailchimp. Email open and click tracking data is preserved where it exists in FunnelMaker's export. The email content itself does not migrate because Mailchimp manages email templates independently; we document which FunnelMaker email templates were associated with each drip campaign for reference during the Mailchimp rebuild.

FunnelMaker lead scores are calculated using customizable rules and stored as a numeric value on the contact record. Mailchimp has no native lead scoring capability. We export the lead score value as a numeric merge field on each contact during migration. The customer documents the scoring rules as a reference for rebuilding in a dedicated scoring tool (ActiveCampaign, SharpSpring, or a CRM with native scoring) if continued lead scoring is required.