Retiring Epicor Kinetic means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise job costs, material movements and quality documents. Compare required reports and documents with source evidence, test permissions and obtain business acceptance before scheduling shutdown.

This guide covers the retirement questions, a mock-data ArchiveHub demonstration and the validation work needed to define a project scope.

What a read-only Epicor costs

Cost categories are a discovery checklist, not a guaranteed savings calculation. Verify support status, deployment, shared infrastructure and contract terms for the actual installation.

  • SQL Server and Windows Server licences for a database nobody writes to, on versions that drift out of support.
  • The Epicor application server and client. Trackers only work while the app server, its configuration and a compatible client still run, and an upgrade just to keep reading data is a project in its own right.
  • Epicor maintenance for a system that no longer runs the plant.
  • Customisations and BAQs. The useful history is often behind business activity queries, BPMs and custom dashboards that only the original Epicor administrator understood.
  • Quality and customer audits. A customer asking for the traveler, labor and NCR history of a job shipped years ago needs a user who still knows the Job Tracker.
  • Security. Payroll checks, employee data and supplier bank details on an unpatched stack are an audit finding waiting to happen.

Scope, versions and evidence

This is an illustrative workflow, not a customer case study. Confirm the source release, deployment, modules, customisations and extraction permissions before using the mappings below. Tables and report labels describe the demonstration catalogue; native-report equivalence has not been independently certified. Use agreed source reports and representative records for acceptance testing.

An archive is not a replacement for every operational feature of the retired ERP. Document required historical tasks, excluded functions and any archive-derived calculations.

Historical data to scope for Epicor Kinetic

ArchiveHub keeps the Epicor schema as Epicor built it, table by table, with Epicor's field names and descriptions.

General Ledger. GLJrnHed and GLJrnDtl (the posted general ledger), GLJrnGrp (posting groups), GLPeriodBal (period balances, with period 13 as the closing period), GLAccount, COA, COASegment and COASegValues, GLBook, JrnlCode, Fiscal, and GLBudgetHd / GLBudgetDt. Most importantly, TranGLC is there: the link from every posted source record to the journal line it created, so you can still go from an invoice or a part transaction to its GL entry and back.

Payables and receivables. APInvHed, APInvDtl, APInvExp and APInvTax; CheckHed and APTran for payments; Vendor. InvcHead, InvcDtl and InvcTax; CashHead and CashDtl; Customer and ShipTo. BankBatch and BankTran cover bank reconciliation.

Production and quality. JobHead, JobAsmbl, JobOper, JobMtl and JobProd; LaborHed and LaborDtl; ResourceGroup, OpMaster and JCDept; NonConf, DMRHead and DMRActn.

Inventory, sales and purchasing. Part, PartCost, PartWhse, PartBin and PartTran; OrderHed, OrderDtl and OrderRel; ShipHead and ShipDtl; POHeader, PODetail and PORel; RcvHead and RcvDtl.

Assets and payroll. FAsset, FAAddition, FADisposal and FADeprAct; EmpBasic, PREmpMas, PRCheck, PRCheckDtl and PRChkTax. ChgLog carries the master-data audit trail.

Because field descriptions come along, JobNum, PartNum, VendorNum and InvoiceNum work in ad-hoc queries just as they did in a BAQ.

Explore the demonstration

Journal Tracker list in ArchiveHub Journal Tracker: posted Epicor GL journals, filterable by book, journal code, fiscal year and period. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Journal Tracker detail page in ArchiveHub Journal Tracker detail: a single archived Epicor GL journal opened from the list. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Bank Reconciliation in ArchiveHub Bank Reconciliation: archived bank statements and their reconciled bank transactions. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Explore the report reference catalogue

These mappings identify intended business workflows, not certified one-for-one equivalents. Confirm availability, source coverage, filters, currencies, dates and calculations for the selected release and implementation.

Finance

  • Journal Tracker: reference workflow: the General Ledger Journal Tracker / GL Detail (GLJrnHed, GLJrnDtl, TranGLC)
  • GL Trial Balance: reference workflow: the Trial Balance / GL Report by period (GLPeriodBal), with period 13 as the closing period
  • Budget vs Actual: reference workflow: GL Budget Entry and the Budget Comparison Report (GLBudgetHd, GLBudgetDt)
  • Bank Reconciliation: reference workflow: Bank Statement Reconciliation and the Bank Transaction Tracker (BankBatch, BankTran)
  • Inventory/WIP Reconciliation: reference workflow: the Inventory/WIP Reconciliation Report, together with the AR, AP, RNI, bank, payroll and asset subledgers against the GL
  • Asset Tracker: reference workflow: Asset Management, the Asset Tracker and Depreciation Report (FAsset, FAAddition, FADisposal)
  • Sales Tax Report: reference workflow: the Sales Tax Report (InvcTax output tax, APInvTax input tax)
  • Change Log: reference workflow: the Change Log / audit trail of master data (ChgLog), with GL posting groups in the Journal Tracker

Sales

  • Customer Tracker: reference workflow: the Customer Tracker (Customer, ShipTo)
  • Sales Order Tracker: reference workflow: the Sales Order Tracker (OrderHed, OrderDtl, OrderRel)
  • Customer Shipment Tracker: reference workflow: the Customer Shipment Tracker and Shipping Performance (ShipHead, ShipDtl)
  • AR Invoice Tracker: reference workflow: the AR Invoice Tracker (InvcHead, InvcDtl, InvcTax)
  • Cash Receipt Tracker: reference workflow: the Cash Receipt Tracker (CashHead, CashDtl)
  • Aged Receivables: reference workflow: the AR Aged Receivables Report at the archive cut-off, tied to the AR control account

