Epicor 10 or 9 on sustaining support: Kinetic Cloud upgrade vs ERPNext for 50 to 500 person manufacturers

Short answer

Epicor publishes its Support Lifecycle Policy to customers behind the EpicWeb login, so we could not confirm version status on a public Epicor page. Partner sources list Epicor 9.05.702 and Epicor ERP 10.0.700 through 10.2.700 in Sustaining Support, with no end date: limited support, no new modules, no new features (checked Nov 17, 2026). Epicor has said publicly that the final on-premises Kinetic release is 2028.1 (tentatively January 2028), with Active Support to December 31, 2029. So an Epicor 10 site really has two choices inside Epicor: move to Kinetic in the Epicor Cloud, or upgrade to on-premises Kinetic for a few years and face the same decision again. Partners describe the jump from Epicor 10 to Kinetic as looking more like a reimplementation than an upgrade. That is why it is worth pricing ERPNext (open source, GPL-3.0, no licence fee) at the same time: if you are re-implementing anyway, compare both. Kinetic Cloud remains the better fit for shops that depend on Epicor’s scheduling, configurator or Epicor add-ons. Epicor is quote-only, so we give no Epicor estimate.

Choosing a platform? Get a free 30-minute advisory call.

Who this guide is for

This guide is for owners, CFOs, operations directors and IT managers at manufacturers with roughly 50 to 500 people who still run Epicor 9.05 or Epicor ERP 10 (10.0, 10.1 or 10.2) on their own servers. Most are make-to-order or mixed-mode shops that have used Epicor for a decade or more and skipped upgrades because the system worked.

We implement ERPNext, so read our view with that in mind. For many Epicor 10 sites, Kinetic in the Epicor Cloud is the right next step, and we say where below. This guide is for those who want an honest comparison before committing to what is, in practice, a new implementation.

It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. If you are already on Kinetic, read our Epicor Kinetic on-premises guide. If you are on Vantage or Vista, read our Vantage and Vista guide.

Sources, checked on Nov 17, 2026: Epicor’s Epicor press release, Jan 6, 2026, the Epicor “Innovation Moves to the Cloud” page, the ERP Advisors Group article on Epicor ERP support (third party), the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.

What we could not confirm

Epicor says that its FAQs and Support Lifecycle Policy are available to customers who log in with EpicWeb credentials. We did not log in, and we found no public Epicor page listing the support level for Epicor 9.05 or 10.x. The status below comes from a partner source and we label it as such. Check your release’s status on EpicWeb or EpicCare, or ask your Epicor account manager, before you plan around it. We give no end date because no public Epicor source gives one.

Support status: what is known, and from whom

ClaimStatusSource
Epicor 9.05.702 is in Sustaining SupportPartner source; not confirmed on a public Epicor pageERP Advisors Group article on Epicor ERP support (third party)
Epicor ERP 10.0.700 through 10.2.700 are in Sustaining SupportPartner source; not confirmed on a public Epicor pageERP Advisors Group article on Epicor ERP support (third party)
Under Sustaining Support: essential support only, no new modules (additional users for implemented modules are possible), limited support servicesPartner sourceERP Advisors Group article on Epicor ERP support (third party)
Newer releases typically get about two years of Active SupportPartner sourceERP Advisors Group article on Epicor ERP support (third party)
Final on-premises Kinetic release is 2028.1, tentatively January 2028; Active Support to Dec 31, 2029; Sustaining from Jan 1, 2030EpicorEpicor press release, Jan 6, 2026
FAQs and the Support Lifecycle Policy are available only through EpicWebEpicorEpicor “Innovation Moves to the Cloud” page

The partner source also lists what Active Support includes: access to the newest releases, security updates, compliance and regulatory updates, application and technical support, and the ability to buy more modules and users. Sustaining Support, by the same account, keeps you running but stops you growing the system with new modules.

The important fact for planning is not the Epicor 10 status itself. It is that the on-premises road inside Epicor now has an end: Epicor says new innovation after 2028.1 goes to the Epicor Cloud only. If you upgrade from Epicor 10 to on-premises Kinetic today, you land on a platform whose last feature release is scheduled for 2028.

Get a tailored shortlist and pricing review

Share your work email and we'll send you a replacement shortlist and cost review tailored to your user count and requirements. A member of our ERP team prepares it personally.

Why the move to Kinetic is close to a reimplementation

