Migrate from Tofu to Zoho CRM

Tofu Accounts represent target companies in the ABM model. We export Account name, industry, tier, owner, and any custom enrichment fields. In Zoho CRM, these map directly to the standard Account (internally named Company) module, using Account Name as the dedupe key during import. Industry, tier, and owner fields map to standard Zoho fields where available and to custom fields where Tofu's schema extends beyond Zoho's default Account fields.

Tofu Campaigns are top-level containers for demand generation work, including landing pages, email sequences, ads, and collateral tied to a targeting strategy. We export all campaign metadata and status and map directly to the standard Zoho Campaign module. Campaign Name maps to Campaign Name, Campaign Status maps to Zoho's Status field, and any targeting criteria (industry, company size) stored as custom fields on the Tofu Campaign migrate to Custom Fields on the Zoho Campaign record.

Tofu Playbooks encode multi-step outreach sequences with conditional branching based on prospect engagement signals. We decompose each Playbook into discrete Task records attached to the corresponding Campaign. Each Task inherits the parent Campaign ID, records the step order, channel type (email, ad, landing page), and timing delay, and carries any branching condition that cannot be represented in Zoho as a Custom Property on the Task. The customer uses this inventory to rebuild the branching logic in Zoho Blueprint or Workflow Rules manually post-migration.

Tofu Personas define the ICP profile (industry, role, pain points, messaging tone) used to personalize content across Accounts. We export all Persona definitions as structured records and create a Multi-Select Picklist custom field on the Zoho Account module (e.g., persona_types__c) to store the Persona name(s) associated with each Account. If Zoho Professional or above is in use, this field is available from the outset; Standard tier requires a review of picklist field limits before Persona migration begins.

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 Audience name and filter definition store as Custom Fields on the Account (e.g., audience_name__c and audience_filter__c as long-text fields). This preserves the segment context for the customer's admin to rebuild Audiences as Zoho Workflow criteria or static Lists post-migration.

Tofu Content Assets include landing pages, one-pagers, ads, and sales collateral generated by AI. We export asset metadata, version history, and Campaign/Account associations as Custom Fields on the linked Zoho Account record. Binary assets (PDFs, images) are downloaded from Tofu's CDN using the asset URLs captured at export time and re-uploaded as Attachments on the corresponding Account. We snapshot all asset URLs at export time and re-validate each URL in a pre-flight check before the final sync run to catch any URL rotations.

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect all non-standard properties during the pre-migration schema scan, map each to an equivalent Zoho custom field (with the correct field type: text, picklist, date, number, checkbox), and create the field in the destination Zoho org before migration. If the destination Zoho edition is Standard or Free, we flag any custom field types (Lookup, Formula) that are unavailable at those tiers and map them to an alternative type or a text field with a note for manual upgrade consideration.

Users in Tofu are assigned as Campaign owners and Playbook creators. We export user email addresses and names and map them to Owner records in Zoho CRM by email match. If a matching Zoho User does not exist, we flag the user in the reconciliation queue for the customer's Zoho admin to provision before record import resumes. Unresolved Owner references on Accounts and Campaigns are set to the importing admin user as a temporary placeholder until the correct User is active.

Tofu records campaign enrollment dates, Playbook activation timestamps, and last-engagement dates that represent a prospect's journey through the demand generation funnel. These do not map to standard Zoho CRM date fields because they are ABM-specific. We preserve them as Custom Date fields on the Account record (e.g., playbook_activated_date__c, last_audience_enrollment__c) so that sales reps in Zoho have the full engagement context without requiring a separate Tofu login.

Tofu tracks the relationship between Campaigns and the Accounts they target. We export this as a mapping table and resolve it in Zoho CRM by creating Campaign Member records (linking Accounts to Campaigns via the standard Campaign Member object) or by populating a lookup custom field on the Account (campaign_id__c) pointing to the Zoho Campaign. The choice depends on the customer's Zoho edition and reporting requirements; we confirm the strategy during scoping.