When should you move from Dynamics NAV to Business Central?
The usual answer looks at the technology: support deadlines, version levels, compatibility. That is not wrong, but it is rarely the point at which a NAV system becomes genuinely risky. NAV runs. It has often been running remarkably stably for fifteen years, and precisely this stability hides the real question.
The real question is the knowledge question
Someone built the customisations that hold up your NAV today. Often a colleague who has been with the company for twenty years, or a partner whose business has long since changed. The documentation lives largely in people's heads. As long as those heads are around, the system is manageable. The question to ask of an existing system is therefore never just "does it still run?", but: who can still explain it, change it and take responsibility for it in five years?
In fairness: a system that has supported the business for fifteen years is an achievement. Few can say that. But the value of that achievement rests on the knowledge, not on the code.
The move is cheapest while the knowledge is still in the company. Every year of waiting does not make it safer, it makes it more expensive.
How to tell that the time is closer than you think
The knowledge is concentrated in a few people
If a handful of people have to make every change and finding cover becomes difficult, the risk is already there, regardless of the version level.
Changes take longer and cost more
Every change to an old customised system needs archaeology: understanding what was built back then, and why. The time this takes grows quietly from year to year.
New requirements are no longer even raised
The quietest signal: the business stops asking, because "that takes forever here" has become accepted truth. Then the system runs stably and still slows the business down.
What the orderly path to Business Central looks like
An orderly move does not start with the migration, it starts with Take stock: which customisations hold real value, which were workarounds for the limits of the old system? In our experience, only part of the legacy needs a future. Then comes the data foundation: master data, rules, responsibilities, cleaned up before the migration, not after. Only then the system.
Approached this way, the move pays off twice: Business Central in the cloud keeps the version current automatically from then on, and the cleaned-up data foundation means new requirements reach the system in weeks instead of quarters. We have run many such moves, senior-led and without a big bang.
Frequently asked questions
Does NAV not simply keep running?
Technically, often yes. The risk rarely lies in operations, it lies in dwindling knowledge and in the growing distance between system and business.
Müssen alle Anpassungen nach Business Central mitkommen?
No, and that is the good news. Part of the customisations were workarounds for the limits of the old system and are covered by the standard or by extensions.
How long does an orderly move take?
Das hängt an Datenlage und Anpassungsgrad, nicht an der Software. Die Bestandsaufnahme, die diese Antwort belastbar macht, dauert Tage, nicht Monate.
