Migrate from Wetroo CRM to Odoo CRM

Wetroo Leads map to Odoo crm.lead records with type=lead (unqualified prospect). We preserve source attribution (Facebook Lead Form, Google Data Extractor, manual entry) in a custom Char field on the Odoo crm.lead. The Wetroo lead score, if present, maps to odoo priority or a custom field. Lead status in Wetroo (new, contacted, qualified, lost) maps to Odoo's stage configuration, which we define during schema setup.

Wetroo qualified Contacts map to Odoo res.partner records. We preserve full contact details — name, phone, email, job title, lifecycle stage — in the partner fields. Address data (street, city, state, country, zip) maps to res.partner address fields. Custom fields on Wetroo Contacts require pre-creation in Odoo as ir.model.fields before import. res.partner is the primary person/account model in Odoo, distinct from the crm.lead model.

Wetroo Companies map to Odoo res.partner records with company_type=company. Company names become partner names; industry tags map to industry_id (a many2one to res.partner.industry). Address and billing data on Wetroo Companies map to res.partner address fields. Companies are created before Contacts so that the child_contact relationship to the parent company partner is satisfied at insert time.

Wetroo Deals map to Odoo crm.lead with type=opportunity. The deal name becomes the Odoo lead name; deal value maps to Odoo expected_revenue and sometimes list_price depending on the pipeline configuration. Pipeline stage names map to Odoo stage definitions within the crm.stage model. Closed-Lost and Closed-Won deal outcomes map to Odoo's lost and won stage states.

Wetroo pipeline configuration (stage names, order, win/loss states) is read via API and mapped to Odoo crm.stage records within the relevant team. We define each pipeline as an Odoo crm.team and assign stages to that team. Stage probability percentages migrate from Wetroo to Odoo stage probability values. Custom stages on Wetroo are recreated as Odoo stages during schema configuration.

Wetroo OBD call records are extracted via the /api/v1/?apirequest=obd_record endpoint. Each OBD record maps to an Odoo crm.phonecall record — call duration, disposition, caller number, timestamp, and linked partner. Odoo requires the crm_phonecall module (part of Odoo's extra-apps suite) to be installed; we confirm this is available in the destination Odoo version before migration.

WhatsApp message threads are extracted from Wetroo's conversation API. We write message content, sender/receiver, timestamp, and message type as mail.message records linked to the res.partner record. Media attachments (images, documents) require a separate download step — we export them to cloud storage and provide re-upload instructions for the admin. Odoo's native WhatsApp Business API connector must be configured post-migration for ongoing message sync.

Email activities migrate as mail.message records with subtype comment linked to the res.partner. Notes migrate as mail.message with subtype note. Tasks migrate as crm.phonecall or project.task depending on whether they are CRM-linked or project-scoped. Calendar events migrate as calendar.event with attendee data mapped to calendar.attendee records linked to the res.partner or crm.lead.

Custom fields on Wetroo Leads, Contacts, and Deals require pre-creation in Odoo as ir.model.field entries before any data import. We create fields during schema setup using Odoo's ir.model.data API, matching Wetroo's field types (Char, Text, Integer, Float, Selection, Many2one, Date, DateTime) to their Odoo equivalents. Picklist and multi-select values on Wetroo become Selection or Char fields in Odoo; value-label mapping is applied during the transform step.

Wetroo user records (name, email, role, team assignment) map to Odoo res.users. We resolve owners by email match against the destination Odoo instance's User table. Any Wetroo owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId (user_id) references are required on crm.lead and res.partner.

Wetroo lead and contact tags migrate to Odoo crm.tag records. We create the tag in Odoo during schema setup, then write crm.lead.tagrel records linking each lead or opportunity to its tags. Tags used for lead classification or segmentation in Wetroo map directly to Odoo's tag taxonomy, which appears in the Kanban pipeline view as filterable tag chips.

Wetroo drip sequences and sales automation cadences live in the automation layer with no exportable schema or API endpoint. We do not migrate them as code. We deliver a written inventory of every active sequence — trigger conditions, step types, delays, and contact list membership — that the customer's Odoo admin rebuilds using Odoo Studio, ir.actions.server, or a sales engagement module. The contact lists exported from Wetroo serve as the audience for rebuilding these sequences.