Migrate from TeamSystem CRM to Mailchimp

TeamSystem Contact records map to Mailchimp subscribers within the primary audience. We extract email, first name, last name, phone, address, and ownership assignment as standard fields. Custom contact fields migrate as Mailchimp merge tags (FNAME, LNAME, PHONE, ADDRESS are built-in; any non-standard field becomes a custom merge tag prefixed with TS_ to identify origin. Email validation runs against Mailchimp's format requirements before import to avoid rejection on the Mailchimp API.

TeamSystem Company records map to Mailchimp Tags (via the Tags API) or Audience Groups (via the Groups endpoint). We recommend Tags for most migrations because they are easier to manage and support dynamic segmentation in Mailchimp Customer Journeys. If the customer uses Companies for multi-location segmentation, Groups provide a structured alternative. The Company domain or industry field becomes a tag label for segmentation across campaigns.

TeamSystem Lead records with a status of Sales Qualified or Active are mapped to Mailchimp contacts and tagged Lead. Leads with stale status (inactive, disqualified, or no recent activity) are mapped to Mailchimp contacts tagged Inactive_Lead for suppression or re-engagement campaigns. Lead source and scoring fields from TeamSystem migrate as merge tags so that the customer's admin can build Mailchimp segments based on original lead origin.

Mailchimp has no Opportunity, Deal, or pipeline management model. TeamSystem Opportunity records do not migrate. We document the active opportunity count, stage distribution, and total pipeline value in the migration inventory so the customer's admin can decide whether to export to a spreadsheet or use a separate opportunity tracking tool post-migration. This is a fundamental architectural difference that should be addressed before migration scoping begins.

Mailchimp does not support deal pipelines, stage probabilities, or weighted pipeline forecasting. TeamSystem pipeline configurations including stage names, stage order, probability percentages, and pipeline-specific workflows are documented as a written inventory for the customer to evaluate against Mailchimp Customer Journeys and any third-party pipeline tools they may adopt. Pipeline data is excluded from the migration package.

Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes) rather than individual activity logs (calls, emails, meetings, tasks). TeamSystem Activity records do not map to any Mailchimp object. We extract the most recent activity date per contact and preserve it as a custom merge tag (LastActivityDate) so that Customer Journeys can filter on recency, but the full activity timeline is not migrated. Call logs and meeting records are documented for the customer's admin if a separate activity tracking tool is adopted.

Organization-specific custom fields on TeamSystem Contact, Company, or Lead objects migrate to Mailchimp merge tags. We query the TeamSystem field registry during discovery to identify all non-standard columns, then create matching merge tags in the Mailchimp audience before import. Field types map as follows: text fields to text merge tags, date fields to date merge tags, and picklist fields to radio or dropdown merge tags depending on Mailchimp's audience field configuration. Merge tag names are normalized to uppercase alphanumeric format per Mailchimp API requirements.

Mailchimp does not have a user-assignment or record-ownership model. TeamSystem user accounts and contact owner assignments have no equivalent in Mailchimp. We extract owner information by contact for audit purposes and include it as a custom merge tag (TS_Owner) in the import, but Mailchimp's collaboration model relies on audience-level access control rather than record-level ownership. User provisioning and role assignments from TeamSystem are documented separately for the customer's IT team.