Migrate from Touchpoint MX to Mailchimp

Touchpoint MX Contacts map to Mailchimp Subscribers within a single consolidated Audience. Email address is the dedupe key. Standard fields (first name, last name, email, phone) map to Mailchimp merge fields FNAME, LNAME, EMAIL, PHONE. Any Contact-level custom fields from Touchpoint MX map to Mailchimp merge fields with type mapping: text fields to TEXT merge fields, date fields to DATE merge fields, numeric values to NUMBER merge fields. Opt-in status and unsubscribes preserve from Touchpoint MX's suppression list during import.

Touchpoint MX Channel assignments (Email active, SMS active, Voice active) map to Mailchimp Tags applied per subscriber (e.g., tag: Email_OptIn, tag: SMS_OptIn) or Group categories. The customer chooses between Tags (for simple boolean flags) or Groups (for subscriber self-selection) during scoping. We flag any Touchpoint MX channel preferences that cannot be represented in Mailchimp's permission model.

Touchpoint MX Message Templates (subject lines, body content, personalization tokens) export as HTML or plain text content. We extract the template content and map it to Mailchimp Email Templates. Note that Mailchimp's template builder uses a specific block structure that may require reformatting of complex HTML from Touchpoint MX. We deliver a template content inventory so the customer's team can rebuild in Mailchimp's builder if visual formatting needs adjustment.

Touchpoint MX Satisfaction Scores (NPS-style or numeric ratings) attach to Contacts with timestamps. We map Score values to a custom Mailchimp merge field (e.g., SATISFACTIONSCORE as NUMBER type) or to Tags if the score history requires per-interaction storage. If Touchpoint MX stores multiple scores per Contact over time, we create a JSON-encoded history in a TEXT merge field or flag the limitation if the customer prefers a simpler current-score approach.

Touchpoint MX Feedback Records contain structured customer responses, comments, and collection dates tied to Contacts. Mailchimp does not have a native feedback or survey object. We map Feedback text to Mailchimp Notes on the Subscriber record (limited to 5,000 characters per note) or to a custom merge field if the feedback is short-form. Multiple feedback entries per Contact are consolidated chronologically within the note body.

Touchpoint MX Journey Maps define custom stage taxonomies and customer lifecycle progression. Mailchimp Customer Journeys are trigger-based email automation flows, not a data object that stores historical stage assignments. We do not migrate Journey Map stage data as code. We produce a stage mapping table listing each Touchpoint MX stage label, its definition, and the recommended Mailchimp Journey trigger equivalent. The customer's team rebuilds the Journey logic manually post-migration.

Touchpoint MX custom fields on Contacts map to Mailchimp merge fields. Mailchimp enforces a 30-character merge field tag name limit (uppercase alphanumeric and underscore only). We truncate and sanitize Touchpoint MX field names to comply. Mailchimp has a 40-merge-field-per-Audience limit on lower plans; we flag if the customer's custom field count exceeds this during scoping.

Touchpoint MX User accounts (team members with access) map by email to Mailchimp Admin or Author accounts. Mailchimp's user permission model is less granular than Touchpoint MX's Manager/Attendee/Everyone visibility tiers. We map users to the nearest Mailchimp role (Admin, Author, Viewer) and flag any Touchpoint MX role assignments that cannot be represented in Mailchimp's three-tier model.

Touchpoint MX loyalty programs (points-based or tier-based reward structures, voucher issuance, spend-based triggers) have no Mailchimp equivalent. Mailchimp does not include native loyalty or rewards functionality; teams requiring this must evaluate third-party loyalty apps from Mailchimp's marketplace or a separate loyalty platform. We export a list of active loyalty program rules and point balances as a reference CSV for the customer's team to evaluate replacement options.