Architecting a Plan for Your Dynamics NAV Upgrade Isn’t Rocket Science – Or Is It? | Qixas Group
4 ways archiving and compression tools can make your Microsoft Dynamics NAV system more efficient
March 13, 2017
The Patriots Have Tom Brady. Microsoft Dynamics Has Floyd Chan!
May 9, 2017

Architecting a Plan for Your Dynamics NAV Upgrade Isn’t Rocket Science – Or Is It?

Architecting a Plan for Your Dynamics NAV Upgrade Isn’t Rocket Science – Or Is It?

Is it overstating the case to say that a Microsoft Dynamics NAV upgrade plan is rocket science?

To answer that question, take a step back to understand the meaning of architecture as it relates to any software system, including your Dynamics NAV solution. Much like the blueprint for a building, every software system has an underlying architecture designed to provide structural support for system reliability and performance. That architecture is defined by the operational requirements of your business processes.

Your original decision to choose Dynamics NAV software for your business was based on a set of requirements that NAV could best fulfill. Similarly, the software systems that NASA chose to control the space shuttle launch were based on the requirement of being very fast and very reliable. There was no room for error or poor performance.

The plan for your NAV software upgrade will also require an architecture to ensure continued reliability and performance standards. So yes, it’s akin to rocket science!

But don’t let that scare you, because the Qixas Group team has that architecture down pat. We are upgrade specialists and we have the tools to make your upgrade run smoothly and painlessly. Before embarking on your upgrade, we will first determine the best avenue to pursue. That will largely depend on which version of Dynamics NAV you’re currently running and whether your enhancement is up to date.

Let’s assume that your goal in upgrading to the most current version of Microsoft Dynamics NAV is to take advantage of NAV’s new features, functionality and technology, of which there are many. IF you are only transitioning from one version to the next latest version, the upgrade path is relatively simple. However, this would be a good time to consider new options. For example, what would be the benefits of moving from on-premise NAV to NAV in the cloud? Or, would Microsoft Dynamics 365 be an even better move? Qixas will help you sort this out.

However, IF you’re several versions behind, the upgrade path is considerably more complex. It’s entirely conceivable that a fresh start will be more cost effective. Let Qixas crunch the numbers for you so that you can make an informed decision.

Whether the best path for you is an upgrade or a fresh start, the size of your databases, which have undoubtedly grown exponentially over the years, will be a key factor in the time required to move to the newest version of NAV and system performance. That’s why we often recommend using our Dynamics NAV Archiving and Compression Tools in order to retain the detailed data you need to move your company forward and boost performance at the same time.

The benefits of archiving and compression are considerable. Perhaps best of all is the ability to perform an upgrade over the course of a mere weekend, which means minimizing any disruption to your business. Faced with so many options and critical decisions to be made, you’ll want to engage the rocket scientists at Qixas who have the expertise to guide you every step of the way.

To discuss a best-practices upgrade plan and architecture for your Microsoft Dynamics NAV system, call us toll free at 888-467-7101. You can also email us at and visit us at

We would love to hear from you!


  1. […] Articles Architecting a Plan for Your Dynamics NAV Upgrade Isn’t Rocket Science – Or Is It? What Are the Steps for Moving from Where Your Dynamics NAV System Is Now to Where You Want It to […]

  2. […] Related Article: Architecting a Plan for Your Dynamics NAV Upgrade Isn’t Rocket Science – Or Is It? […]

Leave a Reply

Your email address will not be published. Required fields are marked *