Migrate from Tofu to Twenty CRM

Tofu Accounts (representing target companies in the ABM model) map directly to Twenty CRM Companies. We export Account name, industry, tier, owner, and any custom enrichment fields. Tofu's account domain or website field maps to Company.websiteUrl. The dedupe key is the account domain. Twenty's Company object requires manual creation of standard fields (industry, domain, address) that may not exist in a fresh Twenty workspace — we add these during schema setup before import. If the Tofu account is linked to a Persona, we attach the Persona data as a custom field on the Company record.

Tofu Campaigns (top-level containers for landing pages, email sequences, ads, and collateral) have no direct Twenty CRM equivalent since Twenty lacks native ABM campaign management. We map Campaign records to a custom Task or Note structure where each Campaign becomes a tracking record with Campaign name, status, start/end dates, and owner. Campaign-CampaignLineItem associations (the individual content pieces within a campaign) are stored as related Task records. For teams that need ongoing campaign tracking in Twenty, we recommend creating a Campaign custom object via Twenty's metadata API during schema setup.

Tofu Playbooks encode multi-step outreach sequences with conditional branching based on prospect engagement signals. Twenty CRM's workflow builder supports linear step sequences with conditions but not the multi-branch logic that Tofu Playbooks use. We decompose each Playbook into discrete Step records in a Playbook_Step custom object we create in Twenty, with fields for Step order, channel (email/call/ad), delay_days, condition_criteria, and the original branching logic stored as a JSON custom field. Any branching conditions that cannot be represented in Twenty's linear workflow model are flagged in the mapping notes for manual rebuild post-migration.

Tofu Personas define ICP profiles (industry, role, pain points, messaging tone) used to personalize content. We export persona definitions as structured records and map them to custom fields on Twenty's Person object (role, seniority, pain_points, messaging_tone) and to Company custom fields (target_industries, company_size) if the persona applies at the account level. The Persona-Account linkage migrates as a custom lookup relationship on the Company record. If Twenty lacks a native Person object, we create one via the metadata API before migration.

Tofu Content Assets (landing pages, one-pagers, PDFs, ad creative) are platform-hosted binaries on Tofu's CDN. We export asset metadata (asset name, type, version, linked Campaign ID, linked Account ID) and store it as a Note in Twenty CRM with a link to the original Tofu asset URL. We snapshot asset URLs at export time and re-validate each URL in a pre-flight check before the final sync run. Binary re-download and re-upload to Twenty's file storage is out of scope as a standard migration task; we provide a written list of asset URLs for the customer's admin to re-upload manually or via a separate file migration engagement.

Tofu Audiences are filtered subsets of Accounts or Contacts used to trigger Playbook activation. We export audience membership as a list of Person records in Twenty with a custom field audience_name__c and the original filter criteria stored as a JSON custom field. The filter criteria themselves (e.g., industry equals SaaS and employee count greater than 50) are documented for manual reconfiguration in Twenty's filtering UI. If the Audience references Accounts, we resolve those to Companies first.

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect all non-standard properties during the pre-migration schema scan using Tofu's export format. For each custom property, we create an equivalent custom field in Twenty via the metadata API before import. Field type mapping: text maps to Text, date maps to DateTime, number maps to Number, and checkbox maps to Boolean. Picklist-equivalent fields map to Twenty's select field type. Tofu custom properties that reference other Tofu objects map to lookup fields in Twenty after the referenced object is created.

Tofu Users assigned as Campaign owners and Playbook creators map to Twenty WorkspaceMembers. We export user email addresses, names, and role assignments and create corresponding WorkspaceMembers in Twenty before any data import. If a matching WorkspaceMember does not exist in Twenty, we flag the user for the customer to provision. Owner references on Accounts and Playbooks are resolved at migration time by matching the email address.

If Tofu surfaces engagement data (calls, emails, meetings, tasks) as a record type accessible via export, we map these to Twenty Task records with channel type stored as a custom field. The original timestamp and owner map to ActivityDate and WorkspaceMember respectively. If Tofu's engagement data is not accessible via export (which is likely given the absence of a public API), we document the gap and recommend manual activity re-entry or a separate engagement capture step post-migration. Notes and attachments migrate as Twenty Note records linked to the parent Person or Company.

The relationship between a Tofu Campaign and its associated Playbooks is preserved as a lookup field on the Playbook_Step custom object (campaign_id__c). This allows the customer to understand which Playbook steps belong to which Campaign in Twenty's UI. If the customer used Tofu's Audience-Campaign-Persona segmentation model, we preserve the segment assignments as custom fields on Person records.