The partner source puts it plainly: when changing system architectures, the move to Kinetic in the cloud “may look more like a reimplementation than an upgrade”. In our experience with long-running Epicor sites, the reasons are familiar:

  • Customisations. Years of screen customisations, BPMs (business process management directives), BAQs, dashboards, SSRS or Crystal reports and external integrations. Each has to be re-tested, and many rebuilt, on a newer release and a different user interface.
  • Process drift. The way you use jobs, quotes, methods of manufacture and costing has evolved since go-live. A move is the moment you either carry that drift forward or clean it up.
  • Data quality. Duplicate parts, old revisions, unused resource groups and part-classes nobody maintains. Moving them to a new system, Epicor or not, multiplies the mess.
  • Training. A new interface and new ways of working affect every user, not just the IT team.

If the Kinetic move is close to a reimplementation, the comparison changes. You are not choosing between a cheap upgrade and an expensive migration. You are choosing between two implementations, one that keeps Epicor’s data model and terminology, and one that does not. Both deserve a proper fit test and a written proposal.

Your options

OptionWhat it involvesBest when
Move to Kinetic in the Epicor CloudEpicor-hosted, updated by Epicor; migration through Ascend with Epicor, which Epicor describes as a methodology with AI tooling for scoping and data conversion, best-practice templates and fixed-fee program pricingYou want to keep Epicor’s manufacturing depth and are comfortable with vendor-hosted SaaS
Upgrade to on-premises KineticSame product family on your servers, until the 2028.1 release and its Active Support end (Dec 31, 2029)You need on-premises now and accept a second decision before 2030
Stay on Epicor 10 or 9.05Sustaining Support, per partner sourcesShort term only, while you plan
Move to ERPNextOpen-source ERP with manufacturing, stock, buying, selling and accounting; self-host or Frappe CloudYou want to own the system, avoid per-user licence growth and your scheduling and configuration needs fit ERPNext

Epicor does not publish Kinetic or Epicor Cloud prices on the pages we checked. The Ascend program is described as fixed-fee, but the fee is a quote. Ask for subscription, Ascend services and what is out of scope in writing.

How Epicor concepts map to ERPNext

In Epicor 10 or 9In ERPNextNotes
Parts, part classes, UOMsItems, item groups, UOM conversions (ERPNext Item documentation)Clean obsolete parts and revisions first
Method of manufacture (materials and operations)BOM with operations, Routing (ERPNext Bill of Materials documentation; ERPNext Routing documentation)Routing stores operations with hourly rate, time and batch size
Resource groups and resourcesWorkstations (ERPNext Workstation documentation)Working hours, holiday list, cost components, production capacity
Jobs and job operationsWork Orders and Job Cards (ERPNext Work Order documentation; ERPNext Job Card documentation)Job Cards are created per operation when the Work Order is submitted
Labour entry (MES or Time and Expense)Job Card time logs; Timesheets (ERPNext Timesheets documentation)Test how operators record time on the floor
Scheduling boardsCapacity planning against workstation hours (ERPNext Capacity Planning documentation); Plant Floor (ERPNext Plant Floor documentation)No documented graphical finite scheduler in ERPNext
Quotes and estimatesQuotation (ERPNext Quotation documentation)Estimating from a method needs a defined process
MRP and purchase suggestionsProduction Plan and Material Requests (ERPNext Production Plan documentation; ERPNext Material Request documentation)Compare planned orders with Epicor for the same demand
Subcontract operationsSubcontracting (ERPNext subcontracting documentation)Test your common outside-processing flows
Lot and serial trackingBatch, Serial No, Serial and Batch Bundle (ERPNext Batch documentation; ERPNext Serial No documentation; ERPNext Serial and Batch Bundle documentation)Run a full trace from receipt to shipment
InspectionQuality Inspection, including in-process from a Job Card (ERPNext Quality Inspection documentation)Operation-level inspection templates
Multi-company and sitesMulti-company, warehouses, inter-company invoices, accounting dimensions (ERPNext inter-company invoices documentation; ERPNext accounting dimensions documentation)Test intercompany flows and consolidation
BPMs and customisationsCustom Fields, Workflows, server scripts (ERPNext Custom Field documentation; ERPNext Workflows documentation)List every BPM and decide: rebuild, replace with standard, or drop

Where ERPNext fits a 50 to 500 person manufacturer, and where it does not

