Bramvia — Business Central Experts
Epicor Kinetic to Business Central: when a manufacturing ERP is more than the plant needs
Epicor Kinetic is a deep manufacturing ERP — and for many mid-sized shops, too deep, too costly to upgrade and too dependent on specialists. Where Epicor genuinely wins, where Business Central covers the same ground at a fraction of the complexity, and how a migration works without stopping production.
Short answer: Epicor Kinetic (formerly Epicor ERP / E10) is a serious manufacturing system: advanced scheduling, MES-style shop floor, configurators, deep engineering change control. For a complex discrete manufacturer with hundreds of routings and a full-time Epicor team, it is the right tool. For a mid-sized shop of 30-200 people that uses a fraction of it, pays for all of it, and dreads every upgrade, it is an expensive way to run production orders. Business Central covers BOMs, routings, production orders, capacity planning, MRP, subcontracting, and — since 2026 — quality inspections, with far less complexity and a much larger pool of people who can support it. Migrations run 4-8 months and $60,000-180,000 in the US, and the production line does not stop: cutover happens at a period end with Epicor read-only as fallback.
Where Epicor Kinetic genuinely wins
- Advanced scheduling. Finite scheduling with constraints, what-if, and a scheduler that a large plant genuinely needs.
- Configurators. Complex configure-to-order products with rules engines.
- Shop floor execution. MES functionality, machine data collection, labour tracking at the workcentre.
- Engineering change control with full revision management.
- Deep industry fit for aerospace, automotive tiers, complex discrete.
If your plant runs finite scheduling on 300 workcentres and a configurator with thousands of rules, stay — and staff for it.
Where it costs more than it gives
The companies that come to us are usually not using that depth. What they describe:
- Upgrade projects measured in months and six figures, delayed for years, leaving them on an old version with the security and support consequences that brings. Why that now matters for insurance.
- Dependence on a small pool of Epicor consultants, expensive and scarce.
- Customisations (BPMs, customised dashboards, custom code) that nobody dares touch.
- Finance functionality that is adequate but not where Epicor's heart is — so reporting lives in spreadsheets.
- Licence and maintenance costs sized for capabilities that are switched off.
- Microsoft 365 as the rest of the company, with the ERP as the island.
What Business Central covers for a mid-sized manufacturer
| Capability | Business Central (Premium) |
|---|---|
| Bills of materials, multi-level, versions | Native |
| Routings with work and machine centres | Native |
| Production orders, consumption, output, actual costing | Native |
| Capacity planning and MRP/MPS | Native |
| Subcontracting | Native; 2026 improvements route instructions and attachments to the subcontractor PO |
| Quality inspections on receipt, production, assembly, warehouse | Native Quality Management extension (2026) |
| Lots, serials, traceability | Native |
| Standard vs actual variance | Native — how we use it |
| Finite scheduling | Basic; advanced via AppSource apps |
| Configurator | Via AppSource apps |
| Shop floor data collection | Via scanning apps and terminals |
The honest line: Business Central's scheduling is capacity-based, not finite-constraint. If finite scheduling is your daily reality, that is the deciding question, and there are AppSource apps that add it.
Why the move pays
- Cost. Licences $80-110 per user per month, no annual maintenance on a perpetual licence, no upgrade projects — two updates a year, included.
- People. A far larger pool of consultants and developers; internal staff can learn AL.
- Finance in one system, with Power BI included, so reporting stops being an export.
- AI in production: payables, sales order and expense agents. Epicor's AI story is developing; Business Central's ships.
- Microsoft integration across Excel, Outlook, Teams.
How the migration works without stopping the plant
- Assess: which Epicor capabilities are actually used (usually a fraction), the BPMs and customisations, integrations, and data quality on items, BOMs and routings.
- Design: BOMs and routings in Business Central — the moment to clean up dead revisions and phantom items.
- Migrate masters: items, BOMs, routings, work centres, customers, vendors, open orders, balances. History archived in Epicor read-only.
- Rebuild what's needed as AL extensions; retire what the standard covers.
- Test with your real production: run last month's orders through the sandbox.
- Cut over at a period end. Epicor stays read-only for lookups.
Timeline 4-8 months; cost $60,000-180,000 depending on plant complexity and customisation. Each part invoiced only after you accept it.
FAQ
We have a configurator. Is that a blocker? Not automatically. Simple configurations map to BOM versions and assembly; complex rule engines need an AppSource configurator. We'll tell you which after seeing yours.
What about our shop floor terminals? Scanning apps and shop floor terminals for Business Central exist; the question is which data you need collected, and that's usually less than Epicor was capturing.
Finite scheduling? Business Central plans by capacity; finite constraint scheduling needs an app. If it is core to your operation, that's the first thing to evaluate.
Is this a step down? For a plant using 30% of Epicor, it's a step to the right size. For a plant using 90%, it isn't the right move and we'll say so.
Paying for an Epicor you use a third of? Free assessment, no commitment — we'll map what you actually use against what Business Central covers.