Migrate from Wetroo CRM to Mailchimp

Wetroo Contact records map 1:1 to Mailchimp Audience contacts. Email address is the primary dedupe key. Contact name (first_name, last_name) maps to Mailchimp merge tags FNAME and LNAME. Phone number maps to PHONE merge tag. Lifecycle stage and contact status from Wetroo map to Mailchimp Tags or a custom contact status field that the customer defines during scoping. Custom fields on Contact (text, number, date) map to Mailchimp merge tags created in the Audience before import.

Wetroo Lead and Contact are distinct objects in Wetroo; in Mailchimp they collapse into the same Audience member record. We de-duplicate by email address: if a Lead and a Contact share the same email, they merge into a single Audience contact with tags applied from both source records (e.g., Lead_Source tag carrying the original acquisition channel). Lead source attribution (Facebook, Google, manual) migrates as a Mailchimp Tag or merge tag for segmentation.

Wetroo Company records have no direct Mailchimp equivalent because Mailchimp does not have an Account object. We map Company name to COMPANY merge tag, and Company address fields (street, city, state, postal_code, country) to Mailchimp's built-in ADDRESS merge field group. If the customer uses Companies for segmentation, we recommend tagging contacts by Company name rather than importing it as a standalone object.

Wetroo Deals (pipeline, stage, value, close date, owner) have no Mailchimp equivalent. Mailchimp does not manage sales pipelines or deal records. We export Deals as a standalone CSV with all standard fields (deal_name, stage, value, expected_close_date, owner_email, company_name) and flag this in the migration scope. The customer uses this CSV in a separate sales tool or imports it to a CRM if one is in place. This is a data export, not a Mailchimp object import.

Wetroo Activity records (call logs via OBD endpoint, manual notes) cannot become individual records in Mailchimp because Mailchimp has no activity-timeline object. We extract call logs and notes as text and append them as a Contact Note in Mailchimp, or apply a tag (e.g., Call_Logged or Note_Attached) with the timestamp and a short summary. Call duration and disposition migrate as a tag value or as a custom merge tag if the customer prefers structured data over notes.

Wetroo custom fields on Leads and Contacts map to Mailchimp merge tags. We create each merge tag in the Mailchimp Audience before import, matching the field type: text fields become text merge tags, date fields become date merge tags, picklist or multi-select fields become either Mailchimp Groups (if the customer prefers segmentation by category) or comma-separated text merge tags. Required fields in Mailchimp merge tag settings are left unchecked to prevent import blocking.

Wetroo drip sequences and sales cadences are automation-layer objects with no exposed schema and no API export endpoint. They do not migrate. We deliver a written automation inventory document during migration scoping: for each active sequence, we document the trigger, step count, step type (email, SMS, delay, condition), and content summary so the customer's admin can rebuild them in Mailchimp Customer Journeys. This document is part of the standard migration scope.

WhatsApp message history is stored in Wetroo's messaging layer and accessible via a separate conversation API. Mailchimp is an email-only platform with no WhatsApp, SMS, or chat object. We extract message content and timestamps as a text export (CSV or JSON) for the customer's records, but this data cannot be imported into Mailchimp. The customer reviews this export and rebuilds any WhatsApp-sequence follow-ups as Mailchimp email automations using the contact list we migrate.