Migrate from Membrain to Mailchimp

Membrain Contact records map to Mailchimp Subscribers in a target Audience. Email address is the dedupe key. First name, last name, phone, and title map to standard Mailchimp merge fields (FNAME, LNAME, PHONE, JOBTITLE). Custom field values from Membrain (stored as CustomField{GUID}) are resolved via the GUID-to-label lookup table and written to Mailchimp merge fields of the matching type (text, number, date, dropdown). Contacts without an email address are flagged in a separate reconciliation report because Mailchimp requires an email address for every subscriber.

Membrain Companies do not map to a single Mailchimp object because Mailchimp has no account hierarchy. Company name and industry are written as merge fields on the Contact record or applied as tags (Company: {name}, Industry: {industry}). If multiple Contacts share the same Company, each subscriber carries the same company tag. The customer decides during scoping whether company data lives in merge fields or as tags based on reporting needs.

Membrain Prospects map to Mailchimp Subscribers in a target Audience. The Prospect lifecycle stage (New, Contacted, Qualified, etc.) translates to a Mailchimp tag (Prospect: New, Prospect: Qualified) that enables segmentation. Note: Mailchimp does not have a separate Prospects object; Prospects become marketing subscribers and are segmented by tag. If the customer needs a separate non-marketing record for in-progress prospects, Mailchimp is not the right tool for that use case.

Membrain Sales Projects (deal/opportunity records with stages, values, and expected close dates) have no Mailchimp equivalent. Mailchimp does not track pipeline stages, deal values, or expected close dates. We export Sales Project data (name, stage, value, expected close date, owner) as a CSV reference file for the customer's records and note that the sales process must be managed outside Mailchimp or rebuilt using a third-party pipeline tool integrated with Mailchimp.

Account Growth Projects track expansion and account planning at the Company level and have no Mailchimp equivalent. We export these as a CSV reference file alongside Sales Projects. The customer rebuilds account growth tracking in a dedicated CRM or project management tool.

Membrain Appointment records (meetings) have no Mailchimp equivalent. Mailchimp tracks campaign-level opens and clicks but not per-contact meeting history. We export Appointments as a CSV reference file ordered by date and linked to the Contact record by email address. The customer reconciles this against their calendar tool post-migration.

Membrain Call records (disposition, duration, notes) have no Mailchimp equivalent. We export Calls as a CSV reference file with contact email, call date, duration, and disposition. The customer reconciles against their phone system or sales engagement tool.

Membrain logged email engagements do not migrate to individual Mailchimp subscriber records. Mailchimp's Email activity model is campaign-centric (sent, delivered, opened, clicked) rather than per-contact timeline. We flag the email engagement gap in scoping and recommend the customer evaluate whether a sales engagement tool (Lavavi, Outreach, Salesloft) integrated with Mailchimp is needed to restore per-contact email tracking.

Membrain Full users (those who can own records, import/export, and trigger automations) are identified during scoping and their email addresses are matched against Mailchimp account users. Lite users (read-only access, cannot own records) are excluded from Mailchimp user mapping because Mailchimp does not have a Lite equivalent role. The customer provisions Mailchimp user seats based on their team size.

Membrain custom fields (stored as CustomField{GUID}) require resolution via the GUID-to-label lookup table before mapping. Text, number, date, and dropdown fields translate to Mailchimp merge field types. Multi-select and checkbox fields become Mailchimp tags (one tag per selected value). Phone number fields use the PHONE merge field. Date fields use DATE merge fields. Fields that exceed Mailchimp's 30-character merge field name limit are truncated per Mailchimp naming rules.