Migrate from WinMan ERP to Microsoft Dynamics 365 Business Central

WinMan's integrated financial module with chart of accounts, cost-centre assignments, and multi-entity structures maps directly to D365's G/L Account table. Account codes map 1:1 using the WinMan account code as the G/L Account number, and cost-centre assignments map to D365 Dimensions (either DefaultDimensions or custom financial dimensions that the customer's admin configures in the destination). Multi-currency assignments on WinMan accounts migrate as D365 Currency codes on the account record.

WinMan Items with multi-level BOMs map to D365 Item Cards. We export the full product hierarchy including the BOM component lines (parent item number, component item number, quantity per, scrap %, and operation number). In D365, the parent item is created as a BOM header and each component line becomes a BOM line. Routing steps attached to WinMan work orders map to D365 Routing records with work-centre codes, setup time, run time, and concurrent capacity. For configured products, we decompose the feature/option matrix into individual BOM lines and preserve the parent-child linkage through explicit mapping rather than a single exported field.

WinMan's built-in product configurator stores feature/option matrices with rules and dependencies. Where the destination is D365 Business Central, configured products are represented as Sales BOMs (a header item with component variants) or via the Configuration Template feature. We break each WinMan configuration into its component BOM lines and map them individually, preserving the feature code and option code as item dimension values in D365. The customer chooses the representation strategy during scoping based on their order-entry workflow in D365.

WinMan Customer records with addresses, contact details, credit terms, and multi-currency assignments map to D365 Customer records. Customer-to-site mappings in WinMan migrate as D365 Customer Posting Groups and Ship-to addresses. Credit limit values map to the Customer Credit Limit field in D365, and payment terms map to Payment Terms codes that the customer's admin configures or maps from WinMan's terms definitions.

Vendor records with purchasing terms and lead times migrate alongside Purchase Orders and goods-received data. WinMan vendor-specific lead times map to the D365 Vendor Lead Time field or as planning parameters on the Vendor Card. Multi-currency vendor assignments migrate as Currency codes on the vendor record, consistent with the customer currency mapping approach.

Open and historical Sales Orders migrate 1:1 to D365 Sales Orders. WinMan guidance specifies that live orders must be migrated last, near go-live, to prevent dual-entry billing. We export a snapshot of open orders immediately before cutover, replay any delta transactions that occurred during the final testing window, and scope the delta-capture window explicitly with the customer. Sales Order lines referencing configured products map using the BOM decomposition done during the Item phase.

Purchase Orders and associated goods-received notes export from WinMan and map to D365 Purchase Orders. Where Purchase Orders reference configured BOMs, we preserve the item-link relationship during migration using the same BOM decomposition approach. Received quantities and pending receipts map to open Purchase Order lines in D365, and the customer's admin confirms receipt status at cutover.

WinMan Work Orders with routing steps, labour allocations, and work-centre assignments map to D365 Production Orders. WinMan's manufacturing mode (job, batch, or repetitive) determines the Production Order type in D365. Routing steps migrate as D365 Routing records linked to the Production Order BOM. Labour allocations and work-centre time bookings map to the Production Journal lines, and the customer admin configures the D365 work-centre calendar to match WinMan's shift and capacity definitions before migration.

Current stock levels, bin locations, and batch/serial numbers export from WinMan and map to D365 Item Ledger Entries and Warehouse Entries. WinMan's warehouse-zone assignments map to D365 bin codes and location structures. The opening inventory snapshot is posted via an inventory posting profile that the customer admin configures in D365 before migration, ensuring that the inventory values match the general ledger opening balances.

Traceability links between batch/serial numbers, incoming materials, and finished goods require careful sequencing to preserve the graph in D365. We export WinMan's traceability records and map them to D365 Item Tracking Codes (lot number and serial number settings) and Item Ledger Entry tracking links. The traceability graph so that downstream recall and compliance reporting remain functional after migration. For regulated manufacturing environments, we validate that the lot and serial number assignments are consistent across the inbound receipt, production consumption, and outbound shipment records.

WinMan supports user-defined fields on standard objects. We extract custom field definitions and map their values to equivalent AL-based custom fields in D365 Business Central or to custom fields in D365 Finance and Supply Chain Management. Where D365 does not have an equivalent field type or the data does not fit a typed field, we flag the value for manual entry review by the customer admin before go-live.

User accounts with role-based permissions export from WinMan, but role definitions vary significantly between ERP systems. We map WinMan role names to the closest D365 Permission Set or Security Role equivalent and flag any security differences. User provisioning in D365 requires the customer's tenant admin to create Microsoft 365 Entra ID-linked users, which we coordinate with the customer during the migration window. Permissions are validated by the customer admin post-provisioning.

WinMan stores documents against orders, items, and work orders as attachments. We export document references, filenames, and file paths. Binary file transfer depends on the destination's attachment storage model: D365 Business Central uses Incoming Documents and Record Links; D365 Finance and Supply Chain Management uses Shared Document Storage or SharePoint integration. We map the document references to the equivalent D365 entity and flag any files that require a manual upload if the file path is not accessible during migration.