Migrate from Tango CRM to Mailchimp

Tango CRM Contact records map to Mailchimp Members within a designated Audience. The Member email address is the primary key and dedupe field. Standard fields (first name, last name, phone, address) map to Mailchimp's FNAME, LNAME, PHONE, and ADDRESS merge fields. We resolve email consent status during transform: contacts with an explicit email opt-in flag migrate as subscribed; contacts without a confirmed opt-in flag are prepared for re-permissioning (either a double opt-in welcome sequence or a re-confirmation campaign) before being marked subscribed in Mailchimp.

Tango CRM Company records do not have a direct Mailchimp equivalent because Mailchimp has no Company or Account object. We flatten Company fields into custom merge fields attached to each Member: Company Name becomes COMPANY (a Mailchimp standard merge field), and Industry, Employee Count, Annual Revenue, and Website map to custom merge fields that we create in Mailchimp before import. Each Contact retains a reference to its parent Company during transformation so that the Company data lands on the correct Member record.

Tags applied to Contacts in Tango CRM migrate as Mailchimp Member Tags. Multi-value tag fields on a single Contact are split into individual Tag values during the transformation step. Tags preserve relationship labels (e.g. 'high-value', 'referral-partner', 'enterprise-prospect') that would otherwise be lost in a flat audience model. We deliver a tag taxonomy worksheet so the customer can consolidate redundant labels before or after import.

Custom properties on Tango CRM Contacts (dropdown, date, number, text, checkbox) map to Mailchimp Merge Fields of corresponding type: text properties to text merge fields, date properties to date merge fields, dropdowns to dropdown or radio merge fields. We pre-create all merge fields in the Mailchimp Audience before any Member import so that field names are available during the load. Dropdown merge fields require value mapping when source and destination picklist values differ.

Tango CRM Deal records (deal name, value, stage, owner, expected close date) have no equivalent object in Mailchimp. Mailchimp does not track pipeline stages, deal values, or deal ownership. We flag Deal volume and value totals in a post-migration summary so the customer's team can decide whether to record this data outside Mailchimp (e.g. a spreadsheet, a connected reporting tool, or a secondary CRM for sales tracking). Deal migration is out of scope and excluded from the data migration plan to prevent silent data loss.

Tango CRM Activities (logged emails, calls, meetings, tasks) do not migrate to Mailchimp because Mailchimp does not store per-contact engagement history as standalone activity records. Mailchimp tracks opens and clicks only in the context of campaigns it has sent. We do not migrate the activity timeline to prevent expectation mismatch. If the customer needs contact-level engagement history preserved, a hybrid CRM strategy (Mailchimp for email, a lightweight CRM for activity tracking) is recommended post-migration.

Tango CRM Pipeline definitions (stage names, stage order, probability percentages) do not have a Mailchimp equivalent. Mailchimp does not support deal pipeline visualization or probability-weighted forecasting. We document the pipeline stage names and deal counts in a post-migration inventory for the customer to assess whether a sales-focused CRM is needed alongside Mailchimp for pipeline management.

File attachments stored within Tango CRM records cannot be extracted without a confirmed API endpoint or download mechanism. We do not migrate attachments to prevent silent data loss. We deliver a written list of attachment references grouped by Contact and Company so the customer's team can manually re-upload or retrieve these files post-migration.