Migrate from Opal CRM to Odoo CRM

Opal CRM Leads map directly to Odoo crm.lead records. We set type=lead for unqualified prospects and type=opportunity once the lead has a quoted value or assigned opportunity in Opal. The crm.lead name field maps from Opal lead name, email maps to email_from, phone maps to phone, and the lead source attribution from Opal becomes a custom tag or stage origin field on crm.lead. We preserve any custom field values Opal exports asChar or asText fields mapped to equivalent crm.lead custom fields created via Odoo Studio before import.

Opal CRM Sales Reps map to Odoo res.users. The res.users login maps from the Opal rep email, name maps from the rep display name, and access rights are set to sales / user: the default Odoo CRM access for a sales representative. Role permissions (Admin, Manager, Sales Rep) in Opal do not export as structured data; we capture the role assignment per user and document it in the handover notes so the Odoo admin assigns the equivalent access rights (Settings > Users > Access Rights) after migration.

Opal CRM Companies attached to Leads map to Odoo res.partner with partner_type set to company. The company name maps to the partner name field, domain maps to website, and any contact person within the company becomes a separate res.partner record with parent_id pointing to the company partner. We use the company name or domain as the dedupe key during import to avoid creating duplicate partner records.

Tour Plans store both itinerary data and expense line items, which require a two-part migration. The tour itinerary (dates, locations, assigned rep) migrates as a crm.lead record with type=opportunity and a custom visit_date field, treating each Tour Plan as a planned field visit. Individual expense line items are extracted and migrated as account.move records (expense entries) with analytic account tags so the customer's accountant can reconcile them post-migration. If Opal exports Tour Plans as a flat record with expense items collapsed into a notes field, we decompress the expense data and reconstruct structured transaction rows before Odoo load.

Opal CRM Quotations map to Odoo sale.order. The quotation header fields (customer reference, date, validity, payment terms) map to sale.order fields; line items (product, quantity, unit price, tax) map to sale.order.line. We resolve the Opal customer reference to a res.partner id and the Opal product name or SKU to a product.product id before inserting. Opal's quotation workflow approval state is captured in a custom field opal_workflow_state__c on the sale.order and documented for the admin to translate into Odoo's sale.advance.payment.inv workflow or a custom approval module.

Opal quotation line items map to Odoo sale.order.line. We map product reference (name or SKU) to product_product, quantity to product_uom_qty, unit price to price_unit, and any discount percentage to discount. Tax handling depends on whether Opal stores tax codes or tax amounts: tax codes are mapped to account_tax ids in Odoo; amounts are stored as price_unit inclusive of tax with a flag note. If Opal does not export product SKUs, we match by product name string to the nearest Odoo product_product record and flag any unmatched lines for manual mapping.

Opal CRM pipeline stage names and ordering migrate to Odoo crm_stage records within the CRM app. We set stage.name from the Opal stage label, stage.sequence for ordering, and stage.is_won or is_closed based on whether the Opal stage represents a closed-won or closed-lost state. Stage probability percentages migrate to stage.probability. If Opal exports pipeline stage as a string property on the lead rather than a separate object, we query all distinct values and create crm_stage records during Odoo configuration before lead import begins.

Opal CRM call engagement logs map to Odoo mail.activity records with activity_type_id set to the built-in Call type (or a custom call type created in Odoo Settings > Technical > Activity Types). Call duration maps to a custom duration field on the activity; call disposition or outcome maps to note or a custom picklist field. We link the activity to the corresponding crm.lead (WhoID) via activity.res_model=crm.lead and activity.res_id pointing to the migrated lead id. Activity date maps from the Opal call timestamp.

Opal CRM email engagements map to Odoo mail.message records on the crm.lead. The email subject becomes message_subject, body becomes body_html (stored as HTML fragment), and sender maps from the Opal rep email to mail.message.author_id. We set message.message_type=email and link to the crm.lead via res_model=crm.lead and res_id. If Opal exports email content as plain text, we wrap it in HTML before storing in Odoo's message body field.

Opal CRM meeting engagements map to Odoo calendar.event records. The meeting title maps to name, start datetime maps to start, end datetime maps to stop, location maps to location, and attendee list maps to partner_ids (resolved via email to res.partner ids). We link the calendar.event to the crm.lead via custom context field or an activity record so that the meeting appears in the lead's activity timeline. Recurrence patterns from Opal do not migrate and are noted in the handover document for manual Odoo calendar recurrence setup.

Opal CRM task engagements map to Odoo project.task records linked to a default CRM project (project_id set to the CRM project's internal id). Task title maps to name, due date maps to date_deadline, priority maps from Opal priority to task priority, and description maps to description. Assigned user maps from Opal rep to res.users. Tasks without a due date are imported with no date_deadline set. If the customer's Odoo instance does not have Project installed, we fall back to storing tasks as mail.activity records instead.

Opal CRM custom fields discovered during discovery do not have a publicly documented schema, so we identify them by comparing the Opal export header row against the known Opal standard field set. Any non-standard columns are treated as custom. We create matching custom fields in Odoo via Settings > Technical > Database Structure > Models, appending x_ prefix to the field name, matching the field type (char, text, integer, float, date, select, multiselect) based on the export data. Custom fields are created before any data import to ensure the Odoo import wizard accepts the mapped values without type errors.

Opal CRM role assignments (Admin, Manager, Sales Rep) do not export as structured permission records. We capture the role assignment per user from the Opal team member list and document it in the handover notes. The Odoo admin recreates the permission set by assigning res.groups (Settings > Users > Access Rights) or by creating custom access rights groups via Settings > Technical > Access Rights > User Types. The mapping table we deliver lists each migrated user, their Opal role, and the recommended Odoo group (e.g., Opal Admin > Sales / Manager, Opal Sales Rep > Sales / User).

If Opal CRM tracks lead source (form, campaign, event, manual) as a property on the lead record, we map it to Odoo's utm.source and utm.medium tracking fields linked to the crm.lead record. We create corresponding utm.source records (one per distinct Opal source value) during Odoo configuration and link each migrated lead to its source via the lead.referrer_id field. This enables the customer to continue using Odoo's native campaign attribution reporting post-migration.

Opal CRM Basic and Standard plans include a sales performance tracking feature using a points or rewards system. This is a platform-specific gamification concept with no Odoo standard equivalent. We capture any point balance, rank, or reward data as a custom field on the crm.lead or res.users record and document the current values in the handover report. The customer's admin decides whether to continue using the gamification model via Odoo gamification challenges or to retire it as a reporting artifact.