Migrate from Breeze ERP to Odoo ERP

Breeze Company records map to Odoo res.partner with partner_type set to 'contact' and company_type set to 'company'. The Breeze company name becomes res.partner.name, and we extract the primary address, phone, and email from the HTML export into the corresponding Odoo partner fields. If Breeze stores multiple contacts per company, we flatten them as separate res.partner records with parent_id set to the company record. Dedupe key is partner name and phone. Indian address formats (door, street, city, state, PIN) are parsed and mapped to Odoo's street, street2, city, state_id, zip, and country_id fields.

Breeze Vendor records map to Odoo res.partner with supplier_rank = 1 and partner_type = 'contact'. Vendor name, address, and contact details follow the same field mapping as Customers. We extract payment terms from the vendor master if present and set res.partner.property_supplier_payment_term_id accordingly. If Breeze stores a vendor-specific GL account for AP, we hold that as a custom field vendor_ap_account__c for the customer's admin to map during Odoo Chart of Accounts configuration.

Breeze Items map to Odoo product.template as the canonical record (name, type, default_code, list_price, standard_price, categ_id) and product.product as the storable variant if the item has attributes. We extract item type (inventory, non-inventory, service) from Breeze's export and set product.template.type to 'product', 'consu', or 'service' in Odoo. The Breeze SKU becomes product.template.default_code. If Breeze tracks variant attributes (size, color), we decompose them into Odoo product.attribute and product.attribute.value records and create product.product variants under the template.

Breeze account codes and names extract from the GL export and map to Odoo account.account with account_type set according to Odoo's taxonomy (asset_current, asset_non_current, liability_current, liability_non_current, equity, revenue, expense). Breeze's account_type classification in the export (Asset, Liability, Income, Expense) guides the mapping. We load account.account in account_type order so that parent_id references on account groups are satisfied at insert time. If Breeze uses Indian accounting conventions (TDS, TCS, GST), we map to Odoo's India localization account codes and flag the customer for GST configuration in Odoo Accounting.

Breeze BOM records map to Odoo mrp.bom with bom_line records for each component. The finished product from Breeze's BOM header becomes mrp.bom.product_id (or product_tmpl_id for product variants). We extract unit of measure from Breeze's item master and map to Odoo's uom.uom model. If Breeze BOMs have operation steps (routing), we map them to mrp.workcenter and mrp.routing.workcenter records in Odoo MRP. Multi-level BOMs (sub-assemblies) are decomposed into a flat BOM with nested sub-boms referenced via mrp.bom_line.bom_id.

Breeze work orders map to Odoo mrp.production as manufacturing orders. We extract product_id, product_qty, bom_id (resolved via product match), and planned/actual start and end dates. Work center assignments from Breeze become mrp.production.workcenter_line entries linked to mrp.routing.workcenter. The work order state in Breeze (draft, confirmed, in_progress, done, cancelled) maps to Odoo's state field (draft, confirmed, progress, done, cancel). Historical closed work orders migrate with state=done.

Breeze Project records map to Odoo project.project. Project name, description, start date, and deadline migrate directly. We extract assigned users from Breeze and match by email to Odoo res.users. If Breeze tracks project tasks within the project, we create project.task records as children. Billable flag and project type map to Odoo's allow_billable and project_type fields. Timesheet data linked to Breeze projects migrates to account.analytic.line with project_id set.

Breeze Purchase Orders map to Odoo purchase.order with lines in purchase.order.line. Vendor reference maps to res.partner (supplier). PO lines reference product.product via the Item lookup, with product_qty, price_unit, and taxes mapped to Odoo's purchase.order.line model. PO state (draft, confirmed, done, cancelled) maps to Odoo's state field. If Breeze stores received quantities separately from PO quantities, we create stock.picking records to reflect actual inbound receipts.

Breeze inventory snapshots (on-hand quantities per item per location) map to Odoo stock.quant with inventory_date set to the snapshot date. We extract location from Breeze's warehouse structure and map to Odoo stock.location records (Internal Locations scoped to the company). If Breeze tracks lot or serial numbers, we create stock.production.lot records and link them to stock.quant via lot_id. Negative stock quants in Breeze migrate as on-hand with inventory adjustment flagged.

Breeze journal entries (debit/credit postings) map to Odoo account.move with line entries in account.move.line. Each account from Breeze's GL is matched to account.account via account code. We extract entry date, journal, period, and narration. Breeze's journal name format maps to Odoo's move_name field. If Breeze entries reference a document number (invoice number, PO number), we preserve it in account.move.ref. Entries are imported with date_order = the original posting date, and state = 'posted' if the source entry was posted, 'draft' if draft.

Breeze user and employee records map to Odoo res.users by email match. Active status, login, and display name migrate. Employee-specific data (department, designation, reporting manager) requires the Odoo HR app to be installed; if not present, we hold employee fields as custom fields on res.partner for future HR onboarding. Owner references on Breeze records (projects, work orders) resolve via this user mapping.