Migrate from Orion ERP to Odoo ERP

Orion's COA maps to Odoo's account.account records with corresponding account.account.type assignments. We preserve Orion account codes as Odoo code values and map account type (Asset, Liability, Equity, Income, Expense) to Odoo's account.account.type selection. Multi-segment charts from Orion (e.g., 4-2-2-2 structure) map to Odoo's account.group hierarchy for balanced financial statement rollup. Currency settings on Orion accounts migrate to Odoo's currency_id on each account record.

Orion customer master records (name, billing address, payment terms, credit limit) map to Odoo res.partner records with customer_rank set positive to classify as customer. Orion's payment terms migrate as account.payment.term records linked via property_payment_term_id. We validate tax ID format against Odoo's country-specific validation rules during transform and flag any malformed IDs for customer-admin correction before load.

Orion vendor master records map to Odoo res.partner records with supplier_rank set positive. Tax ID, bank details, and payment terms migrate similarly to the customer mapping. We separate vendor-specific fields (vendor code, W9 status) into custom fields on res.partner to avoid schema conflicts with Odoo's standard vendor record structure.

Orion GL transactions with header metadata (journal number, date, description) and line items (account, debit, credit) split into Odoo account.move header records and account.move.line child records. The Orion journal assignment maps to Odoo's account.journal (type: sale, purchase, general, bank, cash). We preserve the original posting date as move_date and generate Odoo sequence-based move names matching the original journal number format.

Orion open AP records are extracted as a distinct migration scope item separate from historical AP. We load them as Odoo account.move records with move_type = 'in_invoice' (vendor bill) for open items the organization owes. The due date and amount are preserved, and the vendor reference resolves to the mapped res.partner supplier record. Any AP aging that should appear as opening-balance payables (if the customer prefers to start Odoo with a clean books approach) is injected as a separate opening-balance journal entry with a dedicated Opening Balances journal.

Orion open AR records are extracted as a distinct migration scope item. We load them as Odoo account.move records with move_type = 'out_invoice' (customer invoice) for amounts owed to the organization. Customer reference resolves to the mapped res.partner customer record. Open AR aging that should appear as opening-balance receivables is injected as a separate opening-balance journal entry if the customer requests clean-books initialization in Odoo.

Orion item master records (SKU, description, unit of measure, cost, warehouse location) map to Odoo product.product with type = 'product' for storable items. Unit of measure migrates to product.uom. Cost price migrates to standard_price on the product record. We extract warehouse location from Orion's inventory management module and create corresponding stock.warehouse and stock.location records in Odoo before quant migration.

BOM records from Orion Manufacturing Cloud map to Odoo mrp.bom with type = 'normal'. BOM line items (component, quantity, unit of measure) migrate to mrp.bom.line records. We resolve product references during BOM migration by cross-referencing the product migration already completed. This mapping only applies if the customer is on Orion Manufacturing Cloud; we confirm edition during scoping and exclude BOM objects from non-manufacturing scopes.

Orion PO headers (vendor, date, status) map to Odoo purchase.order with state mapped to Odoo's draft, sent, purchase, cancel states. PO lines (product, quantity, price) migrate to purchase.order.line with product_uom and price_unit. Open versus closed PO status is preserved so that pending POs appear in Odoo as actionable purchase orders while closed POs are migrated as completed records for historical reference.

Orion sales order headers (customer, date, status) map to Odoo sale.order with state mapped to Odoo's draft, sent, sale, done, cancel states. Sales order lines (product, quantity, price) migrate to sale.order.line. We separate fulfilled versus pending lines during transform: fulfilled lines are migrated as sale.order.line records on confirmed orders, and pending lines are migrated as draft orders awaiting confirmation in Odoo.

Orion employee records (name, department, job title, employment dates, compensation) map to Odoo hr.employee. Effective-dated compensation history is sequenced chronologically during migration so that the correct salary appears on the correct contract period in Odoo's HR module. Department and job title migrate as hr.department and hr.job records created before the employee migration.

Orion custom fields on master and transaction records are detected during the scoping export and pre-created in Odoo as custom ir.model.fields before data migration begins. Field data types from Orion are mapped to Odoo field types (char, text, integer, float, date, datetime, selection, many2one, one2many). Edition-specific custom fields are flagged and only created if the corresponding Odoo module (e.g., mrp, stock, hr) is enabled in the destination.