Migrate from TeamWave to Mailchimp

TeamWave Contacts map directly to Mailchimp Audience Members. The email address serves as the unique identifier. We extract name, email, phone, address, and lifecycle stage from the TeamWave contact export and map these to Mailchimp's EMAIL, FNAME, LNAME, PHONE, and ADDRESS merge fields plus a LIFECYCLESTAGE custom merge field. Status (active, unsubscribed, bounced) is resolved from TeamWave's contact state and written to Mailchimp's SUBSCRIPTION_STATUS field during import.

Mailchimp has no native Company or Account object. TeamWave Company records with the company_id foreign key on Contact are resolved during import and written to a COMPANY merge field on each member record. If the customer maintains multiple distinct company segments, we create separate Mailchimp Audiences per segment rather than using tags, since Mailchimp's per-audience analytics provide better segmentation clarity.

Mailchimp has no deal or pipeline object. TeamWave Deals are not migrated as structured records. However, if the customer has fewer than 50 distinct deal records and wants to preserve deal stage context for marketing segmentation, we map deal stage labels as Mailchimp Tags on the linked contact records. This is an optional configuration discussed during scoping; by default, deals are excluded.

TeamWave custom fields on Contacts migrate to Mailchimp merge fields. Mailchimp enforces a 255-character limit on text merge fields. Any TeamWave custom field exceeding this length is flagged during scoping, and we truncate with a manifest entry showing original value and truncation point. Long-text area fields from TeamWave cannot be fully preserved and are noted in the field mapping document.

TeamWave lifecycle stage (Lead, Customer, Evangelist, etc.) is a contact property without a native Mailchimp equivalent. We migrate it as a LIFECYCLESTAGE merge field for direct value access and optionally as a Mailchimp Tag for segmentation. During scoping, the customer chooses between merge field (one field, accessible in email content) or tag (filterable in segmentation, visible in audience analytics).

TeamWave Owners (sales reps) are referenced on Contacts and Deals. Mailchimp does not have an owner assignment model. We map owners to Tags on the contact record (e.g., Owner: Sarah Chen) for visibility in Mailchimp's audience view, or we document the assignment in the migration handoff notes for the customer's admin to action in a CRM-native system if needed.

TeamWave Projects have no Mailchimp equivalent. We export the project list as a CSV inventory and include it in the handoff documentation. Customers who need project context alongside contacts should maintain a separate project management tool; we do not map Projects to Mailchimp structures.

TeamWave Tasks and Calendar Events have no Mailchimp equivalent. Task assignments, due dates, and status fields cannot be represented in Mailchimp's contact model. We export a task inventory CSV as part of the handoff documentation for the customer's admin to migrate to a task management system separately.

TeamWave file attachments linked to Contacts cannot be exported in bulk. We snapshot attachment metadata (filename, file size, linked contact email, TeamWave record ID) and deliver a re-upload manifest. The customer's admin re-uploads attachments to the linked Mailchimp contacts manually or via Mailchimp's file hosting for content blocks post-migration.