Migrate from BizAutomation Cloud ERP to Odoo ERP

BizAutomation Organizations map to Odoo res.partner records with partner_type set to company. The company flag is set to true, and individual Contact records (linked to the Organization) become separate res.partner records with parent_id pointing to the Company record. We preserve Organization type (customer/vendor/prospect) in a custom partner_type field on res.partner.

BizAutomation Contacts map to Odoo res.partner with parent_id set to the corresponding Organization res.partner. Address fields (street, city, state, zip, country) migrate directly. Email, phone, and mobile map to standard Odoo fields. Custom Contact properties in BizAutomation require field-level mapping to res.partner custom fields that we create in Odoo during schema provisioning.

The GL Chart of Accounts is the highest-risk migration object because Odoo Accounting splits accounts receivable and accounts payable into separate reconcile-type accounts, requires account type classification (receivable, payable, equity, income, expense, other), and uses a fiscal position mapping table. We export the full BizAutomation account list, map each to an Odoo account type, set the reconcile flag for AR/AP accounts, and preserve account numbers as code for audit continuity. Opening balances for each account migrate as Odoo Account Move lines in a single opening entry.

BizAutomation Vendors map to Odoo res.partner with supplier=True and customer=False. Payment terms, fiscal position assignments, and purchase currency migrate to the partner record fields. Vendor records must exist in Odoo before Purchase Orders can be imported so that the supplier link is satisfied at line-item time.

BizAutomation Inventory Items map to Odoo product.product records with type=product. SKU, description, cost (Standard Price), sale price (List Price), and warehouse location (stock.location) migrate directly. On-hand quantity at migration snapshot date becomes an initial stock quant record. Custom item properties and matrix parent items require special handling: we create the product.template first, then generate product.product variant records with the correct attribute_value assignments.

BizAutomation matrix items store variant attribute combinations as generated child records under a parent item template. We extract the parent item's attribute definitions (color, size, etc.) and create corresponding Odoo product.attribute and product.attribute.value records, then generate one product.product variant for each unique attribute combination found in the BizAutomation child records. Quantity-on-hand for each variant maps to a stock.quant against the variant's product.product ID.

BizAutomation Sales Orders map to Odoo sale.order records with customer_id resolved to the res.partner, order lines resolved to product.product IDs, and tax IDs resolved to account.tax records via fiscal position mapping. Order status (open, fulfilled, cancelled) maps to Odoo state. Historical fulfilled orders import as sale.order in state=sale; open orders import in state=draft or sale depending on confirmation status.

BizAutomation Purchase Orders map to Odoo purchase.order with vendor_id resolved to the supplier res.partner. Order lines map to product.product IDs with vendor lead times preserved. PO state maps to Odoo's state field (draft, sent, purchase, done, cancel). Historical fulfilled POs import as purchase orders in state=purchase; open POs import in state=draft.

BizAutomation Shipment records tied to Sales Orders map to Odoo stock.picking records of type=outgoing. Tracking number, carrier, and shipment date migrate to stock.picking fields. For incoming shipments tied to Purchase Orders, we generate incoming pickings (type=incoming). Shipment-to-picking linkage is maintained via the sale_id and purchase_id references on the picking.

BizAutomation Projects map to Odoo project.project records. Project status, start/end dates, and assigned project managers migrate directly. Tasks within the project map to project.task records linked to the project. Time entries (billable hours) map to account.analytic.line with product/service mapping to timesheet products. Custom project fields and milestone definitions require field-level mapping review.

BizAutomation Opportunities map to Odoo crm.lead records in pipeline stage. Stage name, probability, amount, expected close date, and owner migrate directly. Custom pipeline stages in BizAutomation map to Odoo stage definitions in the crm.team pipeline view. The contact and company links resolve to res.partner IDs created during the earlier Contact and Organization migration phase.

BizAutomation Activity records (calls, emails, tasks, meetings) map to Odoo mail.message records with message_type set to email, call, or notification as appropriate. The res.partner and record reference (partner_id, res_id, model) resolve to the corresponding migrated CRM or project record. Custom activity types and notes migrate as mail.message body content with subtype tracking.