Migrate from Infor SyteLine / Infor CloudSuite Industrial to Epicor Prophet 21

SyteLine Customer master records (address, payment terms, credit limits, salesperson assignment) map to Epicor Customer. SyteLine's bespoke SQL column set for CRM attributes (credit hold flags, tax exempt status, ship-to defaults) maps to corresponding Epicor Customer fields or UD columns. Multi-site customers in SyteLine may have per-site customer assignments that map to Epicor's CustomerShipTo table with CustomerID as the parent lookup. We resolve Customer records before any Sales Order import to satisfy Epicor's OrderHed foreign-key requirement on CustomerID.

SyteLine Vendor master records map to Epicor Supplier. Bank details, purchasing terms, and ship-via codes from SyteLine map to the corresponding Supplier fields. SyteLine enforces that Vendor records exist before Purchase Orders; Epicor enforces the same referential constraint on POHeader.VendorNum. We sequence vendor imports as a prerequisite phase before any PO migration begins.

SyteLine Items (stocked, non-stocked, and service items) map to Epicor Part. The item type classification (Stocked, Non-Stock, Sales Kit, Miscellaneous) maps to Part.TypeCode. Cost layers from SyteLine (standard, average, lot) map to PartCost records in Epicor. For configure-to-order items, SyteLine CPQ configuration data maps to Epicor Part.ConfigTable and PartRev engineering data. Site-specific stocking locations in SyteLine map to Epicor PartWhse (part-warehouse) assignments.

SyteLine BOMs are multi-level structures stored against the Item record. Each BOM level with materials and operations becomes a set of Epicor PartMtl (material requirement) and PartOpr (operation step) records attached to a PartRev revision. Phantom BOMs in SyteLine map to PartMtl with PhantomBOM = true in Epicor. We preserve BOM sequence numbers and operation work centers, mapping SyteLine work center codes to Epicor Resource Group and Resource records. Sub-assemblies resolve to child PartRev entries in the same import batch.

SyteLine Jobs are the core manufacturing work-order entity containing embedded materials, operations, and status. Each SyteLine Job decomposes into an Epicor JobHead (job header with job number, part number, start date, quantity), a set of JobMtl records (material requirements linked from SyteLine job materials), and JobOper records (operation steps linked from SyteLine job operations). Job status (released, complete, closed) maps to JobHead.JobReleased, JobHead.JobComplete, and JobHead.JobClosed flags. Part numbers on the JobHead resolve to Part records imported in the Item phase; if a part is missing, the Job import pauses until the Part is created to prevent orphan linkage.

SyteLine Sales Orders map to Epicor OrderHed (order header) and OrderDtl (order lines). The SyteLine order-header fields for terms, ship date, and salesperson map to the corresponding Epicor header fields. Each SyteLine order line (item, quantity, price, scheduled date) maps to OrderDtl. Line-level pricing from SyteLine CPQ-driven configurations maps to OrderDtl.DocUnitPrice with any configuration string stored in a UD column for engineering reference. We resolve OrderHed.CustNum from the Customer phase before any OrderDtl import begins.

SyteLine Purchase Orders map to Epicor POHeader and POLine. VendorNum on POHeader resolves from the Supplier phase. Each SyteLine PO line (item number, quantity, price, due date) maps to POLine with the appropriate PartNum or MfgLotQty reference. Blanket PO releases in SyteLine map to Epicor Release records under the parent POHeader. POLine.BuyerID maps from SyteLine purchaser assignment.

SyteLine's Chart of Accounts (account codes, descriptions, account types, sub-account segments for cost-center or department) maps to Epicor's GLAccount structure. We preserve segment structure using Epicor's GL Account format mask configuration (GLAccount.GLShortAcct fields match SyteLine account code segments). Account types map to Epicor GLAccount.AcctType. Intercompany account mappings in multi-entity SyteLine configurations map to Epicor GLBook and intercompany GL mapping rules.

SyteLine Employee records (name, department, job title, supervisor) map to Epicor Employee. HR compensation history stored in SyteLine maps to Epicor EmpBasic if the HR module is activated on the destination. Employee shift assignments and labor rates in SyteLine map to Epicor LaborRate records. We resolve Employee records before Job and LaborDtl imports because Epicor LaborDtl references EmployeeNum as a required foreign key.

SyteLine Quotes generated via CPQ or manual entry map to Epicor QuoteHed and QuoteDtl. Quote headers carry customer reference, salesperson, and validity dates. Quote configuration lines from SyteLine CPQ map to QuoteDtl with configuration string stored in UD fields and PartRev revision references resolved at import time. We preserve QuoteHed.IsValid flag and convert date-based validity into QuoteHed.ExpirationDate.

SyteLine custom fields appear as extended SQL columns on standard tables rather than in a separate custom-field registry. During migration, we inspect every exported table's column set to identify non-standard columns (columns not in the SyteLine base schema). Each extended column maps to a corresponding Epicor UD column or UD01–UD30 table depending on data type. SyteLine-specific enumerated lists require value-mapping tables in Epicor. We document every extended column for customer review before committing to the destination mapping.

Open payables and receivables in SyteLine (invoices, credit memos, debit memos with customer/vendor links, amounts, due dates, payment terms) map to Epicor APInvoiceHed/APInvoiceDtl and ARInvoiceHed/ARInvoiceDtl. Open invoice status (open, partial, paid) maps to Epicor InvoiceStatus fields. We import open AP/AR after Customer and Supplier master records are confirmed, preserving the original invoice numbers and GL distribution for audit trail. Historical closed transactions do not migrate by default; they remain in SyteLine for audit access.