Microsoft Dynamics 365 Business Central

The problems Business Central is bought to solve

Companies rarely buy an ERP because they want an ERP. They buy it because a specific set of problems has become expensive enough to act on.

If none of these describe your company, an ERP project is premature. That is a more useful answer than a feature list.

Who it fits

Business Central targets the middle of the market: companies large enough that spreadsheets have broken down, small enough that a corporate-scale ERP would be disproportionate. In practice that means roughly 10 to 300 system users, usually with inventory, production or projects involved.

The fit is strongest in wholesale and distribution, manufacturing, construction and project businesses, retail chains and professional services. It is weakest where a mature vertical product already covers 90% of requirements out of the box. A fuller breakdown by company size and industry is in Business Central use cases.

What it covers, and why each area matters

The modules below are usually listed as features. They are more useful framed as the business question each one answers.

How an implementation runs

A typical project for a mid-sized company takes 8 to 20 weeks. The variation comes from four factors, in descending order of impact: the state of your data, the number of areas covered, the volume of customisation, and the number of integrations.

1. Process discovery. How the business actually runs, not how the manual says it does.
2. Solution design. Which requirements the standard covers and which need extending — decided before configuration, not during.
3. Configuration. Chart of accounts, posting groups, dimensions, number series, permissions.
4. Data migration. Balances, master records and open documents. The longest stage, and the one that can start in parallel with system selection.
5. Testing. Real scenarios on real data, run by the people who will use the system.
6. Training and go-live. Ideally at the start of an accounting period.
7. Stabilisation. The first weeks after launch generate the most questions.

The step companies underestimate is the fourth. Duplicate counterparties and inconsistent item codes turn into billable hours, which is why the data preparation checklist is worth reading before a project starts rather than during it.

Migration from an existing system

Most projects are replacements rather than first systems. What transfers is balances, master records, open documents and one or two years of history — not a decade of archive, which belongs in read-only access to the old system.

Two situations are common enough to have their own material: moving off 1C, and replacing an older ERP that no longer receives updates. The mechanics of extraction, mapping and cutover are covered in data migration without downtime.

Customisation and integration

Extensions written in AL sit alongside the system rather than modifying it, which is why the two Microsoft update waves each year do not become a project. That removes the upgrade trap of older on-premises ERPs — but it does not make customisation free, and the recurring verification cost is the line most budgets miss. The decision framework is in when AL customisation pays.

Integrations follow the same logic: check AppSource before commissioning development. Bank connections, e-commerce platforms, EDI and courier services frequently have published connectors carrying somebody else's maintenance burden rather than yours.

Licensing in short

Two full-user plans and two supporting licence types. Essentials covers finance, sales, purchasing, inventory, projects and warehouse. Premium adds manufacturing and service management. Team Member suits people who read data and approve documents; Device covers a shared terminal used by several people in turn.

One constraint shapes the arithmetic: Essentials and Premium full users cannot be mixed in the same environment, so the choice applies company-wide. Current per-user figures and how to get the mix right are in Business Central pricing per user; the separate question of what an implementation project costs is covered in implementation cost. To model your own numbers, use the cost calculator.

How NBCS works on Business Central projects

We focus on one platform rather than a catalogue of systems: implementation, AL extensions, integrations, Power BI reporting and post-go-live support. Licences are purchased directly from Microsoft or a distributor — our scope is the project, not reselling subscriptions.

A first conversation is a working session rather than a presentation: we walk your actual scenario, identify what the standard covers, where extensions are genuinely needed, what the migration involves and what drives the budget. If the honest answer is that an ERP is premature for your stage, that is what you will hear.