Migrate from ERPnext Enterprise - Bespoke to Epicor Prophet 21

ERPNext Customer DocType maps to Epicor Customer with name, territory, tax ID, and payment terms. We validate the territory hierarchy against Epicor's Region/Territory setup and resolve any Customer-specific price lists to Epicor Price Code assignments. Customer addresses migrate as Epicor ShipTo records linked by CustomerNum.

Supplier DocType mirrors Customer structure in ERPNext. We map supplier type, payment terms, and address records to Epicor Supplier. Supplier-specific tax categories and lead-time fields carry forward as UD fields on the Epicor Supplier record if no standard equivalent exists in the destination.

ERPNext Item DocType carries item code, description, item group, stock UOM, valuation method, and barcodes. These map to Epicor Part with PartNum, PartDescription,IUM, TrackLots, and ValuationMethod fields. Barcodes migrate to PartLot or PartBin records depending on Epicor's barcode module configuration. Custom fields on the ERPNext Item DocType map to Part UD columns (UD01, UD02, or like-columns) that we pre-create before Part import.

ERPNext BOMs support arbitrary nesting depth; Epicor separates BOM (flat multi-level assembly) from JobMtl and JobOper (exploded assembly operations). We flatten ERPNext BOM hierarchies into Epicor BOM lines and generate JobMtl and JobOper records with operation sequence numbers and work centre assignments. Parent part numbers and quantity-per ratios map 1:1; nested child BOMs are exploded and inserted as separate BOM lines in Epicor with the top-level parent as the assembly.

ERPNext Sales Order maps to Epicor OrderHed (header) and OrderDtl (line). The customer and ship-to references resolve via CustomerNum; line items resolve PartNum. ERPNext's qty-delta logic against Delivery Notes maps to Epicor's open OrderRel records, which we preserve as release rows with requested ship dates and quantity per release.

ERPNext Purchase Order header and line rows map to Epicor POHeader and PODetail. Supplier references resolve via VendorNum; line items resolve PartNum. Advance allocation records that exist as Payment Entries in ERPNext are flagged separately for the customer to create as AP Payments in Epicor post-migration rather than as part of the PO import.

ERPNext SLEs map to Epicor PartTran records for inventory movement history. Open stock positions migrate as Epicor PartBin records with OnHandQty and BinNum resolved per warehouse. Historical movement logs (which require bulk CSV export from ERPNext due to no bulk-read API) are transformed into Epicor PartTran batch imports using Epicor's Data Import template, with MtlSeq and OprSeq resolved against the Job or Order reference.

ERPNext vouchers use a double-entry model mapped to Epicor GLJrnGrp and GLJrnLine. We validate that the source chart of accounts has matching account codes in the Epicor Natural Account structure before importing; accounts without a match go to a reconciliation queue for the customer's Epicor admin to map or create before GL import proceeds. ERPNext cost centre and dimension fields map to Epicor's Division, Department, and Project dimension codes.

ERPNext Project maps to Epicor Project with start and end dates, billing method, and WBS codes. Tasks map to ProjectPhase and ProjectTask records. Billable hours, labour rates, and expense mappings carry forward as Epicor ProjectBilling line definitions. Custom task fields migrate to Project UD columns pre-created on the Project record.

ERPNext Employee DocType migrates to Epicor Employee with employment details, department, and reporting structure. Compensation records (current salary, pay frequency) migrate as UD fields on the Employee record; payroll history migrates only for the most recent fiscal year unless the customer specifies a longer window because ERPNext payroll history is often incomplete.

ERPNext custom field definitions are exported separately and applied on the Epicor destination before data import. Each ERPNext Custom Field DocType becomes an Epicor UD column on the corresponding business object (UD01, UD02, or like-columns on Part, OrderHed, Customer, etc.). UD data types are matched to Epicor column types (String, Integer, Date, Decimal) during the custom field pre-creation phase to ensure target fields exist before any data is loaded.

ERPNext Asset records with active depreciation schedules migrate to Epicor FixedAsset with acquisition details, useful life, and depreciation method. Assets already depreciated to zero are flagged and not migrated unless the customer specifies they need the historical record. Depreciation records migrate as Epicor FaDep records linked to the FixedAsset.

ERPNext stores contacts and addresses as separate DocTypes linked by Dynamic Links. We resolve these relationships during export to produce flat contact records with embedded address data compatible with Epicor's address schema. Customer ShipTo and Contact records are created with the correct parent reference (CustomerNum) and address role (ShipTo, BillTo, Primary).

ERPNext enabled users map to Epicor User records by email match. Role profiles export as Epicor UserComp permission sets. Role permission rules that define field-level or document-level access are documented as a written inventory for the customer's Epicor admin to configure in Kinetic Security Administration post-migration.