Migrate from Plex Smart Manufacturing Platform to Odoo ERP

Plex Production Orders map to Odoo Manufacturing Orders (mrp.production). The structural gap is that Plex treats Production Orders as the parent record from which Work Orders derive, while Odoo treats mrp.production as the primary manufacturing record with optional work order references. We extract the full production order lifecycle (planned, released, in-progress, complete) and the Plex parent-child lineage into a custom field plex_production_order_id__c on the Odoo manufacturing order so the original Plex hierarchy is preserved in Odoo for audit and genealogy purposes.

Plex Items (manufactured, purchased, and phantom subtypes) map to Odoo product.product variants attached to product.template. Item type is preserved in a custom field plex_item_type__c on the product. Multi-unit-of-measure configurations from Plex carry over as UoM records in Odoo, and the Plex item code becomes the Odoo default_code. Phantom items in Plex map to Odoo phantom BoM type.

Plex's site-warehouse-bin hierarchy maps to Odoo's warehouse-stock-location structure. Each Plex site becomes an Odoo warehouse (stock.warehouse), Plex warehouses become location children under the warehouse, and Plex bins become stock.location records at the leaf level. Multi-plant setups map to multiple Odoo warehouses. We preserve on-hand quantities per location as Odoo quant records. Physical locations are migrated before any transactional inventory history so that quants resolve correctly.

Plex Work Orders derive from Production Orders and carry scheduling, labor, material allocations, and linked non-conformance references. In Odoo, work orders (mrp.workorder) are primary records linked to mrp.production. We map Plex Work Order status to Odoo state (pending, ready, in progress, done), labor hours to mrp.workorder duration, and material allocations to Odoo work order components. The Plex Work Order ID is preserved in a custom field plex_work_order_id__c on the Odoo work order. Odoo's operation-step and workcenter routing model may require additional configuration if Plex routes are complex.

Plex Quality Non-Conformances embed in the transactional model linked to work orders, production orders, and inventory lots. We extract disposition, corrective action, and inspection data and map them to Odoo quality.alert. The mapping complexity depends on whether the customer uses Plex's QMS module and Odoo's quality app (quality module). If Odoo's quality checks (quality.check) are also in scope, we configure operation-level checks linked to work orders. We flag any non-conformance patterns that require workflow adjustments to fit Odoo's separate quality module.

Plex consolidates suppliers and customers under Accounts with a type field distinguishing them. We separate by type during extraction and merge both into Odoo res.partner records. Suppliers get supplier_rank set to 1; customers get customer_rank set to 1. Contact details, payment terms, and approved supplier status carry over. Each partner gets a plex_account_id__c custom field for audit. Partners are loaded before purchase orders and sales orders so that Odoo supplier and customer lookups resolve at insert time.

Plex Purchase Orders map to Odoo purchase.order with line-level detail. The Plex account reference maps to res.partner. Expected dates, quantities, and pricing carry over as purchase.order.line records. Open POs migrate as active orders; closed POs migrate as historical records with state = purchase. Odoo PO confirm workflow (RFQ -> confirmed PO -> receipt) is applied post-migration. The Odoo drop ship module known issue with decimal quantities is flagged pre-migration for customers with fractional purchase units.

Plex BOMs are versioned and tied to items. Multi-level BOMs with component yields and scrap factors require careful sequencing. We map each Plex BOM version to an Odoo mrp.bom with bom_line components and the original Plex BOM version ID in a custom field plex_bom_version__c. Phantom BOM types from Plex map to Odoo phantom type. Multi-level BOMs are flattened or preserved per the destination's nesting capability, and the customer chooses during scoping. Route definitions (workcenters, cycles, times) map from Plex routing data.

Plex's MES-native lot genealogy tracks parent-child lot lineage across production and inventory movements. We extract the full traceability tree and map it to Odoo stock.lot records with lot numbers and to stock.move records with lot tracking. Odoo's lot genealogy depth is shallower than Plex's MES-native genealogy; we enable lots/serial numbers and backtracking in Odoo during configuration. If Odoo's genealogy depth cannot satisfy the customer's compliance requirements (IATF 16949, FSMA), we flag the gap before migration so the customer can decide whether Odoo is the right destination for regulated-lot data.

Plex core financials (GL, AP, AR) map to Odoo accounting modules. We extract transactional history, journal entries, and account balances and map them to Odoo account.move records against the destination chart of accounts. Open AP and AR items from Plex map to Odoo vendor bills (account.move with move_type = in_invoice) and customer invoices (account.move with move_type = out_invoice) respectively. Historical closed transactions migrate as read-only records. We do not migrate financial reports or financial workflows as code.

Plex Custom Fields differ per customer implementation. We perform a discovery pass using Plex's API to enumerate every custom field across every object before building the migration mapping. Each custom field's name, data type, and values are mapped to an equivalent Odoo custom field (ir.model.fields with custom = True). Custom field values on all records are transformed to the Odoo field type during the data transform phase. The discovery pass adds a step to the timeline but prevents field-value data loss on migration day.

Plex documents attached to Items, Work Orders, or Quality records are exported as binary content. We map them to Odoo ir.attachment records linked to the target model (mrp.production, mrp.workorder, product.product, quality.alert) via res_model and res_id. File names and metadata carry over; binary content is uploaded via Odoo's attachment API. Where Plex API access to binary content is restricted, we export file references and paths and provide a bulk-upload procedure for the customer's Odoo admin to complete manually.