Migrate from Taguchi to Pipedrive

Taguchi Subscriber records map to Pipedrive Person records. The subscriber email maps to Pipedrive's primary email field, first name and last name map to the corresponding Pipedrive Person name fields, and subscriber status (active, bounced, unsubscribed) maps to Pipedrive's HasOptedOutOfEmail flag and a custom status field. Taguchi's read-only metadata fields (campaign source, import source) migrate as custom fields on the Pipedrive Person record. All custom key-value fields on the Taguchi subscriber profile migrate as Pipedrive custom Person fields, with field type decisions (text, number, date, picklist) made during discovery based on the Taguchi field schema snapshot.

Taguchi's per-subscriber key-value custom fields are preserved as Pipedrive custom Person fields. During discovery, we snapshot the full Taguchi custom field definition list, including any fields that have been deleted from the UI but remain tagged to subscriber profiles (Taguchi does not hard-delete fields). These archived fields are reconstructed as inactive or label-prefixed custom fields in Pipedrive to preserve data integrity. Field types are mapped: string values become text fields, numeric values become number fields, dates become date fields, and enumerated values become picklist fields. Fields that cannot be cleanly typed are migrated as long text fields with the original value preserved.

Taguchi Organization records map to Pipedrive Organization records. The organization name maps to the Organization name field, and any organization-level custom fields migrate as Pipedrive custom Organization fields. Each Taguchi Subscriber's organization link is resolved to the correct Pipedrive Organization record at migration time, and the Person-Organization relationship is established via Pipedrive's person-org link. Taguchi does not enforce that a Subscriber has an Organization, so we flag any Subscriber without an organization link for the customer's decision on whether to create an Organization record or leave the Person unlinked.

Taguchi Clusters identify the subscriber segment a contact is most strongly associated with. We map clusters to Pipedrive tags on the Person record (preferred) or as a custom Person field called Cluster or Segment, depending on whether the customer uses tags for other list-related purposes. The customer chooses the strategy during discovery scoping. Clusters with no value default to an Unsegmented tag.

Taguchi List memberships are mapped to Pipedrive tags on the Person record. List names become tag names as-is, with an optional prefix (e.g., LIST_) to distinguish them from other tag uses. Note that Taguchi list memberships are append-only and cannot be deleted via API, so a Person who was on List A in Taguchi will retain that association in Pipedrive as a tag. If the customer needs to exclude certain list associations from migration, this must be identified during discovery scoping before extraction begins.

Taguchi Campaigns link subscribers and activities and store send history. Pipedrive has no native Campaign object in the standard CRM tiers. We preserve campaign metadata (campaign name, send date, recipient count, open rate) as a linked Activity record against the Person record, with the campaign name in the Activity subject and metadata in the Activity notes. For customers with high campaign volume, we use a custom field approach where campaign associations are stored as comma-separated values in a custom Person field.

Taguchi Broadcasts (one-time email sends to subscriber segments) migrate as Activity records on the Person. We capture broadcast name, send date, recipient count, and open/click counts as structured fields within the Activity notes or as custom Activity fields. Broadcast content is not migrated as a transferable asset; Pipedrive's email templates serve a different purpose than Taguchi broadcast content.

Taguchi behavioral activity records (opens, clicks, custom events) migrate as Pipedrive Activity records linked to the Person. Each activity type maps to a distinct Activity subject (e.g., Email Opened, Link Clicked, Custom Event: [event_name]). The original activity timestamp becomes the Activity due date. Open and click counts for a specific send are aggregated into a single Activity record per event type per send to avoid creating hundreds of granular activity records. Custom events from Taguchi preserve their event name and any associated properties as Activity notes.

Taguchi SMS send history migrates as Pipedrive Activity records on the Person. The SMS send date, recipient status (delivered, failed), and message content migrate to Activity fields. Phone number validation is performed before migration: any Person record without a valid phone number in Taguchi is flagged and quarantined for the customer to correct before import. SMS content is preserved as Activity notes; Pipedrive does not have native SMS sending capability in standard CRM tiers.

Taguchi automation workflows and journey logic are rule-driven configurations that do not map to Pipedrive's automation model. We do not migrate workflows as executable code. We document every active Taguchi automation workflow with its trigger conditions, audience rules, and action sequence in a written inventory that the customer's admin uses to rebuild equivalent Pipedrive Workflows (Advanced tier and above) or document-based process guides for lower Pipedrive tiers.

Taguchi Subscribers do not have an explicit Owner field in the way CRM platforms do, but organizational assignments can exist. If the customer has owner-equivalent data in Taguchi custom fields or subscriber metadata, we map those to Pipedrive User records by email match. Any owner reference without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.