Migrate from BigChange to Odoo CRM

BigChange Persons map to Odoo res.partner records. The partner is created with type 'contact'. Email, phone, and address fields migrate directly. Owner assignment in BigChange resolves to Odoo user_id by email match — unmatched owners flagged before migration so you can invite them to Odoo first.

BigChange Companies map to res.partner records with type 'company'. Domain, industry, employee count, and financial details migrate as fields on the company partner record. Multi-address records in BigChange require Odoo's child contact pattern (each location as a child partner linked via parent_id).

BigChange Jobs are the core operational record — they carry customer, site, status, assigned engineer, and financial data. We map Jobs to Odoo crm.lead with type='opportunity'. Job status values (scheduled, in-progress, completed, invoiced) map to Odoo pipeline stages — each unique BigChange job status requires a corresponding crm.stage created in Odoo before import, since stage names are Char fields with no enforced pick-list.

Jobs with associated BigChange quotes generate two Odoo records: the Job itself as an Opportunity (crm.lead) capturing the commercial context, and the Quote as a sale.order linked via the Opportunity's order_ids field. The quote's agreed rates, line items, and financial totals populate Odoo's sale.order lines. This is the highest-complexity mapping because it touches two Odoo models with foreign-key relationships.

BigChange quotes map to Odoo sale.order records in draft state. Quote number becomes name. Line items map to sale.order.line with product, quantity, and price from the agreed rates. Quote status (sent, accepted, rejected) maps to Odoo's sale.order state (draft, sent, sale_order, cancel). Custom fields on BigChange quotes require Odoo custom fields on sale.order — pre-creation required.

BigChange job types classify the work being performed. We map job types to crm.lead.tag records and attach them to the corresponding Opportunity. A job with multiple types generates multiple tags. Tags are a simple many-to-many relationship on crm.lead, making this a low-friction mapping.

BigChange custom fields defined on quotes are extracted as name/value pairs. Each custom field requires an Odoo custom field created on crm.lead or sale.order before migration (via Settings > Technical > Models in Odoo Studio or via Python code). FlitStack delivers a custom field creation plan as part of the pre-migration schema setup. Note: Odoo's lead-to-opportunity conversion does NOT auto-propagate custom fields from crm.lead to res.partner — this requires a custom module override using _convert_opportunity.

BigChange financial documents (invoices, payments) map to Odoo account.move records. Invoice number, date, amount, and status migrate. Odoo's accounting module must be installed for this mapping to function — we require confirmation of Odoo module stack before planning this object. Account codes and tax configuration must be verified against your Odoo chart of accounts.

BigChange alert rules (job reminder triggers, overdue notifications, status-change alerts) have no Odoo equivalent that migrates automatically. We export the rule definitions as a structured reference document so your Odoo admin can rebuild them as CRM automation rules (Settings > Automation > CRM Rules) or server actions. This is a rebuild item, not a data migration item.

Files attached to BigChange jobs or quotes are downloaded and re-uploaded to Odoo's ir.attachment model, linked to the corresponding crm.lead or sale.order via res_id/res_model. File size limits and Odoo storage configuration must be verified. Large file batches may require chunked upload with retry logic to handle transient API errors.

BigChange users (engineers, schedulers, admins) map to Odoo res.users. The mapping key is email address — FlitStack resolves each BigChange user to an Odoo user by email match. Unmatched users are flagged with their BigChange email so you can create the corresponding Odoo account before the full migration runs. Owner assignments on Jobs and Contacts resolve to user_id via this lookup.