Migrate from Friday CRM to Mailchimp

Friday CRM Contact records map to Mailchimp Audience Members. The email address serves as the primary key and dedupe field. Standard contact fields (first name, last name, phone, address) map to Mailchimp merge fields FNAME, LNAME, PHONE, and the address merge field. We extract and normalize email addresses, flag hard bounces and unsubscribes as suppression records, and split contacts into subscribed and non-subscribed segments for separate Mailchimp import to preserve status. Contacts without email addresses cannot migrate as Members and are flagged in the reconciliation report.

Friday CRM Company records map to Mailchimp Company records. We extract company name, website, industry, and address fields. In Mailchimp, Company records are linked to Members via CRM merge fields (MAILINGCOMPANY maps to Company Name, WEBSITE maps to Company Website). We resolve the Company-to-Member link using the email domain as a heuristic match when a Contact has a linked Company. If the destination Mailchimp account does not have Companies enabled, we map company name to a text merge field instead and flag the configuration difference.

Friday CRM Deals have no structural equivalent in Mailchimp. Mailchimp does not have an Opportunity or pipeline object, and its automation model (Customer Journeys) is email-triggered rather than deal-stage-triggered. We cannot migrate Deals as live CRM records. We generate a reference export of all open Deals including name, value, stage, associated Contact email, and close date as a CSV handoff document. The customer's admin uses this to re-enter deal data manually or to document pipeline context in a spreadsheet post-migration. Closed-won Deals may be entered as Campaign Member notes or tagged Member records if the customer wants a proxy record in Mailchimp.

Friday CRM pipeline stages (kanban columns) have no structural equivalent in Mailchimp. We create Mailchimp Segments that correspond to the original pipeline stage labels. Contacts and Deals linked to a given stage are tagged or segmented in Mailchimp using a segment rule matching the Deal stage field. This preserves the marketing-side pipeline context for segmented campaigns (for example, a campaign targeting contacts in the 'Demo Scheduled' stage), but it does not replicate a live CRM pipeline.

Friday CRM tags on Contacts and Deals migrate directly to Mailchimp Tags. We parse comma-separated tag values from the Friday export, deduplicate across all records, and import tags as Mailchimp Tags associated with each Member by email match. The free Mailchimp plan supports up to 20 tags per Audience; accounts on Essentials and above support up to 60 tags. We check the tag count against the customer's Mailchimp plan tier and flag any overflow requiring plan upgrade or tag consolidation before migration.

Friday CRM notes and activity history (linked to Contacts and Companies) migrate as Mailchimp Notes on Member profiles. We extract note text, author, and timestamp from the Friday export, resolve the associated Contact by email, and create Mailchimp Notes. Mailchimp Notes are stored as flat text on a Member profile without a chronological timeline view, which means the activity history loses its deal and company context in the Mailchimp interface. We flag this limitation and recommend the customer export a full notes history from Friday CRM before cutover as a reference archive.

Friday CRM custom fields on Contacts and Companies map to Mailchimp Merge Fields. We audit Friday's nine field types and perform type mapping: text, multi-line text, URL, and radio select map to Mailchimp TEXT merge fields; single checkbox maps to Y/N text; number maps to NUMBER; date maps to DATE; multiple checkboxes require 1:N split into separate boolean text merge fields. Dropdown becomes a Mailchimp dropdown if the plan supports it, or TEXT on lower tiers. Mailchimp requires merge fields to be pre-created in the Audience Settings before import; we design the merge field schema and submit it for customer approval before running any data import.

Friday CRM attachments are not included in the platform's documented CSV export or public API. We flag this gap during discovery and recommend the customer manually download any relevant file attachments from the Friday CRM interface before the migration cutover date. We do not migrate attachment metadata or file references as part of the standard scope because there is no reliable export path from Friday CRM.

Friday CRM's native Mailchimp integration stores OAuth credentials and connection state within the platform that are not exported as part of the migration data. The bidirectional sync configuration, contact list mapping, and any custom field mapping rules set up in Friday's Mailchimp integration do not transfer to the destination Mailchimp account. After migration, the customer must re-establish the Mailchimp integration from within Mailchimp's connected apps or by creating new API credentials. We provide step-by-step reconnection guidance as part of the post-migration handoff document.