Migrate from Oncourse CRM to Odoo CRM

Oncourse Leads migrate directly to Odoo crm.lead records. The lead source and status properties from Oncourse map to Odoo's source_id (crm.lost_reason reference) and stage_id fields. We preserve the Oncourse lead score if exposed via the export as a custom float field on the Odoo lead. Lead priority maps to crm.lead priority selection.

Oncourse Contact records migrate to Odoo res.partner records. The partner_id field in Odoo CRM Links to a separate Partner record for organization data; we extract the organization value from Oncourse Contacts, create the Odoo Partner first, then link the Contact res.partner record via parent_id (for personal vs company contacts). Name, email, phone, and address fields map directly without transformation.

Oncourse may associate contacts with organization names stored as a Contact property rather than a distinct Account object. We extract the distinct organization values from all Oncourse Contacts, create Odoo res.partner records with partner_type set to company, then update the Contact-level partner records to reference the parent company via parent_id. If Oncourse has no separate Companies object, this N:1 merge creates the account hierarchy in Odoo that the flat Oncourse model lacks.

Oncourse Deals migrate to Odoo crm.lead records in the Opportunity stage. Deal name, value, and stage map to Odoo's name, expected_revenue (stored as float), and stage_id. Owner assignment from Oncourse maps to Odoo user_id via email-match resolution against the Odoo res.users table. Closed-Lost and Closed-Won states from Oncourse stage names map to Odoo lost and won stage values.

Oncourse pipeline stage names are extracted during scoping and mapped to Odoo crm.stage records within the relevant Odoo CRM team sequence. We create any missing stages in Odoo before Deal migration so that stage_id references are valid at import time. Stage probability values from Oncourse migrate to Odoo's stage probability field.

If Oncourse has multiple pipelines per account, we map each Oncourse pipeline to a separate Odoo Sales Team (crm.team) with its own stage sequence. Odoo Sales Teams provide team-level pipeline visibility and are available from Odoo 17 Community onward.

Oncourse Tasks linked to Deals migrate to Odoo project.task records. We create a project.task record per Oncourse task, set the crm.lead reference in the related_id or project_id field, and preserve status, priority, and due date. Tasks not linked to a Deal become standalone project.task records under a default migration project in Odoo.

Oncourse activity history stored as free-text notes on Deals migrates to Odoo mail.message records (chatter entries) attached to the relevant crm.lead. We parse the note body, create an Odoo mail.message with message_type = comment, and attach it to the corresponding Odoo Lead or Opportunity record. Note creation timestamp becomes mail.message's date field. This reconstructs the activity timeline in Odoo's native chatter model.

Custom fields on Oncourse Leads, Contacts, and Deals are mapped to Odoo custom ir.model.fields on the corresponding model (crm.lead or res.partner). Field data types from the onCourse DSL export (text, number, date, currency) map to the closest Odoo field type (char, float, datetime, monetary). We pre-create the custom fields in Odoo via the Settings > Technical > Custom Fields interface before data import so that target columns exist at migration time.

Oncourse Owner references on Deals and Tasks resolve to Odoo res.users records by email match. Any Oncourse Owner without a matching Odoo User is placed in a reconciliation queue; the customer's Odoo admin provisions the missing user before the relevant records import. This step gates Deal and Task imports because user_id is a required field on crm.lead in Odoo.

Oncourse Lead Source values migrate to Odoo crm.tag records if the customer uses tag-based lead source tracking, or to a custom selection field on crm.lead. We do not create new Odoo crm.lost_reason records for lead sources; we recommend a custom char or selection field to avoid conflating lead source with lost-reason tracking.

Oncourse CRM does not expose a public file attachment export via its standard import/export tooling. We cannot guarantee attachment migration in automated runs. We recommend a manual backup of the document storage in Oncourse before migration cutover. If the customer provides a manual export of attachments, we map them to Odoo ir.attachment records with res.model set to crm.lead or res.partner and res.id set to the migrated record ID.