Migrate from Taguchi to HubSpot

Taguchi subscribers map directly to HubSpot contacts. Email address is the unique identifier used for deduplication. If a Taguchi subscriber has a company name field, we map it to the Contact's associated Company or create a HubSpot Company record first.

When Taguchi subscriber records contain a company/organization field, we extract that as a HubSpot Company record and associate the Contact via the Company Name or Company ID property. This creates the parent-child relationship HubSpot's CRM expects. If multiple Taguchi subscribers share the same company name, we deduplicate them into a single Company record and link all related Contacts, ensuring a clean hierarchy and avoiding duplicate company entries.

Each Taguchi custom field key becomes a HubSpot custom contact property. Property type is inferred from the value (text, number, date, single-select). Multi-value or array values map to HubSpot's multi-select or checkbox property type. The property must be pre-created in HubSpot settings before migration.

Taguchi list membership (subscriber → list with subscription status) maps to HubSpot static list membership. Subscription status (subscribed, unsubscribed, bounced) is preserved as a contact property. Lists with over 1,000 subscribers may be split into HubSpot's list import batch limits.

Taguchi campaign metadata (name, send date, subject line, open rate, click rate) has no native HubSpot CRM equivalent. We create a Campaign_History custom object and link it to contacts who received each campaign via a lookup relationship. Your HubSpot admin can build campaign association views from this object.

Taguchi engagement events (timestamps of opens, clicks, bounces, unsubscribes per subscriber) map to HubSpot as custom date/datetime properties on the contact (e.g., Last_Email_Open__c, Total_Clicks__c). The most recent event timestamp is preserved; full event history is logged as a note or JSON blob in a long-text custom property.

Taguchi automation rules (triggered emails, conditional sends based on subscriber behavior) cannot be exported in a format that maps to HubSpot workflows. We export the workflow definitions as a structured JSON document that your HubSpot admin can use as a reference spec when rebuilding in HubSpot's workflow editor.

Taguchi user accounts who sent campaigns or managed subscribers map to HubSpot contact owners by email match. If no HubSpot user exists for a Taguchi user email, records are assigned to a default owner and flagged for manual reassignment. This ensures that each contact has an assigned owner in HubSpot, enabling proper assignment rules, task allocation, and accountability for follow-up activities.

Taguchi subscriber status values map directly to HubSpot contact email status. Bounced and unsubscribed subscribers are marked accordingly in HubSpot's contact record. HubSpot's email suppression list absorbs bounced and permanently unsubscribed addresses automatically. Active subscribers retain marketing email eligibility, while those marked as bounced or unsubscribed are excluded from future sends, ensuring compliance with email best practices and reducing the risk of deliverability issues.

HubSpot's native Createdate is set at import time, not preserved from Taguchi. We store the original Taguchi subscriber creation timestamp in a custom datetime property so reporting reflects actual subscriber age from the original platform. This allows you to segment contacts based on their original signup date, analyze historical engagement trends, and maintain data continuity across the migration, ensuring that long-standing subscriber relationships are not lost.