If you’re still on Dynamics NAV, you’re running a clock you can’t see.

Dynamics NAV is reliable to a fault. It keeps running, year after year, which is exactly why the risk it carries is so easy to ignore. The danger isn’t that NAV stops working tomorrow — it’s that the knowledge required to change it safely is quietly disappearing.

What’s actually at risk

• The C/AL developers who built your customizations are aging out of the market; replacements are scarce and expensive.
• Custom code nobody on staff fully understands becomes a black box that blocks every upgrade decision.
• A forced migration — triggered by an acquisition, an integration deadline, or a failed server — is far costlier than a planned one.

Why a planned move wins

Business Central is where this stack is going, and the path from NAV is well understood when it’s mapped deliberately. The work is to inventory what your customizations actually do, decide what carries forward as an AL extension and what should be retired, and sequence the cutover so month-end never lands mid-migration.

The right time to understand that path is before a deadline picks the date for you. A readiness review turns an open-ended risk into a known, schedulable project.