Migrate from Taguchi to Mailchimp

Taguchi Subscribers map to Mailchimp Audience Members. The subscriber email address is the dedupe key. Subscriber status (active, bounced, unsubscribed) determines whether the record lands in the active audience or the suppression list. Read-only metadata fields (campaign source, import source, cluster) migrate as Merge Tags or Notes on the Mailchimp Member record.

Taguchi's per-subscriber key-value custom fields map to Mailchimp Merge Tags. We snapshot all active and soft-deleted field definitions during discovery because Taguchi retains field keys on subscriber profiles even after UI deletion. Mailchimp Merge Tags are created as Text, Number, Date, Phone, or Address type depending on the field's stored value format. Fields that cannot be re-created with the same key on Taguchi (due to soft-delete behavior) are pre-created in Mailchimp before any Member import to preserve data integrity.

Taguchi list memberships map to either Mailchimp Tags or Groups depending on the customer's preference. Tags are simpler to migrate and replicate append-only behavior in one direction; Groups preserve subscriber preference data and are visible in the Mailchimp Groups UI. We document all active list memberships during discovery and allow the customer to choose the mapping strategy before migration. Taguchi list membership is immutable post-creation, so the migration records the full association history.

Taguchi Organizations link to Subscribers as an owning relationship. Mailchimp does not have a native Organization object, so we map this as a Company field on the Member record (if the Mailchimp account uses the Companies feature on Standard and Premium tiers) or as a Merge Tag (org_name__c) on all Members belonging to that Organization. Company-based segmentation in Mailchimp requires a Standard or Premium tier account.

Taguchi Clusters identify the subscriber segment a contact is most strongly associated with. We map clusters to a dedicated Merge Tag (cluster_name__c) and optionally as a Tag or Group depending on whether the customer wants cluster membership visible in Mailchimp's segmentation builder. Clusters used for automation routing are documented for the customer to evaluate against Mailchimp Customer Journeys.

Taguchi activity history (opens, clicks, custom events) is written as Engagement Notes on the Mailchimp Member record. Each activity type is formatted as a timestamped note entry (e.g., 'Taguchi Activity: Opened campaign "Summer Sale" on 2025-06-15'). Open and click counts per campaign are aggregated into a custom Merge Tag (engagement_count__c) for segmentation. Note that Mailchimp's native reporting covers post-migration campaign engagement; historical Taguchi open/click data does not flow into Mailchimp's reporting dashboard.

Taguchi custom events (behaviors tracked beyond opens and clicks) map to Mailchimp customer实践活动 fields if the destination account is on Standard or Premium tier. Customer实践活动 fields enable event-triggered Customer Journeys in Mailchimp. We create the customer实践活动 field definition in Mailchimp during migration and write the full historical event log as a custom Merge Tag (custom_events__c) in JSON format for audiences without customer实践活动 access.

Taguchi Broadcast metadata (name, send date, recipient count) is preserved as a Note on the Member record for each recipient. The full broadcast content does not migrate as a Mailchimp campaign because Mailchimp campaigns are not reusable templates for re-import. Broadcast send history serves as engagement context for the customer's sales or success team to reference post-migration.

Taguchi SMS send history migrates as an SMS activity Note on the Member record. Phone number fields must be present and validated on the Taguchi Subscriber for the record to migrate. Mailchimp SMS requires a Standard or Premium account and a dedicated phone number provisioned through Mailchimp. If the destination Mailchimp account is on the Free or Essentials tier without SMS access, SMS activity is preserved as Notes only and the customer must enable SMS separately post-migration.

Taguchi automation workflows and journey logic are rule-driven configurations that do not map cleanly to Mailchimp Customer Journeys. Mailchimp Customer Journeys support trigger types including tag added, date-based, and e-commerce events, but the trigger logic and branching conditions differ from Taguchi's behavioral conditions. We do not migrate workflows as code. We deliver a written inventory of every active Taguchi automation with its trigger conditions, audience criteria, and action sequence, plus a recommended Customer Journey equivalent in Mailchimp.