Migrate from Force24 to Mailchimp

Force24 Contacts map directly to Mailchimp Audience contacts. All standard fields (email, first name, last name, phone) migrate as Merge Fields using Mailchimp's standard naming (FNAME, LNAME, EMAIL, PHONE). Lifecycle Stage from Force24 maps to a custom Merge Field (LIFECYCLESTAGE) as plain text. We use the Mailchimp Bulk Import API with email as the unique identifier for deduplication. Any Force24 contacts with status of Unsubscribed or Bounced are exported separately as a suppression list and imported before the main audience to preserve deliverability.

Force24 Company records are lightweight — typically a name and URL — and Mailchimp does not have a native Company or Account object. We map the Company name to a Merge Field (COMPANY) and the website to a Merge Field (WEBSITE) on each contact. If the customer requires a CRM-style account model, we document the company-contact relationship and recommend a Mailchimp integration with Salesforce or HubSpot post-migration to maintain that layer.

Force24 Lead records are stored as Contacts with a lifecycle stage property. They migrate as Mailchimp contacts with the same Merge Fields as standard contacts, carrying the original lifecycle stage value in the LIFECYCLESTAGE Merge Field. There is no separate Lead object in Mailchimp; all prospects live in the same Audience.

Force24 contact tags migrate directly to Mailchimp Tags. Tags are preserved in full — all existing tag names and their association with individual contacts carry across via the Mailchimp Tags API. Mailchimp's tag model supports multiple tags per contact, matching Force24's behaviour.

Force24 Smart Lists define filter conditions against contact properties and behaviours. We export the contact IDs included in each Smart List at migration time and create static Mailchimp Segments with those same contacts pre-selected. The dynamic filter logic (property conditions, behavioural triggers, AND/OR combinations) cannot be transferred and is documented as a written specification for the customer to rebuild using Mailchimp's Segment builder. Active real-time segments will become static lists and require manual refresh in Mailchimp.

Force24's lead scoring engine assigns numeric scores to contacts based on engagement and property rules. We export the current score value stored on each contact as a Merge Field (LEADSCORE) of type number. The scoring rules themselves are Force24 configuration and do not migrate; we document the rule logic so the customer can replicate it using Mailchimp's automation triggers or an external scoring tool post-migration.

Force24 Custom Objects are linked-data tables (such as Bookings or Event Registrations) associated with contacts. This feature requires account manager activation on the source account. If enabled, we export each Custom Object definition and its records, then map the fields to Mailchimp Merge Fields on the associated contact. Highly structured Custom Object data with multiple fields per record is flattened into individual Merge Fields (BOOKING_DATE, BOOKING_STATUS, BOOKING_AMOUNT) or written as a plain-text Note on the contact record if Merge Field count becomes a constraint. This requires confirmation of Custom Object activation during discovery.

Force24 Automated Journeys define multi-step, multi-channel workflows with conditional branching, wait steps, and behavioural triggers. Journey logic is not stored in a portable format and cannot be transferred programmatically. We audit every active journey, document the trigger (entry condition), all steps and branches, timing logic, and exit conditions, and deliver a written journey specification so the customer's team can rebuild each flow in Mailchimp Customer Journey Builder. This is a rebuild task, not a data migration.

Force24 tracks email opens, clicks, and engagement events against contacts. Mailchimp does not have a native engagement history log per contact beyond campaign-level reporting. We export the engagement event count and most recent engagement date as Merge Fields (LAST_EMAIL_OPEN, LAST_EMAIL_CLICK, TOTAL_OPENS, TOTAL_CLICKS) on each contact record. The granular per-campaign engagement timeline is documented as a report export from Force24 for the customer's records.

Force24 stores SMS and WhatsApp message history against contacts. Mailchimp supports SMS on Standard and Premium plans but does not have a native WhatsApp channel (Mailchimp offers SMS through Twilio on paid plans). We export SMS message records as plain-text Notes on the contact with timestamps. WhatsApp records migrate as Notes only; the customer sets up a WhatsApp Business integration separately if WhatsApp messaging continues to be required.

Force24 email templates and dynamic content blocks export as HTML. Since they reference Force24-specific merge fields, we recommend reviewing and adapting template HTML before importing into Mailchimp's template builder. We export the HTML asset alongside the contact data and flag any Force24-specific variable syntax that requires replacement with Mailchimp merge tag equivalents (such as *|FNAME|* replacing Force24 merge field formats).

Force24 forms capture lead data and feed it into contacts and journeys. We export form field configurations and submission counts. Mailchimp's form builder replaces Force24 forms. We document the form field mapping (which Force24 fields map to which Mailchimp Merge Fields) as part of the migration specification so the customer's team can configure equivalent Mailchimp signup forms post-migration.