Dynamics NAV: The Roots of Business Central

Microsoft Dynamics NAV was one of the most popular ERP solutions worldwide. In 2018, it was rebranded as Dynamics 365 Business Central, a name that persists to this day. Even though the ERP system is no longer referred to by that name, “Dynamics NAV” is still very familiar.

Microsoft Dynamics NAV is or was one of the most popular ERP solutions worldwide. Why “was”? After the system initially became known as Navision, Microsoft renamed it Microsoft Dynamics NAV. However, it was then renamed again in 2018 and became known on the market as Dynamics 365 Business Central, which it still is today. Over time, Microsoft has optimized its ERP software and expanded its range. Even if the ERP system is no longer called that today, the name “Dynamics NAV” is still very familiar.

Even though the ERP solution Microsoft Dynamics NAV has been succeeded by Microsoft Dynamics 365 Business Central, we continue to support our customers in older versions.

With the help of the ERP solution Microsoft Dynamics NAV (since 2018 Microsoft Dynamics 365 Business Central), small and medium-sized companies can manage, automate and optimize their business processes.

The costs for Dynamics NAV (since 2018 Dynamics 365 Business Central) depend on the following criteria:

• Deployment method (Cloud, On-Premises)
• Licensing (Essentials, Premium, Team Members)
• Number of users

You can find an overview on our Prices page.

Microsoft Dynamics NAV is the successor to the ERP solution Navision. After the system was initially known as Navision, Microsoft renamed it Microsoft Dynamics NAV. However, it was then renamed again in 2018 and became known on the market as Dynamics 365 Business Central, which it still is today.

The name changes go hand in hand with Microsoft’s optimizations and expansion of the offering.

Microsoft Dynamics NAV is the successor to the ERP solution Navision. After initially being known as Navision, the system was renamed Dynamics NAV by Microsoft. However, it was then renamed again in 2018 and became known on the market as Dynamics 365 Business Central, which it still is today. The name changes go hand in hand with Microsoft’s optimizations and expansion of the offering.

In addition, licensing has changed from concurrent to named users. The programming language has changed from C/AL to AL.

Certainly. You can find all the information on our page about Partner Switch.

There are different methods for upgrading from Dynamics NAV to Dynamics 365 Business Central. Generally, there’s the waterfall model or an agile approach. We’ve developed our own agile methodology: Firstly, we conduct the rough planning within 3-4 days (all necessary functionalities, project kickoff, framework conditions).

Then, we proceed with the implementation in 4-week iterative phases or sprints. In each phase, we plan the sprint, conceptualize the tasks and budget, and execute them. At the end of each phase, the client must test the implementations and assess the quality. Then, the next implementation phase starts. Any unfinished tasks are carried over to the next implementation phase. This process repeats in each of the implementation phases.

Finally, the implementations are compiled. Then, we train your team and allow them to thoroughly test the system before going live.

You can find all the information about upgrading from Dynamics NAV to Dynamics 365 Business Central on our Upgrade Page.

The method and duration of setting up Dynamics NAV (since 2018 Dynamics 365 Business Central) vary from company to company. Various factors come into play here, such as deployment options, size, and the proportion of individual requirements.

The provisioning of the online solution takes only a few minutes. The duration of setting up your on-premises solution is longer solely due to the setup of the on-premises (local) components, as the necessary server systems (database, application, etc.) need to be provisioned. In addition, the following points are relevant:

• Potential support during system implementation (highly individual)
• Potential setup of the Microsoft 365 (formerly Office 365) environment: creating new user accounts or transferring/synchronizing local Active Directory accounts for easier management (highly individual)
• Potential migration of extensions (highly individual)