Size fit
Classic mid-market, 20–500 employees
Single entities and smaller groups with manageable process variance, clear proximity to the standard and limited customising need.
ERP system profile · Microsoft Dynamics 365 Business Central
Microsoft D365 Business Central — widely deployed mid-market solution in the Microsoft ecosystem.
Business Central is the successor line of classic Navision and today one of the most frequently deployed ERP platforms in the German mid-market. Its strength lies in the tight integration with Microsoft 365, Power Platform and Azure, as well as a very broad partner landscape. The critical variable in a project is almost always the choice of delivery partner.
Short profile
What characterises Business Central in the mid-market.
Business Central is tailored to mid-market single entities and smaller groups. The solution covers finance, procurement, sales, inventory, light manufacturing, project and service, and can be deepened through AppSource extensions and partner solutions. For most German mid-market companies, the licence and role model is straightforward to navigate.
The tight integration with Microsoft 365, Outlook, Excel, Teams and the Power Platform creates an overall picture that feels intuitive to users. This proximity is one of the most frequent conversion drivers — and at the same time an obligation to think through the strategy for Power Platform and integration cleanly before add-on sprawl takes hold.
Key data
Typically suitable for
Companies for which Business Central is regularly considered.
The following overview outlines the constellations in which Business Central frequently appears on the shortlist in the German mid-market.
Industry fit
Distribution, project, service, light manufacturing
Particularly strong in distribution, trade, project services, service and assembly. For variant manufacturing and complex MES integration, additional add-ons are often needed.
IT fit
Microsoft stack in place
Companies that already use Microsoft 365, Teams, SharePoint and Power Platform benefit from the unified identity, permissions and reporting stack.
Typical strengths
What Business Central is frequently chosen for
- Integration with Microsoft 365, Teams, Outlook, Excel and Power BI out of the box.
- Financial core with solid accounting, multi-currency and multi-tenant capability in the standard.
- Very broad DACH partner landscape, differentiated by industry and company size.
- AppSource marketplace for industry-specific extensions (e.g. DATEV, POS systems, warehouse).
- Power Platform as an extension layer for workflows, portals and analytics.
- Predictable release cycles (two major waves per year) and an established lifecycle model.
Points to examine critically
What should be clarified before a decision is made
- Partner quality varies significantly. The logo on the website says little about actual project seniority.
- Clarify the add-on strategy: which AppSource extensions are necessary and which are only "nice to have".
- Customising discipline — extensions instead of "C/AL legacy", clean separation of standard and extension.
- Calculate the licence model (Essentials vs. Premium, Team Members) realistically by role.
- Limits with complex variant manufacturing, deep MES integration and large group structures.
- Upgrade discipline: those who ignore releases accumulate technical debt.
Typical usage scenarios
Constellations in which Business Central is frequently used.
Scenario 1
Distribution company, 50–300 employees
Replacement of an inventory system or an older Navision release, integration with a shop system and logistics provider, DATEV interface, reporting in Power BI.
Scenario 2
Project service provider or agency
Project and time billing, resource control, financial core, integration with Microsoft 365 as a working environment. Close to the standard, quickly productive.
Scenario 3
Machinery builder, small to mid-size
Single-unit and small-series manufacturing with manageable variant depth, service and spare parts, integration with PDM/PLM via add-on, Power BI for KPIs.
Scenario 4
Subsidiary in a group structure
Local entity within a group context that works independently on Business Central while the parent consolidates on D365 F&O or SAP.
Typical project sizes
Indicative figures for budget and timeline.
The ranges are experience values from selection projects. They replace neither a quote nor a TCO calculation, but provide initial orientation.
| Scenario | User range | Project duration | Order of magnitude, year 1 investment | Typical scope |
|---|---|---|---|---|
| Small mid-market | 15–50 | 3–5 months | Low six-figure range | Finance, distribution, few add-ons |
| Mid-market with process variance | 50–200 | 5–9 months | Mid six-figure range | Finance, distribution, service, integrations |
| Mid-market with light manufacturing | 100–400 | 6–12 months | High six-figure range | Finance, manufacturing, service, add-ons |
| Smaller group, multiple tenants | 150–500 | 9–15 months | High six- to low seven-figure range | Template + rollout |
All values are orientation ranges, not binding quotes.
Structure your selection →
Alternatives and complements
Systems often evaluated in parallel in comparable selection projects.
These notes are meant neutrally and not as a winner-picking comparison.
Upgrade path
Microsoft D365 Finance & Operations
When requirements grow beyond Business Central (group context, manufacturing depth, compliance), F&O is the structural next step in the Microsoft stack.
Parallel on shortlist
Oracle NetSuite
A frequent alternative in international setups or finance-centric priorities.
Alternative in distribution
Xentral
For online-commerce and e-commerce-focused mid-market companies, a serious counter-design with an API-first approach.
Frequent questions
What is regularly asked about Business Central in selection projects.
Is the move from Navision / NAV to Business Central worthwhile?
For most existing customers, yes — especially when the legacy version is being retired or customisations block upgradeability. The key is not to treat the move as a purely technical migration, but as an opportunity to harmonise processes.
How much customising is sensible?
As much as necessary, as little as possible — and only in the form of extensions. Old C/AL customisations are not carried forward. Those who use the standard consistently significantly reduce maintenance costs and upgrade risks.
How important is partner choice?
Very important. Quality variance among Microsoft partners is significant. What to look for: seniority of the project team, references of comparable size and industry, a clear approach in the requirements and target picture phases.
Is Business Central sufficient for manufacturing companies?
For single-unit and small-series manufacturing with manageable variant logic, the standard often suffices, possibly supplemented by specialised AppSource extensions. With complex variant manufacturing, deep MES integration or international plant structures, D365 F&O or SAP is usually closer to the need.
How good is the DATEV integration?
DATEV interfaces are provided via established partner solutions and are uncritical in most projects. The topic is set up cleanly when tax office, finance team and delivery partner coordinate early together.
Business Central or an alternative — we help answer that question systematically.
The ERP Fit Check captures your starting position systematically. It shows whether Business Central realistically belongs on your shortlist — or whether D365 F&O, SAP or another system is closer to your needs.
As of April 2026 · Profile based on publicly available information and experience values from selection projects. Microsoft and Dynamics 365 Business Central are trademarks of Microsoft Corporation.