Migrate from WinMan ERP to Acumatica

WinMan ERP stores companies in a single table with a type flag (customer, vendor, or both). Acumatica separates these into Customer and Vendor entity classes. Companies with only sales transactions route to Customer; companies with only purchase transactions route to Vendor; companies with both require two Acumatica records linked by the same name. The WinMan type flag is preserved as Customer_Vendor_Type_Source__c for audit continuity.

WinMan contacts map 1:1 to Acumatica contacts with email as the primary lookup key. Contacts are attached to Customer or Vendor records already created in the company-split step. WinMan contact roles (buyer, approver, account manager) map to Acumatica contact classes or are preserved as attributes on the Contact record.

WinMan company addresses migrate as Address records linked to the corresponding Customer or Vendor. Multiple addresses per company (billing, shipping, plant) map to separate Address records in Acumatica with distinct address IDs and purposes. The address-type flag from WinMan drives the AddressID naming convention in Acumatica.

WinMan items in a single table split into Acumatica Stock Items (for stocked/MTS parts) and Non-Stock Items (for MTO, service, and miscellaneous items) based on WinMan's stock-flag field. Every Acumatica item requires an Item Class; FlitStack maps WinMan item categories to existing Acumatica item classes or creates new class codes as part of the schema setup plan.

WinMan site-specific stock quantities map to Acumatica warehouse records scoped to the corresponding branch. Each WinMan site code becomes an Acumatica branch + warehouse pair. On-hand quantities per site transfer as Item Warehouse records linking the migrated item to the correct warehouse ID. Bin-level location data from WinMan is preserved as a custom field on the Item Warehouse record.

Open WinMan sales orders migrate as Acumatica Sales Orders with status Open. Order dates map to Acumatica's OrderDate; requested ship dates map to ShipDate. Line items reference the migrated item records. The WinMan order number is preserved in the ReferenceNbr field for traceability. Historical closed orders are migrated in migration mode with original document dates and amounts preserved as open balances.

Open WinMan purchase orders migrate as Acumatica Purchase Orders with status Open. Vendor lookup resolves to the Vendor record created from the company-split step. Line items reference migrated items. The WinMan PO number is preserved in ReferenceNbr. Historical closed POs migrate in migration mode, preserving the original document date and total amount as the open balance in Acumatica.

WinMan AR invoices map to Acumatica AR Invoice documents; WinMan AP invoices map to Acumatica AP Bill documents. WinMan invoice dates become document dates; original amounts become the open balance. These migrate in Acumatica migration mode — they update customer/vendor balances but do NOT post to the general ledger. A reference field links each migrated document back to the WinMan record ID for audit purposes.

WinMan GL accounts map 1:1 to Acumatica GL accounts using the account code as the AccountID. Account descriptions, account types (asset, liability, equity, income, expense), and active/inactive status transfer directly. Acumatica's subaccount structure is evaluated — if WinMan uses cost centre subaccounts, these map to Acumatica subaccounts with the same segment ID.

WinMan tax codes map to Acumatica Tax Zones based on the jurisdiction (country/state/province) and tax type (VAT, GST, sales tax). WinMan tax rates are applied to the corresponding Acumatica Tax Zone detail lines. If WinMan uses non-standard tax codes, the Acumatica admin configures matching Tax Zones before the migration runs so invoice totals reconcile.

WinMan payment terms (Net 30, 2/10 Net 30, COD, etc.) map to Acumatica Payment Terms by exact name match or closest equivalent. If WinMan uses custom payment term names, these are created as new Payment Term records in Acumatica before the migration, with the same due-day calculation logic applied.

WinMan currency codes (GBP, USD, EUR, etc.) map directly to Acumatica Currency records using the ISO currency code. Exchange rates from WinMan are imported into Acumatica's Currency Rate table before transactions migrate so multi-currency document amounts calculate correctly in the base currency.

WinMan user-defined fields on companies, contacts, items, and orders migrate as Acumatica Custom Attributes attached to the corresponding entity screens. Pick-list UDFs in WinMan are mapped to Acumatica detail IDs within the custom attribute. Long-text UDFs migrate as free-text custom attributes. Acumatica custom fields use the EntityAttribute schema — attributes are defined per-screen and attached during the schema setup phase.

WinMan bills of materials map to Acumatica BOM and Route records for the migrated stock items. BOM line quantities and scrap percentages transfer as-is. If WinMan uses multiple BOM versions per item, these map to Acumatica BOM versions with the same effective date logic. Production routings map to Acumatica production bills linked to the same item class.