To build a business case for migrating off Dynamics AX, you need to document the total cost of staying on an unsupported platform, quantify the operational and financial benefits of a modern ERP, and frame the investment in terms of risk reduction and long-term ROI. The strongest business cases combine hard financial data with a clear picture of what happens if the organisation does nothing. Below, we walk through each component you need to address to get board approval and move forward with confidence.
Why is Dynamics AX no longer a viable long-term platform?
Dynamics AX is no longer a viable long-term platform because Microsoft ended mainstream support for all versions, including AX 2012, and has shifted its ERP investment entirely to Dynamics 365 Finance and Operations. Running on an unsupported platform means no new feature development, limited security patches, and a growing dependency on expensive third-party support contracts. For any organisation with ambitions to scale, integrate, or compete digitally, staying on Dynamics AX is a strategic liability, not just a technical inconvenience.
In 2026, the gap between Dynamics AX and its cloud-based successor has widened considerably. Dynamics 365 offers real-time analytics, AI-assisted workflows, and native integration with the broader Microsoft ecosystem. AX users are increasingly unable to connect with modern supply chain tools, CRM platforms, and reporting environments without custom workarounds that add cost and fragility to the architecture. When you factor in the talent market, finding consultants who still work on legacy AX is also becoming harder and more expensive.
The business case for migration is not just about what you gain. It is equally about what you avoid: security vulnerabilities, compliance gaps, and the compounding cost of maintaining a system that Microsoft no longer actively develops.
What are the financial components of a Dynamics AX migration business case?
The financial components of a Dynamics AX migration business case fall into two categories: the cost of migrating and the cost of not migrating. Both sides need to be quantified clearly for the board to make an informed decision.
Migration investment costs typically include:
- Licensing and subscription fees for the new platform
- Implementation partner fees covering project management, configuration, and testing
- Data migration management, including data cleansing, mapping, and validation
- Change management and training to drive user adoption
- Infrastructure and integration costs
- Cutover and go-live support, including hypercare in the weeks after launch
The cost of staying on Dynamics AX includes:
- Extended support contracts, which are typically significantly more expensive than standard support
- Custom development to fill functionality gaps that are no longer addressed by the vendor
- Security and compliance remediation costs as vulnerabilities emerge
- Productivity losses from manual workarounds and outdated interfaces
- The opportunity cost of delayed digital transformation initiatives
A well-structured business case presents both columns side by side. When boards see the cumulative cost of doing nothing over three to five years, the migration investment often looks considerably more attractive.
How do you calculate ROI for an ERP migration from Dynamics AX?
ROI for an ERP migration from Dynamics AX is calculated by dividing the net financial benefit of the new system by the total cost of migration, expressed as a percentage over a defined time horizon, typically three to five years. The challenge is that many of the benefits are indirect or take time to materialise, which is why the calculation requires careful framing alongside the raw numbers.
Start with the quantifiable benefits: reduced licensing and support costs, headcount efficiency gains from automation, faster financial close cycles, and lower IT maintenance overhead. These are the numbers your finance team can model with reasonable confidence based on vendor benchmarks and your own operational data.
Then layer in the harder-to-quantify but important benefits: improved reporting accuracy, better inventory visibility, faster onboarding of new business units, and reduced audit risk. These do not always translate directly into a single line item, but they strengthen the narrative around the investment.
A realistic ROI model also accounts for the transition period. Productivity typically dips around go-live before recovering and improving. Build this dip into your projections honestly. Boards that see a smooth hockey-stick curve with no implementation friction are more likely to push back than those presented with a grounded, realistic timeline. Consulting partners who have run comparable Dynamics AX migrations can provide reference data to validate your assumptions, which adds credibility to the model.
What risks should the business case address to gain board approval?
To gain board approval, the business case must address four categories of risk: operational continuity, data integrity, user adoption, and budget overrun. Boards are not just approving an investment; they are accepting responsibility for what happens if things go wrong. Showing that you have thought through the risks and planned for them is often what tips a hesitant board toward approval.
Operational continuity is the most visible risk. A cutover that goes badly can halt order processing, disrupt supply chains, or create compliance failures. The business case should describe how cutover will be managed, including a rollback plan and a hypercare period where extra support is in place immediately after go-live.
Data integrity is the risk that often gets underestimated. Years of data in Dynamics AX may include duplicates, legacy structures, and fields that do not map cleanly to the new system. A rigorous As-Is/To-Be analysis of data structures, combined with testing procedures before migration, is the practical answer to this risk.
User adoption is where many migrations quietly fail after a technically successful go-live. The business case should include a change management plan that addresses how people will be supported through the transition, not just trained on the new system. Adoption risk is real, and boards increasingly ask about it.
Budget overrun is managed through scope discipline, a realistic contingency allowance, and a governance structure that tracks decisions against the original business case. You can explore our full range of services to understand how each phase of the migration is structured to protect budget and timeline.
When is the right time to start the migration business case process?
The right time to start the Dynamics AX migration business case process is before the pressure becomes urgent. Organisations that begin when a specific trigger forces their hand, such as a failed audit, a security incident, or a key integration breaking, have far less negotiating room on timeline, budget, and partner selection. Starting early gives you the space to build a credible case rather than react to a crisis.
A useful starting point is a maturity assessment that gives you an honest baseline of where the organisation currently stands in terms of processes, data quality, and system capability. This assessment answers the question your board will inevitably ask: “Do we actually know what we have before we commit to replacing it?” Without this baseline, cost estimates are guesswork, and the business case is built on assumptions that can unravel under scrutiny.
In practical terms, if your Dynamics AX support contract is up for renewal in the next 12 to 18 months, that is your window to start building the business case now. The process of getting board approval, selecting a partner, and planning the migration takes time. The organisations that manage migrations well are the ones that gave themselves enough runway to do it properly.
How Optinus helps you build and execute a Dynamics AX migration business case
We work with ERP programme managers and IT directors across the full migration lifecycle, from the initial business case through to post-go-live support. Here is what that looks like in practice:
- Maturity assessment: We start by giving you a clear, honest baseline of your current processes, data structures, and system maturity, so your business case is built on facts, not assumptions.
- Business case development support: We help you structure the financial components, quantify risk, and frame the ROI in a way that holds up to board scrutiny.
- End-to-end programme management: Our consultants have hands-on experience from real Dynamics AX and Dynamics 365 migrations at leading multinationals, covering project management, data migration, test management, and cutover.
- Cutover and hypercare: We manage the go-live transition end-to-end, with hypercare and aftercare built in to protect operational continuity from day one.
- Change management: We address both the technical and human side of the migration, driving genuine adoption across the organisation rather than just delivering training sessions.
- Flexible engagement: We work on-site and remotely, across the Netherlands, Belgium, and internationally, adapting to how your programme is structured.
If you are at the stage of building or strengthening your Dynamics AX migration business case, get in touch with our team for a practical conversation about where to start. You can also learn more about what we do and how we approach complex ERP transformations.
