Migrate from inoERP to Odoo ERP

inoERP GL accounts with types (asset, liability, equity, revenue, expense), codes, and currency assignments map directly to Odoo account.account records. We extract account_type, code, name, and currency_id from inoERP and map inoERP account types to Odoo's account type enumeration. Multi-currency accounts from inoERP carry the currency_id into Odoo's allow_reconciliation and currency_revaluation fields.

Posted journal entries from inoERP's GL module map to Odoo account.move and account.move.line records. We extract debit/credit amounts, account assignments, and reference numbers. Entries with non-standard currency references or inter-company journal IDs are flagged for manual review before import. The move_name (journal entry number) is preserved as Odoo's ref field for audit continuity.

inoERP's party structures (customer, supplier, employee) map to Odoo res.partner with the appropriate customer_rank and supplier_rank values set. Open AR/AP subledger transactions (invoice headers, line items, payment terms) become Odoo account.move records with move_type of out_invoice, out_refund, in_invoice, or in_refund. Party-level aging reports from inoERP translate to Odoo's Account Moves with open reconciliation.

inoERP item definitions with UOM, cost layers, category hierarchies, and on-hand quantities map to Odoo product.product (for stockable/ consumable/service variants) and stock.quant for location-level on-hand balances. Lot/serial numbers from inoERP migrate as stock.lot records. UOM conversion rules from inoERP map to Odoo's uom.uom model with conversion_factor set. Phantom BOM items are flagged so they are imported as product templates without production routing.

Open orders from inoERP (SO and PO) with header fields (dates, terms, party references) and line items (item, quantity, price, warehouse) map to Odoo sale.order and purchase.order. Order status from inoERP determines whether the record lands as draft, confirmed, or done. Closed orders can be imported as confirmed sale.order or purchase.order records for historical reference, or omitted based on customer scope preference. inoERP warehouse assignments map to Odoo stock.warehouse picking_policy settings.

Work orders from inoERP including routing steps, material issues, resource transactions, and completion records map to Odoo mrp.production (manufacturing orders) and related stock.moves for component consumption and finished goods receipt. WIP ledger aggregated costs from inoERP map to Odoo's manufacturing journal entries so that work order cost accumulation is visible post-migration. Open work orders migrate as confirmed mrp.production records; completed orders migrate as done records with full cost history.

inoERP super BOMs and multi-level structures map to Odoo mrp.bom with type set to normal or kit depending on the inoERP BOM variant. Each BOM line references a product.product for the component and a mrp.routing.workcenter record for the operation step. We perform recursive BOM resolution during extraction so that Odoo's explode algorithm produces the same total component demand as inoERP. Phantom BOMs from inoERP map to Odoo kit-type BOMs.

MRP-generated supply requisitions from inoERP are flagged during extraction and not imported as live Odoo MRP records. inoERP's dynamic pull-based MRP recalculates lot sizes at runtime based on current demand signals, so historical MRP output reflects past demand patterns that may not be valid in Odoo's MRP run. We export the MRP requisition records as a reference CSV and recommend customers re-run MRP in Odoo post-migration rather than importing the historical plan output.

inoERP employee profiles, job definitions, positions, and position assignments map to Odoo hr.employee and hr.job. Compensation records (salary, benefits) from inoERP migrate as hr.contract records attached to the employee. Leave balances from inoERP transfer to Odoo's hr.leave model with allocation records. We flag compensation data for manual review because Odoo's payroll module is country-specific and may require additional configuration beyond the standard import.

inoERP user accounts and role-based access control map to Odoo res.users and the associated groups (access rights sets). We translate inoERP role names and permission sets to Odoo group assignments. Users without an email address in inoERP are flagged for the customer's Odoo admin to assign login credentials before production migration.

Asset records from inoERP including acquisition details, depreciation schedules, asset categories, book values, and accumulated depreciation map to Odoo account.asset.asset. The depreciation method from inoERP (straight-line, declining balance) maps to Odoo's depreciation method field. Depreciation move lines generate as account.move records in Odoo's asset depreciation journal.

inoERP document storage in its CMS module stores attachment links as paths to locally hosted files. Binary attachments do not migrate. We extract the list of attachment references and their file paths as a written inventory for the customer's IT team to migrate via file transfer separately.