Migrate from ManEx to Odoo ERP

ManEx Customer records map to Odoo res.partner with the customer flag set to True. We extract contact details, address data, and account assignments from ManEx's flat customer schema via direct DB query. The partner's name, email, phone, and street/city/state/zip fields map directly. We preserve the original ManEx customer ID in a custom field x_manex_customer_id for audit traceability. If ManEx stores multiple contacts per customer account, we create one res.partner per contact and set the parent_id to the primary account partner.

ManEx Vendor records map to Odoo res.partner with the supplier flag set to True. Vendor PO history and RMA associations from ManEx are preserved as related purchase.order and stock.picking records in Odoo. The vendor-supplier relationship is held separate from customer accounts to avoid merging two distinct business entity types into one Odoo partner record. Vendor-specific fields like tax ID and payment terms map to res.partner's fiscal_country_ids and property_supplier_payment_term_id.

ManEx GL accounts map to Odoo account.account entries with standard account types (asset, liability, equity, revenue, expense). We extract the full account code, name, and type from ManEx and create matching Odoo records in the correct sequence so that child accounts reference valid parent accounts. Inactive or suspended ManEx accounts are imported with the active flag set to False in Odoo. Account codes that conflict with Odoo's default chart of accounts require a custom chart-of-accounts template or a fresh account import before any AP/AR migration begins.

ManEx PO records map to Odoo purchase.order with line items in purchase.order.line. The PO's vendor assignment, line items tied to BOMs, and receiving status all migrate. Partially received ManEx POs are created as purchase.order records with the state set to in_progress and the received quantity on each line reflecting the current ManEx status. We resolve the vendor res.partner reference before PO import so that the vendor_id foreign key is satisfied at insert time. PO dates and currency codes map to Odoo's date_order and currency_id fields.

ManEx SO records map to Odoo sale.order with line items in sale.order.line. Pricing, customer linkage, and fulfillment status migrate directly. Multi-price-list pricing on ManEx SOs requires value-mapping because ManEx price list IDs are not portable to Odoo; we recreate the price list structure in Odoo and map the ManEx price list name to the corresponding Odoo product.pricelist. SO state mapping (open, confirmed, done, cancelled) translates to Odoo's sale_order states during import.

ManEx BOMs include multi-level component structures and routing data that require decomposition for Odoo MRP. Complex multi-level BOMs with phantom assemblies are either flattened (single-level BOM with all components at the top level) or preserved as nested mrp.bom records with type=subassembly depending on the destination configuration. We handle the component-to-product mapping, quantity per finished good, and unit of measure conversion during transformation. Routing data (workcenters, cycle times, sequence) maps to mrp.routing.workcenter on the Odoo bom_id if the customer activates the Manufacturing app's routing feature.

ManEx real-time shop floor data tracks labor time, machine cycles, and material consumption per work order. These transactional records are timestamped and contextual. We map them to Odoo mrp.workorder records linked to the corresponding mrp.production, with time tracking stored in mrp.workcenter.productivity records. Material consumption maps to stock.move lines with consume_location resolved from ManEx's warehouse and location codes. If ManEx shop floor data uses a proprietary transaction log format, we parse it row-by-row and batch-insert into Odoo's mrp.workorder and stock.move tables via direct DB write or Odoo's XML-RPC with batch chunking.

ManEx inventory quantities, locations, and lot/serial data migrate to Odoo stock.quant and stock.location. We handle multiple warehouse locations by creating Odoo stock.location records in a hierarchy (WH/Stock, WH/Stock/Location1, etc.) mapped from ManEx's location codes. Lot and serial traceability preserves as lot_id and last_lot_id on stock.quant. On-hand quantities per location and per product are aggregated from ManEx's materials management module before insert into Odoo to avoid duplicate quant records. If ManEx uses lot expiration dates, these map to stock.productionlot.removal_date_id in Odoo.

Open payables and receivables from ManEx migrate as Odoo account.move records in draft state for customer/admin review before posting. Current status, aging buckets, and payment terms are preserved in Odoo move lines linked to the corresponding res.partner account. Historical transactions require special handling because ManEx may store them in archived or compressed tables; we identify the archive location during discovery and extract them if the customer requests historical AP/AR migration. Posted moves require explicit customer sign-off before migration because posting a move in Odoo affects financial reporting.

Time entries from ManEx's optional Time and Attendance module are tied to employees and work orders. We map them to Odoo hr.attendance (check-in/check-out records) for HR reporting and to mrp.workcenter.productivity (labor tracking on work orders) for manufacturing costing. If Odoo is deployed without the HR app, time entries attach to mrp.workorder records only. We flag any employee records that do not have a corresponding Odoo hr.employee for the customer's admin to provision before the time migration phase.

ManEx RMA records represent return or repair states tied to original SOs or POs. Their status codes (open, in-progress, closed) require explicit value-mapping because the state machine differs between ManEx and Odoo. Open RMAs map to Odoo stock.picking with picking_type_id set to the return type, linked to the original purchase.order or sale.order via origin. We preserve the RMA number as the picking's origin reference and the RMA status as a custom field x_manex_rma_status for reconciliation. If the customer uses Odoo CRM with the claims module, we map repair-class RMAs to crm.claim records as a parallel path.

Document attachments stored within ManEx's document management module are not accessible via a public API and may use proprietary formats. We do not migrate attachments directly. We flag the document module as out-of-scope in the migration scope document and provide a manifest of the document paths and metadata (filename, record type, date) that the customer's admin can manually migrate using Odoo's document management module or a file-server copy script post-migration. If ManEx stores documents as BLOB fields in the database, we extract the raw BLOB data and save it to a fileshare for manual handoff.