Migrate from WINLine to Epicor Prophet 21

WINLine stores the G/L account master with account codes, cost center assignments, and tax codes in flat-file format. We parse the account structure and load into Epicor GLAccount, preserving the WINLine account code as Account and the description as GLAccountDesc. Cost center assignments map to Epicor's Segment codes if the customer uses dimensional accounting; we flag this for configuration during schema design. Tax codes map to TaxRegion records in Epicor based on the WINLine tax setup matrix.

WINLine Customer records include billing addresses, payment terms, credit limits, and currency. We extract all active customers and map them to Epicor Customer by Company as the dedupe key. ShipTo addresses migrate as CustomerPriceCorp records linked to the parent Customer. Credit limits and payment terms map to CreditHold, CreditLimit, and Terms records in Epicor. Currency codes from WINLine map to Currency records in Epicor before Customer insert to satisfy the foreign-key constraint.

WINLine Vendor master data covers contact details, tax registration, payment terms, and bank account info. We extract vendor records and map them to Epicor Supplier, using VendorName as the dedupe key. Tax registration (ABN in the Australian context) maps to SupplierTaxRegion records. Payment terms and bank details migrate to POOptions and VendorBankAcct records. Any custom vendor classifications from WINLine map to SupplierUOM or a User-Defined Field on Supplier.

Outstanding invoices, credit memos, and payment records are tracked per customer and vendor in WINLine. We extract open items with invoice numbers, amounts, due dates, and aging buckets and push them as open APInvoice and ARInvoice records in Epicor. Invoice numbers become InvoiceNum; aging bucket values map to aged balances for reconciliation. Any unapplied credit memos load as negative-balance invoices. We set the InvoiceDate to the original WINLine transaction date and calculate DueDate from the migrated terms. Closed historical invoices may be migrated as reference data or archived per the customer's scope decision.

WINLine Items include SKU, description, unit of measure, cost price, and sell price. We map SKU to PartNum, description to PartDescription, and unit of measure to UOMClass and UOMCode records in Epicor. The inventory valuation method (FIFO or average cost) must be confirmed with the customer before mapping to ensure consistency with Epicor's costing configuration. Part-specific pricing migrates to PartPlant and PriceList records. Discontinued or inactive items from WINLine load as inactive Parts in Epicor unless the customer specifies otherwise.

WINLine tracks stock levels by warehouse location. We extract current quantities and map them to Epicor PartWhse (per warehouse) and PartBin (per location within a warehouse). Negative stock or discrepant quantities in WINLine are flagged in a reconciliation report before loading. Warehouse codes from WINLine must map to existing Warehse records in Epicor; we create the warehouse structure during schema design if it does not already exist.

WINLine BOMs store multi-level product structures with version history and effective dates. Epicor supports BOMs via JobMtl (job-level materials) or BOMProduct (master BOM with revision control). We migrate the active BOM version at cutover and preserve the version identifier in a UDF field. BOM lines map material PartNums to JobMtl records with quantity-per and scrap-percent values. Any BOMs with pending revisions are flagged for customer review before finalizing the load. Phantom BOMs and BOMs with linked recipes require special handling that we document during discovery.

WINLine work orders and production orders map to Epicor JobHead (job header) and JobOper (job operation) records. The JobHead holds the job number, status, start and end dates, and quantity; JobOper holds the routing steps with work center assignments. Open jobs migrate with their current status; completed jobs may be migrated as historical reference or excluded per scope. We map WINLine production order priority to Epicor JobHead.JobPriority and flag any jobs with material shortages for customer review.

WINLine tracks asset registers with acquisition date, cost, accumulated depreciation, and useful life. We extract the full asset register and push it to Epicor FaAsset, recalculating depreciation schedules if the Epicor fiscal year setup differs from WINLine's. Asset class codes from WINLine map to FaAsset.FAssetGroupID and FaAsset.FaDepartmentID. Any fully depreciated assets load with AssetNum, cost, accumulated depreciation, and a zero remaining useful life. Asset postings and disposal records migrate as FaAsset transactions.

WINLine quotes, sales orders, and invoices migrate to Epicor SalesOrder and OrderRel (releases per line). We extract open orders with line items, quantities, and pricing, mapping WINLine order status to Epicor OpenFlag and OrderRel.OpenRelease. Line item PartNums resolve against the Part catalog. Historical closed orders may be migrated as reference records or archived; open orders load as active SalesOrders with OrderRel entries. Pricing from WINLine migrates to OrderDtl unit price and any applicable discounts.

WINLine's sales management and CRM contacts map to Epicor Person and Contact records linked to Customer. We extract contact names, roles, phone numbers, and email addresses and map them to Epicor's Contact table with the Customer as the primary parent. If WINLine stores contact-specific pipeline data (quotes, opportunities), we map it to Epicor QuoteHed or OrderHed linked to the Contact via the CRM extension. Sales activity history from WINLine CRM migrates to Epicor ShipTo or QuoteHed for timeline continuity.

WINLine maintains a document archive tied to transactions and master records. We extract linked documents and binary attachments and re-attach them to corresponding Epicor records using the ice_BackgroundAttachment table or the document management path structure. We map the original WINLine document type to Epicor's DocType field. Very large file attachments or image-heavy document archives may be migrated to Epicor's SharePoint integration or external document storage with a reference link in Epicor, per the customer's preference.

WINLine allows custom fields on most master records. Epicor Kinetic supports User-Defined Tables (UDT) and User-Defined Properties (UDP) to replicate this data model. We extract every WINLine custom field value during discovery, define matching UDT/UDP definitions in Epicor during schema design, and load values alongside the standard fields. Any WINLine custom fields that have no Epicor equivalent are flagged for the customer's admin to configure as additional UDPs before the production migration run.

If the source system is WINLine compact (cloud), we assess the available REST API endpoints on a per-customer basis as access may be edition-gated. We use Epicor Kinetic's REST API for all data loading with OAuth 2.0 authentication, batch chunking, and rate-limit handling. WinLine compact API responses are transformed through the same mapping logic as flat-file exports. Any API rate-limit responses from Epicor trigger exponential backoff before retry.