Migrate from Basic Online CRM to Odoo CRM

Basic Online CRM Contact records map to Odoo res.partner. The source name, email, phone, and address fields map directly. Basic Online CRM custom fields migrate as char, selection, or float fields on res.partner, created in Odoo Studio before import. Partners flagged as company contacts in Basic Online CRM set the is_company checkbox on the Odoo partner record. Email address uniqueness is the dedupe key during import; duplicate emails trigger a skip with a flag for manual review.

Basic Online CRM Company records map to Odoo res.partner with is_company = True. The source company name maps to the partner name field, domain/website to website, and any company-level custom fields to partner fields. If a Basic Online CRM Company shares a name with an existing Odoo partner record, we flag it as a potential duplicate for customer resolution before committing the import.

Basic Online CRM Deal records map to Odoo crm.lead in the Opportunity stage (not the Lead stage). The Deal name becomes crm.lead name, amount becomes planned_revenue, and pipeline stage maps to stage_id via a stage-name lookup we run against the Odoo pipeline configuration before import. Closed-won Deals set the probability to 100 and stage to the Odoo closed-won stage; closed-lost sets probability to 0.

Basic Online CRM exports Deals with Contact linked by internal numeric ID, not by email or name. We run a dual extraction: Contacts first (capturing id and email/name), then Deals (capturing id and contact_id). During the transform phase, we cross-reference every contact_id against the extracted contact list, resolving to partner_id. Deals where contact_id references a deleted or absent Contact are flagged as orphaned Deals and held in a reconciliation queue; we do not create them without a resolved partner.

If Basic Online CRM Deal records also reference a Company by internal ID, we resolve both associations during the same transform pass. Odoo crm.lead allows only one partner_id (Contact) and one partner_assigned_id (salesperson), so Company is informational and stored in a custom char field if it does not align with the Contact's company partner.

Basic Online CRM Notes are free-text and untyped with no explicit timestamp. We map them to the description field on the related crm.lead. If the Note has an explicit creation date, we store it as a custom date field and note it in the migration report. If the customer requires threaded note history, we optionally create mail.message records with note subtype, linked to the crm.lead via res_id and model fields.

Basic Online CRM custom fields are stored as untyped strings on export. We ask customers to confirm intended data types (date, number, dropdown, text) during scoping. We pre-create the fields in Odoo Studio with the confirmed types before any data import. Date fields in particular may export with inconsistent formatting (Jan 15 2024 vs 15/01/2024); we apply a standardisation transform pass before writing.

Basic Online CRM does not surface Owner assignment in its exports. We ask customers upfront which team member should own migrated records in Odoo. If multiple Basic Online CRM users exist, we extract unique user references from Deal and Note records and match them to Odoo res.users by email during the transform phase. Unmatched users are held in a reconciliation queue for the customer's Odoo admin to provision before the write-back phase continues.

If the Basic Online CRM instance contains task records (title, status, no assignee), we migrate them to Odoo mail.activity linked to the related crm.lead. activity_type_id maps to Odoo's standard activity types (Email, Call, Meeting, To Do). Odoo requires an activity_type_id and a res_model reference; we set res_model to crm.lead and resolve the res_id from the parent Deal mapping.

Basic Online CRM pipeline stages (up to 5 on Free, more on paid tiers) map to Odoo crm.stage records within the default CRM team. We query the existing stage configuration in the destination Odoo database, map each source stage name to the nearest matching Odoo stage, and create any missing stages via the Odoo interface or XML-RPC before Deal import begins.

Basic Online CRM tag values stored on Contacts, Companies, or Deals migrate to Odoo crm.tag records. Tags are created on-demand during the transform phase (deduped by name), then linked via crm.lead.tag_ids many2many field. If Basic Online CRM tags are free-text without a dedicated tag field, we create a custom many2many field on crm.lead for them.

If Basic Online CRM stores a Contact's parent Company as a linked Company record (rather than a field on the Contact), we resolve that relationship during the partner import pass and set the child Contact's parent_id to the company partner ID. Odoo enforces that parent_id points to an is_company partner; we validate this constraint before writing and flag any violations.