Many companies are still working with Microsoft Dynamics NAV – sometimes in highly customised versions. But the pressure is growing: rising maintenance costs, lack of cloud capability, no access to new Microsoft technologies such as Copilot or the Power Platform. The future is called Business Central Cloud – and switching is usually not a question of “if”, but “when”.
This article explains how to make the switch from NAV to the Business Central Cloud, what challenges need to be overcome and why the move is worthwhile right now.
1. Why switch to the cloud at all?
The move from NAV to the cloud brings far-reaching benefits – and not just technical ones:
- No need for your own server – Microsoft takes care of maintenance, updates and security
- Automatic upgrades – no more expensive release changes
- Access from anywhere – whether home office, field service or international location
- Integration with Microsoft 365 & Power Platform – workflows, reports and automation made easy
- Future-proof – full support for AI features such as Copilot
For many companies, the change is therefore not just an update – but a genuine modernisation of the entire ERP ecosystem.
2. How does the upgrade from NAV to BC Cloud work?
A cloud upgrade is not a classic “technology update” – but a migration project with several stages. The most important phases at a glance:
a) Systemanalyse & Vorstudie
- Which NAV version is in use?
- What customisations and add-ons are available?
- Which processes can be streamlined or simplified?
b) Technical preparation
- Data cleansing, consolidation of master data
- Checking the compatibility of existing extensions (C/AL → AL)
- Selection of alternatives in AppSource or Power Platform
c) Define migration strategy
- Re-implementation or technical migration?
- Which data is transferred (only master data or also bookings)?
- Which user roles and authorisations are required?
d) Cloud-Setup & Migration
- Setting up the Business Central Cloud environment
- Data migration and function test
- User training
e) Go-Live and hypercare
- Going live with close support
- Support for end users, troubleshooting
- Expansion of further cloud functions (e.g. Power BI, automation)
3. What happens to old customisations?
NAV was often heavily customised. In the cloud world, this principle is outdated. Customisations are developed as extensions in AL – or replaced by low-code apps.
Recommended procedure:
- Check whether an AppSource solution already covers the function
- Standardisation before individualisation
- Where necessary: Extension with AL or Power Platform
Advantage: In future, all extensions will run updateable and without deep intervention in the system.
4. cloud migration is also a cultural change
The technical changeover is only part of the journey. Those who successfully migrate to BC Cloud should also rethink internal processes and mindsets:
- From classic “release thinking” to continuous improvements
- From Inhouse-IT to Managed Services
- From individual tools to integrated platform solutions
This transformation opens up new possibilities – from mobile applications to AI-supported analyses.
5. Conclusion: Act now – don’t hesitate
Migrating from NAV to the Business Central Cloud requires planning – but it is the key to future-proofing. Those who prepare today will benefit from greater efficiency, lower IT costs and full Microsoft integration tomorrow.
A strong partner, a clear migration strategy and the will to change – these are the three key success factors.
