Migrate from Growth System to Epicor Prophet 21

Growth System's COA includes Indian regulatory accounts (GST input, GST output, TCS, TDS payable) that must be replicated as Epicor GL Account records. We map the account code structure, account type (Asset, Liability, Equity, Revenue, Expense), and active/inactive status. Regulatory accounts (GST/TDS) are mapped to Epicor GL Account with a custom segment or UD field flag identifying them as statutory so the customer's admin can configure reporting groups in Epicor Financial Reporting.

Growth System Customer records map to Epicor Customer. The GSTIN, PAN, and state registration fields from Growth System are stored as UD fields on the Epicor Customer record. We pre-create the UD fields (e.g., UD_GSTIN_c, UD_PAN_c) during schema design. Billing and shipping addresses map to Customer-related Address records in Epicor. The customer code in Growth System becomes the Epicor CustomerNum as the dedupe key.

Growth System Vendor records map to Epicor Supplier. TDS section applicability, TDS rate, GSTIN, PAN, and IEC fields on the Growth System Vendor are extracted and mapped to Epicor Supplier UD fields. We resolve the TDS section to the applicable Withholding Tax Code in Epicor before importing Supplier records so that TDS deduction calculations are ready to function from day one.

Growth System stores GSTIN on Customer and Vendor as structured fields; Epicor has no native statutory identifier fields on these objects. We pre-create UD fields on Customer and Supplier during schema design, map all GSTIN values during the master data phase, and validate GSTIN format (15-character pattern) before import. These references must be established before any transaction data that references them is imported.

Growth System Items map to Epicor Part records. Growth System stores inventory valuation, standard cost, and warehouse assignment as line-item attributes on stock transactions rather than as standalone Part properties. We extract the last known cost, average cost, and valuation from the most recent Growth System stock transaction and populate Epicor Part's StandardCost, AverageCost, and PartPlant MinimumOrderQty fields. The Growth System item code becomes Epicor PartNum as the dedupe key.

Growth System warehouse assignments embedded in stock transaction line items require decomposition. We extract all distinct warehouse codes from Growth System stock transactions and create corresponding Epicor Warehse records. For each Part-Warehouse combination found in transactions, we create a PartBin record in Epicor with the current quantity, bin location, and last transaction date. PartBin is the lowest-level inventory record in Epicor's schema.

Growth System Employee records map to Epicor EmpBasic (basic profile, department, role) and HrEmployee (HR attributes). We extract employee ID, name, department, designation, and reporting manager from Growth System. PF/ESI registration numbers are stored as UD fields on the Epicor HrEmployee record since Epicor does not have native PF/ESI fields.

Growth System Payroll records map to Epicor's Payroll module records. Gross salary, earning components (Basic, HRA, Allowances), deduction components (PF, ESI, TDS, professional tax), and net pay migrate to PrcycledPayData lines. Employee-level tax regime data (New vs Old regime selection) is stored as a UD field on HrEmployee. We migrate the most recent 12 months of payroll records; older records are migrated as summary journal entries attached to the GL Account in Epicor.

Growth System GST input and GST output ledgers map to separate Epicor GL Accounts in the Liability section. We configure Epicor's Tax Engine with Indian GST tax codes (CGST, SGST, IGST, UTGST) and map the applicable rate codes to the corresponding GL Accounts. Tax codes are set up before any Sales or Purchase transactions are imported so that GST calculation is active from the first transaction.

Growth System TDS ledger entries map to Epicor's Withholding Tax Codes (with applicable sections 194C, 194J, 194Q, etc.) linked to the corresponding vendor. TDS rates and threshold amounts from Growth System are mapped to Epicor Withholding Tax Code records. We configure withholding before vendor invoice imports so that TDS deduction is calculated automatically when invoices are entered.

Growth System stock transactions with embedded warehouse and valuation attributes map to Epicor PartTran records. We decompose each transaction into PartTran rows with TranDate, PartNum, TranQty, TranValue, WarehseCode, and BinNum resolved from the Growth System line-item attributes. Only transactions from the last 24-36 months are imported; older history is consolidated into GL summary journal entries. PartTran references the pre-mapped Part, Warehse, and Bin records.

Growth System purchase invoices with embedded TDS deduction and GST amounts map to Epicor APInvHed (header) and APInvDtl (lines). TDS deducted and TDS nature fields migrate to APInvHed UD fields. GST breakup (CGST/SGST/IGST) is preserved in APInvDtl with corresponding tax amounts. Vendor GSTIN on the invoice is validated against the pre-mapped Supplier UD field. We import open invoices and the last 12 months of closed invoices.

Growth System sales invoices map to Epicor InvcHead and InvcDtl. GST breakup per line item (CGST/SGST/IGST rates and amounts) is preserved in the Epicor invoice detail tax fields. Customer GSTIN on the invoice is validated against the pre-mapped Customer UD field. E-invoice reference numbers (if applicable) are stored as UD fields on InvcHead. We import open invoices and the last 12 months of closed invoices.

Growth System custom objects and custom fields (common in Indian compliance scenarios) are replicated in Epicor as UD fields on the equivalent standard object or as custom UD tables. We pre-create the Epicor UD field schema (UD01-UD09 or custom UD tables) during schema design and map all Growth System custom field values during master data migration. Growth System custom object relationships are replicated as Epicor UD Table foreign key references.