Migrate from WinMan ERP to Epicor Prophet 21

WinMan maintains a fully integrated financial module with chart of accounts, journal entries, and AP/AR. Accounts map 1:1 using WinMan account codes to Epicor GL Account numbers. We preserve cost-centre assignments where multi-entity structures exist by mapping WinMan site-specific accounts to Epicor GL Account segments. Any intercompany elimination accounts require manual Epicor configuration post-migration.

WinMan Items map to Epicor Part records. WinMan's item type classification (Stocked, Non-Stocked, Service, Labour) maps directly to Epicor Part Type. The WinMan Item Code becomes Epicor Part Number; the description maps to Part Description. Stock UOM, Purchasing UOM, and Sales UOM from WinMan map to Epicor UOMClass and UOM records, requiring a UOM conversion table where they differ.

WinMan multi-level BOMs map to Epicor Part BOM records with parent Part linked to child Part via BOM lines. We preserve the full BOM hierarchy (WinMan allows up to 99 levels) by performing a recursive export from WinMan and loading into Epicor's BOM Master with the correct BOM Level and Sequence. Operation numbers, work centres, and scrap percentages from WinMan map to Epicor JobMtl and JobOper records during Work Order creation.

WinMan's product configurator allows complex feature/option matrices with rules and dependencies that do not have a direct Epicor equivalent. We decompose each configured product into its component BOM lines in WinMan, map the parent configured item to an Epicor Part record, and create child BOM lines for each option. The parent-child linkage is preserved through explicit BOM reference rather than relying on a single exported configuration string. The customer's Epicor admin rebuilds the configure-to-order rules in Epicor's CPQ or Product Configurator module post-migration using the WinMan feature/option export as a reference.

WinMan Customer records map to Epicor Customer including addresses, contact details, and credit terms. Customer-to-site mappings from WinMan become Epicor ShipTo records attached to the Customer. Multi-currency assignments migrate to Epicor Currency and Exchange Rate records. We use WinMan Customer Code as the dedupe key during import.

WinMan Vendor records map to Epicor Supplier with purchasing terms, lead times, and vendor part numbers preserved. Vendor addresses migrate as SupplierShipTo records. Any consignment or subcontract vendor setups require manual Epicor configuration post-migration.

Open and historical Sales Orders migrate to Epicor OrderHed (header) and OrderDtl (detail) records. WinMan order status maps to Epicor OrderHed.OrderStatus. WinMan guidance specifies that live orders migrate last; we handle this by exporting a snapshot of open orders immediately before cutover, then replaying any delta transactions that occurred during final testing. Order lines referencing configured products use the decomposed BOM linkage from the configured product mapping step.

WinMan Purchase Orders and associated goods-received notes export to Epicor POHeader and PODetail records. Where purchase orders reference WinMan configured BOMs or multi-level BOMs, we preserve the item-link relationship during migration by resolving WinMan BOM references to Epicor Part BOM records at migration time. Purchase order status in WinMan (Open, Released, Closed) maps to Epicor POHeader.POStatus.

WinMan Work Orders with routing steps, labour allocations, and work-centre assignments require field-level mapping to Epicor JobMtl (material) and JobOper (operation) records. WinMan's work order structure varies by manufacturing mode (job, batch, or flow), and we handle each variant separately. Estimated labour hours, work-centre codes, and operation sequences from WinMan map to Epicor JobOper with the correct Work Centre reference and cycle times. Released, complete, and closed statuses from WinMan map to Epicor JobHead.JobReleased, JobHead.JobComplete, and JobHead.JobClosed.

WinMan current stock levels, bin locations, and batch/serial numbers export to Epicor PartBin records. WinMan's WMS integration means stock records include warehouse-zone assignments that map explicitly to Epicor Warehse and Bin records. Batch and serial numbers migrate to Epicor PartLot and PartNumLotTrak records respectively, preserving the traceability graph linking incoming materials to finished goods. Multiple WinMan sites map to multiple Epicor warehouse records with separate PartBin entries.

WinMan batch/serial traceability links between incoming materials and finished goods require careful sequencing to preserve the graph in Epicor. We export WinMan traceability records as a linked set (lot number, source document, material used, finished goods produced) and load into Epicor PartLot with LotNbr, LotDescription, and the PartTran records that represent each movement. Post-migration recall and compliance reporting rely on this graph being intact.

WinMan user-defined fields on standard objects export with their definitions and values. Epicor supports UD fields on Part, OrderHed, OrderDtl, JobHead, JobMtl, and other standard tables. We extract WinMan custom field definitions, map their values to equivalent Epicor UD columns, and flag any custom fields with no Epicor equivalent for manual entry or custom Epicor extension (BPM or customization) post-migration.

WinMan user accounts with role-based permissions export by email and mapped to Epicor User records. Role definitions vary between ERP systems; we map WinMan roles to the closest Epicor equivalent (Plant, Production, Sales, Engineering, etc.) and flag any security differences that require manual configuration in Epicor Employee and UserAccount tables. Inactive WinMan users can be migrated as inactive Epicor users for historical reference.