It has been quite a while that Microsoft had introduced Dynamics 365 Business Central as its compact ERP and CRM solution as a replacement to Dynamics NAV. However, it must be remembered that it is not and upside down change to the solution, but an advancement. For those who are still skeptical about shifting to upgrade NAV 2017 to Business Central, we can assure that is it the right move towards improvising and boosting their business processes. In this article we will discuss how you can start and eventually shift from Dynamics NAV 365 to Business Central.

The first thing to wonder about, when you consider moving to Dynamics 365 Business Central is how to move the old NAV solutions and customizations to Business Central. The transition is not just about the transition of codes. The transition is from the monolithic C/AL based solution to an extension-based solution which is not a quick and easy task.

How to start the transition process from old C/AL based solution to the Extension world?

The most important aspect of the transition is to build the right architecture for the solution when you upgrade NAV 2017 to Business Central. Thus, you must figure out what you want to achieve. The following are the available architectures:

1. Monolithic Extension:

This architecture has all your solutions packed on a single Extension. This type of extension allows you to create new and standard objects while it is independent of other modules. This is the simplest architecture and is suitable for small projects only.

2. N Separated Extension:

Another available architecture when it comes to upgrading Dynamics NAV 365 to Business Central is N Separated extension. In this architecture every extension assumes a separate roll and takes over a specific functionality. It does so by creating new objects and extending the standard objects. However, unlike Monolithic Extension it may have dependencies.

This is a modular solution and you can decide on your will which module you wish to activate for your customer. Make sure you take care of the dependency problem between the different extensions.

3. Base Layer+ N Extension dependent on the Base Layer:

In this architecture concerning upgrade NAV 2017 to Dynamics Business Central, the base layer extension consists of new object and extends standard objects while it covers all the underlying aspects of the solution. You have in another hand, the N Separated extension that covers the specific functionalities given to them. This architecture has dependency only on the base layer.


There is no right answer to the question: “which architecture is best?” when upgrading from Dynamics NAV 365 to Business Central, you have to realize the type of operations, whether simple or complex, your company has to tackle. Thus, you have to select the right architecture for you specifically. You can also take help from an implementation partner to help you with more insights.