ERPNext covers the core of a make-to-order shop well: BOMs and routings, work orders with Job Cards, MRP through Production Plans, stock across warehouses with batches and serials, purchasing, sales, and full accounting with multi-company and multi-currency. Routings can enforce operation sequence: ERPNext says it throws a validation error if an operation is completed on a Job Card before its predecessors. Workstations carry hours, shifts and a holiday list, and capacity planning allocates operations against them when a Work Order is submitted.

The gaps we test first with Epicor shops:

  • Scheduling. ERPNext’s capacity planning expects each operation to start and end on the same day unless you enable overtime or split operations, and we found no documented drag-and-drop finite scheduler (ERPNext Capacity Planning documentation; ERPNext Manufacturing Settings documentation). If your planners live on Epicor’s scheduling boards, this is the first test.
  • Product configuration. If you sell configured products through Epicor’s configurator, ERPNext Item Variants are not a like-for-like replacement (ERPNext Item Variants documentation).
  • Shop-floor data collection. Job Cards record start, completion, employee and quantity. If you use Epicor MES terminals heavily, design and test the floor experience early.
  • BPM-heavy processes. Each BPM encodes a business rule. ERPNext can usually reproduce them with workflows, validations or server scripts, but someone has to write and own them.

A useful rule

If more than a third of your fit-test rows score “build”, Kinetic Cloud is probably cheaper to live with, whatever the licence difference. If most rows are “standard” or “configure”, ERPNext deserves a full proposal.

What an Epicor 10 to ERPNext migration moves

Epicor dataERPNext targetNotes
Parts, UOMs, customers, suppliers, contactsItems, UOM conversions, Customers, Suppliers (ERPNext Customer documentation; ERPNext Supplier documentation)Load with Data Import (ERPNext Data Import documentation)
Methods of manufacture for active partsBOMs, Operations, Routings, WorkstationsActive parts only; rebuild, do not copy every revision
Open jobsFinish in Epicor, or recreate as Work Orders at the right stageMost sites finish open jobs in Epicor
Open sales and purchase ordersSales Orders and Purchase Orders (ERPNext Sales Order documentation; ERPNext Purchase Order documentation)Freeze changes during cut-over
Stock by warehouse and bin, with lotsOpening Stock Reconciliation (ERPNext Stock Reconciliation documentation)Count high-value bins before go-live
Open AR and APOpening invoices (ERPNext opening balance documentation)Reconcile to aged reports
GL balancesOpening trial balance on a chart of accounts (ERPNext Chart of Accounts documentation)Keep Epicor read-only for history

Epicor 10 runs on Microsoft SQL Server; community upgrade threads describe the move from Progress to SQL Server happening at the 9.05 to 10 migration (EpiUsers community thread on a Vantage 8.03 upgrade). On Epicor 10 that makes extraction straightforward for a competent data team: export, clean in a staging database or spreadsheets, and load. Keep the Epicor database available read-only for history, audits and repeat-order lookups. Do not try to move a decade of closed jobs and labour into ERPNext.

Costs: what is published

ItemUSD (published)GBPSource
Kinetic, Epicor Cloud, Ascend with EpicorQuote only; no estimate givenQuote onlyEpicor “Innovation Moves to the Cloud” page
ERPNext softwareNo licence fee (GPL-3.0)No licence feeERPNext repository on GitHub
ERPNext on Frappe Cloud, site plansFrom $5 per monthAbout £3.78 (indicative)Frappe Cloud pricing page
ERPNext on Frappe Cloud, dedicated serversFrom $40 per monthAbout £30.25 (indicative)Frappe Cloud server plans page

Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.25), checked on Nov 17, 2026. The GBP figures are indicative conversions, not Frappe prices.

Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3222 per £1 for 13 Nov 2026, the latest published figure when we checked on Nov 17, 2026. They are not official UK prices: Frappe does not publish a GBP list price for these plans, and your invoice currency, rate and VAT treatment may differ.

Hosting is a small line in either budget. For ERPNext, the real costs are implementation, data migration, rebuilding the BPMs and reports you keep, any scheduling or configurator build, integrations and training. For Kinetic Cloud, they are the subscription, the Ascend fee, rework of customisations outside its scope and training. Compare five years, and make sure both proposals cover the same scope.

