Migrate from Tofu to Salesforce Sales Cloud

Tofu Accounts (target companies in the ABM model) map directly to Salesforce Account. We export Account Name, Industry, Account Tier (Target, Priority, Tier 1/2/3), Owner email, Website, and any custom enrichment fields as standard and custom Account fields. The Account's Tofu tier designation migrates to a custom picklist field tofu_account_tier__c for segmentation post-migration. Account is the first object imported so that all subsequent object imports have a resolved AccountId for lookup relationships.

Tofu Campaigns (top-level containers for landing pages, email sequences, ads, and collateral) map to Salesforce Campaign. We export campaign name, status (Draft, Active, Paused, Completed), start and end dates, budget, owner, and associated Audience references. Campaign Type maps to Salesforce Campaign Type picklist values; if Tofu uses channel-specific type labels not in the Salesforce standard picklist, we create custom values during schema design.

Tofu Personas define ICP profiles (industry, role, seniority, pain points, messaging tone) used to personalize content. There is no native Persona object in Salesforce; we map each Persona to a Contact with custom fields capturing persona attributes: Persona_Name__c, Target_Industry__c, Target_Role__c, Target_Seniority__c, Pain_Points__c (long text area), and Messaging_Tone__c. If multiple Personas share the same Contact email (indicating the same person appears in multiple ICP profiles), we merge into a single Contact and store all Persona associations in a junction object or multi-select picklist. Persona-to-Account affinity (which personas are most relevant to which target accounts) migrates to Account custom fields or a Campaign Member segmentation approach.

Tofu Audiences are filtered subsets of Accounts or Contacts used to trigger Playbook activation. We export audience membership as a list of Account IDs (for Account-based audiences) and Contact IDs (for Contact-based audiences) along with the filter criteria that defined the audience. Account-based audiences migrate to Salesforce Campaign with the Account IDs as CampaignAccount relations; Contact-based audiences migrate to Campaign with Contact IDs as CampaignMember records. The original filter criteria (industry equals X, employee count greater than Y, etc.) are stored in a custom text field audience_filter_criteria__c on the Campaign for documentation.

Tofu Playbooks encode multi-step outreach sequences with conditional branching, channel rules (email, web, ads, social, documents, events), and timing delays. Salesforce has no native Playbook or cadence object; we decompose each Playbook into individual Salesforce Task records, one per step, linked to the parent Account or Contact. Step order, channel type, delay duration, and conditional trigger migrate to custom fields: step_order__c (number), channel__c (picklist: Email, Web, Ads, Social, Document, Event, Call), delay_days__c (number), and trigger_condition__c (text). Any branching logic that cannot be represented in a linear Task sequence is stored in a custom text field playbook_branching_logic__c on the first Task of the branch for manual configuration in Salesforce Flow post-migration.

Tofu Content Assets (landing pages, PDFs, ad creative, one-pagers, sales collateral) are stored on Tofu's CDN. We export asset metadata (name, type, version, created date, associated Campaign and Account IDs) and re-download binary files from Tofu's asset URLs at export time. Each binary uploads to Salesforce as a ContentDocument with a corresponding ContentVersion. We link each ContentDocument to the relevant Account or Campaign via ContentDocumentLink. If Tofu rotates asset URLs after export, inaccessible binaries are flagged in the pre-flight URL validation step before the final sync run.

Tofu records historical engagement signals — opens, clicks, page visits, ad interactions, form submissions — associated with a Campaign and an Account or Contact. These migrate to Salesforce Task and Event records linked to the relevant Account and Contact. Engagement type (Email Open, Email Click, Landing Page Visit, Ad Interaction, Form Submit) maps to a custom picklist engagement_type__c on Task; timestamp, source channel, and asset reference map to corresponding fields. This data is used to populate Salesforce Campaign Influence reports and the Contact activity timeline.

Tofu supports custom fields on Accounts. During pre-migration schema scan, we detect all non-standard Account properties and map them to equivalent Salesforce custom fields on Account. Field type mapping: text to Text(255), long text to Long Text Area, number to Number, date to Date, picklist to Picklist. If Tofu's custom field uses a value set not present in Salesforce, we create a matching custom picklist with those values before migration.

Tofu supports custom fields on Campaigns as well. Any non-standard Campaign properties detected during schema scan map to Salesforce Campaign custom fields. These include campaign-specific KPIs, UTM parameters, and targeting criteria that Tofu tracks outside the standard Campaign object fields.

Tofu Users are assigned as Campaign owners and Playbook creators. We export user email addresses, names, and role assignments and map them to Salesforce User records by email match. Any Tofu User without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Tofu users map to inactive Salesforce Users to preserve historical assignment data without creating active seat licenses.

Tofu's targeting model links Accounts to Campaigns directly. This many-to-many association migrates to the Salesforce CampaignAccount junction object, which associates an Account with a Campaign and stores a CampaignAccountStatus value (Responded, Sent, Total Conversions, etc.). We use the Account ID and Campaign ID as the join key.

In Tofu, an Audience triggers a Playbook. When migrating to Salesforce, the Campaign that represents the Audience becomes the triggering entity for sales outreach. We document the mapping between each Playbook and its target Campaign in the Playbook handoff document, and recommend that the customer's admin use Salesforce Flow or Sales Engagement (High Velocity Sales) to create Campaign-based outreach triggers. This is a configuration handoff item, not an automated data migration.

Tofu enriches Accounts with firmographic and technographic data (company size, revenue, tech stack, intent signals from 75+ sources). If this enrichment data is stored in Tofu custom fields on the Account object, we migrate it to Salesforce Account custom fields. If enrichment is sourced from Tofu's internal intelligence layer rather than stored fields, we flag the enrichment gap in the handoff document and recommend a Salesforce Data Cloud enrichment or third-party intent data integration (6sense, Bombora) as the post-migration replacement.

Tofu may apply persona-based scoring to Accounts or Contacts to rank engagement fit. Salesforce does not have a native persona scoring model; we export any scoring values as custom numeric fields on Contact (persona_score__c, engagement_score__c) and store the scoring methodology as a documented note in the handoff document. The customer's admin or a Salesforce partner rebuilds scoring logic using Salesforce Flow, Assignment Rules, or a dedicated scoring tool post-migration.