Migrate from Epicor iScala to Epicor Prophet 21

iScala GL stores journal entries, chart of accounts, and financial periods under company codes within a single database. Epicor ERP separates GLAccount, GLBook, and JournalEntry tables with a formal Company entity. We map iScala's two-letter company codes to Epicor ERP Company entities, preserve multi-segment account structures (iScala supports multi-dimension accounts), and migrate GL balances and open periods with fiscal year alignment validated against Epicor ERP's fiscal calendar configuration.

iScala SL holds customer masters, open AR invoices, and payment history. Epicor ERP uses Customer as the master, InvcHead/InvcDtl for posted invoices, and CashHead for payments. We extract customer masters and outstanding AR with address and contact normalization, then map invoice headers and lines to their Epicor ERP equivalents. Multi-currency AR balances preserve exchange rates from iScala's currency tables.

iScala PL manages vendor records, open AP, and purchase invoices. Epicor ERP uses Vendor for the master, APInvHead/APInvDtl for posted invoices, and APTran for transactions. GRNI (goods-received-not-invoiced) entries from iScala's PC module map to Epicor ERP's APPreuvian records for three-way matching integrity. Multi-currency AP preserves vendor-specific exchange rates.

iScala OR contains order headers and lines with pricing, discounts, and fulfillment status across the two-letter OR prefix. Epicor ERP separates OrderHed, OrderDtl, and OrderRel with release-level scheduling. We migrate open and recent closed orders preserving line-level pricing, discount codes, and warehouse assignments. Attachment references from iScala are flagged as file-location items for the customer's admin to re-link post-migration.

iScala PC manages PO headers, lines, and receipts with GRNI tracking for three-way match. Epicor ERP uses POHeader, POLine, and PORel with PORel representing scheduled releases. We extract open PO records and map receipt history to PORel, preserving the AP match integrity needed for three-way matching in Epicor ERP's Accounts Payable module.

iScala SC covers inventory items, warehouse locations, lot numbers, and serial numbers. Epicor ERP uses Part for item masters, PartBin for warehouse-level quantities, PartLot for lot tracking, and SNTran for serial number movements. We migrate current stock balances first, then receipt transaction history so that lot and serial links remain intact in Epicor ERP. BOM structures from iScala MP map to Erp.JobMtl references for manufactured items.

iScala MP handles work orders, routings, and production schedules. Epicor ERP uses JobHead for work order master, JobMtl for material requirements, JobOper for routing operations, and LaborDtl for labor transactions. We map iScala routing sequences and labor standards to Epicor ERP JobOper with operation-level timestamps and labor codes preserved. Active jobs are prioritized in migration order; completed historical jobs migrate as closed records with job close dates validated.

iScala HR and PA modules store employee records, compensation history, and payroll runs. Epicor ERP uses EmpBasic for employee master, EmpPaycheq for payroll history, and EmpExpense for expense claims. Effective-dated records migrate as-is with start and termination dates preserved. Tax configuration and payroll processing rules are not migrated; we document them in the payroll handoff inventory for the customer's Epicor partner or HRIS team to configure in Epicor ERP Payroll or a linked payroll system.

iScala AM tracks fixed assets, depreciation schedules, and asset locations. Epicor ERP uses FinancialCont for asset master, DepreciationDetail for depreciation history, and AssetLocMap for location assignments. We migrate asset masters with opening book value, accumulated depreciation, and depreciation method (straight-line, declining balance) preserved. Asset associations to departments or cost centers map to Epicor ERP's department and cost center entities.

iScala PR stores project masters, WBS elements, budgets, and time entries. Epicor ERP uses Project as the master, PJTask for WBS breakdown, PJBldCode for billing codes, and PJExpense for expense records. We migrate project headers and current budget balances as PJObjCoe records. Detailed time entries and labor bookings map to Erp.LaborDtl with Project and Task references resolved. Large time entry histories may require chunked migration with date-range filters.

The iScala UD module stores custom fields on standard objects using a version-varying schema across iScala 2.2 through 2022.1. Epicor ERP uses UD tables with the UDColumnMap configuration for each Business Object. We inventory UD field definitions during discovery against the target Epicor ERP version's UD table structure, then map values to the corresponding Epicor ERP UD columns. Fields with no matching destination property are flagged for manual mapping review before migration.

iScala supports multiple companies within a single database using company codes embedded in table data. Epicor ERP uses a formal Company entity with Plant and Warehouse as sub-entities. We scope each iScala company code as a separate Epicor ERP Company during migration, map site-specific configurations to Plant records, and resolve inter-company transaction references to Epicor ERP's inter-company GL entries. This per-company scoping prevents cross-company record merging during extraction.

iScala SM handles service order headers, line items, and field-service scheduling with contract management. Epicor ERP uses ServiceOrderHed and ServiceOrderDtl with technician assignment and SLA tracking. We migrate open service orders with scheduling windows and SLA flags mapped to Epicor ERP's service management configuration. Contract terms from iScala CM module map to Erp.ServiceContractHed with billing cycles preserved.

iScala CM stores contract masters, terms, and billing schedules for service or recurring revenue contracts. Epicor ERP uses ServiceContractHed for the contract master and ContractLine for line items. We map active contracts with billing cycles and associated customer or vendor records. Contract pricing and discount terms migrate as-is; billing rules and revenue recognition schedules require manual configuration in Epicor ERP's contract management module.

Document attachments stored outside the iScala SQL database in file shares, SharePoint, or Epicor's document management are not migrated via API. We inventory file path references during discovery and deliver a written document map with current file locations and recommended target paths in Epicor ERP's document management or Kinetic content storage. The customer's admin re-links documents post-migration using the delivered inventory.