This article includes insights from Kevin Howes II, Director ‑ AX/Finance & Operations at GraVoc.
Kevin helps organizations plan successful transitions from Dynamics AX to Dynamics 365. With hands‑on experience across AX 2009, AX 2012, and Dynamics 365 FSCM, Kevin leads clients through upgrade and reimplementation strategy and post–go‑live stabilization.
Many organizations put off moving away from Dynamics AX. When you have invested years, and significant budget, into shaping an ERP system to fit your business, it’s hard to consider an upgrade or re-implementation. Just as importantly, no one is eager to relive a complex ERP migration or implementation that may have been disruptive the first time around.
That hesitation is understandable. Dynamics AX was a reliable, trusted ERP for many years, especially for finance teams that depended on stable processes, reporting, and controls. But over time, even a familiar system can start to work against you. Manual workarounds creep in; reporting becomes harder to trust or maintain; compliance and security risks grow as the platform ages.
With Microsoft ending support for Dynamics AX, including AX 2009 and AX 2012, those risks are no longer theoretical. At some point, it becomes difficult to justify staying on a system that no longer aligns with modern financial, regulatory, or operational requirements. For most organizations, the next step is planning a move to Dynamics 365 Finance and Supply Chain Management (FSCM).
In this guide, we walk through what moving off Dynamics AX involves. We cover decision points like upgrade versus reimplementation, key differences between Dynamics AX and Dynamics 365 FSCM, and the considerations finance teams should weigh before taking the next step.
Is Dynamics AX still supported?
No, Microsoft has officially ended mainstream and extended support for all versions of the legacy Dynamics AX, including AX 2009 and AX 2012. This means that the ERP no longer receives security fixes, regulatory updates, or feature enhancements.
Microsoft is also no longer offering Dynamics AX licenses for purchase to new customers.
If your company is still using Dynamics AX, you are running on unsupported software that leaves your business exposed to many security, operational, and compliance risks.
- Increased security risk: Dynamics AX no longer receives Microsoft security updates, leaving known vulnerabilities unpatched and increasing exposure to cyber threats.
- Growing compliance challenges: Unsupported ERP software can make it harder to meet regulatory and audit requirements.
- Rising integration and compatibility issues: Modern applications, APIs, and Microsoft products are increasingly difficult to integrate reliably with legacy AX environments.
- Migration becomes more complex over time: The longer AX remains in place, the more technical debt, data issues, and workarounds accumulate, increasing the risk of a future migration becoming more disruptive and costly.
What replaced Dynamics AX?
Dynamics AX evolved into Dynamics 365 Finance and Supply Chain Management.
Where Dynamics AX was primarily an on‑premises ERP with periodic upgrades, Dynamics 365 FSCM is a cloud‑first platform that follows Microsoft’s continuous update model. Dynamics 365 FSCM is designed to stay current without major version upgrades, integrate natively with other Microsoft tools, and support modern financial, regulatory, and reporting requirements.
Understanding what replaced Dynamics AX, and how closely it aligns to the system you know, is the first step in evaluating your migration options.
What is the difference between Dynamics AX and Dynamics 365?
Dynamics AX and Dynamics 365 FSCM differ most in architecture, update model, customization approach, and long‑term maintainability.
Here are some of the key differences between both platforms:
- Dynamics 365 is the modern evolution of Dynamics AX. It has the same lineage, but significantly expanded capabilities.
- Dynamics 365 FSCM has cloud-first architecture (SaaS) vs Dynamics AX’s primarily on-prem footprint.
- Dynamics 365 comes with continuous, automatic updates vs Dynamics AX’s static release cycle.
- Dynamics 365 FSCM has much stronger integration capabilities, including with APIs, Dataverse, etc.
- Dynamics 365 has improved user experience (browser-based, role-based workspaces, embedded analytics)
- Dynamics 365 comes with expanded feature set across finance, supply chain, planning, and automation.
- Dynamics 365 includes native integrations with tools like Microsoft Power BI and Microsoft Power Platform.
- Dynamics 365 FSCM has built-in telemetry, monitoring, and lifecycle tooling via Lifecycle Services.
Dynamics AX vs. Dynamics 365 FSCM licensing
Licensing is one of the biggest structural differences between Dynamics AX and Dynamics 365 FSCM. Dynamics AX was typically purchased as a perpetual license with annual maintenance. Dynamics 365 FSCM, on the other hand, uses a subscription‑based model, shifting ERP costs from a capital expense (CapEx) to an operating expense (OpEx). At a high level, organizations license:
- Dynamics 365 Finance for financial management and reporting
- Dynamics 365 Supply Chain Management for procurement, manufacturing, inventory, and logistics
- Light‑use licenses, such as Activity or Team Member–style licenses, for users with limited, task‑based needs
Most full users require access to both Finance and Supply Chain Management. Microsoft’s “attach” licensing model allows organizations to license a second application at a discounted rate, rather than paying full price twice for the same user. Unlike Dynamics AX, Dynamics 365 licensing also requires ongoing governance. Microsoft now enforces license compliance more strictly, meaning access is tied directly to assigned licenses and security roles. As a result, licensing strategy plays a larger role in budgeting, audit readiness, and system design than it did in Dynamics AX. Read more about Dynamics 365 FSCM license management.
Expert note:
It’s recommended to plan your licensing strategy around user personas and system usage to control cost and stay compliant.
Dynamics AX: Upgrade to Dynamics 365 or re-implementation?
One of the most important decisions in a Dynamics AX migration is whether to upgrade your existing system or reimplement Dynamics 365 Finance and Supply Chain Management (FSCM).
While both paths lead to the same platform, they carry different implications for cost, timeline, risk, and long‑term value.
When an upgrade makes sense
An upgrade is typically considered only for organizations running Dynamics AX 2012 (R2 or R3). In these cases, an upgrade may make sense when:
- Core business and financial processes in Dynamics AX 2012 are still valid
- Customizations are limited and follow best practices
- Data is relatively clean and worth preserving for historical reporting
- Speed and cost predictability are higher priorities than transformation
- There is minimal appetite for broad process change
In these scenarios, an upgrade can provide continuity while moving the organization onto Microsoft’s supported platform.
When reimplementation is the better option
For many organizations, reimplementation is the more practical and lower‑risk path, especially when running Dynamics AX 2009.
If you are on AX 2009:
- The system is out of Microsoft support
- There is no direct upgrade path to Dynamics 365
- The only supported approach is a reimplementation in Dynamics 365, with data selectively migrated using the AX 2009 Data Migration Tool
Reimplementation also tends to be the better option when:
- Dynamics AX contains heavy or complex customizations that don’t align with Dynamics 365 standards
- The goal is to adopt standard Dynamics 365 functionality rather than carry forward legacy code
- Legacy ISVs are being replaced or rationalized
- Data quality issues or lack of governance make a full data migration risky
- Business process redesign is a stated objective
- Multiple legal entities or environments have diverged significantly
- The current AX implementation is viewed internally as overly complex or unsuccessful
In these cases, reimplementing provides an opportunity to reduce technical debt and align the system more closely with how the business operates today. Reimplementation can be slower and more expensive, but it offers more long-term value for companies moving off Dynamics AX.
The hybrid approach
For Dynamics AX 2012, you can also choose a hybrid approach, where we reimplement core functionality while migrating select historical data, such as GL balances, open transactions, and critical master data.
How Microsoft tooling supports Dynamics AX upgrade and re-implementation projects
Microsoft provides purpose built tools that help teams evaluate risk, effort, and feasibility early in a Dynamics AX to Dynamics 365 project. Code Upgrade Analysis tools assess AX 2012 customizations to determine compatibility with Dynamics 365 and estimate the level of refactoring required. Lifecycle Services (LCS) provides structured visibility into environments, deployments, and system health throughout the project. Data Migration Framework (DMF) enables phased data migration when only select historical data is needed, while Regression Suite Automation Tool (RSAT), fed by Task Recorder, helps validate that critical finance and operations processes function as expected.
Not sure which path applies to your Dynamics AX environment?
GraVoc offers a Microsoft AppSource–listed Dynamics AX Upgrade to Dynamics 365 Finance & Supply Chain Management Assessment to help organizations evaluate upgrade vs reimplementation scenarios, data scope, and overall readiness. Request an assessment.
Expert insights: What a successful Dynamics AX to Dynamics 365 FSCM migration looks like
Based on his experience leading businesses through Dynamics AX upgrades, our Director of AX/Finance & Operations, Kevin Howes II, shares some key components of a successful Dynamics AX to Dynamics 365 FSCM migration.
Intentional data decisions
Only data that supports compliance, reporting, and ongoing operations is migrated. Data ownership is clearly defined, and master data is rationalized before migration begins.
Reduced reliance on customizations
Legacy AX custom code is evaluated critically, with teams adopting standard Dynamics 365 functionality wherever possible instead of recreating technical debt.
A right sized ISV ecosystem
Third party solutions are reviewed early to confirm they still add value, align with D365's platform, and integrate cleanly into the future state environment.
Validated end-to-end processes
Core finance and operational workflows are tested across systems and scenarios-not just at a module level-before go live and during future updates.
Prepared and informed users
Training and change management focus on how Dynamics 365 works today, helping users adjust expectations and adopt new processes with confidence.
Dynamics AX upgrade FAQ
How long does it take to upgrade or move from Dynamics AX to Dynamics 365?
Timelines vary based on AX version, customization depth, data complexity, and whether the project is an upgrade or full reimplementation.
How much does it cost to move from Dynamics AX to Dynamics 365?
Costs depend on project scope, number of users, data migration approach, customizations, integrations, and change management effort.
What happens if you are still on Dynamics AX 2009?
Dynamics AX 2009 is fully out of Microsoft support and has no direct upgrade path to Dynamics 365. The only supported option is a reimplementation of Dynamics 365 with selective migration of required historical data.
What if you are still on Dynamics AX 2012?
Dynamics AX 2012 environments may be eligible for an upgrade, but this depends on customization quality, data health, and business objectives. Many AX 2012 organizations still choose reimplementation or a hybrid approach to avoid carrying forward technical debt.
