Migrate from Wetroo to Odoo CRM

Wetroo Contact records map directly to Odoo res.partner with partner_type set to 'contact'. The Wetroo name, phone (stored as mobile or phone), and email map to the corresponding Odoo partner fields. Custom fields on Wetroo Contact are created as ir.model.fields on res.partner before migration. We extract contacts via the Wetroo contact list API endpoints and insert via Odoo's XML-RPC or csv import, using email as the dedupe key where available.

Wetroo Lead records map to Odoo crm.lead with type='lead'. The Wetroo lead_status, lead_source, and qualification_score migrate to crm_lead custom fields or Odoo's built-in priority and tag fields. We preserve the original Wetroo lead identifier in a custom field wetroo_lead_id__c for audit traceability. Leads without an email are stored with phone as the primary identifier in Odoo's phone index.

Wetroo Deals map to Odoo crm.lead with type='opportunity'. The deal_value maps to Odoo's planned_revenue. The Wetroo deal stage maps to the corresponding Odoo crm.lead.stage_id entry by sequence order, not name match, because stage names are customer-defined. We compute the mapping during scoping by querying the stage sequence in Wetroo and matching by position to Odoo's stage list. The Wetroo deal owner maps to Odoo user_id on the crm.lead.

Wetroo pipelines map to separate stage sequences in Odoo crm.lead.stage. If Wetroo has multiple pipelines, we create multiple stage sequences by setting the pipeline_id on the stage records. Wetroo stage names and their WhatsApp workflow trigger associations are preserved as custom fields on the stage records in Odoo for the customer's admin to reference when rebuilding automations.

Wetroo stage sequence and names are customer-defined and tied to WhatsApp workflow triggers. We map stage order by sequence number, not by name, and set the probability percentage on each Odoo stage to match the original Wetroo stage probability where recorded. Any stages with no clear Odoo equivalent are flagged during scoping and mapped to a catch-all stage with a custom note.

Wetroo custom fields on Contact, Lead, and Deal are discovered via the API before migration. We create matching field definitions in Odoo using Studio (for no-code) or direct ir.model.fields XML-RPC creation, matching field types (char, selection, relational, text) to Odoo's field type system. Selection fields in Wetroo become selection fields in Odoo with the same option values. Relational fields (e.g., linking a Deal to a custom object) require the target custom object to be created first.

Wetroo owners (assigned to Deal and Lead) are extracted with name and email. We match by email against Odoo's res.users table. Any Wetroo owner without a matching Odoo User is placed in a reconciliation queue; the customer's Odoo admin provisions missing users before record migration resumes. Inactive Wetroo owners (departed team members) are mapped to inactive Odoo users with a flag field for admin review.

Wetroo team membership records are extracted as a relational export (owner + team name + member list). Odoo CRM Teams (crm.team) are created with the same team names. Member assignment maps to the crm.team member relation; individual members are linked via res.users membership. If Wetroo's per-owner model included sub-team hierarchies, we flatten them to a single team level in Odoo and flag the hierarchy for manual reorganization if needed.

Wetroo automation playbooks and WhatsApp-triggered sequences are JSON-configured workflows stored in Wetroo's system. We export playbook names, trigger conditions, action steps, and delay configurations as a structured reference document delivered alongside the migration. Odoo Server Actions and Automated Actions provide equivalent functionality, but the logic must be rebuilt by the customer's Odoo admin or an Odoo partner because trigger-event architectures differ between platforms.

Wetroo stores WhatsApp conversation metadata and chat transcripts in WhatsApp's infrastructure, not in Wetroo's own database. No export mechanism exists for conversation history via the Wetroo API or any data dump. We extract and migrate all structured Contact, Lead, and Deal records that originated from conversations, but the conversation threads themselves remain in WhatsApp. We advise customers to export critical chat history directly from WhatsApp before the migration cutover date.

Wetroo supports file attachments on Deal records. We extract attachments by referencing the deal ID, download the files, and upload them to Odoo ir.attachment records linked to the corresponding crm.lead via res_model='crm.lead' and res_id set to the migrated opportunity ID. File names and MIME types are preserved. Attachments exceeding 10 MB are flagged for manual review if Odoo file storage limits apply.

Wetroo's lead_status values (e.g., New, Contacted, Qualified, Lost) map to Odoo crm.lead.tag records as a tag set. If the customer uses a specific lead status taxonomy that exceeds what tags represent, we create a selection field lead_status__c on crm.lead and populate it during migration. The mapping is confirmed during scoping with the customer before any data transforms run.

Wetroo records a qualification_score on Lead records. We preserve this as a float field qualification_score__c on crm.lead, created as an ir.model.field before migration. If Odoo's CRM module has a built-in scoring model (available in Enterprise), the score migrates to the native scoring field; otherwise it remains as a custom field for reporting.

Wetroo records closed_won and closed_lost flags and optionally a closed_reason text on Deal. In Odoo, type='opportunity' crm.lead records set probability=0 for Lost and probability=100 for Won, with lost_reason_id populated from a predefined selection list. We create a custom lost_reason selection field if Wetroo's reason vocabulary does not map to Odoo's default options.