Migrate from Success ERP to Epicor Prophet 21

Success ERP customer records map to Epicor Kinetic Customer (CustNum, Name, Address, City, State, Zip, Country, Phone, Email). We preserve the GSTIN number in the Tax ID field and map the billing address to the Customer's bill-to address group. Credit limits and payment terms from Success ERP migrate as custom fields on Customer because Epicor's standard credit limit fields are configured at the AR Parameters level rather than per-customer in all editions. Payment terms code mapping requires the customer to provide the Epicor payment terms list during scoping because Indian payment terms conventions differ from Epicor's default term sets.

Success ERP vendor master maps to Epicor Kinetic Vendor (VendNum, Name, Address, Tax ID). PAN and TAN numbers migrate to the Tax ID field with a vendor-type classification. Bank account details for vendor payments must be explicitly confirmed as present in the Success ERP export because the flat table structure on some implementations does not include bank fields by default. We add a vendor bank account checklist step during migration planning to catch any missing banking data before cutover.

The Indian accounting chart of accounts from Success ERP has a statutory group hierarchy (Assets, Liabilities, Income, Expenses, with sub-groups for GST input, GST output, TCS, TDS) that must map to Epicor's segment-structured COA. We preserve the full account code, name, and group membership, then configure Epicor's account segments to match the Indian statutory grouping. If the customer uses multiple company codes in Success ERP for separate legal entities, we map each to a separate Epicor Company code and configure inter-company elimination accounts as required. This is the most complex mapping step and typically requires a dedicated chart of accounts design session during scoping.

Success ERP invoice rows (one row per line item with HSN code, GST rate, quantity, rate, and amount) split into Epicor Kinetic InvoiceHed and InvoiceDtl records. GST amount and HSN/SAC code map to the tax and item classification fields on InvoiceDtl. We preserve the invoice date, invoice number, customer reference, and payment terms. Only open invoices migrate as active Epicor records; closed and reconciled invoices are archived as a written ledger listing rather than imported as live AR records because Epicor's AR module is designed for open-item tracking.

Purchase invoices from Success ERP map to Epicor AP Invoice with the same row-split logic as AR invoices. Vendor invoice number, invoice date, and GST input tax amounts migrate. TDS deduction amounts are preserved as a separate tax tracking field because Epicor's standard tax engine handles GST but requires configuration for TDS withholding treatment. We flag any purchase invoices with missing GSTIN on the vendor side for customer reconciliation before import.

Success ERP item masters map to Epicor Kinetic Part (PartNum, Description, UOM, Standard Cost, Last Unit Cost). Stock quantities migrate as PartBin records linked to the Part and the configured warehouse. UOM conversions from Success ERP map to Epicor's UOMClass and UOMConv tables. Serial number tracking and batch information migrate as PartLot records only if the Success ERP export includes those fields, which varies by implementation. We add a UOM and lot/serial audit step during scoping to confirm export coverage.

Success ERP does not have a separate object for opening balances; closing balances appear as the ending GL balances in the trial balance export. We reconstruct these as Epicor Kinetic GL Journal entries debiting or crediting each account to bring the Epicor GL to match the Success ERP closing position at the cutover date. Receivables and payables opening balances are loaded as unmatched AR/AP open items linked to the relevant Customer or Vendor rather than as summary journal entries, to preserve the aging schedule in Epicor's AR/AP modules.

Basic employee records (name, designation, department, PAN, UAN for EPF) map to Epicor Kinetic Employee (Name, Title, Department, EmpID). Salary details and payroll basis (PF contribution, ESI, professional tax) migrate as a payroll basis configuration in Epicor's HR module if the customer licenses it; otherwise salary data migrates as a custom HR record set for manual reference. Leave balances, attendance history, and payroll runs require separate export files that the customer must explicitly request from Success ERP during data preparation because they are not part of the standard transaction export.

Open purchase orders from Success ERP migrate to Epicor Kinetic PO records with vendor, date, line items, quantities, and rates. Closed POs are not migrated as live records; they are listed in the historical PO report delivered alongside the migration. PO approval workflows do not migrate because Success ERP does not expose workflow state in the export schema, and Epicor's approval configuration requires admin rebuild in the new system.

Open sales orders from Success ERP migrate to Epicor Kinetic Order records with customer, order date, line items, quantities, rates, and tax. GST amounts per line are preserved. Back-order quantities and partial shipment flags are carried through as OrderRel records. Closed and fulfilled orders are excluded from the live import and listed in a historical order report. Order-specific pricing rules and discounts migrate as OrderMsc records for customer review and sign-off.

Success ERP implementation partners routinely add custom fields to Customer, Vendor, Item, and Transaction tables. Because these fields are not documented publicly, we cannot detect their existence without the customer providing the complete field list and export data during scoping. We instruct customers to audit their own report exports for any columns they do not recognise and to request the custom field definitions from their implementation partner before the migration kickoff. Custom fields are then added to the relevant Epicor standard object as User Defined Fields (UDFs) before data import and populated from the export columns.

Documents attached to invoices, purchase orders, employee records, or item masters in Success ERP reside in the platform's file storage layer and are not accessible via any documented export mechanism. Customers must download attachments manually or request their implementation partner to extract the file store. We include a manual document checklist in every Success ERP migration plan and deliver a written inventory of all documents that require manual re-attachment in Epicor after cutover. We do not extract or migrate attachments programmatically for this pair.