Migrate from Barantum CRM to Mailchimp

Barantum Contact records map directly to Mailchimp Audience members. We extract first_name, last_name, email, phone, and address fields and map them to Mailchimp's standard merge fields. Barantum contact status (active/inactive) maps to Mailchimp member status (subscribed/archived). Custom fields on Barantum contacts (stored as Barantum custom field API names) are enumerated during discovery and created as Mailchimp merge fields of matching data type before migration. Any Barantum contact with no email address is flagged in a reconciliation report because Mailchimp requires an email address for audience membership.

Barantum Company records do not map to a native Mailchimp object because Mailchimp has no Accounts or Organizations record type. We map the company name to a COMPANY merge field on each contact's profile and store the company's address components (city, state, postal code) in Mailchimp's address merge fields. For companies with multiple contacts, the company name appears on each contact's profile. If the customer needs company-level grouping in Mailchimp, we recommend using Tags or building a separate company roster in Google Sheets linked by company name.

Barantum Deals have no Mailchimp equivalent. Mailchimp does not support deal records, pipeline stages, deal values, or expected close dates. We export all Barantum Deal records to a structured CSV file (deal_name, stage, value, owner, expected_close_date, associated_contact_name, associated_company_name) and deliver it alongside the migration. We document rebuild options: import to a Google Sheet with pipeline tracker template, or use Mailchimp's Tags plus a linked external CRM for deal tracking. The customer's admin decides the rebuild path during the handoff walkthrough.

Barantum pipeline boards and stages (e.g., Prospect, Qualified, Proposal, Won, Lost) cannot be recreated in Mailchimp's native structure. We export pipeline metadata as part of the deal CSV and tag each contact in Mailchimp with a tag matching their associated deal stage for segmentation purposes. If the customer wants to track deal stage in Mailchimp for filtering, we configure Tags like DealStage_Prospect or DealStage_Won on each contact's profile during migration.

Barantum Lead records (unqualified prospects from forms, imports, or chatbot interactions) migrate to Mailchimp Audience members with status set based on Barantum's lead status field. We map Barantum lead source to a MAILSOURCE merge field in Mailchimp. Any lead with no valid email address is excluded from the primary contact migration and listed in a separate ineligible-contacts report with the reason for exclusion (missing email, invalid format, hard bounce risk).

Barantum Tickets (customer service records) have no Mailchimp equivalent. We export full ticket records including status, assigned agent, issue description, and conversation history as a structured CSV. Ticket status can be mapped to Mailchimp Tags (Ticket_Open, Ticket_Resolved) on the associated contact's profile if the customer wants to use tagging for customer service segmentation in Mailchimp automations.

Barantum Meeting records (title, scheduled time, attendees, outcome notes) cannot map to native Mailchimp calendar or event objects. We export meetings as a CSV with contact name, meeting title, date, and outcome. For each meeting attendee contact, we append meeting title and date to a MEETING_HISTORY merge field in Mailchimp. If the customer needs native calendar integration, we recommend a separate scheduling tool (Calendly, Calendly's Mailchimp integration) as a replacement for Barantum's meeting scheduling.

Barantum stores WhatsApp chat threads as linked conversation records on contact profiles. Mailchimp has no native messaging or chat history object. We export all WhatsApp chat threads as text files organized by contact name and timestamp, and deliver them as a downloadable archive separate from the Mailchimp audience. These files are not importable as linked activities in Mailchimp; they serve as an audit record for customer service teams. If the customer needs chat history accessible within Mailchimp, a workaround is storing chat summary notes in a MEETING_NOTES merge field on the contact profile.