Migrate from Aptean Industrial Manufacturing ERP, WorkWise Edition to Epicor Prophet 21

WorkWise Customer records map directly to Epicor Kinetic Customer. We preserve the customer number, name, address, AR balance, credit limit, and payment terms. Backlog references transfer as open order counts. On-premise WorkWise deployments expose customer data in the OM_Customer table; we query by active status and cross-reference against the IM_CustomerXRef table for any EDI identifiers used in supplier communications.

WorkWise Vendor records map to Epicor Kinetic Supplier. Vendor terms, AP balances, lead times, and MRP-supplier assignments transfer. Open PO commitments map to Epicor's PO lines with expected receipt dates. Supply-side lead times are used to seed Epicor's Supplier Price Breaks and Supplier Quality Notices if those modules are in scope.

WorkWise Items carry complex attributes: stocking policy, stocking UOM vs. purchasing UOM, cost layers (FIFO, LIFO, Average), revision control, and ECN-effective date fields. We handle unit-of-measure conversions between WorkWise's stocking UOM and Epicor's Part UOM Class structure. ECN-effective date fields on Items flag which revision is currently active; we transfer the current-effective revision and optionally include the ECN date as a custom field if the full revision history scope is agreed upon during discovery.

WorkWise Sales Orders reference Customers and forward to Work Orders, with line-level pricing, promised dates, and order status. Open orders transfer with current statuses preserved. We resolve the Customer reference via the Customer number mapping established in the customer phase. Historical closed orders require a separate scope decision: a full order history transfer or an archive snapshot. Line-level pricing migrates as-is; Epicor's Price Break and Discount engine is not retroactively computed.

Open POs carry vendor commitments and expected receipt dates. We map WorkWise PO header and line fields to Epicor PO/POHeader and POLine, preserving line status, quantities ordered, and unit costs. Receipt records in WorkWise must be reopened against the imported PO identifiers in Epicor post-migration. Vendor number resolves via the Vendor-to-Supplier mapping established in the supplier phase.

WorkWise Work Orders tie to BOMs, Routings, and Work Centers, tracking planned vs. actual cost and completion status. We transfer open Work Orders with their costing layers and resolve BOM reference and Routing reference through the mapping tables. Any downstream closed Work Order records that affect job cost history are included in the Job Cost migration phase. Epicor's JobMtl and JobOper rows are generated from the Work Order's multi-level BOM explosion and routing operation list respectively.

Multi-level BOMs with ECN affectivity dates must be exploded and validated in Epicor's Product BOM structure. Parent-component relationships require careful sequencing to avoid orphan components during import. We handle the BOM explosion by resolving the current-effective BOM revision at the migration date, then building the MtlBurden and MtlPart structure per Epicor's BOM tables. ECN affectivity dates do not have a native Epicor equivalent; we store them as custom fields on the PartRevision record for audit trail purposes.

WorkWise Routings define the sequence of operations, Work Centers, and standard times used in scheduling. We map routing operations to Epicor Job Operations (JobOper), preserving the work center reference, operation sequence, standard labor hours, and run-time values. Scheduling in Epicor recomputes based on its own CRP engine; we seed the work-center calendar from WorkWise but do not pre-calculate the Epicor schedule.

WorkWise supports unlimited locations and bins with full on-hand quantities, lot numbers, serial numbers, and consignment flags. We preserve the full location/bin hierarchy in Epicor's Warehouses and Bins structure and transfer on-hand quantities to PartBin records. Negative-on-hand and consignment flags transfer as PartBin attributes. Available-to-promise is recalculated by Epicor's planning engine post-migration.

WorkWise 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 Epicor's GL Account structure. Any inter-company segment configurations are flagged for review during discovery. Custom account assignments or MOD-extended account fields are catalogued and mapped to Epicor custom fields if the customer confirms scope.

WorkWise Job Cost tracks planned vs. actual at Employee, Work Center, Department, Labor/Operation, and Component Material levels. We transfer the cost ledger entries as Epicor JobPartuhr or LaborDtl records depending on the type (labor vs. material). Planned-vs-actual values migrate as historical snapshots. Epicor's costing engine will recompute forward-looking costs; we preserve the as-reported WorkWise values for audit and comparison in a custom field.

Quality management stores inspection results, compliance alerts, and traceability links to lots and Work Orders. We map inspection records to Epicor NonConf (Non-Conformance) and Related Operation records, preserving traceability links to the imported Job and Part lot. Any destination-specific quality workflow configurations (disposition, corrective action routing) require post-migration setup in Epicor's Quality Management module.

Employee records include payroll integration references, labor rates, and work-center assignments. We migrate the employee master and labor rates from WorkWise. Payroll integration requires re-establishment with the destination payroll provider and is outside the migration scope. Labor rates migrate as Epicor EmpBasic LaborRate values and are used to seed work-center cost rates if the Epicor work-center configuration is not already in place.

Work Centers carry capacity, calendars, and cost rates used in CRP calculations. We transfer Work Center definitions and their calendar schedules to Epicor's Resource Group and Resource tables. Calendar schedules (shifts, capacity) migrate as-is; CRP capacity recomputation runs post-migration using Epicor's CRP engine, which uses the migrated work-center definitions as input.

WorkWise stores documents within the application but there is no documented public API for bulk document export. We do not migrate attachments or documents. For customers on on-premise WorkWise deployments, file paths are preserved in a custom field on the relevant Epicor record for manual retrieval by the customer's admin post-migration. For cloud WorkWise customers, we document the file store location for retrieval outside the migration scope.