microsoft dynamics nav vs business central

Many fashion and retail businesses across Denmark, Norway, Germany, Switzerland, and the Netherlands are still running on Microsoft Dynamics NAV. It has been a reliable platform for years — but the industry has changed, and so has the technology. Microsoft Dynamics 365 Business Central is the modern successor to NAV, and for fashion brands evaluating their next ERP move, understanding the difference matters.

This article explains what changed between NAV and Business Central, what it means specifically for fashion and retail operations, and what to consider if your business is thinking about making the move.

Microsoft Dynamics NAV — known in earlier versions as Navision — was an on-premise ERP system. It was installed locally, customised heavily per business, and updated infrequently. For many fashion companies, it became the backbone of their operations, extended over time with custom code to handle variant management, seasonal buying, and product data.

Microsoft Dynamics 365 Business Central is the cloud-native successor. It runs on Microsoft Azure, receives continuous updates from Microsoft, and is built around an extension model rather than direct code modification. Customisations are built as extensions that sit on top of the core platform — meaning they survive updates without breaking, and the core system stays current.

For fashion brands, this distinction is significant. The heavy customisations many NAV implementations carry — often built to handle colour, size, and variant complexity — need to be evaluated carefully in any migration. The question is not just whether the functionality can be replicated, but whether a modern, fashion-specific extension built on Business Central can replace it more cleanly.

The honest answer is that migrating from NAV to Business Central involves trade-offs. NAV implementations built up over many years often contain a significant amount of business logic embedded in custom code — logic that reflects how the business actually operates. That logic does not automatically transfer.

What fashion brands typically lose in a NAV migration is the accumulated customisation — the workarounds and modifications built over years to handle variant complexity, seasonal buying, and product data. These need to be reviewed, rebuilt as extensions, or replaced with standard functionality from a fashion-specific solution.

What they gain is a platform that no longer requires those workarounds. A modern fashion extension built on Business Central — one that natively handles style-colour-size matrices, collection management, delivery periods, and supplier collaboration — replaces years of custom NAV code with maintained, certified functionality that updates automatically.

A NAV-to-Business-Central migration for a fashion brand typically involves several workstreams running in parallel. Data from NAV — customers, vendors, items, open orders, inventory — needs to be mapped and migrated to the Business Central data model. Item and variant structures built in NAV need to be reviewed and mapped to the fashion-specific data model of whichever Business Central extension is being implemented.

Integrations — to e-commerce platforms, warehouse systems, POS, or external reporting tools — need to be rebuilt using Business Central's modern API layer. And users need to be trained on a new interface and new workflows, even when the underlying business logic is familiar.

The complexity of the migration depends heavily on how customised the NAV implementation is, and how cleanly the business's processes can be mapped to standard Business Central functionality extended with a fashion-specific solution.

Microsoft has been clear that NAV is in maintenance mode. While existing NAV installations continue to receive support, the platform is not receiving new feature development. The direction of Microsoft's investment is Business Central — and the ecosystem of certified extensions, integrations, and partners is growing around it.

For fashion brands, the question is not really whether to move, but when and how. Companies that move proactively — on their own timeline, with a clear plan — are in a better position than those who move reactively when NAV support becomes a constraint or a security concern.

The brands that get the most from a Business Central migration are those who use it as an opportunity to review and improve their processes — not just to replicate what NAV did, but to replace workarounds with native functionality and build on a platform that will keep pace with how their business and their industry evolve.