Migrate from Manu Online to Epicor Prophet 21

Manu Online Products (manufactured, resold, and purchased variants) map to Epicor Part records with PartPlant entries per warehouse. Manu Online cost layers (FIFO) require a translation step: we extract the most-recent layered unit cost and apply Epicor's configured costing method (average or standard) per Part. Product code, description, unit of measure, and stock settings map from manuonline_product to Part and PartPlant during the DMT Part Master template load. Any Manu Online custom fields on products map to Epicor UD fields (Part_c) which require pre-creation in the Epicor customization layer before import.

Manu Online BOMs define the ingredient list and quantities per finished good. Multi-level BOMs (Enterprise edition) are decomposed into Epicor's Part BOM structure where each level is a separate BOM revision. We use the DMT BOM Template to load multi-level structures; sub-assemblies are loaded first so that the parent BOM resolves its PartMtl references at import time. Mini Enterprise single-level BOMs load as single revision records. BOM quantities and scrap percentages from Manu Online carry forward as MtlPartsQty and JunkScrapPercent on JobMtl.

Manu Online stock balances per product per warehouse map to Epicor PartWhse (warehouse-level quantities: OnHandQty, AllocatedQty, ReservedQty) and PartBin if bin-level tracking is used. We preserve the on-hand quantity at cutover date and set the last-cost from the FIFO layer as the Epicor Part standard or average cost. Serial and lot numbers on hand at cutover time load to PartBin with SerialNo or LotNum linkage to the PartTran transaction history that follows.

Manu Online Customers with address, contact, tax registration, and price list assignment map to Epicor Customer, CustCnt (contact person), and ShipTo (delivery address) records. Credit limit, payment terms, and currency from Manu Online transfer to Customer.CreditLimit, Customer.PaymentTermsID, and Customer.CurrencyCode. Open sales orders and the customer's active order references are preserved for linkage during the Sales Order import phase.

Manu Online Suppliers map to Epicor Supplier with SupplierPP (purchasing point) records carrying lead time, preferred purchase unit, and vendor part number. Purchase order history and outstanding open POs transfer with the supplier record so that the Supplier ID is available as a foreign key during PO import. Tax registration and address fields map directly.

Manu Online Sales Orders with line items, pricing, dispatch instructions, and status map to Epicor OrderHed (header) and OrderDtl (detail). Partially despatched lines are common in manufacturing environments; we carry the despatch state as OrderDtl.ShipLineComplete and preserve any remaining quantity as open demand. The Customer ID lookup resolves at import time via the pre-loaded Customer mapping. OrderRel records are created for each scheduled release on the Manu Online order.

Manu Online Purchase Orders link to suppliers and specify expected delivery dates and received-versus-ordered quantities. Open POs with outstanding receipt quantities carry forward to Epicor POHeader and PODetail, with PORel records representing each scheduled receipt date and quantity. Received lines are excluded or marked as closed to prevent duplicate ordering. Supplier ID resolves from the pre-loaded Supplier mapping.

Manu Online Works Orders drive production: they reference a BOM, allocate stock, and record labour time and completed quantities. We map active and in-progress Manu Online Works Orders to Epicor Job records where JobHead.JobNum is assigned, JobMtl lines carry the BOM ingredients with issued quantities, and JobOpers represent the production steps. Any unfinished progress (partial completion, allocated-but-not-issued material) carries forward as open JobMtl and JobOper records with the original start date preserved. Completed Manu Online Works Orders map to closed Epicor Job records with the full JobTran transaction history for traceability. This is the highest-complexity object mapping in the pair due to stage and WIP state handling.

Posted invoices and credit notes in Manu Online carry accounting implications and may have already been pushed to Xero. We coordinate a cutover date with the customer and exclude already-synced posted documents from live migration, or mark them as historical archive records rather than re-posting them in Epicor. The customer determines whether open invoices (not yet posted to Xero) should migrate as open OrderHed records for fulfilment or as invoiced records in Epicor's AR module. This decision gates the invoice mapping scope and is resolved during scoping.

Traceability records link serial or lot numbers to stock transactions, works orders, and delivery documents. Manu Online serial and lot data exports via the DataWarehouse PartLot and PartTran tables. We map these to Epicor SerialNo and LotNum with PartTran transaction records preserving the traceability chain from supplier receipt through production to dispatch. A pre-migration data quality check reports the percentage of lines with complete traceability; if supplier lot numbers were not recorded at goods-receipt, that inbound traceability leg will be blank in Epicor.

Manu Online user accounts with login, email, and role-based permissions map to Epicor User records. Active users are provisioned with matching usernames and emails; elevated admin privileges are flagged for explicit re-creation in Epicor Admin mode. Role and permission sets from Manu Online do not map directly to Epicor's ice_UserRowSecurity table because permission models differ structurally; we document the Manu Online role structure as a reference for the customer's Epicor admin to configure equivalent access.

Manu Online custom fields on products, customers, and orders may not be fully captured in the DataWarehouse export. We inventory all custom field definitions during scoping and verify their presence in the manuonline_ prefixed DataWarehouse tables. For fields present in the export, we pre-create Epicor UD columns (Part_c, Customer_c, OrderHed_c, JobHead_c) via Epicor customization tools before data import begins. Fields absent from the DataWarehouse are flagged for the customer to re-enter manually or extract from the Manu Online UI before cutover.