Migrate from MRPeasy to Epicor Prophet 21

MRPeasy Items map to Epicor Part records. PartNum (from MRPeasy part_number), PartDescription, UnitPrice, and CostMethod (Standard/Average/Lot) migrate directly. We resolve the Part's UOMClass via PartUOM since MRPeasy stores purchase and sales UOMs separately. MRPeasy's stock quantity is NOT set here—it's set during the Inventory Levels step. Items with MRPeasy custom fields require the customer to pre-create Epicor UD columns on Part before Part import, as Epicor does not have an equivalent flexible custom-field system to MRPeasy's Settings -> System -> Custom fields.

MRPeasy BOMs decompose into Epicor PartRev (the revision header, holding revision code, effectivity dates, and BOM type) and PartMtl (one row per component, holding the material's PartNum, QtyPer, and BOMSequence). Multi-level BOMs (where a component is itself a manufactured part) require us to set PartMtl.MtlBurden = 1 and link through the nested PartRev. Co-product and disassembly BOMs (Professional+ in MRPeasy) map to PartRev.ReviewedReq = false flags for admin sign-off in Epicor before production use.

MRPeasy Routings map to Epicor PartOpr records within the same PartRev revision. Each routing operation becomes a PartOpr row with OpSeq, WorkstationSeq, ProdStandard, EstSetHours, and EstLabHours. MRPeasy's Workstation Groups and Workstations cannot be imported via CSV in MRPeasy (per MRPeasy's documentation)—they must be manually configured. We flag this: the customer must create Workstation Groups and Workstations in Epicor (Epicor uses ResourceGroup and Resource tables) before PartOpr import so the PartOpr.WorkstationSeq can reference a valid ResourceGroup or Resource. Parallel and overlap operations from MRPeasy Routing map to PartOpr.SubContract, PartOpr.AutoReceive, and PartOpr.ProdStandard values.

MRPeasy Manufacturing Orders map to Epicor JobHead (header) with linked JobMtl (material components) and JobOper (operations). MRPeasy's single MO record must be split: JobHead stores status, start/end dates, and quantity; JobMtl stores one row per component drawn from the BOM; JobOper stores one row per routing operation. Epicor's scheduling engine recalculates start/end dates on JobHead on import based on current PartOpr capacity and Material Availability, just as MRPeasy's Dynamic Rescheduling engine does. We flag active/open MOs during scoping, advise the customer to close or freeze them before import where possible, and document the post-import JobHead date delta. Historical MOs migrate as completed JobHead records with actual labor and material costs carried forward.

MRPeasy Customers map to Epicor Customer records. CustID (from MRPeasy customer_code), Name, Address, City, State, Zip, Country, Phone, Fax, and EMailAddress migrate directly. TaxID maps to Customer.TaxRegionCode. Customer price list assignments from MRPeasy migrate to Epicor PriceLcl records attached to the Customer. We create Customer records before any Order or Quote import to satisfy the FK reference. MRPeasy's customer-specific price list lines are mapped to Epicor's price break structure via PriceLcl during the Price Lists step.

MRPeasy Vendors map to Epicor Supplier records. VendorID (from MRPeasy vendor_code), Name, Address, City, State, Zip, Country, Phone, Fax, EMailAddress, and PaymentTerms migrate directly. MRPeasy's documented import sequence (Vendors before Items) is followed because Supplier records may be referenced on Part (Part.LeadTime, Part.VendorNum). We map Purchase Terms per vendor-item pair to Epicor SupplierPriceList or PartXRefVend records. Vendors without a vendor_code in MRPeasy are assigned a generated SupplierID based on MRPeasy's internal ID during migration.

MRPeasy Inventory Levels map to Epicor PartBin records. PartBin.PartNum, PartBin.WarehouseCode, PartBin.BinNum, and PartBin.OnhandQty migrate from MRPeasy's storage location and quantity data. MRPeasy's 3,000-line CSV cap applies to Inventory Level exports on lower tiers; large warehouses with thousands of SKUs require chunked export with sequential upload into Epicor. We chunk inventory exports by storage location and upload in sequence, tracking partial completion to avoid duplication. MRPeasy Storage Locations must be manually created in Epicor (Warehouse and Bin records via Epicor Warehouse/Bin maintenance) before PartBin import so that BinNum references are valid.

MRPeasy Stock Lots map to Epicor PartLot records linked to PartBin. MRPeasy's lot/batch number, quantity, expiry date, received status, and storage location map to PartLot.LotNum, PartLot.OnhandQty, PartLot.ExpirationDate, PartLot.DateReceived, and the PartLot.WarehouseCode reference. Serial number tracking from MRPeasy Professional+ migrates to Epicor's PartLot with SerialNumber tracking enabled on the Part record (Part.SerialTracked = true). Expiry dates from MRPeasy carry forward as PartLot.ExpirationDate. We create Part records with the tracking flag enabled before PartLot import to satisfy the PartNum FK constraint.

MRPeasy Price Lists (customer-specific and product-specific pricing with currency) map to Epicor PriceLcl records. MRPeasy's price-per-unit, currency, minimum quantity, and effective date map to PriceLcl.UnitPrice, PriceLcl.CurrencyCode, PriceLcl.BreakMinQty, and PriceLcl.EffectiveDate. MRPeasy's multi-currency support means we map each MRPeasy price list line to an Epicor PriceLcl with the correct CurrencyCode; Epicor's multi-currency GL must be configured (Company.CurrencyMode) before price list import to ensure exchange rate application is correct. Tiered pricing from MRPeasy Professional+ becomes multiple PriceLcl rows with sequential BreakMinQty values.

MRPeasy Transfer Orders map to Epicor TransferOrderHead and TransferOrderDetail records. MRPeasy's lifecycle states (New, Ready, Shipped, Received, Canceled) map to TransferOrderHead.Status. MRPeasy's explicit note that 'Received' status is manual (not auto-completed) in MRPeasy is documented in our cutover checklist: in-transit orders land in Epicor as TransferOrderHead.Status = Shipped and require manual completion. Transportation costs and waybill reference from MRPeasy Transfer Orders map to Epicor TransferOrderHead.Freight charge and TransferOrderHead.Waybill fields. From-warehouse and To-warehouse codes map to WarehouseCodeFrom and WarehouseCodeTo on the detail row.

MRPeasy's built-in accounting module Chart of Accounts migrates to Epicor GLAccount records. MRPeasy account codes (revenue, cost, asset, liability, equity) map to Epicor's COA structure, which includes Company, FiscalYear, FiscalPeriod, and AccountPS fields. Non-standard MRPeasy account codes (custom accounts beyond the standard types) are flagged for manual reconciliation during Epicor's GL account setup. MRPeasy's financial transaction history (invoices, payments, journal entries) migrates to Epicor GLJrnDtl records with appropriate fiscal period assignment; fiscal year and period configuration in Epicor (GLFiscPeriod table) must be completed before financial data import.

MRPeasy Users map to Epicor UserFile records. We export user records (user code, name, email, role, active/inactive status) from MRPeasy via the table export function and import into Epicor's UserFile table. Role assignments from MRPeasy (Admin, Production Manager, Buyer, etc.) map to Epicor SecurityRole assignments. MRPeasy does not support SSO or directory integration on Starter/Professional tiers; Epicor ERP supports SAML-based SSO which may be configured post-migration. Inactive MRPeasy users are created as inactive Epicor UserFile records to preserve historical assignments on closed MOs and historical records.