Migrate from Falcon ERP to Epicor Prophet 21

Falcon ERP's hierarchical COA with account types and currency assignments exports to CSV with account codes, names, and types. We map each Falcon ERP account code to an Epicor GL Account using the same segment structure. Multi-segment accounts in Epicor Kinetic (if configured) require segment mapping against Falcon's account code delimiter during the transform step. We validate total debits equal total credits across all imported accounts against the Falcon ERP GL trial balance before committing.

Falcon ERP customer records include billing address, credit limit, AR terms, and WHT codes. We export all customer fields to CSV and map to Epicor Customer, handling multi-address records (billing, shipping) as separate Epicor ShipTo records linked to the Customer parent. Credit limits and AR terms map to Epicor's credit hold and payment term fields. Any custom fields in Falcon require manual mapping to Epicor UD fields.

Vendor records parallel customer records with AP terms and GCC-specific WHT codes required for statutory compliance. We export vendors and map to Epicor Supplier, preserving WHT jurisdiction codes in the tax jurisdiction field. Falcon ERP vendor addresses map to Epicor Supplier and PO address records. If Falcon stores vendor contacts separately, we create SupplierContact records in Epicor.

Falcon ERP items include product/service classification, cost, price, and inventory tracking flags. We export items with stock levels by location and map to Epicor Part (for inventory-tracked items) or Service (for non-inventoried items). Part.UOMClass and Part stocking type flags map from Falcon ERP's inventory flags. Warehouse-level stock quantities from Falcon ERP map to Epicor PartWhse records per site.

Outstanding Falcon ERP invoices, credit notes, and payment schedules export per customer. We map open balances to Epicor's AR Invoice and AR Credit Memo records, preserving aging buckets and due dates. Each AR Invoice in Epicor is linked to the Customer record resolved during the Customer import phase. Partial payments on invoices require Epicor Payment records linked to the original invoice.

Outstanding Falcon ERP vendor invoices and credit notes export per vendor. We map open AP balances to Epicor AP Invoice and AP Credit Memo records, preserving aging buckets and due dates. Each AP Invoice in Epicor is linked to the Supplier record resolved during the Vendor import phase. WHT deductions on AP records map to Epicor's tax liability fields if configured.

Past invoices, payments, receipts, and credit notes from two to three years of Falcon ERP history export to spreadsheet. We export transaction history with line items and map invoice and payment records to Epicor AR/AP Invoice and Payment records. GL-impacting transactions (receipts, payments, credit notes) also generate Epicor GL Journal entries to maintain the trial balance integrity across the historical period.

Manual and recurring journal entries stored in Falcon ERP export with account references and amounts. We map posted journals to Epicor GL Journal Entry records with debit and credit line items against the mapped GL Account codes. Recurring journal templates are flagged as not migratable (Epicor uses a different recurring journal model) and documented for admin rebuild.

Falcon ERP fixed asset records include acquisition cost, depreciation method, and accumulated depreciation. We export the full asset register and map to Epicor Asset records. Depreciation schedules recalculate in Epicor based on the Epicor depreciation method selected; we document the Falcon ERP depreciation method used per asset for the customer's admin to apply the equivalent Epicor depreciation profile.

Falcon ERP employee records include personal details, department, job title, employment status, and effective-dated changes. We export all employee data and map to Epicor Employee, preserving department assignments as Epicor Department records. Historical employment changes (title changes, department transfers) migrate as separate employment record entries in Epicor's effective-dated structure.

Payroll history from Falcon ERP includes salary, deductions, allowances, and tax deductions per pay period. We export payroll registers and map pay components to Epicor's labor record structure. WHT codes map to Epicor's tax deduction fields for GCC payroll compliance. Epicor's payroll module requires vendor-specific configuration for payroll processing; migrated records are loaded as historical data rather than active payroll.

Falcon ERP VAT returns and ZATCA Phase 2 e-invoice records contain GCC-specific tax codes and e-invoice reference UUIDs. We export tax transactions and build a VAT mapping table cross-referencing Falcon ERP tax codes against Epicor's tax code configuration. Where no match exists, we create new Epicor tax codes before loading. ZATCA Phase 2 UUIDs are preserved in a custom field on Epicor invoice records (or as a reference note) for Saudi PDPL audit continuity. Tax return data migrates as historical records rather than active tax configuration.

Falcon ERP BOM structures and open work orders export to spreadsheet. We map BOMs to Epicor Bill of Materials records, preserving component items, quantities per assembly, and routing steps. Open work orders export and map to Epicor Job records, with the Falcon ERP work order status mapped to the Epicor Job status field. Closed work orders migrate as historical job records in Epicor's production history module.

Falcon ERP bank accounts and cash ledgers are part of the COA but may have additional reconciliation data. We export bank account names, numbers, and current balances and map to Epicor Bank Account records. We reconcile bank account GL balances against the corresponding imported GL accounts for the destination system and flag discrepancies exceeding a 0.01 threshold.