Migrate from Taguchi to Twenty CRM

Discovery and data audit

We audit the source Taguchi account across Subscribers (active, bounced, unsubscribed), Custom Fields, List memberships, Organization hierarchy, Cluster assignments, Activity history (opens, clicks, custom events), Campaign associations, Broadcast metadata, and SMS message logs. We snapshot the full custom field schema, including any fields deleted from the UI but persisting on Subscriber profiles. We assess subscriber count to estimate extraction time given Taguchi's lack of a bulk export endpoint. The discovery output is a written migration scope document with record counts per object type and a custom field inventory.

Bounced subscriber flag extraction and suppression list generation

We extract all bounced Subscribers from Taguchi before any active Subscriber data moves. The bounced flag is written as a custom suppression field on the Twenty CRM People record during import. Any Subscriber with a bounced flag is imported in a quarantined state (custom Suppression Status = Bounced) and excluded from any email activation workflow until explicitly cleared by the customer's admin. We generate a deliverability risk report listing all bounced addresses for the customer's review before cutover.

Twenty CRM schema setup

We configure the Twenty CRM workspace before data import. This includes creating custom fields on the People and Company objects (matched to Taguchi custom field types), setting up Company records from Taguchi Organizations, and creating any custom activity type fields needed to represent Taguchi event types (Email Opened, Link Clicked, Custom Event, SMS Sent, SMS Received). We configure Tags to support List membership import if the customer selects the tag-based strategy. Custom fields must be created in Twenty before CSV import begins because Twenty's CSV import creates records, not fields.

Scripted extraction from Taguchi API

We run cursor-based paginated extraction over Taguchi's subscriber and activity APIs. Subscribers are extracted in batches with Organization, Custom Field values, List memberships, Cluster, and status flags. Activity history (opens, clicks, custom events) is extracted separately and linked to Subscriber records via the Subscriber ID. Campaign and Broadcast metadata is extracted and mapped to People custom properties. SMS message logs are extracted with phone number E.164 validation. All extractions use exponential backoff to respect API rate limits. Large databases (over 25,000 Subscribers) are extracted in staged batches to avoid timeouts.

Data transformation and staging

We transform extracted data into Twenty CRM-compatible CSV format. Subscriber status flags are mapped to the custom suppression field. Organization references are resolved to Company IDs (resolved in the next step). Custom field values are typed (text, number, date, boolean) and validated against the Twenty field types. Activity records are linked to Subscriber IDs that will become People IDs after import. List memberships are serialized as tag strings or multi-select values depending on the customer's chosen strategy. Bounced Subscribers are staged in a separate import batch with quarantine flags.

Production import in dependency order

We run production import in dependency order: Companies (from Taguchi Organizations), then People (from Taguchi Subscribers with suppression flags and Company links resolved), then Tags and People custom properties (List memberships and Clusters), then Activity history (Tasks linked to People records). Each phase emits a row-count reconciliation report. Bounced Subscribers are imported last with quarantine flags active. We run a post-import spot check comparing 25-50 random Subscriber records in Taguchi against their corresponding People records in Twenty to verify field-level accuracy.

Cutover, validation, and automation rebuild handoff

We freeze Taguchi writes during cutover, run a final delta migration of any Subscribers or Activities modified during the migration window, then enable Twenty CRM as the system of record. We deliver a written inventory of Taguchi automation workflows, campaign journeys, and SMS sequences with recommendations for rebuilding equivalents in Twenty CRM's workflow builder. We do not rebuild workflows as part of the migration scope. We support a one-week hypercare window where we resolve any data reconciliation issues raised by the customer's team.