Migrate from COINCAP ERP to Epicor Prophet 21

COINCAP's financial-account hierarchy maps to Epicor Kinetic GLAccount with account segments preserved. Indian GST tax codes (CGST, SGST, IGST) map to Epicor TaxMaster entries with the appropriate tax type and rate. COINCAP's cost-centre dimension (if used in multi-segment accounts) maps to an Epicor dimension code we configure during the chart-of-accounts load. COINCAP's fiscal-year setup is documented in the reconciliation notes for the customer's Epicor admin to align to the Indian April-March fiscal calendar.

COINCAP party master records cover both customers and suppliers in a single entity table. We split by the party's COINCAP type flag: customers map to Epicor Customer with ShipTo and BillTo addresses, GST registration number in Tax Registration ID, and payment terms from COINCAP. Suppliers map to Epicor Supplier with the GST registration number in Vendor Tax Registration and the same payment-term mapping. COINCAP stores addresses across multiple address tables (billing, shipping); we consolidate into Epicor's address structure before load.

COINCAP item masters covering raw materials, semi-finished goods, and finished goods map to Epicor Part records. Item codes map to Part Number, UOM conversions map from COINCAP UOM definitions to Epicor UOMClass and UOM conversions, and pricing tiers map to Epicor PriceLsh groups. Part Class and Commodity codes from COINCAP map to Epicor Part.ClassID for reporting grouping. Indian measurement units (metric tonnes, liters) require UOMClass configuration before Part load.

COINCAP multi-level BOM structures map to Epicor PartRev (revision), PartMtl (materials), and PartOpr (operations) tables. Load order is critical: Part records must exist before PartMtl references them, and PartRev must exist before PartOpr references the revision. COINCAP BOM quantities and scrap percentages map to PartMtl.QtyPer and PartMtl.ScrapFactor. COINCAP routing or operation sequences map to PartOpr with standard rates and labor codes. We resolve BOM levels recursively during the COINCAP export to ensure the correct load sequence.

Outstanding payables from COINCAP's finance module map to Epicor APInvoice records with Supplier, invoice number, due date, amount, and GST tax breakdown. Aged trial-balance data from COINCAP must be reconciled against the Epicor AP aging report after load. COINCAP payment terms (e.g., Net 30, Net 45) map to Epicor's Terms table and are linked to the Supplier during import. Open AP records are loaded before AP payment history to maintain the open-document state.

Outstanding receivables from COINCAP's finance module map to Epicor ARInvoice records with Customer, invoice number, due date, amount, and GST tax breakdown (CGST, SGST split). COINCAP's AR aging data requires reconciliation against Epicor's AR aging report post-load. COINCAP credit limit data maps to Epicor Customer.CreditLimit, and COINCAP invoice-level GST tax breaks are preserved as ARInvoice tax detail lines. Open AR records are loaded before AR payment history.

All posting transactions from COINCAP's finance module—sales invoices, purchase receipts, journal entries, and debit/credit notes—map to Epicor TranGLC (General Ledger Control) and the relevant Epicor transaction tables. Date-range scoping is required during discovery to define the migration window; historical transactions beyond 3-5 years may be archived rather than loaded. Epicor's multi-company structure (if the customer operates multiple COINCAP companies) requires company-code configuration before TranGLC load. GST posting details from COINCAP vouchers map to Epicor's tax-registration breakdown.

COINCAP user records with role assignments map to Epicor Kinetic User and SecUser records. Role names from COINCAP map to Epicor Employee and associated labor codes so that production operators can be assigned to jobs post-migration. COINCAP module-level access restrictions map to Epicor menu安全和 access groups. Passwords, session tokens, and MFA settings cannot be migrated; users must re-authenticate in Epicor Kinetic post-cutover. We deliver a user-role matrix for the customer's Epicor admin to reassign access groups.

COINCAP ERP does not expose a documented API endpoint for bulk attachment export. Transaction-linked scanned documents, PDFs, and images cannot be retrieved programmatically. We identify every COINCAP transaction and master record with linked documents during discovery, present options to the customer (manual re-upload post-migration, a separate COINCAP vendor-assisted document workstream, or accepting that attachments will not migrate), and document the affected record IDs for the customer's admin to action. Epicor's EDMS (Electronic Document Management System) is available as the destination repository for re-uploaded files.

COINCAP deployments in any of its 11 active industry verticals include module-specific custom fields not present in the base product. These are invisible without a live COINCAP schema audit conducted with COINCAP technical staff. We identify all custom field definitions during the schema audit phase, map each to an equivalent Epicor Kinetic user-defined field (UD01-UD20 on the relevant table) or create a new custom field, and document the mapping in the field-matrix deliverable. Any COINCAP custom fields without a clear Epicor equivalent are flagged for customer review and manual data entry post-migration. BOM custom fields are loaded last due to their dependency on Part and PartRev records.

COINCAP production orders and job traveler data map to Epicor Kinetic JobMtl (material requirements), JobOper (operation steps), and Labor transaction records. COINCAP's work-order status, scheduling dates, and labor allocation map to Epicor's job scheduling engine. COINCAP job close dates and actuals map to Labor.PostedFlag and Labor.LaborQty for work-in-progress reconciliation. We scope open jobs for migration; closed jobs from prior periods are not migrated unless the customer specifically requests WIP carry-forward.

Open purchase orders from COINCAP map to Epicor POHeader and POLine records with Supplier, dates, quantities, and pricing. Open sales orders map to Epicor SOHeader and SOLine records with Customer, order number, ship dates, and pricing. COINCAP order-line GST tax codes map to Epicor line-level tax details. Closed orders from prior periods are not migrated; only open or partially-shipped orders are in scope for migration. COINCAP's multi-address delivery model (if used) maps to Epicor ShipTo records linked to the Customer.