Navision Depot Logo

Microsoft Navision Implementation

Achieving a successful Microsoft Navision implementation is not easy, but then successful ERP system implementations never are, regardless of what system you may use. However, there are well-established implementation methodologies that are generally considered implementation 'best practices'. These implementation methodologies come in several different flavors, but they all have the same common elements:

Product Selection

Obviously the first step is to pick the system that is right for you. Here we're going to assume you've already done this, and selected Microsoft Dynamics Nav.

more info -- Is Navision right for You?


Variously called Requirements Analysis, or Gap-Fit Analysis, or Business Process Automation Analysis, this is the first key phase of any Microsoft Navision implementation. The Analysis phase is basically about figuring out what your business processes will be, and how these processes will be mapped to Navision, with a particular emphasis on any modifications that will need to be made to either Nav or your processes in order to make them compatible.

SetUp and Configuration

This phase involves installing the Navision software, performing the setup and configuration, importing or entering master data, and developing and testing any required customizations or modifications to the software. Any gaps identified during the analysis phase that require custom modifications should be filled in this phase by appropriate custom development or process change.

Proof of Concept

After the setup and configuration phase is completed, but before user training takes place, the key people who were involved in the analysis and setup/configuration phases should step through all of the standard business processes in a test environment, to make sure that the setup and configuration phase is really complete, that all modifications are working as intended, and that the finished configuration really meets all of the business requirements and maps to the business processes.


User training on Navision is imperative to the success of the system once it's been deployed; the best implementation will fail if the users don't understand how to use Navision to do their jobs. There are multiple types of training available, including classroom, web-based, CD/DVD self-paced, books, one-on-one, and more -- any or all methods will work, so long as the material is correct and relevant for your organization.

more about Navision Training

System Testing

Once the proof of concept is validated and the users are trained, the system should be thoroughly tested by the users, including having the users perform samples of real transactions from their day to day jobs using Navision. This phase serves to both finalize the system configuration, and ensure the users know how to use Nav to do their jobs. You can think of this as a 'dry run' of your Microsoft Navision implementation.


Usually done on a tight and compressed timeline, over a weekend or over one night, this is the transitional moment that live, up to the minute transactional data is transferred from your previous system to Navision, the 'cut-over' is made, and everyone stops using your old system and begins using Dynamics Nav instead.

join our mailing list
* indicates required
We respect your privacy.

Navision Depot © All Rights Reserved