Migrate from m-savvy to Mailchimp

m-savvy Contacts map directly to Mailchimp Members within a designated Audience. We map First Name, Last Name, Email, Phone, Address fields, and lifecycle stage to Mailchimp tags for segmentation. Opt-in status in m-savvy maps to Member Status (subscribed, unsubscribed, pending). Owner assignment from m-savvy maps to a tag or a Mailchimp Merge Field (OWNER) so campaigns can be attributed to the original owner. Email addresses are used as the dedupe key on import to prevent duplicate Members.

m-savvy Account records have no direct Mailchimp equivalent. We map Account Name to a free-text Merge Field (COMPANY) and Account ID to a hidden tag for cross-reference. If the customer wants Account-level segmentation in Mailchimp, we create Groups for each Account and assign Members to their corresponding Group via the Mailchimp API. Industry, size, and billing address fields map to additional Merge Fields or remain as tags if no equivalent exists in the Audience schema.

m-savvy Deals (pipeline opportunities with stage, amount, close date, probability) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not have an Opportunity or pipeline object. We export Deal records as a CSV during migration discovery and flag them for the customer admin to evaluate in a supplemental CRM, a spreadsheet, or a business intelligence tool. We do not create placeholder records in Mailchimp.

m-savvy Leads are distinct from Contacts in the source data model. We merge Lead records into the same Mailchimp Audience as Contacts, mapping lead source and lead status to tags (LEAD_SOURCE, LEAD_STATUS) and preserving any lead score as a numeric Merge Field. Duplicate email addresses between Leads and Contacts are resolved using the email dedupe key: if a Lead email matches an existing Member, we update the Member record with Lead tags rather than creating a second Member.

m-savvy Activity records (emails, calls, meetings, tasks with timestamps, dispositions, and notes) have no equivalent in Mailchimp. Mailchimp tracks aggregate open and click data per Member but does not maintain a per-interaction activity log. We export Activity records as a timestamped CSV keyed by Contact ID so the customer can import historical activity into a separate analytics tool if needed. The import does not create entries in Mailchimp.

m-savvy Custom Objects require live-org API discovery because m-savvy does not publish a public schema reference. We enumerate Custom Object types and their field definitions during the discovery phase and share the schema map with the customer. Since Mailchimp has no custom object support, we evaluate each custom object field individually: fields that map to Member properties (text, date, number) are promoted to Merge Fields or tags; fields that require relational context (lookups, roll-ups) cannot be represented in Mailchimp and are excluded with a count flagged in the handoff inventory.

m-savvy Attachments are stored separately from record data via file API endpoints. Mailchimp does not support file attachments on Member records. We download all attachments during the source export pass and store them in our staging environment. We deliver the attachment package as a named folder tree keyed by Contact ID and Account ID. The customer admin can host files separately or evaluate a document management integration.

m-savvy Pipeline definitions and stage names are read from the schema during discovery. Mailchimp does not have a pipeline concept. We document the pipeline structure (stage names, order, probability percentages) in the migration handoff inventory so the customer can decide whether to implement pipeline tracking in a supplemental CRM or project management tool post-migration.