Many organizations still run Dynamics AX 2009 or AX 2012 environments in production, with years of customizations, integrations, and processes built around the platform. That's not, in itself, a problem — but it's a signal that it's worth revisiting the long-term ERP strategy.
The risks of delaying the decision
Microsoft's support and product development today are focused on the Dynamics 365 family. That means new product capabilities, modern integrations (Power Platform, Copilot, native Power BI), and much of the partner ecosystem are oriented toward it.
Legacy AX environments accumulate technical debt: customizations that are no longer fully documented by anyone, fragile integrations, and a growing dependence on the tacit knowledge of a few people.
You don't need to migrate tomorrow — but you do need a plan
Continuing to run a stabilized AX environment with adequate support can be a valid business decision for a few more years. What isn't advisable is having no clarity about what would happen in the event of a critical failure, the departure of a key person, or the need for an important new integration.
An assessment of the current environment — covering customizations, integrations, data, performance, and technical debt — is the starting point for deciding between stabilizing, modernizing incrementally, or planning a structured migration to Business Central or Dynamics 365 Finance and Supply Chain Management.