Migrate from eFacto ERP to Epicor Prophet 21

eFacto stores account codes in a flat SQL table without published hierarchy metadata. We extract the account master (account code, name, type, parent reference, inactive flag) and map each code to Epicor Kinetic's GLAccount table using the standard natural account segment. eFacto's account types (Asset, Liability, Equity, Revenue, Expense) map directly to Epicor GLAccount types. We flag any eFacto inactive accounts that must be reactivated in Epicor and any accounts without a clear natural-account equivalent for customer review before insert.

eFacto Customer records include billing/shipping addresses, GST registration ID, payment terms, credit limits, and PAN for Indian compliance. We map to Epicor Kinetic Customer with address stored in ShipTo records linked to CustomerNum, GST/VAT as Tax ID fields, and payment terms to TermsCode. We deduplicate by phone and email before insert and create CustomerPriceTolerance records if eFacto credit limits are non-zero.

eFacto Vendor records mirror the customer structure with additional fields for PAN/TIN registration and banking details. We map to Epicor Kinetic Vendor with the same ShipTo structure, preserving purchase terms in TermsCode and outstanding PO references from eFacto's open PO fields. Vendor's GST/TDS registration maps to Tax ID fields on the Vendor record.

eFacto Items carry SKU, description, unit of measure, standard cost, and selling price. We map to Epicor Kinetic Part (base record) and PartPlant (plant-level cost and planning data). eFacto BOM structures for manufactured items map to Epicor PartMtl (material lines) and PartOpr (operation steps), preserving quantity-per and scrap percentages. We flag eFacto variant data (size/color/style splits) for mapping into Epicor PartRev and PartAttr attributes.

We flag all open eFacto AP invoices and credit notes with a migration-as-of date. Partial payments carry forward as APLnk (AP Payment Link) records in Epicor rather than resetting balances to zero. Vendor-specific AP terms migrate as TermsCode. We set the InvoiceDate and DueDate on APInvoice to preserve the original payment schedule. We do not migrate fully-paid AP history.

Open AR invoices and credit memos from eFacto migrate as ARInvoice records with CustomerNum pointing to the mapped Customer. Partial payments carry forward as ARLnk (AR Payment Link) entries. We set the invoice date and due date from eFacto and preserve the original invoice reference number as an InvoiceRef field for audit traceability. We do not migrate fully-paid AR history.

Open Sales Orders from eFacto migrate with full line-item detail. Each eFacto sales order header maps to Epicor Kinetic OrderHed (order-level fields: order date, customer PO, ship date, terms) and each line to OrderDtl (part number, quantity, unit price, warehouse). We resolve eFacto customer order numbers to Epicor OrderHeld orders, preserving the customer PO reference and any open shipment quantities.

Open Purchase Orders from eFacto migrate to Epicor Kinetic POHeader and POLine. Vendor PO reference, terms, and ship-to warehouse map to POHeader fields; part number, ordered quantity, unit cost, and due date map to POLine. We resolve eFacto part numbers to Epicor Part numbers during transform and flag any unmatched POLine parts for vendor re-cataloging before production migration.

eFacto POS receipts live in a separate transaction log from the accounting ledger. We build a cross-reference table linking each eFacto POS receipt number to the Epicor journal entry created at the destination. Daily POS cash totals aggregate to Epicor ARInvoice records (cash receipts) or OrderHed entries depending on whether the destination is configured for POS cash sales as invoices or orders. We preserve cashier ID, shift ID, tender type, and receipt timestamp on each mapped record.

Current stock quantities per warehouse and per batch/lot extract from eFacto's inventory ledger. We map to Epicor Kinetic PartBin (physical quantity by warehouse and bin) with the stock-as-of date recorded in PartTran. We do not migrate eFacto historical valuation entries; Epicor recreates on-hand value through its PartTran cost roll during the first production transaction. Multi-warehouse eFacto setups create multiple PartBin records per part.

Employee master records from eFacto (designation, department, salary, PAN) map to Epicor Kinetic EmpBasic. Pay structures and department assignments migrate; payroll transaction history does not migrate because Epicor's payroll module maintains its own accrual and payment records. We flag any eFacto employee without a mapped CostCenter for customer review.

eFacto SSRS reports built on stored procedures specific to eFacto's SQL schema cannot be imported directly into Epicor Kinetic. We export the RDL XML and parameter definitions and deliver them alongside a written recommendation for equivalent Kinetic Dashboard Designer configurations using migrated Part, Customer, and Order data. Custom stored procedure business logic requires manual rewrite by the customer's BI team or an Epicor VAR partner.