Why do they stall?
In the ERP world, Microsoft Dynamics AX (and its successor, Dynamics 365 Finance & Operations) is known for its scalability and flexibility. Yet global statistics suggest that around 50% of ERP projects do not reach their expected goals at the first attempt. So what do large international companies do when they hit this "failure" wall? Do they give up, or do they find a way to make the system work for them?
Failure on the global stage: why do projects stall?
When we look at well-known failures around the world (for example HP's problems in the early 2000s, or the difficulties some large retailers ran into during their migrations), we see that the problem is rarely "the software's code". Three main causes of failure stand out in Dynamics AX projects:
-
Over-customisation: Trying to bend the system to fit old habits instead of keeping to standard processes.
-
Data migration errors: Moving dirty data into a new system is like putting muddy fuel into a car with a rebuilt engine.
-
Resistance to change: Employees failing to adapt to the new interface and the new way of working.
The rescue operation: start again, or recover?
Speaking as a project manager, I can say this: when a project stalls, a company's first reflex is usually to blame the system and say "let's start from scratch with different software". Yet successful examples around the world show that an ERP recovery strategy is far more cost-effective.
Instead of throwing away the existing investment, international companies follow these steps:
-
Situation analysis (post-mortem): Before blaming the system, they look objectively at where processes get stuck, what is causing the technical blockages and where users hit bottlenecks.
-
Quick wins: Instead of big changes, they rebuild trust with small but critical fixes that make the system part of day-to-day operations again.
-
Ownership and leadership: A project without an owner is failure's best friend. The "second attempt" projects that succeed globally get back on their feet with strong backing from senior management and clear project leadership.
Projects that became success stories: the right strategy makes the difference
Many large manufacturers and retailers that have now completed their digital transformation with Dynamics 365 actually had a painful start. The ones that succeeded are those that see ERP not as a destination but as a living organism.
For example, a manufacturing company that lost efficiency at first because of complex integration processes moved its processes closer to Microsoft standards (best practices) and invested in user training. Within six months it turned a project that had ground to a halt into a success story that delivered 20% cost savings.
Conclusion: ERP is not software, it is a way of managing
Dynamics AX/365 projects will not always start perfectly. What matters is being able to stop at the right point and redirect the project with an expert eye. Keeping the existing setup and moving forward calmly and to a plan can turn an investment that looks like a failure into one of the organisation's most valuable assets. Remember, the best ERP system is not the one that hides your company's mistakes, but the one that shows them to you and gives you the chance to fix them.