Migrate from Taguchi to Nutshell

Taguchi Subscribers map to Nutshell People records. The subscriber email becomes the Person email field; subscriber status (active/bounced/unsubscribed) maps to Nutshell's HasOptedOutOfEmail and a custom Person field taguchi_status__c for full status audit. Bounced Subscribers are quarantined or written as suppressed contacts depending on the customer's suppression strategy. We resolve organization links against the Organization mapping before inserting People records.

Taguchi key-value custom fields per Subscriber map to typed Nutshell custom fields. We snapshot the Taguchi field schema at discovery, reconstruct any fields deleted from the Taguchi UI but still present on subscriber profiles as archived fields, and create matching custom fields in Nutshell before migration. Field type mapping defaults to text for unknown key-value data; date fields, numeric fields, and boolean flags are typed correctly based on content inspection during discovery.

Taguchi Organizations (the owning entity linked to each Subscriber) map to Nutshell Companies. The Organization name becomes the Company name; Organization metadata becomes Company custom fields. If a Subscriber has no Organization link, we create a placeholder Company using the email domain for deduplication and linkage during the Contact import phase.

Taguchi List memberships are append-only and cannot be deleted via API. We extract the full list of List names during discovery, present a strategy to the customer (map to Nutshell Person tags, custom Person fields, or both), and write accordingly. Because Taguchi list memberships cannot be removed, the migration creates a snapshot of list associations at migration time; ongoing list management in Nutshell becomes a mutable tag strategy that the customer's team manages post-migration.

Taguchi Clusters identify the strongest subscriber segment association. We map this as a custom Person field (cluster_name__c) or as a Person tag depending on the customer's segmentation strategy. The customer chooses during scoping; we apply the chosen strategy uniformly across all Subscriber records.

Taguchi behavioral Activities (opens, clicks, custom events) migrate as Task records on the Person. Each Activity type becomes a distinct Task subject pattern (e.g., 'Taguchi: Email Open', 'Taguchi: Link Click', 'Taguchi: Custom Event') with ActivityDate set to the original Taguchi timestamp. We preserve the event metadata (URL for clicks, event name for custom events) in the Task description field. If the activity volume exceeds 100,000 records, we use batch chunking to avoid API timeout.

Taguchi campaign associations (which campaigns a Subscriber engaged with) migrate as a custom Person field campaign_history__c storing a comma-separated list of campaign names, or as Person tags if the customer prefers tag-based segmentation. We do not create Nutshell Campaigns (a different object type) because Nutshell Campaigns are primarily for email marketing tracking rather than subscriber-level engagement history.

Taguchi one-time broadcast sends (name, send date, recipient count) are written as custom Person fields or as Task records on each recipient Subscriber, preserving broadcast metadata as engagement history. We do not create Nutshell Broadcasts as standalone objects because Nutshell's Broadcast feature is part of its Marketing suite, not the standard CRM People object. The customer chooses metadata storage strategy during scoping.

Taguchi SMS send history migrates as Task records on the Person with subject 'Taguchi: SMS Sent' and the message content in the Task description. Phone number fields must be present and validated on the Taguchi Subscriber record before migration; we run phone number formatting during the transform phase. If a Subscriber has no valid phone number, the SMS history record is skipped and flagged in the reconciliation report.

Taguchi automation workflows and journey logic are rule-driven configurations tied to Taguchi's trigger engine. We do not migrate workflows as code. We extract a written inventory of every active Workflow including its trigger conditions, actions, delays, and audience filters, and deliver it to the customer's admin for rebuild. Nutshell Foundation and Pro do not include native workflow builders; Power AI provides AI-assisted workflow suggestions only. The customer should confirm their intended automation rebuild tool (Nutshell Power AI, Zapier, Make, or a dedicated sales engagement platform) before migration planning concludes.