Migrate from BSI CRM to Odoo CRM

BSI Contact records map directly to Odoo Contact. Standard fields (name, email, phone, job title) migrate 1:1. The BSI Contact-Company relationship is preserved through Odoo's company_id link on Contact. Custom fields on BSI Contact are enumerated during discovery and pre-created as Odoo custom fields before data load. Any custom fields with no Odoo equivalent are flagged in the mapping document for manual review.

BSI Company records map directly to Odoo Company. Hierarchical parent-child structures are preserved as Odoo Commercial Partner or Contact hierarchy depending on the BSI configuration. Industry classification fields migrate as tag fields or custom fields in Odoo. Company is loaded before Contact so the company_id foreign key is satisfied at Contact insert time.

BSI Deal records map to Odoo CRM Opportunity. Deal stage maps to Odoo's pipeline stage names, which are configured in Odoo before migration using BSI's stage names from discovery. Deal value, expected close date, owner assignment, and pipeline assignment migrate directly. BSI custom deal fields are created as Odoo custom opportunity fields before import.

BSI pipeline and stage names vary by industry configuration. We enumerate all distinct pipelines and stages during discovery, then configure corresponding Odoo CRM pipelines and stages before migration. Stage order and probability percentages are translated to Odoo stage definitions. Multi-pipeline BSI configurations map to multiple Odoo CRM pipelines.

BSI logged calls, emails, meetings, and tasks migrate as Odoo CRM activities linked to the parent Contact or Opportunity via Odoo's res_model and res_id linking. Activity timestamps are preserved. Calls migrate with call disposition preserved in the activity description or a custom field. Meeting attendees are mapped to Odoo partner_ids on the activity record. Odoo Activity Mail Tracking is disabled during migration to prevent duplicate notifications.

BSI Owner records map to Odoo User by email address match. Owner is migrated first in the load sequence because all other objects (Contact, Company, Deal) reference Owner as a foreign key. Any BSI Owner without a matching Odoo User is placed in a reconciliation queue for the customer's Odoo admin to provision before the main import resumes.

File attachments associated with BSI Contacts, Companies, or Deals are exported individually and reattached in Odoo using ir.attachment records with res_model pointing to the target Odoo model (res.partner, crm.lead) and res_id pointing to the migrated record ID. BSI's file storage structure varies by configuration; we document the file-to-record linkage during discovery to ensure correct attachment re-association.

BSI tagging and custom classification fields that have no direct Odoo equivalent are mapped to Odoo Tags on the relevant model. Multi-value tags migrate as multiple tag assignments per record. The customer chooses tag strategy during scoping: direct tag migration or custom multi-select field recreation. Classification fields with structured picklist values migrate as Odoo selection fields or tags depending on the field type.

BSI custom objects are enumerated during the mandatory discovery phase (no public schema is available). We pre-create the destination custom model in Odoo with all custom fields, field types, and any lookup relationships to standard objects before data load. Custom object naming follows Odoo's ir.model naming conventions. Records with missing parent record references are held in a reconciliation queue until the parent object is available in Odoo.

BSI User records migrate as Odoo User with name and email preserved. Active/inactive status is preserved. Role and permission sets are documented during discovery as Odoo does not replicate BSI's role model directly; the customer's Odoo admin assigns Odoo access rights based on the documented BSI roles. Users are the first object loaded in production migration.

BSI notes associated with Contacts, Companies, or Deals migrate as Odoo CRM activities with the note body preserved in the activity note or description field, linked to the parent record via the standard Odoo activity model and res_id reference.

If BSI CRM includes a Lead object in the customer's configuration, we map it to Odoo CRM Lead. Odoo Lead records can be converted to Opportunities and Contacts at any time via Odoo's Lead Conversion action, preserving the original BSI lead score if present as a custom field.