ERP guide
Should a manufacturer leave Epicor Kinetic or stay on it?
Stay on Epicor Kinetic when its manufacturing depth fits your plant, the move to its cloud suits you, and the maintenance increases still leave the numbers working. Leave for a custom cloud build when the end of on-premises feature releases in 2028 forces a migration anyway and your configurators, reports and quoting rules are what set the business apart.
| What you are comparing | Staying on Epicor | A custom build |
|---|---|---|
| How it charges | A quoted license or subscription with no published price, plus yearly maintenance. Customers report maintenance increases of 5% to 10% a year. | A one-time build scoped in writing, then hosting and running costs. No license and no maintenance percentage that rises each year. |
| Per-user fees | Users are part of the quote, so adding people to the system usually means adding to the bill. | None. A new planner, buyer or shop floor lead costs nothing to add. |
| On-premises future | Kinetic 2028.1 is the last on-premises feature release, and active on-premises support ends December 31, 2029. Staying long term means moving to Epicor's cloud. | Built as a cloud system in accounts your company owns, so the move off local servers happens once and on your schedule. |
| Cloud access to your own data | Customers report no direct database access in Epicor's cloud, with a read-only copy sold as an extra. | Your company owns the database, so reporting tools and analysts query it directly. |
| Upgrades | Customers report upgrades breaking configurators, custom reports and dashboards, and the cloud release schedule is set by Epicor. | Changes ship when your team approves them, tested against your own processes first. |
| Modules | Capabilities are sold as modules, and customers report paying for modules they no longer use, with re-adding one meaning buying it again. | Built for the functions the plant uses. A new area is scoped and added when it is needed, with no module to license. |
| Getting data out | Customers who left Epicor's cloud report hard exits, with data that was difficult to separate and handed over as file transfers. | Your data sits in a standard database you own, readable by any developer or reporting tool. |
| Fit to process | Built for discrete, make-to-order manufacturing. Shops that differ lean on configurators, custom fields and reports that every upgrade has to carry. | Built from your routings, quoting rules and approvals, so the process lives in the system and not in workarounds beside it. |
| Time to launch | Staying needs no new system, though the move to Epicor's cloud is its own project with testing and retraining. | Starts with discovery and a written scope. Areas go live in stages, and Epicor keeps running until the new system agrees with it. |
When staying on Epicor Kinetic is the right call
Stay when Kinetic fits the way your plant makes things. Epicor built it for discrete, make-to-order manufacturing, and a shop that runs close to that model gets manufacturing logic it would otherwise pay to rebuild.
Stay when the cloud move suits you anyway. If your team was planning to leave its own servers, Epicor's cloud takes over the hosting, and the decision comes down to whether the maintenance increases customers report still leave the numbers working.
Stay when few customizations sit on top of standard Kinetic. A lightly configured system has little to break at each upgrade and little to gain from a rebuild.
What leaving Epicor Kinetic involves
Leaving starts with an inventory of what the plant built inside Epicor. Configurators, custom fields, queries, reports and dashboards each hold a rule someone relied on, and each one is read, kept, changed or dropped.
Data comes out next. Customers report no direct database access in Epicor's cloud, so a plant still on its own servers has an easier export than one already hosted by Epicor. Open orders, routings, bills of materials, inventory and balances move first, and history moves in the form people will query it.
Epicor keeps running until the new system agrees with it over the same period. Implementation, migration and training take effort on any route, and leaving Epicor for another product carries the same work.
How a custom cloud build replaces Epicor Kinetic
Black Badger replaces on-premises systems by moving them to the cloud. The new system runs in cloud accounts your company owns, with the code, the database and the admin logins in your name.
The build follows the plant. Quoting, routings, job tracking, purchasing and inventory are written from how the shop works, and the accounting can stay in a ledger your accountants already trust, connected to the new system.
There is no per-user license, no maintenance percentage and no vendor release to retest against. The ongoing costs are hosting and whoever maintains the code, and Black Badger or any competent developer can do that work.
What a custom build involves, and how to ask about one
Questions buyers ask
Is Epicor forcing on-premises customers to the cloud?
Epicor announced in January 2026 that Kinetic 2028.1 is its last on-premises feature release and that active on-premises support ends December 31, 2029. On-premises customers can keep running without new features, and Epicor's own path forward is its cloud.
How much have Epicor maintenance fees gone up?
Customers on Epicor's user forum report maintenance increases of 5% in 2021, 8% in early 2025 and a 10% notice in November 2025. Epicor publishes no Kinetic price, so each customer's figure comes from its own contract.
Can a company get its data out of Epicor's cloud?
Yes, though customers report it takes work. Epicor's cloud gives no direct database access, a read-only copy is sold as an extra, and customers who left report exports handed over as files. A plant still on its own servers holds its own database and has an easier exit.
Would Black Badger host an Epicor replacement on our own servers?
No. Black Badger replaces on-premises systems by moving them to the cloud, in accounts the company owns, so the code, database and logins stay in its name.
More from this guide
- Top picks
- After a renewal increase
- Multi-entity companies
- NetSuite alternatives
- Acumatica alternatives
- Sage Intacct alternatives
- Business Central alternatives
- Dynamics GP alternatives
- SAP Business One alternatives
- Epicor alternatives
- Odoo alternatives
- Salesforce alternatives
- HubSpot alternatives
- Leaving NetSuite?
- Leaving Acumatica?
- Leaving Sage Intacct?
- Leaving Business Central?
- Leaving Dynamics GP?
- Leaving SAP Business One?
- Leaving Odoo?
- Leaving Salesforce?
- Leaving HubSpot?
- Custom option