Migrate from OplaCRM to Odoo CRM

OplaCRM Accounts map to Odoo CRM res.partner records with is_company = True. The Account name becomes partner display_name, and address fields map directly to Odoo's street, city, state, zip, and country fields. External ID from OplaCRM is preserved as an Odoo external ID so that Contact records can resolve the parent account at import time. We create res.partner records before any Contact import so the parent link is satisfied at insert time.

OplaCRM Contacts map to Odoo CRM res.partner records with is_company = False. Email is used as the dedupe key; if a res.partner with the same email already exists, we attach the Contact data to the existing record. The parent_id on the res.partner points to the Account-derived res.partner created in the prior phase. Role fields from OplaCRM migrate as a custom contact_type selection field if needed.

OplaCRM Opportunities map to Odoo CRM crm.lead records. We split by stage: OplaCRM opportunities with stage = CLOSE_WON migrate as Odoo crm.lead with type = opportunity and stage mapped to a won stage in the Odoo sales team pipeline. CLOSE_LOST stages map to lost. Active pipeline stages map as open leads with type = opportunity. The OplaCRM healthscore value migrates as a custom float field opla_healthscore__c on crm.lead for reporting continuity. The opportunities_joint_id UUID is preserved in a custom char field opla_joint_id__c for the team to resolve manually or via Odoo Studio.

OplaCRM links joint or co-selling opportunities using opportunities_joint_id, a UUID field that is not a standard linked-opportunity pattern. We preserve this UUID as a custom field opla_joint_id__c on crm.lead in Odoo. The team receives a pre-flight report listing every pair of opportunities that share the same joint UUID so they can decide whether to use Odoo Studio to create a custom many2many relationship, a project-linked-opportunity module from the Odoo AppStore, or handle joint deals manually in the opportunity name or description. We do not silently discard the relationship.

OplaCRM Products map to Odoo product.product records. Product name, SKU (hs_sku equivalent), and list price migrate to name, default_code, and lst_price respectively. If OplaCRM stores pricing differently from Odoo's price book model, we flag this during pre-flight review and surface the discrepancy for the customer's admin to align before import.

OplaCRM Invoices created via CreateOpportunityInvoiceDto map to Odoo account.move records with move_type = out_invoice. Invoice amount, date, and status migrate to amount_total, invoice_date, and payment_state respectively. Invoice numbering schemes between systems may require explicit remapping during pre-flight; we flag any numbering conflicts and propose a remapping strategy.

OplaCRM CustomFieldValueDto key-value pairs migrate as Odoo ir.model.fields custom field definitions. We create each field in Odoo's technical settings with an appropriate field type (char, selection, text, float, date) before importing data. Any key that collides with an existing Odoo field name is prefixed with opla_ and surfaced in the pre-flight mapping table so the customer's admin can rename or merge before final cutover.

OplaCRM stage names stored as plain string enums in sale_process_stage map to Odoo crm.stage by display label. CLOSE_WON and CLOSE_LOST are mapped explicitly to the terminal won and lost stages in the Odoo pipeline so closed deals land in the correct terminal state. Probability percentages from OplaCRM map to stage_sequence order in Odoo; the customer configures the visual pipeline Kanban stage order post-migration.

OplaCRM locked records carry a boolean lock flag that prevents editing. In Odoo CRM, we set write_uid and create_uid restrictions on the crm.lead record so that only the admin or the original creating user can modify the record. If the customer does not have Odoo Studio or custom access rights configured, we create a custom boolean field opla_locked__c and surface it in the post-migration handoff so the admin can implement the appropriate access restriction.

OplaCRM tags stored as label arrays on records migrate to Odoo crm.tag records with tag names preserved. We split any comma-delimited tag strings into individual crm.tag entries and create crm.lead.tag.rel link records during import. The customer receives a tag consolidation report if duplicate or near-duplicate tags are detected.

OplaCRM attachments referenced by URL or file ID are downloaded and re-uploaded as Odoo ir.attachment records linked to the parent crm.lead or res.partner. Large binary attachments may require extended migration windows or a staged file transfer approach. We flag any attachments that exceed 25 MB during pre-flight so the customer can plan accordingly.

OplaCRM Users map to Odoo res.users records by email match. Any OplaCRM owner referenced on an Opportunity, Contact, or Account without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments migrate as user_id on crm.lead and responsible_id on res.partner.