Migrate from FACT ERP.NG to Epicor Prophet 21

FACT ERP.NG Customer records carrying addresses, contact details, GST/Tax IDs, credit limits, and payment terms map directly to Epicor Customer records. The customer code, name, address, phone, email, tax registration number, credit limit, and payment terms migrate 1:1. We use CustomerCustNum or a comparable dedupe key during import. Customer-to-Sales-Order references are preserved so that existing orders link correctly to the customer record.

FACT ERP.NG Supplier master records including bank details, tax registration, and payment terms map to Epicor Supplier (Vendor) records. Supplier-to-Purchase-Order and Supplier-to-AP-invoice references are retained as linked records. If FACT stores bank account details in a separate address or contact record, we flatten them into Epicor's VendorBank table during transform.

FACT ERP.NG Items carry pricing, BOM links, serial number flags, and barcode data. They map to Epicor Part records. Standard cost, average cost, and list price fields migrate to Epicor's PartCost and PartPlant records. Serial number tracking and lot control flags map to Epicor's PartLotControl and Part.NumSerial masked fields. Item.UOM from FACT maps to Epicor UOMClass and Part.UOMCode conversions.

FACT ERP.NG multi-level BOM structures map to Epicor's ECOMtl table with parent part and revision revision-level assembly lines. We extract BOM rows individually, chunk by parent part, and load them in revision sequence so that sub-assemblies and components are resolved before the parent BOM loads. If FACT BOMs include phantom assemblies, we map these to Epicor's MtlPartFlag = Phantom on the ECOMtl record.

FACT ERP.NG Sales Orders carry customer references, line items, pricing, taxes, and fulfillment status. Each order header and its lines migrate as a single transactional unit so that partial fulfillments, backorder flags, and pricing tiers are preserved. OrderHed.OrderNum and OrderDtl.OrderLine provide the parent-child linkage. We flag open versus closed order status against Epicor's OrderHed.OpenOrder field.

FACT ERP.NG Purchase Orders carry supplier references, line items, expected delivery dates, and GRN linkages. We preserve the header-to-line structure and map open PO status to Epicor's POHeader.OpenPo field. GRN linkages from FACT map to Epicor PartTran receiving transactions if the customer chooses to carry forward receiving history; otherwise, open PO lines are migrated without historical PartTran records.

FACT ERP.NG's standard COA structure with account codes, descriptions, and account types maps to Epicor GLAccount records. Account codes migrate directly. Any account carrying a balance is flagged so that opening balances post correctly to Epicor's GLJrnDtl in the first open period. Account types (Asset, Liability, Equity, Revenue, Expense) map to Epicor GLAccount.AcctType.

FACT ERP.NG posts AR, AP, and payroll directly to the GL as journal entries. These date-stamped, source-referenced records extract in date-range batches and map to Epicor GLJrnDtl. Journal batch number and journal code from FACT map to Epicor GLJrnDtl.JournalNum and GLJrnDtl.JournalCode. We enforce date-range chunking (typically monthly or quarterly) to manage batch size and maintain ledger integrity.

FACT ERP.NG Employee records include salary components, tax deductions, EPF/CPF contributions, and leave balances. They map to Epicor EmpBasic (employee master) plus Payrollhdr or PayChk (payroll transaction records). Because FACT payroll posts directly to the GL as journal entries, we must extract Payroll first, extract the resulting GL postings as a linked journal set, and then load Payroll before GL in Epicor. The payroll transactions carry period, salary, deductions, and employer contributions as line items that must resolve to the correct Epicor PayCode and Deduction/Benefit codes.

FACT ERP.NG's tight payroll-to-GL coupling means the GL postings generated by payroll processing are the authoritative financial record for salary expenses, tax withholdings, and employer contributions. We extract these as a separate journal batch marked with a payroll source code, then load them into Epicor GLJrnDtl after EmpBasic and Payrollhdr are committed. Loading GL before Payroll would create duplicate or orphaned debit/credit pairs in Epicor. We document the payroll journal sequence explicitly in the migration runbook.

FACT ERP.NG inventory balances maintained per warehouse per item map to Epicor PartWhse records with current qty, reorder point, and min/max levels. Serial and batch tracking fields require value-level mapping to Epicor PartLot. Warehouse codes from FACT map to Epicor Warehse.WarehouseCode and PartWhse.WarehouseNum. Multi-warehouse configurations are preserved with each warehouse's stock position as a separate PartWhse record.

FACT ERP.NG Fixed Asset records include acquisition cost, depreciation method, accumulated depreciation, and asset location. These map to Epicor FAAsset records. Depreciation schedules generated per accounting period migrate as FADepRul (depreciation rule) records. Asset book and tax book values from FACT map to separate FAAssetBook records in Epicor.

FACT ERP.NG's Configuration Only model stores tax rates, approval workflows, pricing tiers, inventory matrix settings, and workflow states as platform parameters rather than custom fields. We extract every active non-default parameter during discovery and map each to an equivalent Epicor UDC (User-Defined Code) table or system control setting. If a FACT parameter has no direct Epicor equivalent, we document it in the configuration-replay section of the migration package and flag it for the customer's Epicor administrator to configure manually post-load.

FACT ERP.NG's CRM module holds Leads, Contacts, Opportunities, and Activities. We migrate all four as linked objects preserving the contact-to-opportunity relationship. Lead records with no opportunity association map to Epicor Prospect or Lead tables if the destination Epicor edition supports them; qualified contacts with active business relationships map to Epicor Customer and Contact records. Opportunity stage and owner assignment are preserved on Epicor Opportunity or Quote records depending on the customer's sales process configuration.

FACT ERP.NG supports Malaysian e-invoicing via LHDN/IRB and Singapore InvoiceNow compliance. We extract e-invoice metadata and XML payloads as reference records but do not load them into Epicor as functional e-invoice transactions. The destination Epicor system must have an equivalent compliance module (Epicor Tax Connect, Avalara, or a regional e-invoicing add-on) or the customer's administrator configures the compliance module separately. We provide a rebuild guide listing the e-invoice fields that require reconfiguration in the destination.