Purchasing

  • Supplier Tracker: reference workflow: the Supplier Tracker (Vendor)
  • Purchase Order Tracker: reference workflow: the Purchase Order Tracker (POHeader, PODetail, PORel)
  • AP Invoice Tracker: reference workflow: the AP Invoice Tracker (APInvHed, APInvDtl, APInvExp, APInvTax)
  • Payment Tracker: reference workflow: the AP Payment Tracker (CheckHed, APTran)
  • AP Aged Invoices: reference workflow: the AP Aged Invoices Report at the archive cut-off, tied to the AP control account

Production

  • Job Tracker: reference workflow: the Job Tracker (JobHead, JobAsmbl, JobOper, JobMtl)
  • Job Cost Analysis: reference workflow: the Production Detail Report / Job Costing, estimated against actual
  • Labor Detail: reference workflow: the Labor Detail Tracker / Time and Expense Entry (LaborHed, LaborDtl)
  • Resource Group Efficiency: reference workflow: the Production Efficiency / Labor Efficiency Report by resource group
  • Scrap Analysis: reference workflow: Scrap Analysis / the Production Scrap Report (LaborDtl ScrapQty by reason)
  • Nonconformance Tracker: reference workflow: the Nonconformance Tracker and DMR Processing (NonConf, DMRHead, DMRActn)
  • Work In Process Report: reference workflow: the WIP Report, open job value at the archive cut-off, tied to the WIP account

Inventory

  • Part Tracker: reference workflow: the Part Tracker (Part, PartCost, PartWhse)
  • Part Transaction History: reference workflow: the Part Transaction History Tracker (PartTran)
  • Stock Status Report: reference workflow: the Stock Status Report, on-hand quantity and value at the cut-off, tied to the inventory accounts

HR and Payroll

  • Employee Tracker: reference workflow: the Employee Tracker (EmpBasic, PREmpMas)
  • Payroll Check Register: reference workflow: the Payroll Check Register (PRCheck), tied to the payroll expense accounts by department

Source documents stay attached

Document types below illustrate the intended scope. Include source attachments and external repositories explicitly, and test retrieval and record linkage before decommissioning.

ArchiveHub keeps documents with the records they belong to. AR invoices, packing slips, purchase orders and AP invoices carry their PDFs; jobs keep their travelers and nonconformances their NCR documents; assets, employees, customers and suppliers keep their files. When a customer's quality team asks about an old shipment, the packing slip, the job traveler and the NCR are all one click from the record.

Beyond the reports

Confirm these capabilities, configuration requirements and limits during the demonstration and scope review; the report catalogue alone does not validate them.

  • Ad-hoc query builder across all archived Epicor tables, with Epicor field descriptions and suggested joins (JobHead to JobOper to LaborDtl on JobNum).
  • Retention rules and purge with approval, so payroll and employee detail can expire while finance and quality records stay as long as contracts require.
  • Legal hold for product liability claims and customer disputes.
  • Personal-data governance: agree the lawful retention, access and deletion requirements with the responsible privacy and records teams. Product features alone do not establish regulatory compliance.
  • Access controls: define and test permissions for the required companies, records and sensitive fields. Do not assume that system-level roles reproduce the original ERP permissions, particularly for payroll and HR data.
  • OData feeds into Excel, Power BI and SAP Analytics Cloud.

How an Epicor decommissioning runs

  1. Extract the Epicor database tables in scope, with field metadata, for every company.
  2. Validate. Row counts per table, then balances that tie out: AR and AP aging to their control accounts, stock status and WIP to the inventory and WIP accounts, payroll to its expense accounts, and the trial balance to GLPeriodBal by period.
  3. Parallel read access for finance, production, quality and purchasing users while Epicor is still there.
  4. Retire after acceptance. Obtain documented sign-off for data reconciliation, document retrieval, user access, retention and legal holds, recovery and remaining integrations. Retire only the approved components; shared infrastructure may still be needed. End or reduce subscriptions, licences and support only where the contract permits. Budget for archive operation and any residual costs.

Questions about Epicor Kinetic retirement

Does a ledger archive answer historical job-quality questions?

Not by itself. Scope job operations, material and labour detail, nonconformance records and relevant documents. Test a real business question from job identifier through its supporting history.

Can one extraction recipe cover every Epicor generation?

Do not assume it can. Confirm the actual product generation, release, deployment and customisations before mapping tables or selecting an extraction method.

What does this ArchiveHub demonstration prove?

The screenshots illustrate how selected records can be presented using mock data. They do not prove production completeness, customer outcomes or parity with every Epicor Kinetic report. Request a demonstration against your own approved scope and acceptance cases.

Related retirement resources

For the broader project approach, see Legacy application retirement planning. To evaluate how users will find transactions, follow relationships and retrieve documents, explore archived data reporting. These resources complement this Epicor Kinetic-specific scope rather than replace source-system validation.

Evidence and further reading

The report catalogue and screenshots originate from an internal mock-data demonstration. They are not vendor certification or customer implementation evidence.

For version-specific mappings, obtain the applicable vendor documentation and compare it with the installed system. No independently verified, release-specific mapping reference is supplied with this draft.

Fixed-price Epicor Kinetic retirement engagement

ArchiveHub offers a fixed-price engagement for Epicor Kinetic retirement and historical data access, based on an agreed scope, deliverables and acceptance criteria. Request a scoped proposal covering your source systems, data, documents, reporting and validation requirements. The proposal should specify included services, exclusions, ongoing platform or hosting charges, and how scope changes will be handled.

Discuss your Epicor Kinetic retirement requirements with ArchiveHub

Epicor Kinetic is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Epicor.