Migrate from Tofu to Nutshell

Tofu Accounts (target companies in the ABM model) map directly to Nutshell Companies. We export Account name, industry, tier, owner, and any custom enrichment fields. The domain from the Account record populates the Nutshell Company website field. If multiple Tofu Accounts share the same domain (common in enterprise ABM targeting parent-subsidiary hierarchies), we map the primary Account to the Company record and attach subsidiary Account references as custom fields.

Tofu Campaigns (top-level containers for landing pages, email sequences, ads, and collateral) map to Nutshell Deals. The campaign targeting strategy migrates as Deal description text; campaign status (active, paused, archived) maps to Deal status. If the customer uses multiple Nutshell Pipelines to distinguish campaign types, we assign a Pipeline and Stage during import based on campaign metadata.

Tofu Personas define ICP profiles (industry, role, pain points, messaging tone) used to personalize ABM content. Nutshell has no native Persona object. We map persona definitions to Contact custom fields — persona_industry__c, persona_role__c, persona_pain_points__c — so that the ICP attributes travel with each Contact record. During scoping, the customer selects which persona fields are active and which are archived.

Tofu Playbooks encode multi-step outreach sequences with branching logic, timing, and channel rules. Nutshell does not have a native branching automation construct. We decompose each Playbook into discrete Step records and import them as a series of Nutshell Tasks with sequential due dates and channel metadata in custom fields. Any branching conditions that cannot be represented linearly are stored as custom text fields (e.g., playbook_branch_condition__c) for the customer's admin to review and reconfigure in Nutshell's Goals or automation layer post-migration.

Tofu Audiences are filtered subsets of Accounts or Contacts used to trigger Playbook activation. We export audience membership as a list of linked Account IDs with the filter criteria preserved. The filter criteria migrate as a text note on a Nutshell saved search or list view that the customer can replicate manually. Individual Contact membership is preserved as a custom multi-select or tag field on each Contact record.

Content Assets include landing pages, one-pagers, ads, and sales collateral generated by Tofu. We export asset metadata (title, type, version, linked Campaign/Account associations) and re-download binaries from Tofu's asset URLs at export time. Nutshell stores binaries as Attachments on the related Company or Deal record. We re-validate each asset URL in a pre-flight check before the final sync run. If Tofu rotates asset URLs post-migration, we flag inaccessible assets in the handoff document.

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

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect any non-standard properties during the pre-migration schema scan and map them to equivalent custom fields in Nutshell. Custom field types are mapped: text to text, number to number, date to date, and multi-select to a custom multi-select picklist. Nutshell supports custom fields on all paid tiers including Foundation ($13/user/mo), so no tier upgrade is required for custom field migration.