Migrate from Mothernode to Mailchimp

Mothernode Contact records map to Mailchimp Members via the Members API endpoint (POST /3.0/lists/{list_id}/members). The contact email address is the required identifier and dedupe key. We use status=subscribed for contacts with active email addresses and status=unsubscribed for contacts flagged as opted out in Mothernode. First name and last name map to the FNAME and LNAME merge fields. Any Mothernode contact with a missing email is flagged as a skipped record and reported separately because Mailchimp requires an email address for member creation.

Mothernode Customers are distinct from Contacts in the Mothernode data model (confirmed in their FAQ distinguishing Leads from Opportunities, and the separate Customers and Contacts API endpoints). We deduplicate by email: if a Customer email matches an existing Contact email, we merge into a single Member record, preserving the most complete set of custom fields from both records. If no email match exists, the Customer becomes a standalone Member with a tag of Customer to distinguish from Contact-sourced Members.

Mothernode Leads share an API endpoint with Opportunities (https://api.mothernode.com/leads-and-opportunities) and are distinguished by a record type field in the response. We separate Leads from Opportunities at extraction time using this indicator. Leads migrate to Mailchimp Members with a tag of Lead applied. The lead status from Mothernode maps to a merge field (LEAD_STATUS) rather than a Mailchimp status because Mailchimp Member status is subscription state (subscribed, unsubscribed, pending, cleaned), not a sales pipeline stage.

Mothernode Opportunities have no Mailchimp equivalent because Mailchimp does not have deal, pipeline, or opportunity tracking. We extract Opportunity name, stage, value, and expected close date as merge fields on the linked Contact or Customer Member record (OPPORTUNITY_NAME, OPP_STAGE, OPP_VALUE, OPP_CLOSE_DATE). We also apply a tag of Opportunity to the Member for segmentation purposes. The pipeline structure itself cannot be preserved in Mailchimp.

Mothernode Notes and Events share an API endpoint. We extract note body and timestamp and map them to a Mailchimp Member merge field (NOTE_BODY, truncated to 255 characters per Mailchimp's merge field limit). For notes exceeding 255 characters, we preserve the full text in a FlitStack AI migration notes file and flag which Members have truncated notes so the customer can review in their source system post-migration. Notes are not native activity timeline records in Mailchimp the way they are in a CRM.

Mothernode Events (meetings, calls, tasks) map to Mailchimp Member tags with the event type and date encoded in the tag name (e.g., EVENT_Call_2024-03-15, EVENT_Meeting_2024-04-20). Mailchimp does not have an activity timeline; events serve as historical reference for segmentation but do not appear in a native activity feed. We do not create campaigns or automations from events; those require manual rebuild in Mailchimp Customer Journeys.

Mothernode Invoices are not migratable to Mailchimp. Mailchimp has no invoice object, no line-item management, and no payment tracking. If the customer needs to preserve invoice history alongside contact records, we extract Invoice data as a structured CSV export (Invoice ID, Customer, Line Items, Total, Status, Date) and include it in the migration deliverable as a reference file. The customer manages billing in their accounting system post-migration.

Mothernode User records (sales reps, owners) are referenced in Contact, Lead, and Opportunity records via owner_id. Mailchimp has no user or rep object; permissions are managed at the account level rather than on individual records. We map the owner_id to a Mailchimp merge field (OWNER_NAME, OWNER_EMAIL) on each Member so that the sales rep assignment is visible as a data field, but Mailchimp does not enforce rep-level access controls on Members.

Mothernode custom fields on Contacts and Customers are extracted from the API response payload (we probe for non-standard fields during the extraction phase since they are not explicitly documented). Each custom field maps to a Mailchimp merge field with a 255-character limit. Fields exceeding 255 characters are truncated with a flag. Field type mapping: text to TEXT, number to NUMBER, date to DATE, checkbox to TEXT (Y/N). Picklist and multi-select fields map to TEXT or, where appropriate, to Mailchimp Tags.

Mothernode Opportunity pipeline stages (e.g., Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) have no Mailchimp equivalent. We map stage names to a merge field OPP_STAGE on the linked Member record and optionally apply a tag per stage for segmentation. The customer uses these for reporting and campaign targeting rather than pipeline management.