Migrate from Genius ERP to Odoo ERP

Genius ERP Work Orders are the central production record carrying job status, operations, assigned technicians, and real-time tracking. We map Work Order headers to Odoo mrp_production with state mapped to Odoo's rma, confirmed, planned, in_production, and done states. Line-level operations migrate to Odoo mrp_workorder with the operation sequence, work center assignment, and duration. Work Order cost tracking maps to Odoo analytic account lines linked to the production order.

Genius ERP multi-level BOMs with nested assemblies and subassemblies map to Odoo mrp_bom records. The BOM type (kit vs manufacturing) maps from Genius type flags. Component quantities and units of measure migrate directly. CAD-linked component relationships and revision numbers migrate as product variant attributes and BoM revision tracking. Odoo requires each subassembly to have its own explicit BoM definition — we run a BOM explosion script during discovery to identify orphaned subassemblies missing a BoM in the destination.

Genius ERP job costing tracks actual versus estimated costs per work order including labor, materials, and overhead allocations. We export the full cost ledger per job and map cost elements to Odoo analytic account lines linked to the corresponding manufacturing order. Actual versus budget reporting in Odoo uses the analytic reporting module. Note that if Genius ERP cost entries reference Work Order numbers not preserved as Odoo production references, the link requires manual reconciliation after migration.

Genius ERP Items, stock quantities, warehouse locations, and reorder points migrate to Odoo product_product records with linked stock.quant records for on-hand quantity at each location. Serial and lot number traceability migrates where present as Odoo stock.production lot records. Open purchase orders are flagged separately because they represent future receipts; we migrate PO headers and lines with vendor details and expected delivery dates.

Genius ERP customer records, contact information, and account hierarchies map directly to Odoo res.partner records with customer flag set. Account hierarchies in Genius map to Odoo contact type (individual versus company) with child contacts as related partner records. Where Genius CRM fields differ from Odoo contact fields, we apply field-level mapping and preserve any custom fields as Odoo custom fields on the partner model.

Genius ERP Sales Orders and Quotes carry pricing, line items, and link to Work Orders. Open orders migrate with status preserved (quotation versus sales order). Historical quotes that were never converted require explicit scoping — we ask customers whether to migrate these as quotations or close them in Odoo before migration. Line items with manufactured products link to Odoo product variants; services link to consumable or service products.

Open purchase orders migrate to Odoo purchase.order with vendor details, line items, expected delivery dates, and received-versus-ordered quantities. Closed POs are treated as historical records and scoped separately based on the customer's audit and reporting needs. Odoo purchase approval workflows (if configured) are not migrated — the customer's admin sets these up post-migration.

Genius ERP's G/L is intentionally lightweight. We export all posted journal entries from Genius ERP but flag every entry that references a Work Order or inventory movement as a reconciliation risk. Odoo's account.move schema differs from Genius ERP's posting model, so journal entry mapping requires a chart of accounts reconciliation step. We recommend the customer's accountant reviews all inventory and production-linked journal entries post-migration — these links may not survive the import intact due to the different posting structures.

User accounts, role assignments, and permission sets export from Genius ERP as user records. Active versus inactive status is preserved. Permissions map to Odoo's access rights model and record rules, which differs structurally from Genius ERP's role framework. We deliver a written access matrix during discovery that maps each Genius ERP role to the closest Odoo default group (Manufacturing / Sales / Inventory / Accounting), with a note for any custom permissions requiring manual Odoo group creation.

Genius ERP custom field definitions and their current values migrate together. We map field types (text, numeric, date, picklist, checkbox) to the equivalent Odoo field type on the corresponding model. Picklist values in Genius ERP map to Odoo selection fields or many2one relations depending on value count. Custom field definitions are created in the destination Odoo database before any data import begins.

Quality management records including inspection results, non-conformance logs, and lot traceability data migrate from Genius ERP as Odoo quality.check and quality.alert records. The record headers and links to lot numbers migrate; unstructured inspection notes are attached as Odoo attachments to the quality record. Odoo quality module must be installed in the destination; if it is not, we migrate the record data as custom fields on the stock.production lot or mrp.production models.