Migrate from Fraction ERP to Epicor Prophet 21

Fraction ERP Customers map to Epicor Company records. The Company record holds the company name, address, and contact details as the primary account-level entity. We preserve the customer code from Fraction ERP as Company.CustID in Epicor and use it as the dedupe key during import. Any linked contacts within Fraction ERP migrate as Company contacts or as Contact records attached to the Company, with the primary contact flagged per the Fraction ERP record.

Fraction ERP Quotations with status of DRAFT or ACTIVE map to Epicor Quote records. Line items (Part, quantity, unit price, discount) migrate to QuoteLine records. Validity dates and quotation notes transfer to Quote.QuoteStatus and Quote.Note field respectively. Quotation-to-order conversion is documented as a manual step in the handoff guide because Epicor's quote-to-order flow requires a confirm-and-convert action in the UI; we do not auto-convert quotations to orders as part of the migration scope.

Fraction ERP Sales Orders map to Epicor SalesOrder records with order number, customer reference, order date, and line items preserved. Order status (DRAFT, OPEN, COMPLETED, CANCELLED) maps to OrderHed.OpenLine, OrderHed.OrderHeld, or OrderHed.Cancelled based on Epicor's OrderHed schema. Line items with Part numbers resolve to Epicor Part records via the Part mapping phase before Sales Order import begins.

Fraction ERP Parts (item master records) map to Epicor Part records with part number, description, unit of measure, and cost data preserved. Part.Number as Part.PartNum, Part.Description01 as Part.SearchWord, and the Fraction ERP stocking UOM as Part.IUM. Cost data (standard, average, or last) migrates to PartLot records if lot tracking is active, or to the PartPlant cost fields if single-site. Fraction ERP's part type (manufactured, purchased, or Phantom) maps to Epicor Part.TypeCode.

Fraction ERP Bills of Materials with multi-level component structures map to Epicor Part Revision records (the revision header) and JobMtl records (the component lines). The BOM level structure (parent-part, sub-assemblies, components) is preserved as parent-child JobMtl relationships. Drawing files stored as BOM attachments migrate in a separate file pass (see Gotchas) and are linked to the Part record or the Part Revision as document attachments via Epicor's DocType and FileAttach modules. BOM-first sequencing is mandatory in our pipeline: all BOM records must reach Epicor and validate before any Works Order phase begins.

Fraction ERP Works Orders map to Epicor Job records with the Works Order number as Job.JobNum, linked Sales Order as Job.LinkToOrder, and the production schedule dates as Job.StartDate and Job.DueDate. The linked BOM determines JobMtl (materials) and JobOper (operations) records. We preserve operation routing, scheduled hours, and capacity planning context. Existing closed or cancelled Works Orders migrate with their final status; open Works Orders migrate with the status that allows Epicor MRP to honour the production schedule.

Works Order operations migrate as JobOper records linked to the parent Job. Each JobOper carries the operation sequence, work centre reference, scheduled hours, and the routing step description from Fraction ERP. Because Fraction ERP derives operation routing from the linked BOM, BOM validation must complete before JobOper records are inserted (see BOM-first sequencing constraint). If any BOM was modified post-Works Order creation in Fraction ERP, we flag the affected JobOper records for customer review before inserting.

Fraction ERP Inventory tracks stock levels, locations, and valuation per Part. We migrate current stock quantities and warehouse location assignments to Epicor PartWhse records, with PartBin records for bin-level location tracking. Valuation methods (FIFO, Average, Standard) transfer where possible; Epicor's cost layer structure may require post-migration cost rollup to reconcile unit costs at the PartLot level.

Fraction ERP Purchase Orders map to Epicor POHeader records with vendor reference, PO number, and expected dates; POLine records carry line items, quantities, unit cost, and promised dates. Open Purchase Orders migrate with PORel records for partial receipts. Closed or completed POs migrate as historical records. Any receiving transactions linked to Fraction ERP POs are mapped to EpicorPORel or logged as a discrepancy for the customer's purchasing team to reconcile against physical inventory after go-live.

Fraction ERP NCRs track quality issues against Works Orders or Parts. We map NCRs to Epicor Service Job records or Quality data linked to the Job or Part, depending on the customer's Epicor configuration. Custom quality workflows and approval chains defined in Fraction ERP do not transfer; we document them in the automation inventory for the customer's implementation team to rebuild in Epicor's Service Call or Quality modules.

Fraction ERP User accounts (name, email, role, permissions) map to Epicor User records. We resolve Fraction ERP roles to Epicor Security Groups and Plant associations during scoping. Individual passwords cannot be transferred; we flag user provisioning as a manual step for the customer's admin to complete before cutover. Fraction ERP's Advanced tier features (enhanced capacity planning, advanced scheduling) may restrict which Fraction ERP roles map cleanly to Epicor permission groups if the customer's Fraction ERP tier was Basic (£36/user/mo) at the time of data export.

Fraction ERP stores BOM and Part drawing files as binary attachments linked to BOM records or Part records. These files do not export through standard grid or report exports and require a separate document extraction pass using Fraction ERP's file export feature. We schedule a parallel extraction pass, retrieve each drawing file with its parent BOM or Part reference, and upload to Epicor's Document Management system under the corresponding Part or Part Revision with DocType set to DRAWING. The mapping from Fraction ERP attachment ID to Epicor DocType record ID is captured in our migration manifest for audit.