Migrate from Tofu to HubSpot

Tofu contacts map directly to HubSpot contacts, preserving standard fields like name, email, phone, and job title. Custom engagement scores, intent signals, and UTM strings are migrated as HubSpot custom properties (engagement_score__c, intent_signals__c, campaign_utms__c). Tofu contact‑to‑account associations map to HubSpot's primary company association; any secondary links are flagged for manual review. Original create date and last‑modified timestamp are stored in custom datetime fields (original_create_date__c, original_last_modified_date__c) for historical context.

Tofu accounts migrate to HubSpot companies, mapping fields such as industry, employee count, and revenue range to HubSpot's company properties. We apply domain‑based duplicate detection to prevent duplicate records when Tofu accounts share the same domain. Multi‑account contacts collapse to a company with secondary associations; secondary links are flagged for review. Address fields map directly, and the original create date is preserved in a datetime field (original_create_date__c) for historical context.

Tofu campaign metadata—campaign name, status, start and end dates, budget—migrates as HubSpot campaign records, mapping to HubSpot’s standard campaign properties (hs_campaign_name, hs_campaign_status, hs_start_date, hs_end_date, hs_campaign_budget). Tofu’s targeting criteria and audience segmentation have no HubSpot equivalent and are not migrated; FlitStack exports them as a JSON reference for rebuilding audiences as HubSpot lists or smart lists after migration. Original campaign IDs are stored in a custom property (original_campaign_id__c) for cross‑system reference.

Tofu sequences have no direct HubSpot equivalent, as they combine multi‑step outbound cadences, conditional routing, and contact‑level triggers. FlitStack exports the sequence definition—including step order, step types (email, call, task, delay), conditions, and branch logic—as a JSON file. Your HubSpot admin can use this JSON to rebuild each sequence as a HubSpot workflow, re‑creating email templates, task assignments, and delay durations in HubSpot’s workflow builder. The export also preserves step‑level tags or scoring actions for re‑implementation.

Tofu engagement scores are calculated metrics stored as custom properties on contacts. HubSpot does not have a native engagement‑score field, so we create engagement_score__c as a number custom property on the Contact object to preserve historical scoring values. During migration, the score from Tofu maps to engagement_score__c, and missing scores are set to zero. Your team can use engagement_score__c in HubSpot lists, workflows, or reports to replicate Tofu‑style lead prioritization.

UTM strings and attribution data attached to Tofu contacts migrate as a long‑text custom property (campaign_utms__c) on each contact record. This preserves source attribution, campaign tracking, and referral information for reporting continuity while your team builds HubSpot’s native attribution model. During migration, any empty or malformed UTM strings are cleaned and stored as‑is; the field is indexed for use in HubSpot’s reporting filters, lists, and workflow triggers based on source data.

Tofu intent‑signal flags stored as contact properties migrate to a HubSpot custom text property (intent_signals__c). This preserves the original intent data for reference, even though HubSpot’s native intent signals typically come from third‑party providers or HubSpot’s own tracking. During migration, each Tofu flag is written as a comma‑separated string into intent_signals__c, allowing your team to filter contacts by historic intent, use the property in workflows for lead scoring, or compare it against HubSpot‑generated signals after go‑live.

Any Tofu custom properties beyond engagement score and intent signals map to HubSpot custom properties by matching data type. Boolean, number, date, and text types map directly. Pick‑list types require value‑by‑value mapping between Tofu’s option labels and HubSpot’s pick‑list option labels.

Tofu engagement activities (calls, emails, meetings, notes) with timestamps and owner attribution migrate to HubSpot's engagement objects. Original timestamps and owner email addresses are preserved. FlitStack resolves owner emails to HubSpot user records before inserting.

Tofu records which contacts are members of which campaigns. This migrates as HubSpot campaign membership associations on the Campaign object. HubSpot’s campaign membership does not carry per‑contact engagement scores from Tofu; those scores are stored separately as the engagement_score__c custom property. After migration, your team can use HubSpot’s campaign membership views to see which contacts belong to each campaign, and filter by the original Tofu membership date stored in original_campaign_member_date__c if needed.