Migrate from Tofu to Freshsales

Tofu Accounts (target companies in the ABM model) map directly to Freshsales Account. We export Account name, industry, tier, owner, and any custom enrichment fields. The Account becomes the parent record for all Contact and Deal records. We use Account name as the dedupe key during import.

Tofu does not have a native Contact object. Contact records exist as membership entries within Audiences (filtered subsets of Accounts). We extract Audience membership by Account, retrieve Contact fields from Tofu's Audience export (name, email, title, company), and create Freshsales Contacts with AccountId resolved to the parent Account. Any Contacts without a matching Account are held in a reconciliation queue.

Tofu Campaigns (top-level containers for demand generation work) map to Freshsales Deal records with campaign metadata preserved as custom fields. Freshsales has no native Campaign object equivalent to HubSpot or Salesforce Marketing. We create Deal records for each Tofu Campaign, preserve campaign status and targeting strategy in custom fields, and link the Deal to the primary Account.

Tofu Playbooks encode multi-step outreach sequences with conditional branching based on prospect engagement signals. We decompose each Playbook into discrete Step records. Each Step becomes a Freshsales Task with Subject, Description, and due date from the step timing. Conditional branching that cannot be represented in Freshsales' linear workflow model is preserved as a Custom Field on the Task record. The customer receives a Playbook Map document listing each original Playbook, its steps, and any unrepresentable conditions.

Tofu Personas define ICP profiles (industry, role, pain points, messaging tone) used to personalize content. Freshsales has no native Persona object. We export persona definitions as structured data and create corresponding Contact custom fields in Freshsales (persona_industry__c, persona_role__c, persona_pain_points__c, persona_messaging_tone__c). During scoping, the customer chooses whether to assign Persona directly to Contacts or to use Freshsales lists for persona-based segmentation.

Tofu Audiences are filtered subsets of Accounts or Contacts used to trigger Playbook activation. We export audience membership as a list of linked Account or Contact IDs with the filter criteria preserved. In Freshsales, we create Lists matching each Audience and populate membership based on the exported ID list. Any filter criteria that cannot be represented as a static list are flagged in the scope document for the customer to configure manually.

Content Assets (landing pages, one-pagers, ads, sales collateral) generated by Tofu live on Tofu's CDN as platform-hosted binaries. We export asset metadata (name, type, version, linked Campaign/Account associations) and re-download binaries from Tofu's asset URLs at export time. Binaries are re-hosted in Freshsales as ContentDocument records linked to the relevant Account or Contact. If Tofu rotates asset URLs post-migration, some Content Assets may become inaccessible; we snapshot URLs at export and re-validate before the final sync.

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect any non-standard properties during the pre-migration schema scan, map them to Freshsales custom fields of equivalent type (text, number, date, picklist, checkbox), and create them in Freshsales before data import begins. Custom field API names follow Freshsales naming conventions.

Tofu Users are assigned as Campaign owners and Playbook creators. We export user email addresses and names and match by email against the Freshsales User table. Any Tofu Owner without a matching Freshsales User is held in a reconciliation queue for the customer's Freshsales admin to provision before record import resumes.