Migrate from Mazrica Sales (formerly Senses) to Mailchimp

Mazrica Sales Contact records map to Mailchimp Members using email address as the primary key. First name and last name map to FNAME and LNAME merge fields. We preserve lifecycle stage values as Tags on the Member record (e.g., Tag: lifecycle_stage_lead, Tag: lifecycle_stage_customer). Owner assignment from Mazrica Sales does not transfer because Mailchimp has no owner concept; we document the owner-to-tag mapping for segmentation purposes if needed.

Mazrica Sales Company names map to the COMPANY merge field on the Mailchimp Member record. If a Contact is associated with multiple Companies in Mazrica Sales, we use the primary (most recently updated) Company as the COMPANY merge field value and document secondary affiliations as Tags (e.g., Tag: associated_company_acme_corp). Company financial info, press releases, and external data from Mazrica Sales have no Mailchimp equivalent and are not migrated.

Mazrica Sales Opportunities and the card-based Kanban pipeline have no direct Mailchimp equivalent. Mailchimp is an email marketing platform, not a CRM or sales management tool. We extract the full Opportunity list (stage, amount, close date, owner, company) into a CSV export and deliver it as a written handoff inventory. Customers who require opportunity tracking in Mailchimp must use a third-party integration (e.g., Zapier connecting Mailchimp to a CRM) or document opportunities externally.

Mazrica Sales Activities (calls, meetings, emails logged within the CRM, tasks, notes) cannot migrate to Mailchimp. Mailchimp tracks email engagement metrics (opens, clicks, unsubscribes) tied to Campaigns, but it does not maintain a general activity timeline for individual contacts. We extract Activity summaries into a CSV log for the customer's records. Calls, meetings, and internal notes must be archived or moved to a separate tool.

Mazrica Sales Lifecycle Stage values (lead, marketing_qualified, sales_qualified, customer, evangelist, and any custom stages) map to Mailchimp Tags on the Member record. We create a tag taxonomy that preserves the original stage name and maps it to a Mailchimp-friendly format (lowercase, underscores replaced by hyphens). Tags are used for segmentation in Mailchimp Automations and Campaign targeting. Lifecycle stage values are also preserved as merge fields if the customer wants a permanent record.

Mazrica Sales Custom Objects with user-defined schema have no Mailchimp equivalent. Mailchimp's data model supports Members, Lists, Campaigns, Automations, Segments, Tags, and merge fields only. We extract all Custom Object records into structured CSV files with their field definitions and deliver a schema inventory. The customer rebuilds the data in a dedicated CRM or database tool if needed.

Mazrica Sales User and Owner records (with roles and team assignments) do not map to Mailchimp because Mailchimp has no concept of sales owners or CRM users. We map Owner email addresses to a tag on their assigned Contacts for audit purposes (e.g., Tag: owner_tanaka_sample_com) but do not create User objects. Owner provisioning and role assignments must be handled separately in Mailchimp's Team management if multiple users require access.

File attachments on Mazrica Sales Contacts, Companies, or Opportunities are not exposed via the public API and cannot be exported programmatically. We advise customers to download any critical attachments manually before migration. Mailchimp does not support file attachments on Member records; documents shared with contacts must be distributed via Mailchimp-hosted files or external links.