From NAV to Business Central Migration: What Businesses Should Expect
For years, Microsoft Dynamics NAV has been the workhorse ERP solution for thousands of businesses around the world. It is reliable, robust, and has become an integral part of many business operations. But as technology continues to advance into a cloud-first world, the days of the on-premises legacy server are numbered. Enter Microsoft Dynamics 365 Business Central. It is the successor to NAV, but Migrating from NAV to Business Central is more than that it is a complete overhaul of your business operations. If you are a NAV user considering making the jump to Business Central, you are likely asking yourself what it means to migrate from NAV to Business Central. Will it hurt? Will I lose all my customizations? How long will it take? What to Expect What can businesses expect when making the jump from NAV to Business Central? 1. It’s Not Just an “Upgrade”; It’s a Platform Shift The largest mental shift for you will be in understanding that this is not just installing Service Pack 2 on your existing server. This is a move from a strictly on-premises solution to a Cloud-first solution, a true SaaS (Software as a Service) model. What to expect: You will no longer be responsible for managing Windows updates, SQL backups, and server hardware. The Benefit: Your IT team is free from above tasks, and you’re always running the latest version. 2. The Code Change: C/AL to AL The “technical stuff”, a necessary evil that will impact your project timeline and/or budget. Also classic NAV uses a coding language called “C/AL.” Microsoft Business Central uses a new language called “AL,” which is “cloud-ready” and “modern.” What to Expect: If your NAV implementation is heavily customized (and most are), these customizations cannot be “copy and pasted.” They must be “re-written” or “ported” as “Extensions.” The Impact: Now is the time to clean up those customizations. Do you really need a customization written five years ago? Migration time is a good time to go “standard,” which makes future upgrades easier. 3. The “Extension” Model vs. Object Modification In previous versions of NAV, developers would often make modifications to the system’s core objects. This would cause problems if they tried to upgrade the system, as these modifications would interfere with new updates from Microsoft. What to Expect: Business Central utilizes an extension model. This means instead of modifying the code, customizations and add-ons sit on top of the system, stacked on like blocks. The Benefit: If Microsoft updates Business Central, the extensions will be preserved. This means you will no longer have to re-create customizations every time an update is rolled out. 4. Data Migration: The “Clean Slate” Opportunity Data migration is usually the biggest concern for a business. You have years of historical data. What to Expect: You may not actually need to migrate all that data. While Master Data like Customers, Vendors, and Items is a priority, as is Open Ledger Entries like unpaid invoices, migrating data for the last 10 years of historical data may be unnecessary and expensive. The Strategy: Most businesses will end up migrating open data and possibly the last two years of historical data. The older data can be kept in a “read-only” NAV instance for reporting. 5. A Shift in User Experience (UI/UX) The user interface for Business Central is quite dissimilar from the classic NAV interface. What to Expect: The interface is a browser interface that is very similar to Outlook or Office 365. It is a responsive interface, meaning it works well with tablets and smaller screens. The Adjustment: You will need to adjust your staff to the new interface. However, as it is a standard Microsoft interface, most users will find it quite intuitive after a short training period. 6. Integration is Native, Not an Afterthought With NAV systems, integration to Office 365 was sometimes required to be done through third parties or extensive configurations. With Business Central, integration is now native. What to Expect: Expect to be able to see your Business Central data within Outlook, be able to edit Excel data that is synced to Business Central in real-time and be able to use Power Automate to automate business processes. The Benefit: No more living in a silo. The sales team can be working in Outlook and be putting data into the ERP system without even realizing it. 7. The Timeline and Process The typical phases of a migration project are as follows: Analysis – Reviewing the existing NAV customizations and data. Code Upgrade – Converting the customizations to AL extensions. Data Migration – Migrating the data and open entries. Training – Educating users on the new interface. Go Live – Switch over. The project duration for a simple upgrade may be a few weeks, while a complex project with heavy customizations may take several months. The project is full of surprises, and data cleanliness is a problem that may need resolution. Conclusion: Embrace the Change Migrating from NAV to Business Central is not only a technical imperative; it is a business enabler. It offers accessibility (work from anywhere), scalability, as well as access to new technologies like Artificial Intelligence and Power BI. The secret to success is to work with the right experts and see this as an opportunity to improve your business processes, rather than simply moving your old system into the cloud. Are you ready to future-proof your business? The cloud is waiting.
