Migrate from Tofu to Odoo CRM

Tofu Accounts represent target companies in an ABM model with optional multi-persona support (multiple Contact records per Account). We map each Tofu Account to an Odoo Company (res.partner with company_type=company) as the parent record, then create one Odoo Contact (res.partner with company_type=person) per Persona on that Account. The Account name maps to Company name, industry to industry_id, and tier to a custom field. Each Contact inherits the parent Company via partner_id. Owners resolve by email to existing Odoo users or enter a reconciliation queue for admin provisioning.

Tofu Campaigns are top-level targeting containers with status, owner, and budget metadata. Odoo CRM has no native Campaign object matching Tofu's demand generation scope. We preserve campaign membership by creating Tags on the related Company and Contact records (tag_name = campaign_name) and storing campaign status, owner, and targeting criteria as custom fields on the Company record. The customer's Odoo admin can activate Odoo Marketing Automation (a separate app) or a third-party integration to rebuild campaign targeting logic.

Tofu Playbooks encode multi-step outreach sequences with conditional branching based on prospect engagement signals. Odoo has no native Playbook or cadence object. We decompose each Playbook into discrete Step records at export time and import them as Odoo Notes (or Tasks with a Playbook tag) linked to the relevant Company or Contact. Branching conditions that cannot be represented in Odoo's linear model are preserved as structured custom fields on the Note (e.g., branch_condition, branch_target_step). The timing and channel rules from each step are stored in Note body as structured text. A separate Playbook Decomposition document lists every step for manual rebuild in Odoo Automated Actions or a third-party sales engagement tool.

Tofu Personas define ICP profiles (industry, role, pain points, messaging tone) used to personalize content. Odoo CRM has no native Persona object. We export persona definitions as structured records and apply them to Odoo Contacts as Tags (e.g., tag: 'Persona: Enterprise VP Sales'). Persona attributes (industry focus, role seniority, pain points) are stored as custom text fields on the Contact record for reference by the sales team. Multi-persona Accounts produce multiple tagged Contacts, all linked to the same parent Company.

Tofu Audiences are filtered subsets of Accounts or Contacts with activation triggers. Odoo CRM has no native audience segmentation capability. We export audience membership as a list of Contact IDs with the filter criteria preserved as structured notes on a dedicated Tag record. The filter logic (e.g., industry=tech AND employee_count>500) cannot be encoded in Odoo CRM natively and requires manual rebuild in Odoo Marketing Automation, a third-party segmentation tool, or a custom module. We document the original filter criteria for the customer's admin to reference during rebuild.

Content Assets in Tofu include landing pages, one-pagers, ads, and sales collateral generated by AI with version history and Campaign/Account associations. We export asset metadata (name, URL, version, linked Account/Campaign) and re-download binary files from Tofu's CDN at export time. Each binary is re-attached to the corresponding Company record in Odoo as an ir.attachment. If Tofu rotates CDN URLs post-migration, some binaries may become inaccessible; we snapshot all URLs at export time and re-validate before the final sync run. Landing pages and ad creative cannot be rendered inside Odoo CRM and are delivered as downloadable documents.

Tofu Users are assigned as Campaign owners and Playbook creators. We export user email addresses and display names and map them to existing Odoo User records by email match. Any Tofu Owner without a matching Odoo User enters a reconciliation queue; the customer's Odoo admin provisions the User before record import resumes. Inactive Tofu owners map to inactive Odoo Users so that historical assignment is preserved even if the user no longer has an active seat.

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect all non-standard properties during the pre-migration schema scan and map them to equivalent custom fields on the corresponding Odoo model. Field type translation applies: Tofu text fields map to char or text, Tofu numeric fields map to float or integer, Tofu date fields map to date. Custom fields on Accounts map to custom fields on the res.partner (company) record. Custom fields on Playbooks map to custom fields on the Note or Task record where the Playbook steps land.

Non-standard Campaign properties (beyond name, status, owner, and targeting metadata) migrate to custom fields on the Company record that carries the corresponding Campaign tag. If the custom property is Campaign-scoped rather than Account-scoped, we create a dedicated Campaign custom model or store the values in a Char field on the relevant tag record. The customer's Odoo admin determines the final storage approach during the schema design phase.

If Tofu emits any records classified as unqualified prospects or leads (separate from Accounts), those map to Odoo crm.lead records. The crm.lead object in Odoo supports both Lead and Opportunity in a unified model, with a toggle to convert to Opportunity. Lead source and score from Tofu custom fields map to Odoo medium_id and a custom priority field. The conversion workflow in Odoo (lead to opportunity) is a manual or rule-triggered action that the customer's sales team executes post-migration.

Some Tofu configurations surface deal-like records tied to target Accounts. If present in the export, these map to Odoo crm.lead records with type=opportunity and stage mapped from Tofu's deal status. Expected revenue maps to Odoo's planned_revenue field. The Company lookup is resolved from the parent Account mapping. Pipeline stages are pre-configured in Odoo before migration so the stage assignment is satisfied at insert time.

Tofu records prospect engagement events against Playbook steps (email opens, link clicks, form submissions). These engagement signals map to Odoo mail.message records linked to the Contact or Company record, with message_type=notification and a structured body encoding the engagement type and timestamp. Scheduled Playbook steps that have not yet fired map to project.task records with a deadline and a tag indicating the parent Playbook. Completed engagement history is preserved; future-triggered steps are documented for manual scheduling in Odoo.