Migrate from Tofu to Pipedrive

Tofu Accounts represent target companies in the ABM model. We export Account name, industry, tier, owner, and custom enrichment fields. The mapping to Pipedrive Organization uses the Account name as the Organization name field and domain (if available) as the Website field. The dedupe key is Organization name with a secondary check on domain. Custom fields on Tofu Accounts that have no direct Pipedrive equivalent become Organization custom fields created via Pipedrive's Organization fields API before migration.

Tofu Campaigns are the top-level container for landing pages, email sequences, ads, and sales collateral tied to a targeting strategy. We map Campaign name to Deal title, Campaign status to Deal status, and Campaign owner to Deal owner_id resolved via User email lookup. Campaign budget, start date, and end date migrate as custom fields on the Deal. The Campaign's associated Accounts link to the Deal via Organization lookups. Pipedrive does not have a native Campaign object in the same sense as Salesforce; we use Deals as the closest structural equivalent with Campaign metadata preserved in custom fields.

For Tofu Campaigns that represent multi-touch engagement programs rather than sales pipeline deals, we map them to Pipedrive Activities with a custom field campaign_source__c set to the Tofu Campaign name. This preserves the program-level context without forcing marketing programs into a Deal structure that doesn't fit them.

Tofu Playbooks encode multi-step outreach sequences with conditional branching, timing, and channel rules. Pipedrive does not have a native Playbook or cadence object; we decompose each Playbook into discrete Step records and import them as a chronological sequence of Activity records linked to the Account or Contact they target. Any branching conditions that cannot be represented linearly are flagged as custom fields on each Activity record (e.g., playbook_branch_condition__c) with the condition description for manual Pipedrive Workflow rebuild.

Tofu Personas define the ICP profile (industry, role, pain points, messaging tone) used to personalize content. Pipedrive does not have a native Persona object. We map Personas to a Pipedrive Custom Object (Persona) on plans that support it, or to a combination of Organization tags and Contact custom fields. The Persona-industry, Persona-role, and Persona-pain-point fields map to custom fields on the Persona Custom Object or to multi-select picklist fields on Contact. The Account-to-Persona association migrates as a lookup relationship.

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. If Pipedrive's Custom Objects feature is available, we create an Audience Custom Object and link it to the Accounts it contains. If Custom Objects are not on the plan, we recreate the filter logic as a Pipedrive Activity list or as Organization tags representing the audience segment.

Tofu Content Assets include landing pages, one-pagers, ads, and sales collateral generated by the AI. Binary files live on Tofu's CDN. We export asset metadata (name, type, version, linked Campaign, linked Account) and re-download binaries from Tofu's asset URLs at export time. In Pipedrive, we create Note records linked to the relevant Organization or Deal, storing the asset URL in a custom field asset_url__c. A pre-flight URL validation pass runs against all asset URLs before the final sync to catch any rotated or inaccessible URLs.

Tofu Users are assigned as Campaign owners and Playbook creators. We export user email addresses and display names and map them to Pipedrive User records resolved by email. If a matching Pipedrive User does not exist, we flag the owner as unassigned and hold those records in a reconciliation queue for the customer's admin to provision before migration resumes. Owner records are migrated before any Account, Contact, or Deal records because Pipedrive requires a valid OwnerId on most standard objects.

Tofu supports custom fields on Accounts. We detect all non-standard Account properties during the pre-migration schema scan and create matching Organization custom fields in Pipedrive via the OrganizationFields API before importing any data. Field types are mapped: text to VARCHAR, number to INT, date to DATE, multi-select to multi-select picklist where supported.

Tofu Campaign custom properties (budget, channel, targeting criteria) map to Deal custom fields in Pipedrive. We pre-create all Campaign-derived custom fields on the Deal object before migration so that the Deal import has nowhere to drop data.

Playbook-level custom properties (step type, channel, delay_days) become custom fields on the Activity records that represent individual Playbook steps. We pre-create these as Activity custom fields during schema design.