Migrate from CREST ERP to Epicor Prophet 21

CREST ERP Customer records map to Epicor Customer (CustCnt and CustForm tables). We preserve customer code, name, address, payment terms, credit limits, and any custom fields captured during discovery. Customer addresses map to Epicor's address structure (Address1, Address2, City, State, Zip, Country). Payment terms map to Epicor Payment Terms; credit limits map to Credit Hold and Credit Limit fields. CREST ERP's custom customer properties require manual recustomization in Epicor if no direct field equivalent exists.

CREST ERP Vendor records map to Epicor Supplier (Vendor table). We preserve vendor code, name, bank details, performance ratings, and purchase terms. Supplier catalogues (vendor-specific part numbers and pricing) migrate to Epicor's Supplier Part records where applicable. CREST ERP's multi-level vendor approval workflows are documented but not migratable—Epicor's approval routing is reconfigured by the destination admin.

CREST ERP Item master records map to Epicor Part records. The Item code becomes Epicor PartNum; the description maps to Part.Description; UOM, pricing, and cost data migrate to Part.UOMClass, Part.BuyIt, and Part.MtlBurden. CREST ERP's custom properties on Item require a mapping manifest. This is the first record type that may contain BOM data—CREST ERP BOMs on Item records must be separated from the Item itself and migrated to Epicor PartMtl in a subsequent phase.

CREST ERP multi-level BOM structures (parent Item with child components, each potentially a sub-assembly with its own BOM) map to Epicor PartMtl table. This requires re-modeling the BOM as a job-based or repeating manufacturing structure in Epicor. CREST ERP BOM levels migrate as separate PartMtl records with MtlSeq and QtyPer values. Operations and routing data from CREST ERP's manufacturing module migrates to Epicor JobOper and PartOpRout tables. This is the highest-complexity mapping in a CREST ERP migration and requires a BOM analysis phase before any Item migration begins.

CREST ERP GL account codes map to Epicor GL Account (GLAccount table). We map account code, name, account type, and cost center assignments. CREST ERP's segment structure (if multi-segment account codes are in use) maps to Epicor's GL Account Natural Account and Department segments. Segment length and character format differences between platforms are resolved in the mapping manifest before import. Intercompany accounts are flagged for manual review.

CREST ERP open AP records migrate to Epicor AP Invoice (APInvHed, APInvDtl) with vendor association, invoice number, amount, due date, and payment status preserved. We track which invoices remain open at migration cutover to avoid re-importing satisfied records. Prepaid and partially paid invoices migrate with their current balance; full-history AP aging reports are reconciled against Epicor's AP Aging report post-import.

CREST ERP open AR records migrate to Epicor AR Invoice (InvcHead, InvcDtl) with customer association, invoice number, amount outstanding, and aging bucket preserved. Credit memos and partial payments migrate with correct offset handling—Epicor requires CreditMemo records to be linked to the original invoice via a reference field. We validate AR aging totals between CREST ERP and Epicor before declaring this phase complete.

CREST ERP Sales Orders map to Epicor OrderHed (header) and OrderDtl (lines). Customer and vendor linkage, line items, quantities, pricing, delivery dates, and order fulfillment status transfer directly. CREST ERP's SFA pipeline stages map to Epicor Order Status values—these are configured before migration so that open order status aligns with Epicor's Hold, Credit Hold, and Picked statuses. Closed orders are migrated to historical OrderHed records.

CREST ERP Purchase Orders map to Epicor POHeader and PODetail records. Vendor linkage, line items, quantities, pricing, expected delivery dates, and receipt status transfer. CREST ERP approval workflows on PO are documented but not migratable—Epicor's PO approval configuration is handled by the destination admin post-migration. Receipt records linked to open POs migrate as Epicor PORel (promise) and POReceipt records.

CREST ERP production job records map to Epicor JobHead (job header), JobMtl (material requirements), and JobOper (operation steps). CREST ERP job status (Released, In Process, Complete) maps to Epicor JobHead.JobReleased, JobHead.JobComplete, and the corresponding JobMtl and JobOper status fields. CREST ERP sub-contracting records map to Epicor Subcontract (SubConJob) with supplier linkage. CREST ERP routing data (operation sequences, work centers, cycle times) migrates to JobOper with labor and machine hours. This mapping requires BOM structures to be migrated first.

CREST ERP Fixed Asset records map to Epicor Asset registers (FAAsset table). Acquisition cost, depreciation schedule, asset category, location, and maintenance history transfer. Epicor supports multiple depreciation methods (straight-line, declining balance, sum-of-years-digits) which we match from CREST ERP's depreciation configuration. CREST ERP asset custom fields migrate as Epicor UD columns on FAAsset.

CREST ERP Employee records map to Epicor Worker records (EmpBasic table with WorkerType = Employee). Personal details, job role, and employment status transfer. Effective-dated compensation records from CREST ERP require sequencing by pay period date to preserve historical pay period accuracy in Epicor's HR module. PTO balances and leave history migrate as Epicor TimeOffRequest or Absence records depending on the Epicor version in scope.

CREST ERP Department structure maps to Epicor Department records (Dept table). Department codes, names, and parent-child relationships transfer. We validate that cost center assignments on GL accounts align with the destination department hierarchy after import. CREST ERP organizational custom fields migrate as Epicor UD columns on Dept.

CREST ERP HR records including leave applications, approvals, leave balances, and attendance logs migrate to Epicor HR modules. Custom leave policies and approval workflows are documented for manual rebuild in Epicor's HR configuration. Epicor's Time and Attendance module must be enabled and configured by the destination admin before attendance data can be fully operational in Epicor.

CREST ERP Project records map to Epicor Project (ProjectHed, ProjectDtl) with budget, resource assignments, tasks, milestones, and time entries. CREST ERP project templates migrate as Epicor WBS templates. Time entries associated with projects migrate to Epicor LaborDtl linked to the Project and Job. CREST ERP project custom fields map to Epicor Project UD columns.

CREST ERP historical GL journal entries migrate to Epicor GLJrnDtl records for the scoped historical period. Multi-year histories are chunked into Epicor DMT batches of 5,000-10,000 records per batch with journal number and date preserved. Journal entry descriptions, account distributions, and debit/credit amounts transfer. CREST ERP reversing entries are migrated as Epicor reversing journal entries with appropriate EffectiveDate and ReversedDate values.