Upgrade vs. Re-implementation: How to Update Your ERP Solution
- Tarana Rana
- Apr 13
- 8 min read
Should you upgrade or re-implement when moving from Dynamics NAV to Business Central? Learn how to evaluate cost, value, customizations, and ERP erosion.
If your organization is still using an older version of Dynamics NAV, an update to Dynamics 365 Business Central is likely in your future. While Microsoft has continued to evolve Business Central into a modern, cloud-based ERP designed for today’s businesses, many organizations still face a key question when planning their transition: is it better to upgrade or re-implement your ERP solution?
The short answer is that it depends on several factors: technical, operational, and strategic.
In this blog post, Jens Baun, Director of Sales of Kwixand Solutions, offers insight into the differences between upgrading and re-implementing Dynamics NAV into Business Central, along with guidance on how to evaluate which option is the best fit for your organization today and in the long term.
We'll Cover:
Defining an Upgrade vs. Re-implementation
Before choosing a path forward, it’s important to understand what each approach involves.
Typically, most mid-market cloud ERP solutions support some form of automated upgrade path.
An upgrade focuses primarily on moving your existing system to a newer version of the software while preserving your current data, configurations, and processes. When you perform an upgrade, the system migrates your existing data from the old version to the newer one. If there are changes in the database structure or underlying architecture between the two versions, tools or scripts are used to bridge those differences.
“Essentially, with this version upgrade, the end user can continue using the updated software in the same way they used their previous system,” explains Baun. “The idea with an upgrade is that the newer version will have additional functionality and capabilities that may deliver incremental value to the business—without significantly changing how people work day to day.”
Upgrades are often perceived as the least disruptive option and can be appealing when the current system still largely meets business needs.
A re-implementation, on the other hand, takes a very different approach. Rather than carrying the current system forward, a re-implementation involves deploying Dynamics 365 Business Central as a new solution, then configuring it based on your current business processes, not the ones you had when the system was originally implemented.
This approach looks beyond replicating your existing setup. It re-evaluates how your business operates today, what the system needs to support now, and how Business Central’s standard functionality, extensions, and integrations can be used to deliver better outcomes.
“A re-implementation isn’t just about installing new software,” says Baun. “It’s about aligning technology with how the business actually runs today—and how it wants to run tomorrow.”
How to Decide Between an Upgrade vs. Re-implementation
So how do you know which approach makes the most sense? There’s no universal answer, but there are common indicators that can help guide the decision.
🔷 What is the Age of Your ERP Solution?
One of the most common, and most overlooked, factors is the age of your existing ERP solution and how consistently it has been maintained.
Many organizations running Dynamics NAV today are several versions behind. In some cases, the system may have been implemented a decade or more ago, with minimal upgrades along the way.
If you haven’t been keeping up with version upgrades, you may find that your solution is significantly outdated. In these situations, a simple upgrade can become complex and costly.
Baun explains why. “If your business is on NAV and has skipped multiple version upgrades over the years, a re-implementation may actually deliver more financial value. Upgrading across several major releases often requires stepping through intermediate versions, each of which involves effort, testing, and cost.”
By contrast, a re-implementation allows organizations to bypass years of accumulated technical debt and move directly to a modern Business Central environment built on current architecture and best practices. In short, the older and more static your system is, the more likely a re-implementation becomes the smarter choice.
🔷 What is the Value vs. Cost?
Cost is often the first concern organizations raise but cost alone shouldn’t drive the decision.
According to David, organizations also need to closely examine value.
One of the immediate benefits of upgrading is access to vendor and partner support. Most ERP vendors and partners support only the current version of their software and a limited number of previous releases. Staying current ensures security updates, performance improvements, and compatibility with future enhancements.
However, while newer versions of Business Central offer significantly expanded capabilities, an upgrade doesn’t always guarantee that businesses will benefit from them.
“One of the challenges with upgrades is that legacy configurations and historical decisions can limit access to newer functionality,” Baun explains. “You may technically be on a newer version, but not fully able to take advantage of what the platform offers.”
In contrast, a re-implementation begins with a discovery and analysis phase. This phase examines how the business operates today, what the current system doesn’t support well, and where workarounds have been introduced over time. Common questions explored during this phase include:
Have your business processes changed?
Are teams relying on spreadsheets outside the ERP?
Are manual steps compensating for system limitations?
Are reporting and visibility meeting current needs?
“All of those factors get surfaced during a re-implementation,” says Baun. “Then Business Central can be configured to support current processes while also leveraging capabilities that weren’t available or weren’t used in the past.”
While re-implementations typically require more upfront effort than upgrades, they often deliver greater long-term value by eliminating inefficiencies, reducing manual tasks, and supporting future growth.
🔷 Have You Considered ERP Erosion?
Over time, even well-implemented ERP systems can experience what’s often referred to as ERP erosion.
ERP erosion occurs when the system no longer reflects how the business operates. Processes evolve, staffing models change, new regulatory requirements emerge, and reporting expectations increase but the system stays the same.
Organizations compensate by adding manual steps, exporting data to spreadsheets, or building workarounds outside the ERP.
A re-implementation directly addresses ERP erosion by redesigning the system around how the business works today. Rather than preserving outdated assumptions, it allows organizations to simplify processes, standardize workflows, and make better use of built-in automation.
For businesses that feel their ERP no longer supports them effectively, a re-implementation can act as a reset, realigning technology with operational reality.
🔷 Does Your Solution Rely on Customizations?
Customizations are another critical factor, especially for organizations that have been using Dynamics NAV for many years.
It’s common for long-running NAV systems to include a large number of customizations built to address gaps that existed at the time. Over the years, however, Business Central has incorporated many of those capabilities into standard functionality.
This often leads organizations to overestimate the effort required to move forward. “Typically, we find that around 30% of customizations were written years ago and simply aren’t required anymore,” Baun explains. “Business Central now includes many of those features out of the box—or supports them through extensions.”
A re-implementation creates an opportunity to re-evaluate each customization:
Is it still used?
Does it still support a valid business requirement?
Is there now a standard or extension-based alternative?
In many cases, eliminating unnecessary customizations reduces complexity, lowers ongoing maintenance costs, and improves upgradeability in the future. While upgrades can retain customizations more easily, they may also perpetuate technical limitations that restrict future improvements.
📍 Read More: Should You Upgrade from NAV to Business Central?
Key Takeaways
If you're debating between a version upgrade or a re-implementation for your Dynamics ERP, step back and assess the bigger picture. Ask yourself:
How old is your ERP solution?
How many customizations does your system rely on?
How closely does your current setup reflect how your business actually operates?
What value will each approach deliver, not just today, but over the next several years?
Baun emphasizes the importance of that final question.
“You need to measure cost against value, not just implementation cost, but operational value over time,” he explains. “One of the best ways to start is by having open, honest conversations with your ERP partner. What does an upgrade really give you? What does a re-implementation enable?”
The right partner should help you quantify that value, identify trade-offs, and align the decision with your business goals, not push a one-size-fits-all answer.
At the end of the day, organizations should feel confident that their ERP strategy supports their growth, efficiency, and ability to adapt. And if those conversations aren’t happening, or don’t feel transparent, it may be time to look for a new partner.
FAQ: Upgrade vs. Re-implementation for Dynamics NAV to Business Central
Should I upgrade or re-implement Dynamics NAV when moving to Business Central?
There is no one-size-fits-all answer. The right choice depends on factors such as the age of your Dynamics NAV system, how many versions behind it is, the number and complexity of customizations, and how closely your current system reflects how your business operates today.
If your NAV system has been kept relatively current and still supports most of your business processes, an upgrade may be sufficient. However, if the system is several versions behind or relies heavily on workarounds and outdated customizations, a re-implementation often delivers greater long-term value by aligning Business Central with current operational needs rather than past decisions.
When does a Business Central re-implementation make more sense than an upgrade?
A re-implementation is often the better option when an ERP system no longer reflects how the business actually operates. This commonly happens when companies have skipped multiple NAV upgrades, accumulated technical debt, or introduced external tools and spreadsheets to compensate for ERP gaps.
Re-implementation allows organizations to reassess business processes, eliminate inefficiencies, and configure Business Central around current workflows. It is also a practical way to address ERP erosion, where systems become less effective over time due to evolving business requirements.
Is upgrading from Dynamics NAV cheaper than re-implementing?
In the short term, upgrades are often less expensive and faster than re-implementations, particularly when moving from a recent NAV version. However, cost should not be evaluated in isolation.
While an upgrade may reduce upfront effort, it can limit access to newer Business Central functionality if legacy configurations are carried forward unchanged. Re-implementations typically require more initial planning, but they often reduce long-term costs by simplifying processes, removing unnecessary customizations, and improving system maintainability.
Ultimately, the better option is the one that delivers the most value over time—not just the lowest implementation cost.
What happens to customizations when moving from NAV to Business Central?
Customizations are one of the most important considerations when deciding between an upgrade and a re-implementation.
In many cases, organizations discover that a significant portion of their NAV customizations are no longer required because Business Central now includes similar functionality as standard features or through extensions. A re-implementation provides an opportunity to review each customization, determine whether it still adds value, and decide whether it should be rebuilt, replaced, or retired.
Upgrades may carry existing customizations forward, but this can also perpetuate complexity and limit flexibility in future system updates.
What is ERP erosion, and how does it affect the decision?
ERP erosion occurs when an ERP system no longer supports how a business operates due to changes in processes, growth, or external requirements. Over time, this often leads to manual workarounds, disconnected spreadsheets, and reduced visibility.
Re-implementation directly addresses ERP erosion by realigning Business Central with current business needs. Rather than preserving outdated assumptions, it allows organizations to simplify operations, increase automation, and take full advantage of modern ERP capabilities.
How do I determine the value of an upgrade vs a re-implementation?
The best way to evaluate value is by examining both operational impact and long-term outcomes. Organizations should assess how well their current system supports employees, reporting, and decision-making, as well as how easily it can adapt to future changes.
Engaging an experienced Dynamics 365 Business Central partner can help clarify this assessment. A trusted partner should be able to outline what each option enables, identify trade-offs, and help quantify the business value of upgrading versus re-implementing, based on your specific environment.
About Kwixand Solutions
Kwixand Solutions is a Microsoft Dynamics 365 Partner, specializing in Dynamics 365 Business Central. Our team of experts help businesses across Canada and USA digitally transform and get the most value out of their systems. Whether you're looking to adopt Business Central for the first time, migrate from GP or NAV to Business Central, or need help with your existing Business Central solution, we are here for you. Book your free consultation today.
