Migrate from Tofu to monday CRM

Tofu Accounts represent target companies in the ABM model. We export Account name, industry, tier, owner, and any custom enrichment fields and map them to Monday.com CRM Company items. The Monday.com CRM board uses the native Companies board type, which supports custom fields per company. We use Company name as the dedupe key and resolve the Account owner to a Monday.com User by email match. Any Tofu custom enrichment fields are mapped to Monday.com custom fields on the Company board, with type conversion (Tofu text properties become Monday.com text fields, numeric properties become number fields).

Tofu Campaigns are the top-level container for landing pages, email sequences, ads, and collateral tied to a targeting strategy. Monday.com CRM has no native Campaign object. We create a dedicated Campaign Board in Monday.com with groups per Tofu Campaign. Each Campaign group contains linked Contact and Company Items representing the Campaign's audience. We preserve campaign status, start and end dates, and owner as board-level or group-level fields. The customer chooses whether to model campaigns as separate boards or as items within a master Campaign board during scoping.

Tofu Personas define ICP profiles (industry, role, pain points, messaging tone) used to personalize content. Monday.com CRM has no native Persona object. We export persona definitions as structured records and map them to either Monday.com tag groups (for classification) or a dedicated Personas Board with custom fields (Industry, Role, Pain Point, Messaging Tone) linked back to the Accounts board via a connected board relationship. The customer selects the strategy during scoping based on how their team uses personas day-to-day.

Tofu Playbooks encode multi-step outreach sequences with conditional branching based on prospect engagement signals. Monday.com Automations model triggers and actions but do not support the multi-step cadence or conditional branching depth that Tofu Playbooks use. We decompose each Playbook into discrete Step records during export and capture the step sequence, timing, channel rules, and any branching conditions as structured fields. Any branching conditions that cannot be represented in Monday.com Automations are flagged as a custom property on the Step record. The migration output is a written Playbook Inventory document listing each Playbook's steps and conditions, which the customer's Monday.com admin uses to rebuild automations post-migration.

Tofu Content Assets include landing pages, PDFs, ad creative, and sales collateral generated by the platform's AI. These binaries live on Tofu's CDN. During migration we export the asset metadata and re-download binaries from Tofu's asset URLs at export time, then attach them as files to the relevant Monday.com Item (Contact, Company, or Campaign Board). We snapshot asset URLs at export time and re-validate each URL in a pre-flight check before the final sync run. Landing pages that cannot be re-downloaded are flagged as external links pointing to the archived Tofu URL, with a note that the page will require rebuilding on a CMS 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. In Monday.com CRM we create segmented views on the Contacts board using the original filter criteria, or we create dedicated Contact groups per Audience. The filter logic (for example, Industry equals Technology and Account Tier equals Enterprise) is documented as a Monday.com filter view definition and included in the handoff documentation.

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 Monday.com CRM. Monday.com custom fields support text, number, date, person, status, dropdown, checkbox, and link types. We match Tofu field types to Monday.com field types during the schema mapping phase. Fields with no Monday.com equivalent are flagged as custom properties requiring a workaround (for example, multi-value arrays stored as text).

Users in Tofu are assigned as Campaign owners and Playbook creators. We export user email addresses and names and map them to Owner/User items in Monday.com CRM. If a matching Monday.com user does not exist, we flag the unmapped owner for the customer's admin to provision before record import resumes. Owner assignments on Accounts, Campaigns, and Audiences are migrated by resolving the Tofu owner email to the Monday.com User member on the relevant board.