Migrate from Teamwork CRM to Mailchimp

Teamwork CRM Contacts migrate to Mailchimp Subscribers within a designated Audience. We use email address as the primary dedupe key. Standard fields (first name, last name, phone, address) map to Mailchimp merge fields FNAME, LNAME, PHONE, and the address merge fields. Contact status in Teamwork (active, archived) maps to Mailchimp Subscriber Status (subscribed, unsubscribed, archived). If a Contact has no email address, we flag it for the customer to review because Mailchimp requires an email address for every subscriber.

Teamwork CRM Companies do not map to a native Mailchimp object because Mailchimp has no account-level record. We handle this in one of two ways depending on customer preference: (1) add the Company name as a CUSTOMCOMPANY merge field on each Contact record so company attribution is preserved in subscriber metadata, or (2) create an Audience Tag per Company and apply it to all Contacts linked to that Company. Multi-contact companies receive the same tag on every related subscriber. The customer selects the strategy during scoping.

Teamwork CRM Tags migrate directly to Mailchimp Tags on the subscriber record. Tags are a 1:1 name transfer — the tag label in Teamwork becomes the tag label in Mailchimp. Mailchimp Tags are applied programmatically via the Tags API endpoint after subscriber creation. We preserve tag names exactly to avoid breaking any segmentation logic the customer intends to rebuild in Mailchimp Customer Journeys.

Teamwork CRM custom fields of type short text map to Mailchimp text merge fields, integer number fields map to Mailchimp number merge fields, and dropdown fields map to Mailchimp dropdown merge fields. Multi-select is not supported in Teamwork CRM natively so we do not encounter this case, but if any dropdown contains semicolon-separated values, we treat it as text and note the limitation. We create the merge field definitions in the Mailchimp Audience before any subscriber data loads.

Teamwork CRM Owners represent the sales team members who own records. Mailchimp has no concept of record ownership or user assignment on subscriber records. We do not migrate Owners. If the customer needs to preserve owner information (for example, which sales rep owns which customer relationship), we map Owner to a OWNER merge field on the Contact so it appears in the subscriber profile but does not confer any CRM-style assignment or routing.

Teamwork CRM Leads represent early-stage unqualified prospects in a separate pipeline from Opportunities. Mailchimp has no Lead object and no concept of lead qualification stages. We do not migrate Leads as a record type. We migrate the Contact data for any Lead records (email, name, phone) as Mailchimp Subscribers with a LEAD_SOURCE merge field carrying the original lead status from Teamwork CRM. The customer rebuilds lead tracking in Mailchimp via tagged segments and Customer Journey entry conditions if needed.

Teamwork CRM Opportunities carry deal value, stage, probability, pipeline association, and close date. Mailchimp has no Opportunity, Deal, or Pipeline objects. We do not migrate Opportunities. If the customer needs to preserve deal data, we export the Opportunity records as a CSV at migration time and deliver it alongside the subscriber import. The customer uses this for reference or loads it into a separate deal-tracking tool. We flag this gap explicitly during scoping so the decision is made before migration begins.

Teamwork CRM Activities (calls, meetings, tasks, notes) represent the engagement timeline linked to Contacts or Opportunities. Mailchimp tracks email engagement metrics (opens, clicks, unsubscribes, bounces) but has no general activity log or timeline. We do not migrate Activity records. The engagement history lives in Teamwork CRM and is available as a CSV export for manual reference. Email engagement data from Mailchimp accumulates post-migration only.

Teamwork CRM Pipelines represent named sales processes with configurable stages and probabilities. Mailchimp has no pipeline or stage concept. We do not migrate pipeline configurations. We deliver a written inventory of every Teamwork CRM Pipeline and its stage definitions as a reference document so the customer's admin can decide whether to rebuild stage logic as Mailchimp segments or customer journey conditions, or to maintain deal tracking in a separate CRM.