Migrate from Bluwave CRM to Odoo CRM

Bluwave Contact records with a link to a Bluwave Company map to a single Odoo res.partner record with company_type=contact and parent_id pointing to the merged Company partner. Contacts without a Company link map to res.partner with company_type=contact and no parent_id. Email, phone, mobile, address fields map directly. The Bluwave geocoded latitude/longitude appends as custom fields latitude and longitude on res.partner. We resolve the parent-company lookup before inserting Contact partners because parent_id is a required foreign key on the relationship.

Bluwave Company records map to Odoo res.partner with company_type=company. The company name becomes the partner name, industry maps to industry_id via Odoo's industry picklist, and address fields map directly. This record is inserted before Contact records so that the parent_id lookup is satisfied at import time. Duplicate companies (same name) are deduped by name normalisation before insert.

Bluwave Leads map to Odoo crm.lead records with type=lead. Source attribution (how the lead entered) maps to medium_id, and lifecycle stage maps to tag_ids or a custom stage field we create during schema setup. Lead priority and rating map to priority and tag_ids on crm.lead. Owner assignment maps to user_id via email-match lookup against Odoo res.users.

Bluwave Deals map to Odoo crm.lead with type=opportunity. Deal value maps to planned_revenue, expected close date maps to date_deadline, stage name maps to stage_id via Odoo's crm.stage lookup, and owner maps to user_id. The associated Bluwave Contact becomes the partner_id on the Opportunity; the associated Bluwave Company becomes the partner_id parent or is resolved via contact_id. We configure the Odoo pipeline stages before migration so that stage_id references are satisfied.

Bluwave pipeline stage names and reorder logic are extracted during scoping and recreated as Odoo crm.stage records within the target team's pipeline. Stage probability percentages are stored on crm.stage as probability. Each Odoo crm.team gets its own stage sequence. If Bluwave uses multiple pipelines, we create multiple crm.team records in Odoo with separate stage sets.

Bluwave face-to-face activities map to Odoo mail.activity records linked to the migrated crm.lead (opportunity) or res.partner. Activity type picklist values (Call, Meeting, Site Visit) are mapped to Odoo's activity_type taxonomy during scoping. Geocoded latitude/longitude from the Bluwave activity record is stored as custom fields on mail.activity since Odoo has no native visit-location feature. Travel claim associations are preserved as a note attachment or a custom field link.

Bluwave custom fields are inferred from exported sample data during scoping — we infer the data type (text, number, date, picklist) from content patterns and validate with a small batch before committing the full load. Each custom field becomes a custom ir.model.fields entry on the relevant Odoo model (res.partner, crm.lead, or mail.activity). Picklist values in Bluwave become selection fields or ir.model.fields.selection entries in Odoo.

Bluwave Owner records are matched to Odoo res.users by email address. We extract every distinct owner referenced on Contact, Company, Deal, and Activity and create a reconciliation queue for any that have no matching Odoo user. The customer's Odoo admin provisions missing users before record migration resumes because user_id is a required foreign key on crm.lead and a displayed field on res.partner.

Bluwave file attachments on Deals and Contacts do not export via Excel. We extract them separately via the Bluwave web interface where accessible, mapping file names and linked record IDs. Each attachment becomes an ir.attachment record in Odoo linked via res_model and res_id to the target res.partner or crm.lead. Binary attachment volume is estimated during scoping to determine whether a separate file-storage step is required.

Bluwave mail list segments and their member Contact associations are migrated to Odoo mailing.list and mailing.contact records. The mailing.list name maps from the Bluwave segment name, and mailing.contact records are created from each member Contact. Email campaign history (send logs, open rates) does not transfer; we note the segment structure for the customer to rebuild campaign sends in Odoo's Email Marketing app post-migration.

Bluwave stores the Company-Contact relationship as a linked pair. In Odoo, the equivalent is the parent_id field on res.partner. We build a lookup table from the Bluwave export linking each Contact to its parent Company, then set parent_id on each Contact partner during import. This preserves the account hierarchy that sales reps use to navigate from a contact up to its parent company in Odoo's kanban and list views.

Bluwave geocodes addresses at entry, appending latitude and longitude to customer addresses and to face-to-face activity records. These are forward-geocoded approximations, not GPS captures at visit time. We preserve them as custom float fields on res.partner (for customer address location) and on mail.activity (for visit location). We flag these values for customer review because they represent approximate geocoding, not actual travel routes, and any travel claim accuracy depends on this distinction.