ERP Health Assessment Case Study: Helping a Manufacturer Decide Whether to Stay on AX 2012 or Move to Dynamics 365
SITUATION
A mid-market process manufacturer was at a strategic technology crossroads.
The company had been running Microsoft Dynamics AX 2012 across roughly a dozen legal entities and several hundred users. The platform was still operationally stable, but leadership had growing concerns about long-term viability, support risk, technical debt, and the cost of continuing to operate on a system Microsoft had already retired from mainstream support.
The question was no longer simply whether AX 2012 still worked.
Leadership needed to understand whether staying on AX was a sustainable strategy, whether the organization should begin preparing for Dynamics 365 Finance & Supply Chain Management, and what risks, costs, and operational trade-offs were attached to each path.
Before committing to a major ERP investment, the company engaged Ryse Technologies to conduct an independent ERP health assessment and strategic platform advisory.
CHALLENGES
Platform risk
Microsoft Dynamics AX 2012 extended support had ended in October 2023, creating growing exposure around security patches, hotfixes, compliance, and long-term maintainability.
Technical debt
The AX environment contained more than 50,000 non-standard codebase elements and hundreds of best practice violations. This made the platform more fragile, slowed change delivery, and increased the risk of future modernization complexity.
Data and recovery vulnerability
The database was running in SIMPLE Recovery mode with a single nightly backup. There were no transaction log backups and no tested disaster recovery procedure, leaving the business exposed in the event of a major failure.
Manual finance burden
Core finance processes were operational, but inefficient. Fixed Assets were tracked in Excel, the budgeting module was unused, month-end close took roughly three weeks, and bank reconciliations relied heavily on manual work.
Security and governance gaps
The organization had no Segregation of Duties rules configured in AX, excessive SysAdmin access, and no formal access review process. While perimeter security was stronger, role governance inside AX needed significant improvement.
Operational complexity
The environment was stable, but under-optimized. Infrastructure, database configuration, custom code, reporting, supply chain processes, and governance all carried risk that had accumulated over time.
OUR APPROACH
Ryse conducted a seven-week structured engagement across four parallel workstreams: Infrastructure & Database, Application & Custom Code, Finance & Supply Chain Process, and Operational Governance.
The engagement followed a three-phase methodology: Discover, Analyze, and Deliver.
During discovery, Ryse facilitated stakeholder workshops, reviewed business processes, gained direct environment access, and conducted quantitative analysis across the AX environment. This phase focused on understanding not just how the system was configured, but how it supported daily operations, financial processes, reporting, security, and supply chain execution.
During analysis, Ryse validated observations, sized business and technical opportunities, developed remediation options, and modeled risk probability. The team examined infrastructure posture, database configuration, AOS architecture, custom code, security design, reporting practices, and process maturity.
The final deliverable was a comprehensive assessment package, including a 120+ page assessment report, a technical debt register, a RAID log with more than 83 identified items, and an executive roadmap designed for board-level decision-making.
Key assessment areas included:
Infrastructure and database readiness
Ryse reviewed server capacity, SQL Server configuration, recovery model, backup strategy, disaster recovery posture, and database maintenance practices.
Custom code and application architecture
Ryse assessed the AX codebase, identifying non-standard elements, best practice violations, lack of version control, and gaps in Application Lifecycle Management.
Security and access governance
Ryse reviewed SysAdmin access, Segregation of Duties controls, access review processes, and AX role governance.
Finance and supply chain operations
Ryse evaluated core finance usage, manual workarounds, month-end close processes, budgeting, Fixed Assets, warehouse management, and production-related process issues.
Reporting and data governance
Ryse assessed the use of Power BI and SSRS, reporting database practices, ALM governance, data stewardship, and backup discipline.
Strategic cost modeling
Ryse developed a five-year Rough Order of Magnitude cost and risk model comparing four strategic paths: stay on AX, migrate now, delay migration, or face a forced emergency migration later.
RESULTS
Executive clarity
Leadership received a clear, evidence-based view of ERP risk, cost, and strategic options. Instead of relying on speculation or internal assumptions, the organization had a structured assessment of where AX 2012 remained stable, where it was under-optimized, and where risk was compounding.
Prioritized 120-day roadmap
Ryse delivered a sequenced remediation plan with 44 action items across all workstreams. The roadmap was designed to create value regardless of the final platform decision, helping the business stabilize immediate risks while preparing for a longer-term ERP strategy.
Financial decision model
The five-year TCO model reframed the executive discussion. Staying on AX 2012 and migrating to Dynamics 365 had similar base-case costs over five years, but the AX path carried a wider uncertainty band and greater risk exposure.
The model showed that AX was not a low-cost steady-state option. Ongoing support, risk premiums, manual workarounds, delayed analytics adoption, and potential forced migration costs made delay increasingly expensive.
Clear platform recommendation
Ryse identified Dynamics 365 Finance & Supply Chain Management as the strategically superior path. The recommendation was based on lower long-term risk, modern capabilities, evergreen platform architecture, and cost parity by year five.
Stabilization priorities
The roadmap identified critical near-term actions, including moving to a FULL Recovery Model, implementing transaction log backups, reducing excessive SysAdmin access, tuning SQL Server configuration, addressing code-level performance vulnerabilities, and improving backup and governance practices.
Governance and managed services pathway
Ryse also proposed an ongoing managed services model to support continuous monitoring, security governance, quarterly advisory, and sustained improvement beyond the initial assessment.
IMPACT
The assessment gave leadership the clarity to make a high-stakes ERP decision with confidence.
Instead of framing the choice as “keep AX because it still works” or “move to D365 because it is newer,” Ryse helped the organization evaluate the decision through risk, cost, operational burden, technical debt, and future capability.
The company gained a practical roadmap for immediate stabilization, a financial model for board-level discussion, and a strategic recommendation for long-term modernization.
Most importantly, Ryse helped turn ERP uncertainty into an actionable plan.
WHY IT MATTERS
ERP platforms rarely fail all at once.
More often, risk accumulates quietly through unsupported systems, undocumented customizations, manual workarounds, weak governance, outdated recovery practices, and delayed modernization decisions. By the time the business feels the full impact, the cost of action is usually much higher.
For organizations still running Microsoft Dynamics AX 2012, the question is not only whether the system is stable today. The better question is whether it can continue to support the business securely, efficiently, and strategically over the next five years.
Ryse Technologies helps leadership answer that question with evidence.
Through structured ERP assessments, technical debt analysis, risk modeling, and strategic platform advisory, Ryse gives organizations the clarity to stabilize what matters now, plan what comes next, and make ERP decisions based on facts rather than assumptions.
