Migrate from Konnect ERP to Epicor Prophet 21

Konnect Customer records (name, contact details, GSTIN, billing address, outstanding balances) map to Epicor Customer. GSTIN from Konnect becomes a Tax ID field on Epicor Customer and is used as a dedupe key during import. We resolve any outstanding balance fields into Epicor's open AR aging records after the Customer record is created. ShipTo addresses migrate as CustomerShipTo records linked to the parent Customer.

Konnect Item master (SKU, description, unit of measure, HSN/SAC code, cost, price) maps to Epicor Part as the master record and PartPlant for site-specific data (plant-specific cost, lead time, On-hand quantity, BOM structure). If the Konnect instance has multi-warehouse configuration, we create one PartPlant record per site in Epicor. The HSN code maps to the Part's Tax Category, and we flag any HSN value that has no matching Epicor tax jurisdiction configuration before import.

Konnect Chart of Accounts (account codes, names, hierarchies) requires a full mapping table to Epicor's natural-segment GL structure. Epicor GL Accounts are structured as a chart with Account Type (Asset, Liability, Expense, Revenue, Equity) and a segment hierarchy. We extract the full Konnect COA, classify each account by type, map to the nearest Epicor natural-account segment, and document any Konnect accounts that have no Epicor equivalent (escalated before import). Account masks in Epicor (number of segments, segment lengths) must be configured before any GL data loads.

Konnect Project records (customer association, billing plan, milestone schedule, man-hour allocations) map to Epicor Job records with Project Billing enabled. The project structure, milestones, and billable hours migrate as JobHead and JobMtl/JobOper records. If Konnect uses time-and-materials billing tied to timesheet entries, those hours migrate as labor transactions against the Job. Project close status maps to Job closed status in Epicor.

Konnect Timesheet records (employee, project, date range, hours logged) map to Epicor Labor records. We resolve the employee reference from Konnect to the Epicor Employee table, and the project reference to the Epicor Job. Hours, labor rate, and entry date migrate directly. Entries without a valid project reference in the destination are held in a reconciliation queue for the customer's admin to map before import resumes.

Konnect Employee master (personal details, department, designation, effective-dated status) maps to Epicor Employee. Department in Konnect maps to Epicor's DcdUserID or Department fields depending on the Epicor version. Active compensation fields migrate to Epicor's HR module if the destination includes Epicor Human Capital Management. The employee status (active/inactive) is preserved to prevent inadvertently loading terminated employees as active in Epicor.

Konnect open invoice records (invoice number, customer, amount, due date, line items) map to Epicor AR Invoice and AR Invoice Detail. The invoice line items reference Konnect Item IDs that must be pre-migrated to Epicor Part IDs before the invoice detail import runs. Open/closed status determines whether the invoice loads as open AR in Epicor or as a historical record. We reconcile the total AR aging against Konnect's outstanding balance report before marking the phase complete.

Konnect open AP records (vendor, invoice number, amount, due date) map to Epicor AP Invoice and AP Invoice Detail. Vendor references are resolved to Epicor Vendor records. If Konnect does not have a separate Vendor master, we extract unique vendor names from AP transactions and create Vendor records during this phase. Line items reference Konnect Item IDs mapped to Epicor Part IDs before import.

Konnect GST E-Invoicing records carry IRN (Invoice Reference Number), GSTIN of parties, HSN codes, and tax amounts (CGST, SGST, IGST). These do not map directly into Epicor's standard invoice structure because Epicor's tax engine is jurisdiction-agnostic. We extract the GST transaction headers and lines, map the CGST/SGST/IGST amounts to Epicor's tax detail structure, and preserve the IRN as a reference field. We flag any HSN/SAC value that does not have a direct match in the destination's tax code table and escalate before import. The customer's Epicor admin configures the GST tax code jurisdiction in Epicor before this phase runs.

Konnect E-Way Bill records (transport document, vehicle number, IRN reference, HSN, distance, and party GSTINs) map to Epicor Shipping Transaction records. We extract the e-way bill number, transport details, and item-level HSN codes. Epicor's shipping module must be active in the destination license to receive these records. If the destination Epicor instance is configured for a non-Indian jurisdiction, these records are archived rather than imported and the customer's compliance team is notified.

Konnect Item pricing records (price per unit, currency, customer-specific pricing) map to Epicor Price List records and Price Break structures if tiered pricing is used. We extract the full pricing matrix from Konnect, map to Epicor's PriceLBrk and PriceLMas tables, and apply the customer-specific pricing as Price Break records linked to the Part and Customer.

Konnect custom properties stored at the module level (CRM, Projects, Accounting, HRM) have no documented extension model. We extract all non-standard fields during the data audit, map each to either an Epicor UD (User-Defined) field on the equivalent table (Part, Customer, Job, Employee) or a custom extension field, and document the mapping. Fields that require BPM-driven logic in Epicor (calculated fields, conditional defaults) are flagged for the customer's Epicor admin to configure post-migration.