Migrate from Accolent ERP to Odoo ERP

Accolent Customer records map to Odoo res.partner records with is_company=True. We extract billing address, shipping address, contact name, phone, email, payment terms, and account type flags. Odoo stores the customer type (individual vs company) on the partner itself; we set is_company=True when the Accolent record represents an organization and populate individual contacts as related partners with parent_id pointing to the company partner. Dedupe key is the customer code or, if absent, a normalized email address.

Accolent Vendor master records map to Odoo res.partner with is_company=True and supplier_rank=1. Address, payment terms, and PO defaults from Accolent map to Odoo's address fields and the vendor.payment_term_id and vendor_price list fields. We flag any Accolent vendor that has no email address for manual review before import because Odoo requires a partner to have at least a name or email for the purchase order workflow.

Accolent Item records map to Odoo product.product for stockable variants and product.template for the product definition. We extract item code, description, unit of measure, cost, sales price, pricing tiers, reorder point, warehouse locations, and any BOM link. Odoo's product_type field (product.type) is set to 'product' for stockable items, 'consu' for consumables, and 'service' for service items based on the Accolent item type flag. We resolve multi-warehouse stock levels as Odoo quant records per warehouse location.

Accolent Sales Order headers and lines map to Odoo sale.order and sale.order.line. We extract order number, order date, customer reference, line items with quantities and prices, discount amounts, shipping address, and order status (open vs fulfilled). Fulfilled orders from Accolent import as sale.order in state='done' so they are read-only in Odoo; open orders import as 'sale_order' state='draft' or 'sent' for review before confirmation. We preserve the original Accolent order number in the client_order_ref field.

Accolent Purchase Order headers and lines map to Odoo purchase.order and purchase.order.line. PO number, vendor, line items, quantities, prices, and receipt status migrate. Odoo's purchase.order workflow uses a receipt step linked to stock.picking; if the Accolent PO was partially received, we create the corresponding Odoo PO with the matched received quantity flagged in a custom field so the receiving team can reconcile on arrival.

Accolent GL chart entries (account number, name, type: Asset/Liability/Expense/Revenue, cost-center flag) map directly to Odoo account.account records. We set the account type mapping per Odoo's account.account.account_type choices. If Accolent uses cost-center assignments at the account level, we recommend enabling Odoo's analytic accounting module during configuration to preserve cost-center reporting. Parent account hierarchy from Accolent becomes Odoo's parent_path for balance-sheet rollup.

Outstanding Accolent invoices and credit memos do not migrate as re-created invoices — they land as Odoo account.move records in draft state representing the balance-forward opening position. For AR, we create an opening customer statement move with the outstanding invoice amount as a receivable line against the partner. For AP, we create a vendor bill move with the outstanding amount as a payable line. We flag any record where the original invoice date is more than 90 days in the past for manual review before posting. This approach prevents Odoo from re-running tax computation on aged invoices that should reflect historical state.

Accolent multi-level BOMs (parent-component relationships, quantity-per, routing steps, work-center assignments, phantom BOM flags) map to Odoo mrp.bom and mrp.bom.line. We flatten BOMs to a maximum of two levels during import and flag any BOM with more than three levels for manual review before loading to prevent circular-reference errors in Odoo's MRP engine. Phantom BOMs from Accolent become Odoo phantom-type bom records with type='phantom'. Work-center assignments from Accolent routing steps map to Odoo mrp.workcenter records.

Accolent multi-warehouse site definitions with bin/shelf location codes map to Odoo stock.warehouse records and the associated stock.location tree (view, internal, partner, and physical location types). We preserve Accolent bin and shelf codes in the Odoo location.lot_stock name field and map the warehouse code to Odoo's short_code field. Any cross-warehouse transfer orders in Accolent become Odoo inter-warehouse stock.picking records.

Historical Accolent GL journal entries (date, account, debit/credit amounts, source reference) map to Odoo account.move records with move_type='entry' for manual journal entries. We set the journal_id to a migration journal created specifically for historical data and preserve the original posting date and memo. We confirm Odoo's fiscal year sequences are open for all posting dates before loading; entries outside the configured fiscal periods require a journal entry sequence extension or a separate adjustment journal.

Accolent fixed-asset records (acquisition cost, depreciation method, accumulated depreciation, asset class) map to Odoo account_asset module's account.asset records. We extract asset class, acquisition date, original cost, depreciation method (straight-line or declining), and accumulated depreciation. We create corresponding depreciation board entries in Odoo aligned with the Accolent depreciation schedule. Asset status (active, disposed, fully depreciated) maps to the Odoo asset state field.

Accolent tax code master records map to Odoo account.tax records with tax_scope and amount fields. We extract tax rate, applicability (sales vs purchase), and jurisdiction flags. Tax codes with complex compounding rules or jurisdiction-specific logic require manual review against Odoo's tax configuration because Odoo handles tax computation differently from Accolent. We flag any Accolent tax code with a name longer than 50 characters for field-length adjustment during import.