Migrate from Reflex ERP to Odoo ERP

Reflex GL accounts map directly to Odoo Account Account records with account codes preserved as code, descriptions as name, and account types mapped to Odoo's account type taxonomy (receivable, payable, liquidity, revenue, expense, other). Inactive flags from Reflex become active=False in Odoo. We validate that Reflex's account code structure (typically numeric segments for balance sheet and income) maps cleanly to Odoo's account code format before import. Multi-company chart of accounts require Custom plan or careful company_id scoping on Community.

Reflex Customer master records (billing address, shipping address, payment terms, credit limits, contact details) map to Odoo Res Partner records with customer_rank elevated so they appear in the Odoo sales pipeline. We preserve Reflex's customer ID as ref for dedupe, map payment terms to Odoo Property Payment Term, and split billing and shipping addresses into separate address records linked by type. Open AR invoices at cutover migrate as draft Account Move records linked to the Res Partner.

Reflex Vendor records mirror the Customer structure with address, payment terms, and 1099 settings, mapping to Odoo Res Partner with vendor_rank elevated. We preserve the vendor ID as ref, map 1099 settings to Odoo's American tax reporting fields where applicable, and map payment terms to Property Supplier Payment Term. Open AP invoices at cutover migrate as draft Account Move records (vendor bills) linked to the vendor Res Partner.

Reflex Items with part numbers, descriptions, costing methods (FIFO, average), and pricing tiers map to Odoo Product Template with the costing method mapped to Odoo's valuation type (manual, FIFO, average). We extract all item records and map them before BOM processing so that the product variant list is available for Bill of Materials routing. Items without BOM map to Product Template directly; manufactured items require BOM migration as a separate phase.

Reflex Items with Bill of Materials structures map to Odoo MrpBom records with component lines (mrp.bom.line) linking to the finished product as Product Template. Multi-level BOM (BOM referencing sub-assemblies that are themselves BOMs) requires a recursive traversal during extraction to preserve the complete product structure in Odoo's flat BOM line model. We sequence BOM migration after Product migration so that all component Product Templates exist before BOM lines are created.

Reflex Projects with cost-tracking, revenue recognition, change orders, and sub-project breakdowns map to Odoo Project with analytic account linking. We extract project headers, budget lines, and actuals, but Odoo Project's native cost-tracking model differs from Reflex's Project cost engine. Budget-versus-actual reporting and revenue recognition scheduling require post-migration configuration in Odoo Analytic Accounting. We flag any Reflex project with active sub-projects for manual scoping before import.

Reflex Fixed Asset records (acquisition date, cost, depreciation method, accumulated depreciation, useful life) map to Odoo's account.asset.asset model with corresponding account.asset.depreciation.line entries. We extract the full asset register and map depreciation conventions (straight-line, declining balance, units of production) to Odoo's depreciation method fields. Accumulated depreciation at cutover migrates as an initial depreciation entry. Assets in Odoo Enterprise Fixed Assets module are covered natively; Community requires a third-party app or manual journal entries.

Open Accounts Payable linked to vendor IDs map to Odoo account.move records with move_type=in_invoice (draft state). We extract open AP at the agreed cut-off date with invoice numbers, amounts, due dates, and payment terms. Vendor bill lines map to account.move.line with appropriate account_id, debit, and credit values. The customer reconciles payments post-migration in Odoo's AP register. We flag any Reflex AP record with a payment terms split across multiple due dates for line-level decomposition.

Open Accounts Receivable linked to customer IDs map to Odoo account.move records with move_type=out_invoice (draft state). We extract open AR at cutover with invoice numbers, amounts, due dates, and aging bucket assignments. Customer invoice lines map to account.move.line with revenue account_id and partner_id resolved. Credit memos and prepayments require separate move_type=out_refund and entry-type journal entries respectively. We validate that aged receivable totals match Reflex's AR aging report post-import.

Reflex Work Orders link Items, BOMs, and labor routing, mapping to Odoo MrpProduction records. We extract open work orders with labor hours and material consumption. Closed work orders that simultaneously impacted COGS and inventory require careful sequencing: COGS journal entries from closed Reflex work orders do not map to Odoo manufacturing records and must be handled as manual GL entries post-migration. We flag any work order with a status of in_progress at cutover for Odoo MO creation, and any completed work order for GL journal review.

Reflex Tax Codes (jurisdiction and rate for sales and purchase transactions) map to Odoo account.tax records with the tax scope, amount, and type (sale, purchase, none) set accordingly. We extract all active tax codes and map them to Odoo's tax template system or custom taxes depending on whether the destination uses a chart template. Historical tax adjustments and nexus-specific codes that Reflex handled automatically require manual review in Odoo's tax mapping.

We extract Reflex User records with role assignments, but permission sets are Reflex-specific and do not map to Odoo's access rights model. We extract the full user list and map by email to Odoo res.users. Active/inactive status transfers. The destination Odoo admin must rebuild access rights (Groups and record rules) based on the written inventory we deliver. Minimum 5-user floor from Reflex does not apply in Odoo; Odoo Community has no per-user minimum.