Migrate from SYSPRO to Epicor Prophet 21

SYSPRO Customer master records map to Epicor Customer. The Customer.CustID becomes Epicor Customer.CustNum with a pre-seeded CustID mapping table. We extract all standard address, contact, credit limit, and tax code fields, plus custom Form Entry fields attached to the customer take-on program. AR open invoice balances migrate as Epicor open invoices linked to the Customer. Multi-site Customers that exist in SYSPRO with site-specific pricing or credit limits are resolved against Epicor's Customer and ShipTo relationship with territory assignments per Plant.

SYSPRO Supplier master records map to Epicor Supplier. We extract vendor address, EDI/XML trading-partner flags, contract pricing, and payment terms. Supplier's AP open invoice balances migrate as Epicor open AP invoices linked to the Supplier. Multi-site Suppliers are resolved against Epicor's Supplier and PurPoint relationship with PO approval routing per Plant.

SYSPRO Inventory items map to Epicor Part. The Part.PartNum becomes the primary key; we map Stock Code attributes to Epicor's Part master including unit of measure conversions, cost layers, and stocking location flags. Multi-warehouse SYSPRO setups require us to flatten or pivot bin-level quantities into Epicor PartWhse records per Plant and Warehouse. Lot traceability settings migrate to Epicor's Lot setup and the PartLot table.

Open and historical Sales Orders migrate with header and line items, pricing, and fulfillment status. SYSPRO order status (back-order, partial ship, complete) maps to Epicor OrderRel.OpenRelease status. We flag back-ordered lines that may not resolve in Epicor without manual line-item re-entry. Header-level discounts and line-level pricing from SYSPRO's pricing matrix migrate to Epicor's OrderDtl with the price break logic preserved as OrderQtyMind and related price break records.

SYSPRO Purchase Order headers and lines migrate including receipt status. Blanket PO releases and EDI/XML export flags are preserved to maintain supplier relationship continuity. POLine.ReceivedQty maps from SYSPRO's receipt tracking, and partial receipts are represented as Epicor PORel records with open release quantities. Release-against-blanket logic from SYSPRO carries forward as Epicor blanketcurrency and blanketrelease records.

SYSPRO BOM structures with multi-level component routing and phantom assemblies require recursive extraction. We preserve bill versions and effective dates per SYSPRO revision tracking and map to Epicor's BOM and BOMAsm records with revision-controlled engineering and production BOMs. Phantom assembly flags in SYSPRO map to Epicor BOMAsm.MtlPartNum references with the SubContract=False and RelatedOperation=0 pattern. Effective date sequencing from SYSPRO becomes Epicor revision effective dates.

SYSPRO Jobs map to Epicor's JobHead with constituent JobOper (operation routing), JobMtl (material issues), and LaborDtl (labor posting) records. Job status, work-center assignments, and WIP valuations from SYSPRO map to Epicor JobHead.JobClosed, JobOper.SetupBurRate/RunBurRate, and JobMtl.IssuedQty. We resolve SYSPRO work-center codes to Epicor Workstation records in the destination Plant before migration. Multi-site SYSPRO jobs map to Epicor Plant-based job records with Plant-specific cost center assignments.

SYSPRO AR invoices and AP invoices including multi-currency headers and line-level tax codes migrate to Epicor InvcHead and InvcDtl. Contra-invoice relationships used for AP netting are preserved via custom mapping logic to Epicor's APTran and APLiaison records. Historical invoice PDFs stored as attachments in SYSPRO migrate as Epicor DocumentRefs linked to the corresponding InvcHead.

SYSPRO account codes, cost-center structure, and journal-entry templates extract cleanly from the master file setup. We map account types and posting groups to Epicor GLAccount with the account structure preserved as Epicor's natural account, division, department, and subaccount segments. Journal entry templates from SYSPRO map to Epicor GLJournalTemplate and recurring GL entries.

SYSPRO operators carry security-role assignments and MFA enrollment records. Operator-level restrictions translate to Epicor's UserComp and SecUser values, but the security models differ significantly. SYSPRO's program-level security restrictions require us to map to Epicor's Plant-specific and Company-specific permission sets. We extract operator definitions and deliver a written permission map for the customer's admin to apply in Epicor.

SYSPRO custom Form Entry fields attached to specific programs (customer take-on, order entry, etc.) include lookup references and formula-driven values. We extract the field definition first to understand which fields exist on which programs, then pull field data in the same program context. Formula fields are flagged as requiring re-evaluation in Epicor Kinetic because the underlying data transformation logic differs. Epicor UD fields and Ice table columns are created with equivalent types and the migrated data is loaded into the UDXX tables.

SYSPRO's multi-site architecture with independent or shared master data maps to Epicor's Plant and Warehouse hierarchy. We identify all active SYSPRO sites, determine which data is site-local vs. shared, and extract site-specific data separately before reconciling against Epicor's Plant records. SYSPRO site-specific customers, suppliers, and inventory items receive Plant-specific assignments in Epicor. Cross-site transactions (inter-company orders, transfer orders) are mapped to Epicor's InterCompany trading partner configuration.

SYSPRO job routing data with work-center codes, setup time, run time, and labor rates maps to Epicor JobOper. We resolve SYSPRO work-center definitions to Epicor Workstation and WorkCenter records in the destination Plant. Step labor and overhead rates migrate to JobOper.SetupBurRate, RunBurRate, and ProdBurRate. Alternate routing sequences from SYSPRO map to Epicor JobOper with AlternateMethod=True.

SYSPRO multi-warehouse inventory with bin-level quantities per Stock Code requires flattening into Epicor PartWhse records per Plant and Warehouse. SYSPRO stocking location codes map to Epicor WareHouse and Bin records with bin-type designations (STOCK, PICK, PACK, SHIPPING) set during configuration. Quantity on hand, committed, and available migrate to PartWhse.QtyOnHand, QtyReserved, and QtyAvailable with adjustment reason codes preserved.

SYSPRO Business Objects custom apps and lightweight automations built within the framework cannot be migrated as code to Epicor. We deliver a written inventory of every Business Objects app with its trigger, business logic, data source, and recommended Epicor Kinetic equivalent (BAQ, REST endpoint, or Kinetic Framework custom code). The customer's admin or an Epicor implementation partner rebuilds these post-migration.