ERP Implementation Success Rate
Research from Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals. That’s a sobering statistic, and one we want to change here at PKF SCS.
Your ERP system touches every part of your business, it supports your people, processes and decisions every day. Careful planning and change management is essential for successful adoption and a system you’ll be happy with for many years.
In this article, we’ll run through the most common mistakes, and how to make sure yours is a success.
5 Common Reasons ERP Implementations Fail
Having stepped in for lots of clients with implementations that weren’t going to plan, we’ve spotted a lot of the same patterns which could easily be avoided:
1) Misaligned Goals & Expectations
Starting an ERP project without clearly defined objectives is a bit like setting off on a road trip without deciding where you’re going first. Everyone is travelling in the same vehicle, but they have very different ideas about the destination.
We’ve seen projects where finance wanted one thing, operations wanted another, and the implementation partner only had half the story. If your expectations aren’t aligned from the start, the project can quickly drift off course.
This often leads to delays, unexpected costs and misalignment with the overall business strategy.
Solution: Bring together key stakeholders to agree a clear list of requirements and priorities, making sure to share the final list with the implementation partner.
2) Resistance to Change
People naturally feel uncomfortable with change and prefer to stick with what is familiar. This may seem a small issue, but poor adoption can bring down your whole project.
We’ve spoken to lots of businesses that have had issues with end users resisting change because the old way is familiar and “still works”, even if it is slow and manual. Whether that manifests in slow learning, clinging onto old processes or just general negativity.
Leaving end users out of the project until right at the end only fuels resistance, because they’ve not been given a voice to shape the system and they may not fully appreciate the reasons for the change.
Solution: Get end users involved early on and ask for their input, so they feel like they’re part of the journey and are more likely to embrace change.
3) Underestimating the Time & Work Required
While the software partner will do most of the work, allowing enough time to get it right and providing your input is still important to ensure the final product fits your needs.
With so many processes, possible features and departments affected, rushing to meet an unrealistic date can mean not getting the full potential from your system.
Department leads, operational users or anyone else involved in the project will all need sufficient time to balance the project with their usual work. For example, they may need to attend meetings, review documents, prepare data, test the system etc.
Solution: Set realistic deadlines and free up dedicated time for key individuals to give the project the attention it needs.
“A phased approach is quite common in the Sage Intacct world, which reduces the time to live, derisks the project by simplifying the initial phase and allows users to start understanding the system, which can influence their approach to future phases.” – Sam Pidegon, Sage Intacct Product Lead at PKF Smith Cooper Systems
4) Rushing Testing & Training
When the finish line comes into view, it’s tempting to push ahead to go live faster, but testing and training are important to ensure a smooth transition.
Going live without sufficient testing could seriously disrupt your business if there are any issues affecting critical processes. Catching issues early ensures they can be fixed before you go live.
Staff training can be delivered in-person, online or via self-serve resources, depending on what suits your team. Training helps users to feel confident using the system and helps you see value from your investment sooner.
Solution: Arrange staff training and take the time to thoroughly test the system for any issues before going live.
5) Issues With System & Data Compatibility
Many of the projects we’ve completed involved combining data from a variety of systems, that’s where system and data compatibility becomes a priority.
Each system may store data in a slightly different structure or format, which will need to be standardised prior to migration. There can also be gaps, duplicates and outdated information which need to be resolved to prevent any issues.
Not all software providers will have experience with all systems, so it’s worth discussing your current situation with them early on.
Solution: Decide how much data needs to be moved over and clean it up if needed. Keep a read-only version of your old system for historical data.
What Successful ERP Projects Have in Common
After working on countless implementations, we’ve noticed that successful projects tend to share a few common characteristics:
- Clear business objectives
- Clean and accurate data
- Realistic deadlines
- Strong stakeholder involvement
- Engaged end users
- Comprehensive testing and training
Rather than choosing which partner to work with based purely on price and awards, you should look for a partner that can prove their experience and align with your way of working.
How We Help Clients Succeed
Whilst implementing new software may be something your organisation does once every decade, for us, it’s what we do every day.
That’s why we take the time to get to know your business and guide you through the process every step of the way. Once you go live, we continue to give you the same care and attention, making sure the system continues to meet your needs for many years.
Our clients benefit from:
- Dedicated Sage 200 and Sage Intacct support teams
- Regular check-ins from your assigned Account Manager
- An in-house team of Sage-accredited developers
- A customer portal with self-serve learning resources
Whether you’re wanting to discuss your software requirements, a project that’s going off track, or anything else, we’re here to answer any questions you may have – get in touch here.
Sage Implementation FAQs
How long does a Sage implementation take?
Most organisations complete implementation within 3 to 6 months, however this can vary depending on which product you’re implementing and how much customisation and development is needed.
Who should be involved in a Sage implementation project?
Who you include will depend on your specific organisation structure, but you may want to include; CEO, CFO, Finance Director, Finance Manager, Accountant, IT support and a few end users. We advise making one of these the project manager, who will take the lead from your end and be the main point of contact.
How much data should I migrate to my new Sage system?
Our starting position tends to be Static Data and Opening positions, plus prior month/year trial balances to allow prior year reporting. There are options for bringing historical data, but most clients start with a clean slate, as their old data has been in place for a long time and changing systems is an opportunity for a clear out.
We also recommend retaining a read-only copy of your old system, in case you need to access any historical data. If you’re unsure, chat to us and we’ll advise on a case-by-case basis.
Written by: Jessica Allen, Marketing Executive at PKF Smith Cooper Systems.
Reviewed by: Sam Pidgeon, Sage Intacct Product Lead at PKF Smith Cooper Systems.
Last reviewed: July 2026.
