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
New product experiences focus on Dynamics 365. On-premises data sources can still connect to Power BI, Power Apps or Power Automate through a gateway. For an AX environment, feasibility depends on connectors, the data model, security and integration maintenance.
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.