Migrate from ERPNext to Epicor Prophet 21

ERPNext Customer DocType maps directly to Epicor Customer record. ERPNext stores addresses in a linked Address DocType; Epicor uses separate Customer and CustCnt (contact) records. We flatten ERPNext address rows into Epicor CustCnt contact records linked to the Customer, using the primary-address flag to set the ShipTo default. Tax ID (gstin, tax_id) maps to Customer Tax ID. Customer type (individual, company) maps to Epicor Customer Group. The customer_code field from ERPNext becomes Epicor's CustID with a dedupe pass to avoid conflicts if the customer code space overlaps with existing Epicor data.

ERPNext Supplier DocType maps to Epicor Supplier record. The same address-flattening logic applies as with Customer. ERPNext's supplier type and payment terms map to Epicor Supplier Group and Terms code respectively. Bank details stored in ERPNext's Bank Account child table migrate to Epicor Supplier Bank Account records.

ERPNext Item DocType maps to Epicor Part master with type distinction: Item Type of Stock maps to Part Type Stock, Item Type of Service maps to Part Type Service, Item Type of Asset maps to Part Type NonPart. ERPNext's item_group hierarchy maps to Epicor's Product Group codes. UOM (stock UOM, sales UOM, purchase UOM) map to Epicor's UOMClass and UOMCode fields. Valuation method (FIFO, Moving Average, Manual) maps to Part's costing method. Standard rate from ERPNext sets the initial Part standard cost in Epicor.

ERPNext's multi-level BOM nesting with operation routing and workstation definitions does not map to a single Epicor object. We flatten the ERPNext BOM tree during extraction: top-level finished goods map to Epicor Part, each ERPNext BOM level becomes an Epicor Part BOM (material lines), and ERPNext operation routing maps to Epicor JobMtl and JobOper records with work_center_code linked to an Epicor Work Center created from ERPNext's Workstation DocType. If ERPNext's BOM has piece-rate or hour-rate costing on operations, we store those as UD fields on JobOper. Multi-level BOMs are exploded into flat Epicor job records for manufacturing planning.

ERPNext warehouse structure (with bin-level data) and open stock ledger entries export via database query or CSV. We map ERPNext warehouse codes to Epicor Warehouse codes and ERPNext bin entries to PartBin records. We flag whether the destination Epicor environment uses periodic or perpetual inventory; Epicor Kinetic uses perpetual by default, which requires GL account mapping from ERPNext's stock reconciliation accounts.

ERPNext Sales Order header maps to Epicor OrderHed with order date, customer reference, shipping terms, and payment terms preserved. Line items map to OrderDtl with PartNum resolved, UOM converted, and qty transferred. ERPNext packed items and product bundle components are extracted as separate relational CSVs and mapped to OrderDtl's sub-assembly lines. Delivery schedule dates from ERPNext (delivery date per line) map to Epicor OrderRel release records for controlled shipment scheduling.

ERPNext Purchase Order maps to Epicor POHeader with vendor reference, terms, and currency preserved. POLine items map to PODetail with PartNum resolved (for stocked items) or Description and LineDesc (for non-stocked items). ERPNext's material supplied flag and schedule dates map to PORel release records.

ERPNext Sales Invoices map to Epicor AR Invoice. ERPNext v14+ introduced a split Payment Ledger where Payment Entry documents are no longer child rows on Invoices. We resolve each invoice's actual payment status by joining ERPNext's Payment Ledger to the Invoice during extraction; invoices with no Payment Ledger entry are imported as Open in Epicor, and invoices with a settled Payment Ledger entry are imported as Closed. Skip this step and every open invoice in Epicor will show unpaid even when settled.

ERPNext Purchase Invoices map to Epicor AP Invoice with the same Payment Ledger resolution logic applied. Supplier reference, invoice date, due date, and tax amounts transfer directly. Pre-payment and credit note entries from ERPNext are mapped to Epicor Debit Memo records.

ERPNext Project DocType nests Tasks with assignees, time logs, milestone dates, and cost tracking. Epicor Project uses a hierarchical Task structure where the ERPNext Project maps to Epicor ProjectHed and ERPNext Tasks map to ProjectTask records. ERPNext time logs and expense entries are mapped to ProjectTaskEntry records with the project phase as the costing category. ERPNext's project type (external vs internal) maps to Epicor Project Type code. Milestone dates become Epicor Phase dates on the ProjectTask.

ERPNext Employee DocType maps to Epicor Employee record. Department and designation map to Epicor's HRM module Department and Job Title fields. Date of joining, date of relieving, and employment status transfer as HireDate, TerminationDate, and Active field. ERPNext's salary structure assignments (stored in Salary Slip or Salary Structure Assignment DocTypes) are consolidated into Epicor HRM Employee records with pay group and compensation frequency as UD fields. Attendance and leave records are extracted as separate time-and-attendance data for customer admin to configure in Epicor HRM's time and attendance module.

ERPNext custom fields are stored in the Custom Field DocType referencing a parent DocType, with fieldtype, options, and mandatory flags. We export the full custom field registry separately before any data migration begins. Each ERPNext custom field is created as an Epicor User Defined field (UD field on the target UD table or standard table UD column) with the appropriate data type mapped: ERPNext Select becomes Epicor Combo, ERPNext Link becomes Epicor UD lookup, ERPNext Int/Float/Decimal become Epicor number types. The customer reviews the custom field inventory and confirms which ones are business-critical and should be migrated versus which can be dropped.

ERPNext File DocType stores binary files in Frappe's private files folder or S3-compatible storage, with metadata linking to the parent DocType and doctype name. We export file metadata (filename, URL, doctype reference, doctype_name) as a separate inventory. Binary attachments are not migrated directly through our API ingestion layer; instead we deliver the file metadata inventory and a recommended path for the customer's Epicor admin to move file blobs into Epicor's internal document management system or SharePoint integration post-migration.