The real question is not uptime. It is decision confidence.
Old Dynamics NAV is still helping the business only if leaders can trust the information it gives them quickly enough to act. If finance, stock, margin or operational reports need exports, spreadsheet checks or personal confirmation before decisions are made, NAV may still be running — but it is no longer giving the business the visibility it needs.
That distinction matters.
Many NAV environments are stable in the narrow technical sense. Orders can still be processed. Invoices still go out. Stock movements still post. Month-end still happens. From the outside, the system looks serviceable.
The strain appears in leadership moments: a board pack takes longer than expected, a stock figure needs validating before purchasing can act, sales and finance disagree on margin, or operations need someone who “knows the workaround” before a number can be trusted.
That is where an old ERP system starts to cost more than it appears to.
How do you know when NAV is no longer giving enough visibility?
A NAV system usually starts to fail the visibility test before it fails technically. The warning signs are practical:
- Finance teams export data to Excel before leaders trust the figures.
- Inventory reports are checked against warehouse knowledge or offline lists.
- Month-end depends on manual reconciliations that only a few people understand.
- Managers ask for “the real number” outside the system.
- Reporting takes longer because data sits across NAV, spreadsheets, add-ons or disconnected tools.
None of these problems proves that a NAV to Business Central migration is automatically the right next step. They do prove that the current setup deserves a business review, not just a technical support conversation.
The first test is simple: Can leaders make confident decisions from NAV without offline evidence?
If the answer is no, the business is not only dealing with an ageing ERP platform. It is dealing with weaker decision quality, slower response and more hidden effort than leadership may realise.
The NAV Usefulness Test
Before discussing scope, licences or migration routes, use this diagnostic:
| Test area | Question leaders should ask |
| Trust | Do teams believe the numbers in NAV without checking them elsewhere? |
| Timeliness | Are reports available when decisions need to be made? |
| Effort | How much manual work is needed to turn NAV data into usable insight? |
| Fit | Do current processes reflect how the business now operates? |
| Readiness | Would moving to cloud Business Central reduce risk, friction or delay? |
This is the more useful starting point. The issue is not whether old NAV has been loyal. It is whether it still supports control, visibility and confident management.
Familiar routines can hide the real cost of staying as you are
A familiar NAV process is not always an efficient process. It may simply be a process the business has learned to protect with manual checks, spreadsheet fixes and experienced people who know where the weak spots are.
That is where old NAV can become difficult to judge. Teams rarely describe these routines as risk. They call them “the way we do it”. A finance user exports data before sharing a report. A warehouse manager checks stock outside the system. A purchase approval depends on a person remembering the next step. A month-end adjustment is understood by one long-serving employee.
The system still runs. The business absorbs the extra effort.
Over time, that absorbed effort becomes part of the cost base. It slows decisions, weakens ownership and makes change feel harder than it needs to be.
Where NAV workarounds become business risk
| Weak input in NAV or around NAV | Business risk it creates |
| Spreadsheet reconciliations before reporting | Leaders wait longer for trusted figures |
| Manual stock adjustments | Inventory confidence weakens across sales, purchasing and operations |
| Person-dependent approvals | Decisions slow down when key people are unavailable |
| Duplicate data entry between systems | Errors rise and teams lose time checking records |
| Old customisations nobody wants to touch | Support becomes harder and change becomes slower |
| Add-ons with unclear ownership | Reporting, upgrades and integrations become more fragile |
| Month-end fixes outside the system | Finance visibility depends on manual memory, not process discipline |
These issues are not always dramatic. That is why they last.
The commercial damage appears in smaller, repeated moments: a customer answer takes longer, a purchasing decision is delayed, a stock promise needs checking, a management report needs rework, or a new starter takes months to understand the exceptions.
For a CEO, this affects control and growth. For a CFO, it affects reporting confidence and close quality. For a CIO or IT leader, it creates a support burden around customisations, integrations and knowledge trapped in people’s heads.
A Business Central migration should not recreate every old habit
A NAV to Business Central migration is a useful moment to ask which routines still deserve to exist. Some processes should move across because they work well. Others should be simplified, redesigned or removed.
This is where many businesses make the wrong decision. They assume the safest route is to copy old NAV as closely as possible. That can feel lower risk at the start, but it may carry forward the same reporting delays, manual checks and custom logic that caused the problem.
The better question is: which parts of NAV represent proven business fit, and which parts represent historical compromise?
Dynamics 365 Business Central can provide a cleaner cloud platform for finance, stock, reporting and core operational control, but the value depends on the decisions made before migration. Scope, data quality, process design, integrations, training and ownership all matter.
Moving systems without challenging the hidden workarounds may only relocate the friction. A practical review should expose that friction early, before the business decides what to keep, what to redesign and what to leave behind.
The right questions separate business fit from technical nostalgia
The decision is not whether people are used to NAV. The decision is whether NAV still fits the way the business needs to operate.
That shift changes the quality of the conversation. Instead of asking, “Can we keep this running?”, leaders can ask, “What is the current system helping us do well, and where is it slowing control, reporting or growth?”
A good NAV to Business Central review should start before anyone debates migration scope. It should test the business model the ERP is supporting.
How do you know when NAV no longer fits the business?
NAV may no longer fit the business when everyday work depends on avoidable manual effort, fragile customisations, disconnected reporting or knowledge held by a small number of users. The system may still process transactions, but the operating model around it has become too dependent on checks, fixes and exceptions.
Useful review questions include:
- Which reports do leaders trust immediately, and which need checking first?
- Which NAV customisations still create value, and which simply preserve old habits?
- Which integrations are reliable, and which create support risk?
- Where do users rekey data between NAV, Excel, CRM, warehouse tools or finance systems?
- Which processes have changed since NAV was first implemented?
- Which data is accurate enough to migrate, and which needs cleansing or archiving?
- Which teams have the ownership and time to support change properly?
These questions make the review commercial, not sentimental. They help leaders separate what should be protected from what should be challenged.
Should you upgrade NAV or take a clean start in Business Central?
There is no universal answer. The safer route depends on process fit, data quality, reporting needs, customisations and appetite for change.
| Option | When it may suit | Main caution |
| Keep NAV short term | NAV still supports reliable reporting and core processes | Delay can increase support risk and hidden manual cost |
| Upgrade from NAV to Business Central | Processes are broadly sound and historical continuity matters | Old complexity may be carried into the new system |
| Clean start in Business Central | Current processes, data or customisations need redesign | Requires more upfront business involvement and decision discipline |
The cleanest technical route is not always the best business route. Recreating every old report, field, approval and add-on can make the migration feel familiar, but it may also preserve the reasons leaders wanted change in the first place.
A Business Central migration should protect what works and question what no longer earns its place. That means looking carefully at finance processes, inventory visibility, data structure, reporting, integrations, user training and supportability before deciding the route.
The strongest review does not begin with “How do we move everything?” It begins with “What does the business need to trust, control and improve?”
Migration readiness turns delay into a controlled decision
A NAV to Business Central migration should not start with speed. It should start with readiness. The point is to decide whether modernising now reduces more risk, cost and friction than staying as you are for another year.
That decision needs more than a licence comparison. Leaders need to understand the condition of the current system, the quality of the data, the maturity of key processes and the level of internal ownership available to support change.
What should a NAV to Business Central readiness review include?
A useful readiness review should test seven areas:
| Readiness area | What to check |
| Business case | Which problems are worth solving now: reporting delays, manual effort, stock visibility, finance control or support risk? |
| Data condition | Which master data, balances, open items and history are clean enough to move? |
| Process maturity | Which workflows should be kept, simplified or redesigned? |
| Customisations | Which old NAV changes still add value, and which create unnecessary complexity? |
| Integrations | Which connected systems are business-critical, fragile or poorly documented? |
| User readiness | Which teams need training, process clarity and super-user ownership? |
| Delivery route | Is the safer path an upgrade, a clean start or a phased improvement plan? |
This review gives leaders a better conversation than “when should we migrate?” It reframes the issue as: what level of change is justified, and what must be true before the business commits?
Are you ready to scope, or do you need a review first?
A simple maturity view can help.
- Not ready: reporting is disputed, data ownership is unclear, customisations are poorly understood and users have little capacity for change.
- Review needed: NAV still runs, but leaders rely on manual checks, integrations need assessment and the business is unsure whether to upgrade or redesign.
- Ready to scope: key pain points are agreed, data risks are known, process owners are available and the business has a clear reason to move to cloud Business Central.
Most businesses sit in the middle. That is not a problem. It simply means the next sensible step is diagnosis, not commitment.
FAQs
Is old NAV still worth keeping?
Yes, if it still supports reliable reporting, stable processes and manageable support. If it depends on workarounds, manual checks and ageing customisations, it needs review.
Should we migrate all NAV history?
Not always. Many businesses are better served by moving essential records and keeping older history accessible elsewhere.
Is a clean start better than an upgrade?
A clean start can be better when old processes and data need redesign. An upgrade may suit businesses with cleaner data and processes that still fit.
What is the next step?
Start with a NAV to Business Central readiness review covering reporting trust, process fit, data condition, integrations, customisations and user readiness.
GO ERP can support that review through a practical discovery or scoping workshop, helping you decide whether to optimise NAV short term, plan a focused migration or move towards Business Central with a cleaner operating model.
