Migrate from RETAINUSER CRM to Odoo CRM

RETAINUSER Contact records map to Odoo res.partner with partner_type = 'contact'. Standard fields (name, email, phone, street, city, country) migrate 1:1. Custom properties on RETAINUSER Contacts require Odoo Studio field creation in res.partner before migration, with types matched (text to char, number to float, picklist to selection). The RETAINUSER contact-to-company linkage is preserved via the partner_id many2one on res.partner.

RETAINUSER Leads map to Odoo crm.lead where type = 'lead' (not yet converted to an Opportunity). Lead source, lead status, and owner assignment migrate to crm.lead fields. If RETAINUSER stores leads as a status on the Contact object rather than a separate record type, we split them into crm.lead records during the transform phase. The customer decides during scoping whether leads without engagement history should be converted to Opportunities immediately or remain as Leads for re-qualification.

RETAINUSER Company records map to Odoo res.partner with partner_type = 'company'. Company name, website, industry, employee count, and address fields migrate directly. Companies are loaded before Contacts so that the parent partner_id can be resolved at Contact insert time, satisfying Odoo's foreign key constraints.

RETAINUSER Deals map to Odoo crm.lead where type = 'opportunity'. Deal name becomes crm.lead name, deal value maps to planned_revenue, owner maps to user_id by email resolution, and expected close date maps to date_deadline. Pipeline stage names from RETAINUSER are mapped to Odoo's stage_id during the transform; the Odoo CRM app must be installed and stages configured in Sales settings before Opportunities are loaded.

RETAINUSER pipeline configuration (stage names, order, win/loss criteria per pipeline) is extracted as a structured manifest and mapped to Odoo CRM stages and Sales Teams. Odoo's CRM module uses a single pipeline per Sales Team by default; multi-pipeline setups in RETAINUSER require Odoo Studio or developer-mode configuration to replicate. Stage probability percentages are mapped to Odoo's stage probability where applicable.

RETAINUSER Activity records are split by type: call engagements map to crm.phone.call (or generic mail.activity with activity_type = 'call' if the phone module is not installed); email logs map to mail.message records linked to the target partner or lead; meeting logs map to calendar.event; notes map to mail.message with note flag. All activities carry the original timestamp, owner attribution, and linked record reference. Note content migrates as mail.message body text.

RETAINUSER Owner records map to Odoo res.users by email resolution. Each distinct owner email referenced on Contact, Company, Deal, and Activity is matched against the Odoo destination's user table. Owners without a matching Odoo user are held in a reconciliation queue; the customer provisions missing users before record migration proceeds.

RETAINUSER email template bodies, subject lines, and merge field placeholders are exported as text assets. Merge field syntax is transformed from RETAINUSER's proprietary placeholder format to Odoo's QWeb or Jinja-style syntax before import into mail.template. Templates are migrated as text content; Odoo's template editor may require minor formatting adjustment post-migration for HTML-rendered templates.

SMS and WhatsApp templates from RETAINUSER are exported as plain-text message bodies. Character limits are noted for Odoo's SMS composer (160 characters per segment). Templates are migrated as sms.template records; if Odoo's SMS module is not installed in the destination, templates are delivered as a structured text artifact for manual re-creation in the customer's chosen messaging tool.

Custom fields on RETAINUSER Contacts, Companies, and Deals are extracted with field type, picklist values, and defaults. Each custom field requires pre-creation in Odoo via Studio (no-code) or developer mode (programmatic) before the migration loads data into it. Picklist values in RETAINUSER are mapped to Odoo selection options or many2one relations as appropriate. Fields that have no Odoo equivalent are flagged in the mapping document for the customer's admin to decide on disposition.

File attachments stored against RETAINUSER Contacts, Companies, or Deals are exported as individual files with their original filenames and MIME types. Each file is re-uploaded to Odoo's ir.attachment table linked to the corresponding res.partner, crm.lead, or other record via res_model and res_id. Large attachment batches are processed in a separate file migration phase after all records are loaded, to avoid blocking the record-import window.

RETAINUSER workflow rules (triggers, conditions, and action sequences) are documented as a structured JSON artifact covering every active automation. This artifact is delivered to the customer's Odoo admin for re-implementation in Odoo Automations (available via Studio) or server actions in developer mode. Note that Odoo deprecated its classic Workflow Engine in v17 in favor of Studio Automations and business domain triggers; any RETAINUSER workflows using deprecated Odoo patterns require re-design rather than a direct translation.