Migrate from BizeeBuy to Odoo ERP

BizeeBuy Supplier records carry contact details, sourcing categories, and performance metadata. We map them to Odoo Contacts with the Is a Vendor checkbox enabled and vendor-specific fields (payment terms, supplier rank) populated from BizeeBuy's performance metadata. Vendor Pricelist records are created for each supplier-item combination found in BizeeBuy's PO data. If BizeeBuy stores supplier addresses separately, we merge them into the Odoo Contact's address fields before import.

BizeeBuy Items carry SKU (hs_sku equivalent), unit of measure, cost, and category assignments. We map them to Odoo Product Template records with type set to Storable, Consumable, or Service based on item usage in BizeeBuy stock and PO records. Variant structures in BizeeBuy (if any) are flattened into separate Odoo Product Template records because variant management in Odoo requires attribute and value configuration separate from the template. Product cost from BizeeBuy sets the Standard Price on the Odoo product.

BizeeBuy Warehouse records include name, address, and role (receiving, storage, shipping). We map them to Odoo Warehouse records, creating the corresponding Storage Locations under the warehouse if BizeeBuy distinguishes sub-locations. Warehouse is a prerequisite for all stock and production mapping, so it is imported before any inventory or production data.

BizeeBuy POs carry approval workflows, cost-center assignments, and line-item linkages to Items. We extract PO headers, line items (product, quantity, unit price, taxes), approval status, and cost-center references. In Odoo, POs are created with the vendor (from Contact mapping), order dates, and line items resolved to Odoo Product records. PO approval routing is not migrated as Odoo automation rules; it is documented in the workflow inventory for admin rebuild in Odoo Purchase configuration.

GRNs in BizeeBuy serve as the three-way match anchor linking POs and vendor invoices. We export GRN headers with their linked PO references, received quantities, and receipt dates. In Odoo, each GRN maps to a Stock Picking with type Receipt. The PO reference is stored in the picking's origin field for traceability. Three-way match state (matched, partial, unmatched) is preserved as a note or custom field in Odoo because Odoo's matching logic runs through the Accounts Payable app and is configured by the customer's accountant post-migration.

BizeeBuy stock data includes real-time quantities, stock status classifications, and FIFO-based unit cost per item per warehouse. We export the latest stock snapshot and map each record to Odoo Quant. Quantity, reserved quantity, location (warehouse), and unit cost migrate directly. If BizeeBuy stores movement logs (inbound/outbound transactions), those are mapped to Odoo Stock Move records linked to the Quant for audit traceability, though this extends migration time significantly for data-heavy accounts.

BizeeBuy BoMs define multi-level component structures with component quantities and scrap rates. We export the BoM hierarchy, component SKUs, quantities per finished unit, and scrap percentages. Nested BoMs in BizeeBuy are flattened into single-level Odoo BoM records or routed into multi-level Odoo BoM structures depending on the destination Odoo Manufacturing configuration. Component SKUs are resolved to Odoo Product records at migration time. Scrap rates are stored in the Odoo BoM's scrap_rel field.

BizeeBuy Production Batch records link to BoM references, raw-material consumption logs, and finished-goods output. We export batch headers with production date, BoM reference, quantities produced, and the inventory adjustments (material consumed and finished goods received). Each batch maps to an Odoo Manufacturing Order with state set to Done (closed) or the equivalent production record type, preserving the material consumption and output quantities for audit reporting.

BizeeBuy AP records include supplier invoices, payment status, and two-way or three-way match results against POs and GRNs. We export invoice headers, line items, invoice dates, amounts, and match outcome. In Odoo, these map to Vendor Bills in the Accounting app. The match state (matched to PO, matched to GRN, unmatched) is preserved in the Bill's reference or internal note field because Odoo's reconciliation logic is applied post-migration by the customer's accounting team.

BizeeBuy Cost Centers and budget allocations drive procurement approval routing and cost tracking. We export the cost-center hierarchy and active budget balances. In Odoo, cost centers map to Analytic Accounts or Departments depending on the customer's Odoo Accounting configuration. Budget tracking is a separate Odoo module (budget_management) that may require activation and configuration post-migration; we document the BizeeBuy budget balances and allocation rules for the customer's admin to configure in Odoo.

BizeeBuy supports custom fields on core entities but does not expose a dedicated custom-field schema endpoint. We infer custom field presence from BizeeBuy record payloads during discovery extraction and map each to Odoo custom fields (x_ prefixed) on the corresponding Odoo model. The customer chooses during scoping whether to create these as custom fields or store them as notes, depending on how the custom fields are used in BizeeBuy reporting.