Migrate from INNERGY ERP to Odoo ERP

INNERGY Estimates with material takeoffs, labor assumptions, margin calculations, and line items map to Odoo Quotations (sale.order) and sale.order.line records. Margin simulation does not migrate as a computed field — we document the margin formula as a field note for the customer's Odoo admin to configure via Odoo Studio or a custom computed field on the quotation model. Estimate status (draft, sent, accepted, lost) maps to Odoo sale.order state.

INNERGY Jobs — the core project record tracking a millwork project from award through installation — map to Odoo Project records. We map job metadata, status history, assigned staff, and division cost pool references into the Project and associated Task records. Division-specific cost pools become Project tags or custom project fields; the customer's Odoo admin configures financial reporting against these tags post-migration. Original Job number becomes the Project external reference field.

INNERGY BOMs are multi-level with subassembly relationships, material specs, quantities, and operations routing auto-generated from CAD data. Odoo's mrp.bom is primarily single-level. We decompose INNERGY's nested BOM into a parent BoM with subassembly lines referencing child BoMs, preserving operation routing as mrp.routing.workcenter lines. Phantom BoM is used for subassemblies that Odoo should collapse during manufacturing order generation. Material specs and quantities map directly to BoM lines (product, product_qty, bom_line_type). CAD-linked geometry data does not migrate as it is design-system content, not ERP data.

INNERGY Work Orders linked to Jobs and BOMs map to Odoo Manufacturing Orders (mrp.production). Assigned operations, sequencing, and completion status migrate to mrp.production records with their associated workcenter operations. The parent Job's Project reference is stored on the Manufacturing Order so that production progress is linked to the project record in Odoo. Work order status (pending, in-progress, completed) maps to Odoo state (draft, confirmed, progress, done).

INNERGY Change Orders modifying Job scope with approval dates, revised quantities, and lineage references have no native Odoo equivalent. We preserve the full change-order log as a structured linked table — either Odoo Project Tasks with a custom Change Order type tag, or a custom mrp.change.order model if the customer requires formal change-order workflow in Odoo. Original Job number, approval date, and revised scope are stored as fields on the linked record so auditors retain sequence fidelity and the cost impact of each change order is traceable to the parent Project.

INNERGY material and component inventory with units of measure, reorder points, warehouse locations, average cost, and stock status map to Odoo Product records. Inventory balances migrate as Odoo stock.quant records in the designated warehouse. Units of measure map to Odoo's uom.uom model with the correct category (unit, length, area, volume). Average cost becomes the product's standard_price for inventory valuation. We flag any INNERGY inventory items with no matching product in Odoo for the customer's admin to review before stock quant import.

INNERGY Customer records with contact details, billing and shipping addresses, and associated Jobs map to Odoo Partner records. Billing address maps to partner_id (commercial partner); shipping address maps as a child Partner record with type=delivery. The associated Jobs list is preserved as linked Project records so the customer's sales and project teams can view the full job history per customer in Odoo's Opportunities and Projects views.

INNERGY Vendor records with supplier information, lead times, and preferred items map to Odoo Partner records with the Supplier checkbox enabled. Associated purchase history and preferred items migrate as purchase.order records and product supplierinfo records respectively. Lead times map to the vendor's product supplierinfo delivery_delay field so Odoo's purchase planning uses accurate lead times from go-live.

INNERGY custom fields added post-implementation through INNERGY's custom field framework are cataloged during discovery via the API and mapped to equivalent Odoo custom fields created in the target database before data import. Feature Release 115 confirmed INNERGY ships new custom field capabilities over time; we cross-reference the customer's current export against the API field definitions to catch any orphaned or mislabeled custom properties. Custom fields on Shipments are mapped to Odoo stock.picking custom fields if the customer activates the Warehouse Management app.

INNERGY account structures configured per-customer during implementation export as a full account list with account codes, names, and types. We map these to Odoo account.account records using the account.account template structure. Account codes and names migrate directly; account types (asset, liability, equity, revenue, expense) map to Odoo's account.account account_type field. The customer must validate that the destination Odoo fiscal year and tax configuration aligns with the imported account structure before posting transactions.

Outstanding invoices, credit memos, and open payable and receivable items are extracted from INNERGY's API and reconciled before migration. Open items migrate as Odoo account.move records (Invoices and Bills) with the reconciled flag set to false so they appear in Odoo's AP/AR aging reports at go-live. Vendor bills (AP) and customer invoices (AR) are distinguished by the move_type field. The customer must confirm that the bank account and payment terms configuration in Odoo matches the imported open items before making any new payments or receipts in Odoo.

Documents and drawings associated with INNERGY Jobs, Work Orders, and Estimates — including PDFs, images, and CAD export files — are exported in their native format and linked to the corresponding Odoo record (Project, Manufacturing Order, or Quotation) via ir.attachment records. CAD files (DXF, STEP, etc.) are stored as binary attachments; the customer's Odoo admin assigns the appropriate access rights for engineering and production staff.