Migrate from Aptean Industrial Manufacturing ERP, WorkWise Edition to Odoo ERP

WorkWise Customer records (contact details, accounts receivable balances, backlog references) map to Odoo res.partner with the customer flag set to True. The AR balance migrates as a starting receivable balance to be recorded in Odoo's account_move for proper GL impact. We match by customer_code as the dedupe key and resolve any duplicate names before insert.

WorkWise Vendor master records (purchasing terms, AP balances, lead times used in MRP) map to Odoo res.partner with the supplier flag set to True. Purchasing terms and lead times migrate to product.supplierinfo records linked to the vendor partner for use in Odoo's Purchase app. AP balance transfers as a starting payable balance recorded via account_move.

WorkWise Items carry complex attributes: stocking policies, stocking UOM vs. purchasing UOM, cost layers, revision control, and ECN-effective date fields. We handle unit-of-measure conversions using Odoo's uom.uom table and map the primary cost layer to product.standard_price. ECN-effective dates on items determine whether to load the current-active revision only or load revision history into Odoo product template variants. We flag any items with ECN future-effective dates during discovery.

WorkWise Sales Orders reference Customers and forward to Work Orders, with line-level pricing, promised dates, and status. Open orders transfer with current statuses; historical closed orders migrate as sale.order records with state=done for reporting. We map promised dates to commit_date and line pricing to sale_order_line with taxes resolved against Odoo's account.tax table.

Open POs carry vendor commitments and expected receipt dates. We map line items to Odoo purchase.order.line with the vendor's product.supplierinfo resolved at migration time. Destination-side receipt records (stock.picking IN) must be reopened against the imported PO identifiers. We flag any PO with a past expected receipt date for manual review before import.

WorkWise Work Orders tie to BOMs, Routings, and Work Centers, tracking planned vs. actual cost and completion. We transfer open Work Orders with their costing layers (planned labor, planned material) and flag any downstream closed records requiring a state= done migration. Odoo's mrp.production record requires a linked mrp_bom and stock_location; we resolve these dependencies before inserting production records in dependency order.

Multi-level BOMs with revision control and ECN affectivity dates must be exploded and validated before loading into Odoo mrp.bom. Parent-component relationships require careful sequencing to avoid orphan components. We determine during scoping whether to migrate the current-effective revision only or preserve full revision history. Odoo's mrp.bom does not have native ECN affectivity; we handle this by either loading the effective revision only or adding a custom effective_date field on mrp.bom if the customer requires revision history.

WorkWise Routings define the sequence of operations, work centers, and standard times used in scheduling. We map routing operations to Odoo's mrp.routing and mrp.workcenter objects. Standard times migrate to mrp.workcenter.line with cycle_time and hour_nbr. Odoo's CRP capacity recomputation must run post-migration; we flag this in the handoff documentation so the customer's Odoo admin schedules the capacity refresh.

WorkWise supports unlimited locations and bins. We preserve the full location/bin hierarchy into Odoo's stock.location tree (view locations at top, internal locations below, and bin locations at the leaf level). On-hand quantities migrate to stock.quant, including any negative-on-hand or consignment flags. Available-to-promise recalculation runs post-migration to validate that Odoo's APT math matches WorkWise's pre-migration snapshot.

WorkWise's GL structure includes department cost centers, fixed/variable cost flags, and inter-company segment codes used in job costing. We map accounts by segment code to Odoo's account.account with the appropriate user_type_id (expense, revenue, asset, liability). Custom account assignments that extend beyond the standard COA require a mapping decision during discovery.

WorkWise Work Centers carry capacity, calendars, and cost rates used in CRP calculations. We transfer work-center definitions to Odoo mrp.workcenter with capacity_efficiency, time_efficiency, and the Odoo working hours calendar (resource.calendar) attached. CRP capacity recomputation is a post-migration step that the Odoo admin must run after the first MRP calculation completes.

WorkWise Job Cost tracks planned vs. actual at Employee, Work Center, Department, Labor/Operation, and Component Material levels. For multi-level Work Orders, cost aggregation must be recomputed across the full tree. We transfer the cost ledger entries as snapshot records against Odoo mrp.workorder, populating the planned_cost and actual_cost fields. Destination-side job cost reports will reflect the moment-in-time migrated values, not live Odoo recalculations, which we document explicitly in the handoff report.

WorkWise Quality management stores inspection results, compliance alerts, and traceability links to lots and Work Orders. We map inspection records to Odoo quality.check and quality.alert, preserving the traceability chain to stock.move and mrp.production. Destination-specific quality control point configuration (control points, instructions, acceptance criteria) requires setup in Odoo after migration and is documented in the handoff inventory.

WorkWise Employee records include payroll integration references, labor rates, and work-center assignments. We migrate the employee master and labor rates to hr.employee with labor_rate stored as a custom decimal field. Payroll integration (direct deposit, tax filing) requires re-establishment with the destination payroll provider and does not migrate. Work-center assignments map to Odoo resource.calendar working hours for scheduling compatibility.

WorkWise stores documents within the application but has no documented public API for bulk document export. For on-premise WorkWise deployments, we may access the file storage directly during database extraction and archive attachments into Odoo ir.attachment linked to the corresponding record. We flag this as a best-effort operation; the customer receives a file manifest of documents not successfully linked and may use Odoo's document management module to re-associate them manually.