Migrate from Monica CRM to Mailchimp

Monica Contacts map to Mailchimp Audience Members via email address as the primary dedupe key. Each Contact's first name, last name, and avatar URL migrate to the standard Mailchimp FNAME, LNAME, and avatar merge fields. We normalize Monica's gender field (not required in v5) to a Mailchimp text or radio merge field if the customer chooses to include it. Any Monica Contact without an email address is held in a reconciliation queue for the customer to supply before import because Mailchimp requires an email address for Member records.

Monica contact details (email, phone, WhatsApp, Twitter, LinkedIn, address, birthday) map to Mailchimp merge fields. Mailchimp supports text, number, date, address, phone, and website merge field types. We map Monica's phone to a phone-type merge field, addresses to Mailchimp's address merge field format, and social profile URLs to text merge fields. Birthday from Monica's birthdate field maps to a date-type merge field. All Monica contact avenues with a non-email channel type that has no native Mailchimp equivalent are mapped to labeled text merge fields (e.g., WHATSAPP, TWITTER) for segmentation use.

Monica relationship types (spouse, child, parent, friend, colleague, significant other, pet, and custom types) are flattened into Mailchimp Tags or Groups. During scoping, the customer chooses between a Tags strategy (all relationship types as flat tags on the Member, e.g., 'relationship:spouse') or a Groups strategy (one Group per relationship category with Group names as the relationship type). Tags are simpler to migrate; Groups allow Mailchimp's native group-based segmentation for campaigns. We preserve both the relationship type and the related contact's name in the tag or group label so that relationship context is searchable in Mailchimp.

Monica Tags (arbitrary labels applied to contacts, separate from relationship types) map directly to Mailchimp Tags. Tags export from Monica as a string array per contact and import as individual Mailchimp Tags on the corresponding Member record. We do not merge Monica Tags with Monica relationship types unless the customer requests a combined tagging strategy during scoping.

Monica Journal entries are timestamped activity logs with an optional title and rich text body. We convert each Journal entry to a Mailchimp Member Note attached to the corresponding Audience Member. The Journal creation timestamp becomes the note creation date in Mailchimp. The note body preserves the original rich text content. Mailchimp does not display notes in a chronological activity feed — they appear as a static note list on the Member record — so we document this limitation and recommend the customer use Journal content to pre-populate an initial campaign segment or welcome sequence rather than treating it as a timeline.

Monica Reminders (birthday reminders, event reminders, and ad-hoc follow-ups tied to contacts) do not have a native Mailchimp equivalent. Birthday reminders migrate to a date-type merge field on the Member if not already mapped from contact details. Event reminders and ad-hoc follow-ups are converted to Mailchimp Member Notes with a formatted label (e.g., 'Reminder: Follow up re [subject]') and the due date in the note body. We flag that Mailchimp has no native task or calendar integration, so reminder-based workflows require rebuild as Mailchimp automation triggers post-migration.

Monica Gift records (given, wanted, offered, idea) with estimated values and dates convert to labeled Mailchimp Member Notes. Each gift note includes the gift description, value, status, and date. Mailchimp has no native gift object, so the note format preserves the record for reference but does not support filtering or reporting by gift value. The customer may choose to exclude gift records entirely if the data is not relevant to Mailchimp-based marketing workflows.

Monica Debt records (money owed to or by a contact with amount and currency) convert to labeled Mailchimp Member Notes with debt direction, amount, and currency. Mailchimp has no native debt or financial obligation object, so debt records are informational only after migration. We recommend the customer flag whether debt records should migrate or be excluded based on whether that context is relevant to their Mailchimp audience segmentation and campaign strategy.