Migrate from Zenscale to Epicor Prophet 21

Zenscale stores a hierarchical financial chart of accounts with cost-center tagging for manufacturing and financial reporting. We extract account codes, account names, and cost-center assignments and map them to Epicor's GL Account structure (Account field in GenLed table), preserving the Zenscale account code as a reference field and mapping cost-center assignments to Epicor's Division or Business Unit fields if those are active in the destination configuration.

Zenscale maintains a combined or separate vendor/customer ledger with GSTIN registration details, payment terms, and credit limits. We split these into Epicor's Vendor and Customer tables, preserving GSTIN in the Tax ID field, payment terms in Terms field, and credit limits in the respective credit control fields. Any GST registration type (regular, composition, SEZ) stored as a Zenscale custom field maps to a Vendor/Customer custom UD field. Epicor's Address table stores multi-address records; Zenscale's single address per entity maps to the primary Address row.

Zenscale item masters include finished goods (FG), raw materials (RM), and semi-finished variants with BOM linkages, unit of measure (UoM), stock thresholds, and valuation methods. We map to Epicor Part (Part table) with PartType code (M= manufactured, P=purchased, S=subassembly), stock quantities to PartBin, and valuation method to the costing type on the Part's cost record. UoM conversions from Zenscale map to Epicor's UOMClass and UOM definitions. Item-level GST HSN codes from Zenscale migrate to a custom Part field for tax engine integration.

Multi-level BOMs in Zenscale with component quantities, consumption rates, and version histories require Epicor's PartMtl and PartOpr tables, plus PartRev for revision control. Each Zenscale BOM version maps to an Epicor Part Revision with revision code and effective date preserved. Zenscale BOMs without an explicit revision date map to the current Epicor revision. We request the full production order history from Zenscale, not just the current BOM definitions, to capture revision trails for manufacturing audit compliance.

Zenscale production orders with routing steps, work-center assignments, and BOM component quantities map to Epicor Job (JobHead, JobMtl, JobOper tables). The production order number becomes the Job Number with the original production start and due dates in JobHead.StartDate and JobHead.DueDate. Work-center assignments map to Epicor Resource Groups and Resources. Status mapping: Zenscale open, in-progress, and closed orders map to Epicor Job status codes (open=open, released, in process; closed=complete). Open production orders are the priority cutover objects because they affect active shop-floor scheduling.

Zenscale open PO records with line-item pricing, delivery schedules, and GST tax components migrate to Epicor POHeader and POLine. We extract pending order balances (quantity ordered minus quantity received) as the open quantity in Epicor, with delivery schedules mapped to PO releases. Zenscale GST tax rate and amount per line map to Epicor's PO line tax fields. Any partially-received Zenscale POs show receipt history in Epicor POLine.RcvdQty after migration.

Zenscale open SO records map to Epicor OrderHed and OrderDtl. The pending order balance (quantity ordered minus quantity shipped/invoiced) becomes the open quantity in Epicor's order record. GST tax rate, tax amount, and HSN code from Zenscale migrate to OrderDtl tax fields. Customer-specific pricing, credit limits, and delivery instructions from Zenscale map to the Epicor order header and ship-to address records. Closed or invoiced Zenscale orders migrate as historical records if Epicor's implementation requires full transactional history.

Indian GST compliance data—GSTR-1, GSTR-3B summaries, and input tax credit registers—are stored against transactions in Zenscale. We extract GSTR summary records and line-item GST amounts, flagging any mismatch between ZSTR-2A and GSTR-3B before migration. In Epicor ERP, which has no native Indian GST engine, these records migrate as reference data into a custom tax reconciliation table. We recommend a third-party GST compliance solution (Cleartax, Tally, or equivalent) post-migration for ongoing GSTR filing. GST record retention under Indian law extends 8 years.

Zenscale stores employee records with salary components (basic, allowances, deductions), attendance, and statutory contribution data (PF, ESI, TDS). We extract employee masters, compensation records, and statutory deduction registers and map them to Epicor's HR Employee table if the destination includes the HR module. PF, ESI, and TDS deduction rates from Zenscale migrate as deduction codes with amounts preserved. Attendance records from Zenscale's payroll module migrate to Epicor HR attendance tracking if active; otherwise they are documented as reference data. Epicor's HR module requires separate configuration for Indian statutory compliance.

Zenscale's quality management module stores inspection results linked to purchase orders and production lots—QC pass/fail records, inspector names, rejection reasons, and disposition codes. These map to Epicor's Receipt Inspection and NonConformance records (QMS module if licensed). We extract QC pass/fail as inspection result codes, inspector names as WhoID references, and rejection reasons as NonConformance detail records with cause and disposition mapping.

Zenscale stores attached documents—invoices, GRNs, quality certificates—in a proprietary file store without a publicly documented attachment export API. We can migrate metadata (filename, file type, attached entity, upload date) as records in Epicor's Document Management table (EDocClass and related tables), with the customer retrieving physical files from Zenscale's UI manually or with Zenscale's assistance and uploading to Epicor post-migration. Binaries cannot be automatically transferred.

Zenscale financial transaction history (journal entries, voucher records, and GST posting lines) maps to Epicor's GLJrnDtl general ledger detail table. Full historical GL data is available in Epicor but carries cloud storage costs per transaction volume; we recommend archiving GL entries older than 3 years to an external data warehouse or document repository and migrating 3 years of current-year and prior-year GL data as active records, with older periods referenced via document linkage. Epicor auditors and regulators may require data back 7-10+ years depending on business context.