Migrate from Taguchi to HighLevel

Taguchi Subscribers map directly to GoHighLevel Contact records. We map Subscriber email to Contact email, Subscriber status to a combination of GoHighLevel's email opt-out fields (bounced becomes a DND flag, unsubscribed becomes HasOptedOutOfEmail). We preserve the Subscriber ID in a custom field taguchi_subscriber_id__c for audit traceability. Metadata fields (campaign source, import source, cluster) migrate as additional Contact custom fields rather than as separate objects.

Taguchi key-value custom field keys become GoHighLevel Contact custom fields of matching or nearest-typed equivalent (text fields for string values, number fields for numeric values, date fields for date values). We snapshot the full Taguchi custom field schema during discovery before any data extraction so that fields deleted from Taguchi's UI but still present in Subscriber profiles are reconstructed as archived custom fields on GoHighLevel. This prevents null-value drift in the destination.

Taguchi list memberships are append-only and cannot be deleted via API. We migrate list names as GoHighLevel Tags on the Contact record, which are fully mutable on the destination. The customer chooses during scoping whether to import all lists as tags, a selected subset, or list names as a custom multi-select field. We document the complete list membership inventory during discovery so the customer can make an informed decision before any records move.

Each Taguchi Subscriber is linked to an owning Organization. We map Organization records to GoHighLevel Company records, resolving the Company reference at Contact import time. Organization metadata (name, domain if present) populates the Company name and website fields.

Taguchi Clusters identify the primary subscriber segment a contact is most strongly associated with. We map this as a Contact custom field (cluster_name__c) or as a GoHighLevel Tag, depending on whether the customer uses clusters for segmentation filtering or for a single primary association. The customer selects the strategy during scoping.

Taguchi per-Subscriber Activities (opens, clicks, custom events) drive automation triggers and represent behavioral history. We extract the full activity log and write each event as a GoHighLevel Task record or as a custom activity log custom field on the Contact. Event type, timestamp, and event metadata (URL for clicks, campaign for opens) are preserved. The customer chooses whether to write all activity as Task records or to summarize high-volume event types (opens, clicks) as aggregated custom fields to avoid inflating the GoHighLevel Activity Timeline with hundreds of events per Contact.

Taguchi one-time broadcast sends (name, send date, recipient count) are migrated as metadata entries on each recipient's Contact record rather than as top-level objects, since GoHighLevel does not have a native broadcast concept. We write a Task record with broadcast metadata for each recipient to preserve the send record against the Contact timeline.

Taguchi Campaigns link Subscribers and Activities but have no direct GoHighLevel equivalent at the top level. We migrate campaign associations as a custom Contact field (campaign_name__c) for single-campaign subscribers or as GoHighLevel Tags for multi-campaign contacts, preserving which campaigns each Contact was part of.

Taguchi SMS send history migrates as SMS activity records on the Contact. Content, send timestamp, and status are preserved. Phone number fields must be present and validated on the Subscriber record for SMS activity to link correctly in GoHighLevel; we validate phone number presence during the data quality phase and flag missing phone fields before migration begins.

Taguchi automation workflows and journey logic are rule-driven configurations that do not map to GoHighLevel Workflows. We do not migrate workflows. We extract every active Taguchi workflow, document its trigger conditions, subscriber criteria, actions, and delays, and deliver the written inventory to the customer. The customer's admin rebuilds workflows in GoHighLevel using the documented logic as a functional specification.