Migrate from Breakcold to Mailchimp

Breakcold Contact email, first name, last name, phone, and address map directly to Mailchimp Email Address, FNAME, LNAME, PHONE, and ADDRESS merge fields. The Breakcold contact lifecycle stage maps to a Mailchimp tag (e.g., lifecycle_stage: sales_qualified_lead) rather than a native field since Mailchimp has no lifecycle concept. We extract all custom property values and translate them to Mailchimp merge fields if the property type is compatible (text, number, date, boolean). Multi-select values are serialized as semicolon-delimited strings in merge fields.

Breakcold Lead records merge into the same Mailchimp Audience as Contacts. The Lead source attribution (e.g., LinkedIn, Website form, Referral) migrates as a tag (source: linkedin) or merge field depending on the customer's segmentation strategy. Leads without email addresses are flagged in the migration report since Mailchimp requires a valid email address for audience membership.

Breakcold Company records do not have a direct Mailchimp equivalent because Mailchimp has no Company or Account object. The Company name and domain migrate as merge fields on the Audience Member (COMPANY_NAME, COMPANY_DOMAIN) so that Mailchimp segmentation can still filter by company. We resolve the Company reference by email domain match at migration time and apply it to the associated Contact and Lead records.

Breakcold tags on Contacts and Leads migrate as Mailchimp tags with identical names. Tags are the primary segmentation mechanism in Mailchimp equivalent to Breakcold's tagging model. We preserve the full tag list and apply it during the audience import phase. Tag-based automation triggers in Mailchimp (e.g., 'when tag added') can replace some Breakcold workflow logic.

Breakcold LinkedIn profile URLs, connection dates, Sales Navigator data, and social engagement metrics stored as Contact properties have no Mailchimp equivalent. Mailchimp is an email platform with no social data model. We flag which contacts carry LinkedIn data during scoping and document it in the migration report so the customer can decide whether to export this data separately to a spreadsheet or social selling tool like Apollo or Sales Navigator.

Breakcold multichannel activity records (emails, LinkedIn messages, WhatsApp messages, Telegram messages, calls, meetings, tasks, notes) do not migrate to Mailchimp. Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes) but has no concept of a pre-campaign activity history. We export the activity timeline as a CSV attachment to each contact record so the customer's admin can reference it manually, but it does not load into Mailchimp as native records.

Breakcold Pipelines and Deals (Opportunities) have no Mailchimp equivalent. Mailchimp has no deal stage, probability, or sales pipeline concept. We document the customer's current pipeline structure and stage names in the migration report. If the customer needs deal tracking post-migration, we recommend pairing Mailchimp with a dedicated CRM (Pipedrive, HubSpot, or Salesforce) rather than trying to approximate pipeline management within Mailchimp's audience structure.

Breakcold custom Objects map to Mailchimp through one of two strategies: if the custom Object relates directly to Contacts (e.g., a Subscription custom object linked to a Contact), the relevant fields migrate as merge fields on the Audience Member. If the custom Object is independent (e.g., a Product or Project object), we evaluate whether to create a separate Mailchimp Audience with its own merge field schema. We discuss the preferred strategy during scoping since Mailchimp charges per audience per subscriber.

Breakcold workflow rules and automation triggers are not accessible via API and do not migrate. We document the automation logic during discovery including trigger conditions, branch logic, and CRM update actions so the customer's admin can rebuild equivalent Customer Journey automations in Mailchimp. Mailchimp Customer Journeys support trigger-based branching, time delays, and action steps (send email, add tag, update merge field) but not CRM-native record updates like Breakcold workflows can perform.

Breakcold workspace users and role assignments (Admin, Member) do not map to Mailchimp because Mailchimp does not have a CRM user model. Mailchimp user accounts control platform access and permissions but do not attach to contacts as record owners. We document the user list and their Breakcold roles for the customer's IT admin to map manually against Mailchimp user accounts.