Where Kinetic Cloud is the better answer

  • Your planners depend on Epicor’s scheduling and you do not want a separate scheduling tool.
  • You sell configured products through Epicor’s configurator.
  • You use Epicor’s surrounding products heavily, and replacing them at the same time is too much change.
  • Your team knows Epicor well and has limited capacity for a new data model and new terminology.
  • You are happy with vendor-hosted SaaS and want Epicor to run updates.

ERPNext is a better fit when you must self-host or control where your data lives, you want to own the code, per-user licence growth is a real concern as you add floor and warehouse users, and your scheduling and configuration needs are moderate.

A practical plan for Epicor 10 and 9.05 sites

Months 1 to 2: status and inventory

Confirm your release’s support level on EpicWeb. Ask Epicor for an Ascend proposal in writing. List BPMs, customisations, BAQs, dashboards, reports and integrations, and mark each as must-have, later or drop.

Months 2 to 4: ERPNext fit test

Rebuild 30 active parts with methods, a month of jobs, a week of labour and one warehouse in ERPNext. Run MRP for the same demand in both systems. Score scheduling, configuration, floor data and BPMs.

Month 5: decide

Compare five-year cost and risk for Kinetic Cloud and ERPNext on the same scope.

Then: build, pilot, cut over

Conference-room pilot, train key users, then cut over at a period end with one month-end in parallel. Finish open jobs in Epicor where possible.

Decision table

If this is true for youLean towardsWhy
Scheduling boards and configurator are centralKinetic CloudERPNext would need a build or add-on
Must stay on-premises with Epicor for nowOn-premises Kinetic, with a plan for 2029Final on-premises release 2028.1; Active Support to Dec 31, 2029
Must self-host long term, want to own the codeERPNext worth pricingOpen source, runs on your servers or Frappe Cloud
Heavy BPMs and customisations you want to keepFit test both carefullyBoth paths mean rebuilding them
Moderate scheduling, MRP plus dispatch listERPNext worth pricingRoutings, Work Orders, Job Cards and Production Plans cover it

Best for, and wrong choice when

ERPNext is best for

Manufacturers with 50 to 500 people on Epicor 10 or 9.05 who want to own their ERP, can live with workstation-based capacity planning, have a manageable number of BPMs and reports to rebuild, and would rather pay for implementation than for per-user subscriptions.

Kinetic Cloud is best for

Epicor shops that rely on Epicor’s scheduling, configurator and add-on products, are comfortable with SaaS, and value continuity of data model and terminology.

ERPNext is the wrong choice when

Your business depends on Epicor’s configurator or finite scheduling and you will not build or buy a replacement, you need to go live within months with no fit test, or no one internally can own the system after go-live.

Frequently asked questions

Is Epicor 10 still supported?

Partner sources say Epicor ERP 10.0.700 through 10.2.700 are in Sustaining Support: essential support, no new modules or features (checked Nov 17, 2026). Epicor’s own policy is behind the EpicWeb login; confirm your status there.

Is Epicor 9.05 still supported?

Partner sources list Epicor 9.05.702 in Sustaining Support, with no end date. We found no public Epicor page that confirms it.

When does on-premises Kinetic end?

Epicor says the final on-premises Kinetic release is 2028.1, tentatively January 2028, with Active Support through Dec 31, 2029 and Sustaining Support from Jan 1, 2030 (press release Jan 6, 2026).

Is moving from Epicor 10 to Kinetic an upgrade or a reimplementation?

Partners describe the move to Kinetic in the cloud as looking more like a reimplementation than an upgrade. Plan, budget and test it as one.

What is Ascend with Epicor?

Epicor’s cloud migration program: a methodology with AI tooling for scoping and data conversion, best-practice templates and consulting, with fixed-fee program pricing. The fee is quoted, not published.

Can ERPNext replace Epicor 10?

For many 50 to 500 person make-to-order manufacturers, yes. Methods, jobs, labour, MRP, lots and serials map to BOMs, Routings, Work Orders, Job Cards, Production Plans, batches and serials. Test scheduling and configuration first.

What does ERPNext cost?

No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (about £3.78 and £30.25 at the Bank of England rate for Nov 13, 2026; checked Nov 17, 2026). Implementation is separate.

On Epicor 10 or 9.05 and weighing Kinetic?

We rebuild a sample of your methods of manufacture, a month of jobs and your key BAQ reports in ERPNext, so you can set it next to an Ascend with Epicor proposal before you commit to either reimplementation.

We'll get back to you shortly. We use your details only to reply to this request.