ERP systems promise a lot. A single, unified platform that connects your finance, operations, supply chain, and people - giving leadership real-time visibility and giving teams the tools to do their jobs without wrestling with spreadsheets and disconnected software.
It's a compelling vision, and for many organisations it's exactly what gets realised.
But not always. ERP projects have a well-documented history of running over budget, missing deadlines, and in some cases, being abandoned altogether. Research consistently places ERP failure rates uncomfortably high (up to 25% by some estimates). And behind every statistic is a business that spent significant time and money on a system that didn't deliver.
Understanding why this happens - and recognising the warning signs early - is the first step to making sure it doesn't happen to you.
The Warning Signs Before You Even Go Live
Many ERP projects are set up to struggle long before a single line of configuration has been written. The problems often begin in the earliest stages, when the foundations are being laid.
Poor requirements gathering is one of the most common culprits. When the right stakeholders aren't involved from the start - when it's treated as an IT project rather than a business transformation - the system ends up being designed around assumptions rather than actual operational needs. Gaps emerge later, often at the worst possible moment.
Closely related is underestimating complexity. Organisations frequently underestimate the challenge of migrating legacy data, the knock-on effects of customisation requests, and the effort required to integrate the ERP with other business systems. Integrations in particular tend to be treated as an afterthought, only to become a significant source of delay and cost.
Weak executive sponsorship is another early warning sign that's easy to overlook. When leadership isn't visibly committed to the project - when it's delegated entirely to an IT team without a senior champion driving it forward - the project loses priority, decisions get delayed, and the wider business fails to engage.
Finally, unrealistic timelines and budgets create pressure that cascades through the entire project. When there's political pressure to go live by a certain date, corners get cut in testing, training gets shortened, and the system that goes live isn't the one that was actually ready.
The Signs It's Going Wrong Mid-Project
Even well-planned projects can start to drift. The mid-project phase is where many of the most damaging problems take hold, often quietly at first.
Scope creep, the gradual expansion of what the project is expected to deliver, is one of the clearest indicators of trouble. Without a formal change control process, every additional request adds time and cost without any adjustment to the plan. Teams become stretched, priorities blur, and the original objectives get lost.
Key users becoming disengaged is another serious warning sign. If the people who are supposed to be testing the system, providing feedback, and championing it internally start to check out, whether through frustration, workload, or a lack of confidence in the project, it's a signal that something has gone wrong with how the project is being run.
Rushed or skipped testing phases are a red flag that almost always leads to a difficult go-live. It's also a sign that the implementation partner and the internal team are pulling in different directions: when there's misalignment on goals, priorities, or even basic communication, the project loses the coherence it needs to succeed.
Data quality problems surfacing late are particularly damaging. Discovering that your source data is incomplete, inconsistent, or structured in a way that doesn't map cleanly to the new system in the final weeks of a project is a crisis that could have been caught months earlier.
The Human Factor
Technology gets a lot of the blame when ERP projects fail, but the root cause is just as often human. Change management - the discipline of preparing, equipping, and supporting people through organisational change - is consistently underinvested in ERP programmes.
When employees aren't adequately trained on the new system and its workflows, they don't use it properly. Workarounds emerge. Data quality suffers. The system that was supposed to create a single source of truth becomes another tool people work around rather than with.
Resistance from middle management is a particularly stubborn problem. For people whose authority has historically come from controlling information or processes, a new ERP system can feel threatening. Without deliberate effort to bring these individuals along - to involve them in the process and demonstrate what's in it for them - they can quietly undermine adoption across entire departments.
The organisations that succeed with ERP implementations treat change management as a core discipline, not a box to tick at the end.
Where Microsoft Dynamics 365 Projects Can Specifically Struggle
For organisations implementing Microsoft Dynamics 365 Business Central, there are some specific failure patterns worth calling out.
Over-customisation is a major one. Microsoft's ERP products are built on well-established business processes, and part of their value lies in adopting those standard processes rather than replicating the quirks of whatever the business was doing before.
When organisations insist on customising the system to mirror legacy workflows, rather than using the implementation as an opportunity to improve those workflows, they create a brittle, expensive-to-maintain system and sacrifice much of the long-term value.
Choosing the wrong licensing model for the organisation's current maturity and needs is another common issue that creates problems down the line. So too is failing to think about the broader Microsoft ecosystem from the outset: not building a strategy around Power Platform, not considering how Power BI will serve reporting needs, or failing to plan Azure infrastructure properly before the project begins.
ISV (independent software vendor) add-on solutions are also frequently bolted on without proper architecture review, creating integration headaches that compound over time.
Signs That Your Existing ERP System Needs Intervention
Sometimes the project did go live - but what was delivered isn't working. The signs of a dysfunctional ERP system are often just as visible as a troubled implementation.
Low user adoption is the most telling indicator. If people are avoiding the system, maintaining parallel spreadsheets, or finding workarounds for core processes, the system simply isn't serving them. Inaccurate or incomplete data within the system undermines every report, every decision, and every process that depends on it.
Limited mobile access, poor integration with other business systems, sluggish performance, and inadequate reporting capabilities all point to a system that is holding the business back rather than moving it forward. And when a system can't scale as the business grows - when adding new users, new entities, or new processes becomes a significant undertaking - it becomes a barrier to growth.
These aren't reasons to write off the investment. They're reasons to act.
All Is Not Lost: How to Rescue a Failing ERP Project
A stalled or underperforming ERP project is not the same as a failed one. The work done to date - the configuration, the data migration, the process mapping, the organisational change - retains value. What's needed is the right expertise to diagnose what went wrong, re-scope what needs to happen, and deliver it properly.
Akita's ERP rescue services are built specifically for this situation. As an experienced Microsoft partner working with Dynamics 365 and Business Central, Akita has helped organisations across sectors recover from implementations that had gone off the rails or been left incomplete by previous partners.
The recovery process follows four structured stages. It begins with a thorough assessment - an honest, detailed review of the project or system as it currently stands. Akita's consultants examine the project methodology, internal workflows, integration landscape, and the gap between where the system is and where it needs to be. The output is a clear picture of what's broken, what's salvageable, and what needs to change.
From there, Akita works collaboratively with the client on re-scoping - rebuilding the plan around what the business actually needs. Wherever possible, existing development is preserved to protect the investment already made. In cases where the foundations are unsound, a fresh start may be required, but one delivered at pace and with a clear structure that the original project lacked.
The implementation phase then proceeds with close stakeholder involvement, rigorous testing, and a managed go-live designed to cause as little disruption as possible. This isn't a repeat of what went wrong before — it's a structured, experienced-led delivery that takes the lessons of the failed project seriously.
The final stage is post-implementation support and training. A recovered ERP system only delivers value if the people using it are confident and capable. Akita provides hands-on training for teams alongside ongoing support, ensuring that the system continues to perform and that the business is never left without help when issues arise.
Where appropriate, Akita also looks beyond the ERP itself to the broader Microsoft ecosystem, whether that's Power BI to unlock better reporting and visibility, Power Apps to automate specific workflows, or Dynamics 365 Sales to bring CRM capability into alignment with the operational platform.
Conclusion
ERP failure is rarely the result of one catastrophic decision. It's the accumulation of small compromises - in planning, in governance, in change management, in technical design - that compound over time until the project or the system can no longer sustain them.
Recognising the signs early is what separates a recoverable situation from a written-off investment. And having the right partner to step in, one with genuine Microsoft expertise, a structured recovery methodology, and a track record of turning troubled projects into successful ones, makes all the difference.
If your ERP project has stalled, overrun, or delivered a system that isn't working for your business, the investment you've made doesn't have to be lost.
Speak to Akita's ERP consultants today. Whether you're dealing with an ongoing project that's gone off track or a live system that simply isn't delivering, Akita's team has the experience to assess your situation honestly and get you back on course. Get in touch to discuss an ERP rescue →
