Migrate from Syscom ERP to Epicor Prophet 21

Syscom ERP item records (SKU, description, unit of measure, cost, pricing tiers) map to Epicor Part table. The Syscom item type (inventory vs non-inventory vs service) maps to Part.TypeCode in Epicor. Standard cost and current cost migrate to Part.StandardCost and Part.CurrentCost. Pricing tiers from Syscom require a pricing matrix rebuild in Epicor Kinetic or a linked CPQ tool; we flag the pricing tier data in a UD field for the admin to configure the Kinetic Price Matrix post-migration.

Syscom multi-level BOMs map to Epicor BOMHead (header with revision and effectivity dates) and BOMDetail (component lines with qty-per and scrap factors). BOMs are loaded before Work Orders because Work Orders reference BOM revisions. We extract the full BOM hierarchy and flag alternative BOMs and BOM versions that exist in Syscom; Epicor supports multiple revisions per BOM and we preserve the Syscom version label in the RevisionCode field. If Syscom BOMs reference phantom sub-assemblies, those map to Epicor Part.Method of Manufacturing = Process or Pull, which we identify during BOM analysis.

Syscom ERP customer records (billing address, shipping address, contact details, credit limits) map to Epicor Customer with the associated Party record for contact deduplication. The customer code in Syscom becomes Customer.CustID in Epicor. We flag any customers that share an email domain or address with a Syscom vendor record; in Epicor's Party model these may need to be split into a Customer record and a Supplier record rather than a single combined record.

Syscom ERP vendor records (contact information, payment terms, bank details) map to Epicor Supplier. The supplier code in Syscom becomes Supplier.VendorID. Epicor uses a separate Supplier table from Customer with its own payment terms and AP settings. We migrate vendor-specific notes and custom fields to UD columns on Supplier, and map the Syscom payment term code to Epicor's Termscd lookup table before import.

Syscom ERP Sales Order headers and lines migrate to Epicor OrderHed (order-level: customer, order date, terms, warehouse) and OrderDtl (line-level: part number, quantity, price, due date). We preserve order status (open vs closed) and flag any lines referencing discontinued Parts that require a substitute Part decision before import. Header-level discounts map to Epicor OrderHed.DiscountPercent; line-level pricing maps to OrderDtl.DocUnitPrice.

Syscom ERP Purchase Order headers and lines migrate to Epicor POPOHeader (PO-level: supplier, terms, ship-to) and POPOLine (line-level: part number, quantity, unit cost, due date). PO status (open vs closed) is preserved. We resolve the Syscom vendor ID to the Epicor Supplier.VendorID established during supplier migration. POLine.DocUnitCost migrates directly; any landed cost components from Syscom require manual configuration in Epicor's Landed Cost module post-migration.

Syscom ERP Work Orders map to Epicor JobHead (job-level: part, quantity, start date, warehouse), JobMtl (material requirements with qty-per and mtlPartNum), and JobOper (operation sequence with work center and estimated hours). Work Orders are loaded after BOMs and Parts because JobHead references the Part number and JobMtl references the BOM revision. We preserve the Syscom work order status (released, in-process, complete) and map any routing-specific notes to JobOper.OpDesc.

Syscom ERP current inventory balances at the warehouse and bin level migrate to Epicor PartWhse (on-hand quantity per part per warehouse) and PartBin (bin-level breakdown). We map Syscom warehouse codes to Epicor Warehouse.WarehouseCode and resolve the location hierarchy. On-hand values migrate to PartWhse.OnHandQty; transaction history (inventory movements, adjustments) does not migrate in standard scope. Multi-location inventory in Syscom requires Plant and Warehouse pre-configuration in Epicor before inventory data loads.

Syscom ERP chart of accounts (account codes, names, types, parent hierarchy) maps to Epicor GLAccount with segment-based structure. We extract the Syscom account code and map it to the primary account segment in Epicor; if Syscom uses a multi-segment account code (e.g., division-department-account), we map each segment to a corresponding Epicor GLAccountSeg row. Active vs inactive status migrates. Currency-specific gain/loss accounts referenced in the Syscom multi-currency setup require identification and mapping to Epicor's Unrealized Exchange Gain/Loss accounts in the GLAccount configuration.

Syscom ERP user accounts (login, roles, permissions) migrate to Epicor Kinetic UserComp and Ice.SysUserFile for security role assignment. We extract the Syscom user list and map roles to Epicor's security groups (Production, Inventory, Finance, Sales, etc.). Owner assignments on records (Orders, Work Orders) are resolved by matching the Syscom user email to the Epicor User record; users without a match enter a reconciliation queue for the customer's Epicor admin to provision before record import.

Syscom ERP custom objects and user-defined fields (which vary by module and customer configuration) map to Epicor UD tables (UD01, UD02, etc.) and UD columns on standard tables. We identify all Syscom custom fields during discovery, map their data types to Epicor field types (character to string, numeric to decimal, date to date), and pre-create the destination UD table schema before data import. Custom objects with lookup relationships to standard objects (e.g., custom projects linked to Jobs) require Epicor UD table relationship configuration before the parent record migration phase.

Syscom ERP multi-currency configuration maps to Epicor Currency (currency codes and symbols) and ExchangeRate (effective dates and rates). We extract the Syscom currency codes and exchange rate table and create corresponding Currency records in Epicor. The Syscom base currency maps to the Epicor company base currency. Any unrealized currency gain and loss accounts from Syscom's multi-currency setup are flagged as required GL account mappings in Epicor's Foreign Currency Gain/Loss configuration screen before the first currency transaction imports.

Syscom ERP multi-location warehouse configuration maps to Epicor Plant (top-level facility), Warehouse (storage location within a plant), and Bin (physical bin or location within a warehouse). We extract Syscom warehouse codes and bin records and map them to the corresponding Epicor hierarchy. If Syscom uses a single-warehouse model, we create one default Plant and Warehouse in Epicor before inventory migration. Bin control settings (active/inactive, bin type) migrate as-is.