Migrate from Taguchi to Freshsales

Taguchi Subscribers map to Freshsales Contacts. The subscriber email becomes the Contact email field, first_name and last_name map from subscriber name fields (Taguchi stores a full_name field; we split into first and last on Freshsales). Subscriber status (active/bounced/unsubscribed) maps to Freshsales email_status or a custom picklist field since Freshsales does not have a native bounced status equivalent. We set HasOptedOutOfEmail = true for unsubscribed records and flag bounced records separately so the customer can suppress or re-permission them in Freshsales.

Taguchi stores arbitrary key-value custom fields per Subscriber. Taguchi custom field keys with spaces must be called with dashes in activities (e.g., recipient.custom.my-custom-field). We map these to Freshsales Contact custom fields using the lowercase key name with underscores replacing spaces. Field type mapping: text fields to Text, numeric fields to Number, date fields to Date. Taguchi custom fields deleted from the UI persist on subscriber profiles; we snapshot all field definitions during discovery and recreate any orphaned fields as archived custom fields on Freshsales to preserve historical data.

Taguchi Organizations are company-level entities linked to Subscribers. Each Subscriber belongs to an Organization. We map Organization to Freshsales Account, using Organization name as Account Name and Organization domain as Account Website. We create the Account first, then link the Contact via the Account Lookup during Contact import so that the relationship is satisfied at insert time. If a Subscriber has no Organization link, we create a placeholder Account or set Account to null depending on the customer's preference.

Taguchi List memberships are append-only; they cannot be deleted via API. We map list memberships to Freshsales Contact tags using the list name as the tag value. Alternatively, if the customer prefers a structured field, we create a multi-select picklist or custom text field on Contact and write list names as comma-separated values. The customer chooses the strategy during scoping. Note that because Taguchi list memberships cannot be deleted on the source, any list a subscriber was ever added to will appear in the migration regardless of whether they were subsequently removed on the source.

Taguchi Clusters identify the subscriber segment a contact is most strongly associated with. Clusters map to a Freshsales Contact custom field (single-select picklist or text) or as a Contact tag. We preserve the cluster name as the value. If a Subscriber has no cluster assignment, the field is left null or set to a default.

Taguchi logs per-subscriber behavioral events (opens, clicks, custom events) used to drive automation triggers. We extract activity history and write it as a summary activity log against the Freshsales Contact or as structured custom field entries. Because Freshsales does not have a native behavioral event object equivalent to Taguchi's activity feed, we aggregate the most recent activity date, total click count, and total open count into Contact custom fields, preserving the behavioral signal without creating a separate activity table.

Taguchi Campaigns link Subscribers and Activities. Freshsales does not have a native Campaign object in its CRM module (Campaign belongs to Marketing Cloud). We preserve campaign associations as metadata on the Contact record: campaign name, campaign ID, and last campaign send date migrate as Contact custom fields rather than as a top-level object.

Taguchi Broadcasts are one-time email sends to subscriber segments. We preserve broadcast metadata (name, send date, recipient count) as a linked activity log entry or as Contact custom fields on each recipient record. Because Freshsales does not have a broadcast tracking object, we write broadcast engagement as a custom activity note or timestamp field against the Contact rather than as a standalone record.

Taguchi SMS send history migrates as a message activity record on the Freshsales Contact. We use a custom activity type or note field to record SMS content, send date, and delivery status. Phone number fields must be present and validated on the Taguchi Subscriber for SMS records to migrate; we skip SMS activity records for Subscribers without a phone number and report the count during reconciliation.

Taguchi automation workflows and journey logic are rule-driven configurations that do not map to Freshsales Flow or any other CRM automation model. We do not migrate automation workflows. We extract a written inventory of every active Taguchi workflow with its trigger conditions, audience rules, and action sequence so the customer's admin can evaluate rebuild options in Freshsales Flow or Freshmarketer. This inventory is delivered as a structured document, not migrated data.