Migrate from Bright to Odoo CRM

Bright contacts map directly to Odoo res.partner records with type='contact'. The company_id field is set by resolving Bright's primary company association via the contact-to-company link table. If a Bright contact has no associated company, the contact lands as a standalone res.partner with no parent_id set. Email and name fields are transferred as-is to maintain contact identity.

Bright companies map to Odoo res.partner records with type='company'. The company_id on child contacts points to this record's id. Parent-child company hierarchies in Bright map via res.partner's parent_id field, preserving organizational structure. Industry, website, and employee count are transferred to the corresponding Odoo fields on the res.partner record.

Bright deals map to Odoo crm.lead records where type='opportunity'. The crm.lead.name field holds the deal name, expected_revenue holds the amount, and team_id routes the record to the correct Odoo sales team. Close date maps to date_deadline, and probability values are transferred to maintain deal scoring consistency across the migration.

Bright contacts that have not yet entered a deal map to Odoo crm.lead records with type='lead'. These records can later be converted to opportunities via Odoo's 'Convert to Opportunity' action, which creates a res.partner if needed and links the lead to the new opportunity record. Original Bright lifecycle_stage values are preserved in a custom field for reference.

Each Bright pipeline becomes an Odoo crm.team. The crm.team defines the sales team, its member list, and the pipeline view. Stage records (crm.stage) are created under each team with the Bright stage names as stage names. Team_id on crm.lead records routes opportunities to the correct team-based Kanban view in Odoo.

Bright stage names map to Odoo crm.stage records by team. Probability values and sequence orders are preserved. Custom stage colors from Bright are not transferable and must be reconfigured in Odoo's Studio. Stage IDs are recorded in the migration config for explicit mapping during the lead migration phase.

Bright activity records map to Odoo crm.activity entries logged against the crm.lead, and mail.message records for the communication history. Original timestamps and owner_id are preserved via the Odoo mail.message model. Activity type (call, email, meeting) is stored in the crm.activity.activity_type_id field using Odoo's activity type configuration.

Bright notes migrate as Odoo mail.message records with subtype='note' attached to the corresponding res.partner or crm.lead. Rich-text formatting is preserved as HTML in the body field. Author information is set to the migrated Odoo user who owns the note, with create_date matching the original Bright note timestamp for audit continuity.

Bright file attachments are downloaded and re-uploaded to Odoo as ir.attachment records with res_model set to 'crm.lead' or 'res.partner' and res_id referencing the target record. The original filename and file content are preserved. Attachment metadata including create_date and author is transferred to maintain document provenance in the Odoo filestore.

Bright custom fields must be pre-created in Odoo Studio before migration. FlitStack generates a field creation plan naming each custom field's Odoo model (crm.lead or res.partner), field type (char, selection, float, etc.), and any required selection values. Data is then mapped into these custom fields during the migration run. Selection field values include the full Bright pick-list options for dropdown compatibility.

Bright owner IDs are resolved by email matching against Odoo res.users records. Unmatched owners are flagged before migration; your team either invites them to Odoo first or assigns records to a fallback Odoo user designated during pre-flight. Owner resolution failures prevent data integrity issues by ensuring every migrated record has a valid user_id reference.