Share via


Upgrade Microsoft Dynamics NAV

Purpose of this article is to provide an overview of the Upgrade process, the approach to progress an existing Microsoft Dynamics NAV solution to a subsequent release of that solution.

The Upgrade process describes the approach to progress an existing Microsoft Dynamics NAV solution to a subsequent release of that solution. This approach starts with a Technical Upgrade to address moving existing functionality to the subsequent release. The Functional Upgrade approach builds on the Technical Upgrade – in the first release of the solution, existing functionality is addressed using Technical Upgrade, and in the second release, new functionality is added.

Technical Upgrade from one to another version is possible and prefereble. Microsoft provide Upgrade Toolkit for all versions. But, make Functional Upgrade is not always so easy. It depends of number and complexity of customizations. Sometimes customization is easy for migration, but sometimes it is a very complex job. Specialy proble is when we get new clients, when many objects (usually we think on customize objects) became unusable.

The recommended upgrade approach, including a roadmap and alternatives, is as follows:

  • Technical Upgrade: This approach is used to progress existing solution functionality to the latest product release.  It is especially applicable when the existing solution includes minimum customizations and the solution is close to an “out-of-the-box” installation.
  • Functional Upgrade: This approach starts with a Technical Upgrade to address moving existing functionality to the subsequent release.  Any new functionality desired can then be deployed using the one of Sure Step project management types. The approach is especially relevant when a significant number of customizations have been made to the standard Microsoft Dynamics installation, necessitating a more complex upgrade process.

There are formal description of upgrade:

[[Microsoft Dynamics NAV Overview|Return to Dynamics NAV Overview]]