Migrate from WinMan ERP to Infor CloudSuite Corporate

WinMan's integrated financial module with account codes, cost-centre assignments, and journal entry history maps to the Infor CloudSuite chart of accounts. We preserve multi-entity assignments where WinMan uses cost centres as sub-account dimensions, mapping them to Infor's company or cost centre structure. Prerequisite data (account types, currency codes, fiscal calendar setup) must be entered in Infor forms before transactional data migrates per Infor's sequential form entry requirement.

WinMan Items with Bills of Materials, variants, and product attributes map to Infor CloudSuite MITM (Master Item) records. The WinMan product type (finished good, component, sub-assembly, phantom) maps to Infor's item type field. Unit of measure conversions from WinMan (each, kg, litre) map to Infor's UOM setup. Inactive items flagged during the data-quality phase are excluded from migration or imported as inactive in Infor.

WinMan multi-level BOMs with component links and quantities per assembly map to Infor Manufacturing BOM (MBOM) records. We preserve the parent-child BOM structure through explicit MBOM sequence lines with component item references, quantity-per, and operation references. Phantom BOMs (for sub-assemblies used only as components) map to Infor phantom BOM indicators. Work-centre assignments from WinMan routing steps map to Infor PRTM (production routing) operations.

WinMan's product configurator with feature and option matrices, rules, and dependencies decomposes into individual MBOM component lines in Infor CloudSuite. We extract the configuration header from WinMan (configuration code, selected options, pricing) and break it into separate BOM lines, preserving the parent-child relationship through explicit MBOM linkage rather than relying on a single WinMan configuration export field. The Infor Configurator module is required in the destination edition for ongoing configuration capability.

WinMan Customer records with addresses, contact details, credit terms, and multi-currency assignments map to Infor OCUST records. Customer-to-site mappings from WinMan become Infor address book entries linked to the customer. Credit limit, payment terms, and tax code assignments migrate as OCUST extensions. Multi-currency assignments from WinMan map to Infor's currency configuration for the customer.

WinMan Vendor records with purchasing terms, lead times, and address information map to Infor OSUPP (Supplier Master) records. Vendor-specific price lists and purchasing terms migrate as supplier extensions. The WinMan goods-received note linking to purchase orders requires the PO to be migrated before GRN records are imported, preserving the purchase-order-to-receipt relationship.

Open and historical WinMan Sales Orders map to Infor OHCO records. Open orders are migrated last per WinMan's own migration guidance and Infor's prerequisite-data sequencing model to avoid dual-entry during the cutover window. WinMan order status (pending, confirmed, despatched, invoiced) maps to Infor order status. Order-line pricing, discounts, and taxes migrate as OHCO extensions. We capture a delta snapshot of any orders modified during the final testing window before go-live.

WinMan Purchase Orders and associated goods-received notes map to Infor OPOR and OIGN (goods receipt) records. Where WinMan purchase orders reference configured BOM components, we preserve the item-link relationship during migration. Open purchase orders follow the same late-cutover sequencing as sales orders. Purchase order approvals and holds from WinMan map to Infor workflow status flags.

WinMan Work Orders with routing steps, labour allocations, and work-centre assignments require field-level mapping to Infor CloudSuite production order structure. WinMan's manufacturing mode (job, batch, or repetitive) determines the Infor production order type. Routing operations with work-centre codes, setup time, and run time map to Infor PRTM operations attached to the production order. Labour bookings and WIP transactions from WinMan become Infor labour reporting entries against the production order.

Current WinMan stock levels, bin locations, and batch or serial numbers map to Infor MITX (Inventory Transaction) and MITL (Lot) or MISSN (Serial) records. WinMan's WMS integration means stock records include warehouse-zone assignments that map to Infor warehouse and location codes. Batch and serial number tracking for regulated manufacturing (medical devices, food and beverage, automotive) preserves the traceability link to incoming materials and finished goods.

WinMan traceability links between batch and serial numbers, incoming materials, and finished goods require careful sequencing during migration. We preserve the full traceability graph so that downstream recall and compliance reporting in Infor CloudSuite references the correct MTRL lot records and MITXN transaction links. WinMan traceability queries must map to Infor's lot genealogy and serial genealogy reports, which have different field names and navigation paths.

WinMan user-defined fields on standard objects (Item, Customer, Sales Order, Work Order) are extracted with their field definitions and mapped to Infor CloudSuite user-defined field equivalents or to standard Infor extension tables. Field types (text, numeric, date, checkbox, dropdown) are matched to Infor's UDF data types. Custom fields without a direct Infor equivalent are flagged for manual entry or logged as a post-migration configuration task for the customer's Infor administrator.