Migrate from Udyog ERP to Epicor Prophet 21

Udyog ERP Customer master stores billing address, GSTIN, PAN, and contact details as flat fields. We map these to Epicor Kinetic Customer fields: CustID becomes CustNum, GSTRegistrationNumber maps to a custom GSTIN field, billing address maps to Address1, Address2, City, State, and Country. We run GSTIN checksum validation against the public GSTN API during data cleaning to flag inactive registrations before import. PAN fields map to a custom TaxID field in Epicor. The customer is created before any related Order or AR data loads to satisfy parent-record lookups.

Udyog ERP Vendor master mirrors the Customer structure with additional TDS deduction fields (TDS rate, TDS section). We map these to Epicor Kinetic Supplier: VendID becomes VendNum, GSTIN to Supplier GSTIN custom field, and TDS fields to a TDS-related custom field group. Indian statutory deduction codes (TDS under Sections 194C, 194J) require mapping to the destination's vendor tax configuration, which the customer's Epicor consultant configures post-migration. We preserve vendor GSTIN and CIN (Corporate Identification Number) during extraction and validate against GSTN before load.

Udyog ERP Item master includes SKU, HSN code, unit of measure, opening stock, and valuation method (FIFO or weighted average). We map these to Epicor Kinetic Part: PartNum from Item code, PartDescription from item name, and HSN code to a custom HSNCode field. Unit of measure from Udyog maps to the Epicor UOM class. BOM linkages stored as parent-child relationships in Udyog carry forward as PartBom records in Epicor with the parent part number resolved at load time. Opening stock migrates to PartWhse on-hand quantity records.

Udyog ERP carries India-specific statutory ledgers for GST input tax, GST output tax, TDS payable, TDS recoverable, TCS payable, and TCS recoverable. These have no native equivalent in Epicor Kinetic's standard multi-country chart of accounts. We create a mapping table during scoping that assigns each India-specific Udyog account to a new Epicor GL account under a designated India statutory account range (typically 25000-29999), and the customer's Epicor consultant creates these accounts before the GL migration phase. Standard accounts (cash, bank, debtor, creditor) map 1:1 to Epicor GL Account segments. Udyog's account code structure is flattened to Epicor's single-segment or multi-segment GL account format depending on the customer's chart configuration.

Outstanding payable vouchers in Udyog ERP include voucher number, party name, amount, due date, and GST tax component. We map these to Epicor Kinetic AP Invoice records: InvoiceNum from voucher number, VendorNum from the supplier lookup, InvoiceDate from voucher date, DueDate preserved, and the GST tax component mapped to a tax-related amount field. Each AP Invoice line links to the appropriate GL account from the chart-of-accounts mapping. We preserve voucher-level detail to allow the AP team to reconcile outstanding payables against Epicor's AP aging report after go-live.

Outstanding receivable vouchers in Udyog ERP include voucher number, party name, amount, due date, and GST tax component. We map these to Epicor Kinetic AR Invoice records: InvoiceNum from voucher number, CustNum from the customer lookup, InvoiceDate from voucher date, DueDate preserved, and the GST tax component mapped to a tax amount field. Each AR Invoice line links to the appropriate revenue GL account from the chart-of-accounts mapping. We deliver a reconciliation report comparing Udyog open AR totals to Epicor AR invoice totals post-load.

All posted journal vouchers with narration, date, and multi-legger debit/credit lines export in chronological sequence from Udyog ERP. We map to Epicor Kinetic GL Journal Entry: JEDate from voucher date, JournalNum from voucher number, JournalLine debit and credit amounts, and GL Account from the chart-of-accounts mapping. We maintain the original voucher numbering to preserve audit trail continuity. Entries are loaded in date sequence to respect Epicor's fiscal period validation. Any entries with India statutory account references are routed to the mapped India statutory range created in the chart-of-accounts phase.

Multi-level BOMs with nested sub-assemblies, scrap percentages, operation sequences, and work centre assignments require careful extraction. Udyog ERP stores BOM versions by date, and we extract the active version at migration time using a SQL explosion query that flattens the full hierarchy to single-level BOM rows. Each exploded row maps to an Epicor Part BOM record with MtlPartNum (component), QtyPer (quantity per), and ScrapPct (scrap percentage). The revision number in Epicor links the BOM to the parent Part. We validate component quantities against production orders before loading. This N:1 merge approach is necessary because Epicor's Part BOM table stores single-level parent-child relationships rather than nested hierarchies.

Udyog ERP Work Orders reference a BOM, planned quantity, actual production quantities, and status flags (Pending, In Progress, Closed). We map to Epicor Kinetic Job Head and Job Mtl records: JobNum is generated, JobNum.Priority from Udyog priority, JobHead.StartDate and JobHead.DueDate from planned dates, JobHead.JobEngineeredQty from planned quantity, and status flags mapped to JobHead.JobReleased, JobHead.JobComplete, and JobHead.JobClosed. Material allocations map to JobMtl with MtlPartNum and RequiredQty. We sequence work orders by creation date and resolve the Part number from the item master to populate JobHead.PartNum.

Production orders in Udyog ERP capture input material consumption and finished goods output with date-stamped transactions. We map to Epicor Kinetic Job Entry with job type set to manufacture: JobHead.StartDate from production start, JobHead.DueDate from planned completion, and JobMtl records for material consumption from Udyog's consumption ledgers. Output finished goods map to JobHead.AssemblySeq and JobProd records linking to the warehouse and bin. We flag any under-closed production orders (where Udyog shows material consumed but production not formally closed) as requiring manual Epicor job closure review before final migration load.

Udyog ERP Employee records include designation, department, and bank details for payroll processing. Leave balances and attendance data are stored in the HRMS submodule separately. We map the core employee record to Epicor Kinetic HCM Employee: EmpID from employee code, Name from full name, Department from department field, Position from designation, and Bank details to the Employee Bank Account section. Udyog leave balance data migrates as a custom field group in Epicor HCM because Epicor's standard leave tracking requires configuration of the absence rules before records can be loaded. The HR consultant configures absence types and accrual rules during Epicor implementation.

Project master and cost centres in Udyog ERP link to budget lines, revenue recognition schedules, and milestone billing. We map Project Code to Epicor Project, Project Description to Project Description, and WIP balances to Project WIP records. Milestone billing schedules migrate as Project Phase records with Phase start and end dates and billing amounts. Revenue recognition schedules map to Epicor's recognition rules, though the customer's Epicor consultant validates these post-migration because revenue accounting rules vary by project type and jurisdiction. Open task lists migrate to Project Task records.

India-specific GST filing data stored in Udyog ERP links to invoice records. The GSTR-1 (outward supplies) and GSTR-3B (summary return) data does not map directly to any Epicor object because Epicor Kinetic does not include a native India GST filing module. We extract invoice-level detail from Udyog including GST rate, taxable value, and IGST/CGST/SGST breakdown, and store this in a structured CSV as a tax documentation reference file for the customer's finance team to use with a third-party India GST compliance tool post-migration. We flag this as a configuration gap that requires either an Epicor partner India localization add-on or a standalone GST filing platform.