Migrate from De Facto ERP to Epicor Prophet 21

De Facto Customer records from the Financials and CRM modules map to Epicor Kinetic Customer. We extract via TSQL including name, contact details, addresses (ship-to and bill-to), payment terms, currency assignments, and account balances. The Customer.CustID becomes the Epicor Kinetic CustNum with CustID as a reference field. Open invoice balances from De Facto's AR ledger migrate as Epicor InvcHead records with payment status preserved to prevent double-billing. Multi-country customer configurations require currency and tax code mapping per De Facto's country assignment.

De Facto Vendor master records map to Epicor Kinetic Vendor. We extract vendor name, addresses, payment terms, bank details, and currency assignments via TSQL. The landed cost tracking that De Facto uses for imported items references the Vendor record for freight and insurance cost centers; we preserve these assignments and map them to Epicor LandedCostPart records after vendor settlement.

De Facto Items (the core of the Product Supply Chain module) map to Epicor Kinetic Part. Each De Facto item may carry landed cost components (freight, insurance, duty, tax) that require decomposition and re-entry as Epicor Part.LandedCostPercent allocations per part class or per vendor. BOM structures from De Facto map to Epicor PartMtl (materials), PartOpr (operations), and PartRoute (routing) records. We use De Facto's TSQL export of the items table including columns for bom_flag, landed_cost_flag, and multi-country tax codes, then resolve Epicor Part.ClassID and PartPkgSize at migration time.

De Facto BOM structures decompose into Epicor PartMtl (material requirements), PartOpr (manufacturing operations), and PartRoute (production routing). De Facto's multi-level BOMs require iterative parent-child resolution in our TSQL extraction script. We preserve BOM revision effective dates and ghost BOM flags by mapping them to Epicor PartRev.ECO_mtl_group and revision-by-date logic.

De Facto open AP and AR records (invoices, credit notes, outstanding balances) migrate as Epicor Kinetic InvcHead and InvcDtl. Payment status, due dates, and aging buckets transfer from De Facto's transaction ledger via TSQL. We set Epicor InvcHead.InvoiceType and preserve the original De Facto invoice number as a reference field. Reconciliation gaps between De Facto's AR aging and Epicor's cash receipt matching are flagged before production load.

De Facto's chart of accounts exports via TSQL in CSV or XML format and maps to Epicor Kinetic GLAccount. Account segment structure (natural account, department, cost center) from De Facto maps to Epicor's COACodes segment definitions. We apply the Epicor GLAccount structure using the account segment order from De Facto's ledger setup and preserve De Facto's account descriptions as GLAccount.Description.

De Facto User records and role assignments map to Epicor Kinetic User records. Role definitions are highly custom in De Facto and do not map 1:1 to Epicor Kinetic Security Role Groups. We extract all users with their associated De Facto roles and deliver a written Role Mapping Report identifying which Epicor Kinetic Role Groups, Menu Sets, and Edward J. McFadden Object Access controls correspond to each De Facto permission set. The customer's Epicor admin rebuilds these post-migration.

De Facto's fixed asset register including acquisition cost, accumulated depreciation, and asset location maps to Epicor Kinetic FAsset. Depreciation schedules migrate as FAssetReg and FAssetDist records. De Facto's landed cost tracking for imported items may overlap with fixed asset cost capitalization (duty and freight embedded in acquisition cost); we disambiguate these during extraction and set FAsset.CostAdjustment appropriately in Epicor.

De Facto's CRM module with opportunity tracking maps to Epicor Kinetic Quote and SalesOrder. Opportunity name, value, stage, and associated contacts from De Facto's CRM export become Epicor Kinetic QuoteHdr and OrderHed records. De Facto custom CRM fields require UD field creation in Epicor Kinetic before migration. We preserve the opportunity close date and probability percentage from De Facto as QuoteHed fields.

De Facto stores documents linked to data records via its document management module with OCR processing for inbound documents. Document-to-record linkages and embedded attachments may not export cleanly without explicit extraction. We extract documents by resolving the De Facto document reference against the associated entity record (Customer, Vendor, Part, Order) and load them as Epicor Kinetic DocumentAttach records. Embedded OCR metadata requires custom parsing and mapping to Epicor Kinetic's attachment metadata fields.

De Facto historical transactions (purchase orders, sales orders, warehouse movements) export via TSQL script output. Large transaction volumes require chunked extraction with date-range partitioning. We migrate the last two fiscal years of transactional history by default, with the customer's choice of whether to include prior years as historical archive or as an external archived reference. Warehouse movements map to Epicor Kinetic PartTran records.

De Facto's Reporting & Analysis module uses Microsoft SSRS-based report definitions that are not portable across platforms. We export the data that feeds De Facto SSRS reports as structured CSV via TSQL, then deliver a BAQ design guide to the customer's Epicor admin showing how to recreate the equivalent queries in Epicor Kinetic's BAQ framework. This is a documentation deliverable, not a migration of report code.