Migrate from BusinessCloud to Odoo ERP

BusinessCloud Company or Entity records map to Odoo res.partner with partner_type set to company. The company name, registration number, tax ID, website, and address fields map directly. BusinessCloud multi-entity setups (parent-subsidiary structures) require Odoo multi-company configuration to be enabled and a parent_id link set on the subsidiary partner record. We resolve the company identifier from the exported database schema during the discovery phase since BusinessCloud's entity model is not publicly documented.

BusinessCloud Contact records (individuals linked to companies) map to Odoo res.partner with partner_type set to individual and a parent_id pointing to the linked company partner. Email, phone, mobile, job title, and address fields migrate directly. Any BusinessCloud contact notes or custom fields map to res.partner custom fields created during schema design.

BusinessCloud product or item records map to Odoo product.product (storable product) or product.template depending on whether the customer uses variants. Product name, SKU code, barcode, unit of measure, standard cost, and list price map to Odoo standard fields. We determine product type (stockable, consumable, service) from BusinessCloud inventory category flags in the exported schema.

BusinessCloud inventory records map to Odoo stock.quant for on-hand quantity tracking by product and location. We extract current stock levels per warehouse from the BusinessCloud export, then create stock.quant records linked to the corresponding product.product and stock.location (defaulting to Odoo's Physical Locations view if no multi-warehouse setup exists). The inventory valuation amount maps to product.standard_price on the product template.

BusinessCloud purchase order headers map to Odoo purchase.order with partner_id resolved to the supplier res.partner, order_date mapped to date_order, and order reference preserved in the Odoo origin field. Purchase order lines map to purchase.order.line with product_id, product_qty, price_unit, taxes_id, and discount fields resolved. Open and draft POs migrate; cancelled POs are not migrated unless the customer requests historical audit records.

BusinessCloud sales order records map to Odoo sale.order. The customer partner, order date, and order reference map directly. Sale order lines migrate with product_id, product_uom_qty, price_unit, tax_id, and discount preserved. If BusinessCloud records include confirmed invoices rather than just orders, we migrate sale.order with the invoiced status flag set and create account.move records for posted invoices. We resolve any outstanding amounts against the customer account balance.

BusinessCloud vendor or supplier invoices map to Odoo account.move with move_type = in_invoice. Partner_id resolves to the supplier res.partner, invoice_date maps to invoice_date, and invoice number maps to ref. Line items map to invoice_line_ids with product_id, quantity, price_unit, and tax tags resolved. Outstanding amounts on open invoices carry over as account.move line entries with matching partner_credit values.

BusinessCloud customer invoices map to Odoo account.move with move_type = out_invoice. The customer res.partner, invoice date, due date, and invoice number migrate. Invoice line items map with product_id, quantity, unit price, tax tags, and discount preserved. Open invoices carry their outstanding balance as a credit or debit line in Odoo's accounts receivable account.

BusinessCloud chart of accounts structure maps to Odoo account.account records. Each account's code, name, account_type (asset, liability, equity, income, expense), and reconcile flag migrate. We map account codes directly when they align to Odoo's account type taxonomy; accounts that do not map cleanly require the customer's accountant to review and assign the correct Odoo account type before data import. This is the most accounting-sensitive mapping in the migration and is done in collaboration with the customer's finance team.

BusinessCloud journal entries (general ledger transactions) map to Odoo account.move with move_type = entry. We migrate posted entries only unless the customer requests draft entries for audit. Each journal entry line maps to account.move.line with account_id, debit, credit, partner_id, and analytic account resolved. The account references must be validated against the migrated chart of accounts before journal entry migration begins.

BusinessCloud CRM leads or prospects map to Odoo crm.lead (Odoo's unified lead/opportunity model). Contact name, email, phone, company name, lead source, and stage/status fields migrate to crm.lead standard fields. Any BusinessCloud lead scoring or priority flags map to custom fields on crm.lead. Odoo's crm.lead does not split into separate Lead and Contact objects like Salesforce; it uses a single model with type toggle between lead and opportunity.

BusinessCloud custom fields or extended entity records map to Odoo's dynamic ORM model extension. We create ir.model records for any BusinessCloud entity that has no Odoo standard equivalent, then add ir.model.fields to define the custom fields. This requires schema discovery from the BusinessCloud export to identify extended fields not present in the standard BusinessCloud data model. Custom object naming in Odoo follows the standard ir.model approach and does not require code-level module development unless the custom object requires custom business logic.