Migrate from Aptean Compiere ERP to Odoo ERP

Compiere Business Partners unify customers, vendors, and contacts in a single entity type with roles. We split the source Business Partner into Odoo Contact records (for individuals) and Address records (for locations) with the partner_id lookup. Vendor-role Business Partners map to Odoo Contacts with supplier=True; customer-role maps to contacts with customer=True. Contact information (name, email, phone, address) migrates directly. Multi-address Business Partners generate multiple Address records linked to the parent Contact.

Compiere Products map to Odoo Product Template (the product definition) with optional Product Variants (for size, color, or other attribute combinations). The source product_type (Item vs. Service vs. Resource) maps to Odoo's product_type field. We preserve the Compiere product's price, cost, uom, and product category. Products with multiple attribute values in Compiere generate variant combinations in Odoo.

Compiere multi-level BOMs for kit products and manufactured items map to Odoo BoM records with nested BoM Line entries. We preserve the full BOM component hierarchy, mapping each Compiere product component back to the corresponding Odoo Product Template. For manufacturing-centric migrations, we create Odoo BoM records with routing (workcenters and operations) if the source Compiere deployment includes production scheduling data. Phantom BOMs in Compiere map to Odoo's phantom variant logic.

Compiere Warehouses map directly to Odoo Warehouse records. We preserve the warehouse code, name, and the Buy / Manufacture / Deliver Drop Shipment flag from Compiere. Source warehouse locations are used to seed Odoo's warehouse configuration. Multi-warehouse setups in Compiere become separate Odoo Warehouse records that can share inventory locations or operate independently based on the customer's multi-company configuration.

Compiere Locators (up to five user-defined dimensions: aisle, bin, rack, level, bay) map to Odoo Stock Location records within the corresponding Warehouse. We preserve the locator's complete path as a Location hierarchy in Odoo (parent_id chain). Odoo's location model uses a parent-child structure that can represent up to five levels, matching Compiere's dimension count. We flag any source Locators with more than five dimension components for manual cleanup before migration.

Compiere Purchase Price Lists map to Odoo Product Pricelist records with pricelist_type = purchase. We migrate the base price, cost, and supplier-specific pricing entries as Pricelist Item records with the supplierinfo link. Date-controlled pricing from Compiere (effective start and end dates) maps to Odoo's date_start and date_end on Pricelist Item.

Compiere Sales Price Lists map to Odoo Product Pricelist records with pricelist_type = sale. Customer-specific pricing migrates as Pricelist Item records with the applicable partner_id or partner_category link. General (non-customer-specific) pricing migrates as global Pricelist Items. The Compiere concept of a default Sales Price List maps to the Odoo company's sale_pricelist setting.

Compiere Product Categories (grouping products with shared pricing structures, accounting rules, and discount controls) map to Odoo Product Category records with the same name and parent_id hierarchy. We preserve the accounting category mapping for valuation and cost of goods sold posting. Categories are imported before Products so that the category_id lookup is satisfied at import time.

Compiere country-specific AccountingXX.csv chart of accounts migrates to Odoo's account.account records. We create each account with the appropriate code, name, account_type (asset, liability, equity, income, expense), and reconcile flag. Compiere's Accounting Schema (the combination of Chart of Accounts and accounting rules) maps to Odoo's fiscal position and tax configuration. Country-specific templates in Odoo (l10n modules) may provide a cleaner starting point; we compare the source chart against the Odoo template and apply a delta import for accounts not covered by the template.

Open Accounts Payable invoices in Compiere map to Odoo Vendor Bills (account.move with move_type = in_invoice). We preserve invoice number, vendor partner_id, invoice date, due date, line items (product, quantity, price), and the total amount. Unpaid invoices migrate with status = draft; partially paid invoices carry the payment retainage as Odoo line amounts. Historical closed AP records are scoped separately and not imported unless the customer specifies a lookback requirement.

Open Accounts Receivable invoices in Compiere map to Odoo Customer Invoices (account.move with move_type = out_invoice). We preserve invoice number, customer partner_id, invoice date, due date, line items, and total amount. Compiere invoice payment terms map to Odoo Payment Term records. Unpaid AR invoices migrate as draft; partially paid records carry the outstanding balance as invoice lines with a payment difference account. Historical closed AR records are scoped separately.

Compiere role-based security (System, Client, Organization levels) maps to Odoo User records with Group assignments. We map Compiere roles to Odoo access groups (Sales Manager, Inventory User, Accounting User, etc.) based on the menu and window access defined in Compiere. The three-tier Compiere entity hierarchy (System-Client-Organization) maps to Odoo's multi-company setup where each Compiere Org becomes an Odoo Company record. Users are created with a placeholder password requiring reset at first login.