Migrate from LOGIC ERP to Epicor Prophet 21

LOGIC ERP items with style/color/size variants map to Epicor Part Master records. We normalize the variant matrix into Epicor Part Revision controlled by site and effective date. Each style becomes a top-level Part; each size/shade becomes a Revision or a Part UOM conversion. Multiple barcodes and EAN codes per item from LOGIC ERP map to PartPlant barcode records. Item sets in LOGIC ERP Ultimate tier map to Epicor Part Bill of Materials for kit parts. We flag any item with ambiguous unit-of-measure mappings before the import run.

LOGIC ERP party records with party_type customer map to Epicor Customer. GSTIN validation, billing address hierarchies, and location defaults transfer as Customer-specific address and contact records. Party-wise discount locks and credit limits map to Customer Price Break and Credit Limit fields. We preserve the original LOGIC ERP party code as an external reference field for audit traceability.

LOGIC ERP party records with party_type vendor map to Epicor Vendor. GSTIN, PAN, and supplier-wise defaults for lead time and ordering map to Vendor records and PartSupplier records. Pre-set item-wise orders from LOGIC ERP Professional tier map to Epicor Vendor POs or blanket PO release records. We resolve any vendor-to-part assignments before the import so that PartSupplier records are active at time of first PO creation.

Standard sales transactions with line items, taxes, and payment modes migrate as Epicor Sales Order records. LOGIC ERP salesman/agent assignments map to OrderHed.RequestedBy or a custom field. Open orders migrate with their current status; closed orders migrate as historical records if the scope includes order history. We resolve Customer and ShipTo references before order import to avoid orphaned records.

Purchase orders including reorder-level-driven POs and supplier/item defaults map to Epicor Purchase Order records. Pre-set item-wise orders from LOGIC ERP Professional tier preserve their defaults as Epicor PO line item configurations. We map LOGIC ERP's purchase party_type to the Epicor Vendor reference and resolve any PartSupplier assignments at migration time.

LOGIC ERP GL accounts with grouping structures and cost centres map to Epicor GL Account and Cost Centre entities. TDS configurations are India-specific and do not map universally to Epicor's global tax engine; we map TDS as a custom tax code and flag any HSN/SAC mappings that cannot be expressed in the standard Epicor tax configuration for India-specialist review.

LOGIC ERP BOMs with style-wise operation stages (Cutting, Stitching, Washing, Finishing) and material inputs map to Epicor multi-level Part Bill of Materials. We map each BOM level individually, preserving operation sequence, work centre assignments, and subcontractor job-work stages. Any BOM with a subcontractor step is flagged separately because subcontractor billing cycles vary by garment configuration and may require a supplier-specific PO or job receipt workflow in Epicor.

Production orders with work-in-progress stages map to Epicor Job Entry records. Each job operation stage from LOGIC ERP becomes a JobOper line with the correct sequence, work centre, and estimated cycle time. WIP values and job progress percentages transfer as-is; we recommend a pre-import reconciliation of WIP against the GL to catch any unit-of-measure discrepancies before the import run.

Opening stock records with exact unit counts and warehouse locations per item map to Epicor PartBin on-hand quantities. Batch-level stock tracking from LOGIC ERP Ultimate tier maps to Epicor PartBin lot/serial tracking where configured in the destination Plant. Any decimal or rounding discrepancy in source quantities lands as an inventory valuation error; we flag opening stock rows that lack exact quantities or have ambiguous unit-of-measure mappings before the import run.

POS receipts from LOGIC ERP including UPI, cash, and card payment modes migrate as Epicor AR Invoice and Cash Receipt records. Agent-level sales data and customer feedback notes map to custom fields on the AR Invoice. POS transactions are migrated as historical records if the scope includes POS history, with payment mode preserved as the Epicor payment method reference.

Multiple currency management from LOGIC ERP Professional tier and above maps to Epicor Currency and Exchange Rate records. Per-transaction exchange rates are preserved from the source. We recommend a post-migration reconciliation of exchange rate history for audit accuracy, particularly for any transactions that span multiple fiscal periods.

LOGIC ERP configurable defaults, discount locks, and item-wise rules do not map to a traditional custom fields API. We map each rule as a named Epicor UD field or a custom BO property and flag any that cannot be expressed natively in Epicor's schema. The customer's Epicor implementation partner configures BPMs or data rules for business-logic rules that require procedural logic rather than static field mapping.