Business Central for the mid-market — where the Microsoft solution carries, and where its limits are.

Where Business Central sits in the market

Business Central is Microsoft's mid-market ERP — the cloud-first evolution of Dynamics NAV ("Navision"), developed in two major release waves per year. In the DACH region it meets one of the densest partner landscapes anywhere and a very large installed base from the NAV era. That makes it the reference point of most selection projects: even companies that ultimately choose differently usually compare against Business Central.

This ubiquity is both a strength and a risk. A strength, because experience, extensions and staff are widely available. A risk, because "let's just take Microsoft" replaces an architecture decision with a habit. The short version of our assessment lives on the Business Central profile page; this guide covers the decision logic.

Who it typically fits

Selection projects show a clear fit profile. Size: the classic mid-market of roughly 20–500 employees — single entities and smaller groups with manageable process variance and closeness to standard. Industries: strongest in trade and distribution, project services, field service and light manufacturing; variant-heavy manufacturing and deep MES integration usually require add-ons or industry solutions. IT landscape: organisations already working on Microsoft 365, Teams and Power BI benefit from a shared identity, permission and reporting stack.

The counter-profile is just as clear: multi-GAAP group consolidation, large international rollouts and heavy manufacturing are not Business Central's core — that territory belongs to Dynamics 365 Finance & Operations, SAP S/4HANA or, for multi-entity cloud setups, Oracle NetSuite. See ERP selection for multi-entity structures for how to assess those.

Editions and licensing logic

Business Central has two main full-user editions: Essentials covers finance, purchasing, sales, inventory, projects and basic CRM; Premium adds manufacturing (production orders, routings) and service management. Team Member licences serve occasional users with tightly limited rights — in practice the most important lever for keeping licence cost realistic.

Two rules have proven useful. First: the edition is chosen per environment, not per user — if you need manufacturing, all full users are licensed as Premium, which belongs in the budget early. Second: roles before licences — only when each role's real activity is clear (who posts, plans, confirms; who merely approves or views) can the mix of full and Team Member licences be calculated seriously. Concrete prices deliberately stay out of this guide: they change, they are negotiable, and they live in Microsoft's current price list — in a selection, structure matters more than list price.

The Microsoft ecosystem — argument and trap

The strongest argument for Business Central rarely appears in feature lists: it is the environment. Excel integration in both directions, Outlook document handling, Teams sharing, Power BI as the reporting standard, Power Automate for approval workflows, and AppSource as the marketplace for industry extensions. Organisations already living in this stack get integration value that would be project effort elsewhere — see ERP in the Microsoft ecosystem for the architectural view.

The trap: the ecosystem argument does not replace process validation. A company with complex variant manufacturing is not helped by sharing the backlog in Teams. Demos should therefore run your own core processes with your own data volumes — not the vendor's standard Office-integration show.

NAV migration: a project type of its own

A large share of Business Central projects in the region are not new selections but replacements of ageing Dynamics NAV installations. Set expectations correctly: this is not an upgrade, it is a migration project with its own rules. C/AL-era customisations do not carry over to the cloud model — they are rebuilt as extensions or, better, checked against today's standard and often retired, because the standard now covers the requirement.

For the decision this means: treat a NAV migration like a fresh selection — with process discovery, must-have criteria and a partner comparison. The incumbent partner who ran the old NAV belongs in that comparison, but not as an unexamined default.

Delivery reality: partners, extensions, release waves

Partner quality varies widely. Density is an advantage, but it makes selection harder: certificates say little about project seniority in your industry. Named key people, references in a comparable process environment and an honest answer on team capacity are the stronger signals — partner choice and product choice are two separate decisions.

Extension discipline decides upgradeability. Customisations live as clean extensions beside the standard. Teams that keep this discipline absorb the two yearly release waves without drama; teams that soften it accumulate technical debt that compounds at every update. The contract should fix how extensions are built, documented and carried across releases — and operations should test every wave in a sandbox before it goes live.

Limits: when something else fits better

Three constellations regularly argue against Business Central as the core system: complex manufacturing (multi-level variant configuration, tight MES coupling — add-on territory that must be validated as a concrete industry stack), corporate finance (multi-GAAP, complex consolidation, large international structures — F&O, SAP or NetSuite territory, see group consolidation in the mid-market), and non-Microsoft landscapes, where the central integration argument disappears and alternatives such as Odoo or weclapp deserve an equal hearing — see the ERP solutions overview.

Eight questions before you decide

1. Which of our core processes run in the standard, which need AppSource add-ons — and what do those add-ons cost over five years?
2. Essentials or Premium: which roles force the edition, and how many users are honestly Team Members?
3. What does our role/licence mix look like in detail — who posts, who confirms, who only views?
4. With NAV legacy: which old customisations does today's standard cover, which are rebuilt as extensions, which are retired?
5. How many projects of our size and industry has the partner delivered — with which named people for our project?
6. How is the release process organised: who tests the two yearly waves, in which sandbox, with what fallback?
7. Which integrations (accounting hand-off, shop, logistics, PDM/PLM) are standard, which are partner work — and who operates them long-term?
8. What is our exit scenario: data export, contract terms, dependency on partner-specific extensions?

These questions translate directly into a demo script. For a first structured self-assessment of your profile, the ERP Fit Check provides an initial orientation without requiring contact details (German-language tool).

Frequently asked questions

Is Business Central the successor to Dynamics NAV / Navision?

Yes. Business Central is the cloud-first evolution of Dynamics NAV. For existing NAV installations the move is not an upgrade but a migration project in its own right: legacy C/AL customisations have to be rebuilt as extensions — or, better, retired where today's standard already covers the requirement.

What company size does Business Central typically fit?

The core is the classic mid-market of roughly 20 to 500 employees — single entities and smaller groups with processes close to standard. Below that range it is often oversized; above it, or for complex group structures, Dynamics 365 Finance & Operations or another corporate-grade solution is usually evaluated.

Does Business Central require the Microsoft ecosystem?

No, but that is where it earns its keep: identities, Teams, Outlook, Excel and Power BI interlock out of the box. Organisations not working on Microsoft 365 lose a substantial part of the argument and should weigh alternatives on equal terms.

What does a Business Central project cost?

As an orientation range from selection projects: smaller mid-market rollouts start in the low six-figure range for year one; setups with process variants and integrations reach the mid six figures; group templates with rollouts go beyond. Licences are only one part — total cost of ownership over five years is the number that matters.

Why do Business Central projects fail?

Rarely because of the product. The usual causes are partner choice and missing extension discipline: too much customisation outside the standard, ignored release waves, and an implementation team without industry experience.

Author: Joerg H. Paul Schaefer · As of: September 2026 · Assessment based on documented selection projects; always verify product details against current Microsoft documentation. erp-check.info is a vendor-independent information platform.