ERP projects rarely succeed or fail because of the software alone. Problems are more often linked to decisions made before, during and after implementation, including unclear scope, weak data preparation, unnecessary customisation and insufficient user engagement.
This article breaks down the 7 ERP implementation challenges that come up again and again, with specific examples for multi-site hospitality groups, breweries, Pubco’s, furniture retailers and fashion retailers. If you’re scoping a Microsoft Dynamics 365 Business Central project or trying to work out why your last one didn’t go to plan, these are the ERP implementation challenges worth getting ahead of.
In this article:
- Mistakes that happen before the project even starts
- Mistakes that surface mid-implementation
- The mistake that happens after go-live
- Getting your ERP implementation right the first time
- Frequently asked questions
Mistakes that happen before the project even starts
The mistakes that sink an ERP project are usually made months before anyone logs into the new system. If you haven’t mapped how your operation actually works, whether that’s a multi-site pub estate, a furniture retailer with sharp seasonal stock cycles, or a fashion business juggling thousands of SKUs, you’re scoping a system around guesswork rather than reality. Everything downstream gets harder to fix once implementation is underway.
Mistake 1: No clear scope or success metrics
“Success” needs to mean something specific, rather than a vague sense that the business has “gone digital”. Before the project is scoped, agree the business outcomes, measures and responsibilities. These might include improved stock accuracy, faster reporting or a defined reduction in manual re-entry between till, EPOS and finance systems. Clear measures provide a basis for prioritising requirements, controlling scope and assessing the outcome after go-live.
Mistake 2: Choosing a generalist partner over an industry specialist
An ERP partner may understand the technology well without having sufficient experience of your sector or operating model. A brewery group, PubCo, fashion business and furniture retailer can each have very different requirements for stock, purchasing, reporting and integration. Relevant industry experience helps the partner challenge assumptions, identify requirements earlier and make better use of proven functionality. When assessing partners, ask for evidence of comparable implementations, the people who will deliver the project and how their proposed approach fits your business.
Mistakes that surface mid-implementation
Once a project is underway, a different set of mistakes tends to appear, usually around data, customisation, and the people actually using the system day to day.
Mistake 3: Underestimating data migration
Legacy data is often less consistent than expected. Older systems, spreadsheets and till or EPOS exports can contain duplicate records, inconsistent coding and information that does not map cleanly into the new solution. Data migration should therefore be treated as a workstream in its own right. The customer normally owns the accuracy, cleansing and validation of its data, while the implementation partner provides the agreed templates, mapping guidance and import process. Using customer-populated migration templates for review and validation is normal ERP implementation practice, not something unusual or specific to Business Central. Responsibilities, cut-off dates and validation steps should be agreed at the outset.
Mistake 4: Over-customising instead of using industry-built functionality
Custom development can be appropriate where it supports a clear business requirement, but it should not be the default response to every process difference. Unnecessary customisation adds cost, testing and upgrade considerations. Start with standard Business Central and proven industry-specific functionality, then assess any remaining gaps on their business value. Where development is justified, define the requirement, ownership and ongoing support implications before it is approved.
Mistake 5: Neglecting change management for distributed, shift-based teams
A single training session in a head office meeting room doesn’t work for teams spread across multiple sites, working shifts, and rarely sitting at a desk. Change management for a multi-site hospitality or retail business needs to fit around the way people actually work: shorter, role-specific training, on-site champions who can answer day-to-day questions, and materials staff can refer back to once the trainer has left. Skip this, and even a technically sound implementation will struggle with adoption.
The mistake that happens after go-live
Mistake 6: Treating go-live as the finish line
Go-live marks the move from implementation into live operation. A defined hypercare period can help the project team manage genuine go-live issues, while ongoing support should then continue through an agreed service and support arrangement. This does not mean every operational query or future improvement remains part of the original implementation. The customer and partner should be clear about what is covered, how issues are logged and prioritised, and how enhancements are assessed and approved.
Mistake 7: Not measuring performance against original goals
This brings the project back to Mistake 1. The measures agreed at the start should be reviewed after go-live against an agreed baseline and timetable. Ownership also matters: each measure should have a named business owner responsible for monitoring it and deciding whether further action is required. This gives the organisation evidence of the benefits delivered and separates genuine project issues from new requirements or later improvement opportunities.
Getting your ERP implementation right the first time
Look back across all 7 mistakes and one thing links nearly every one of them: partner choice and industry fit matter more than the technology itself. Business Central is a strong platform, but its success in your business depends on whether the people implementing it understand hospitality, breweries, PubCos, furniture, or fashion retail specifically, and whether they’re still there to support you once go-live has come and gone.
If you’re planning a Business Central implementation or trying to work out where a previous one went wrong, it’s worth talking to a partner who specialises in your sector. Get in touch with MADIC dynamics’ implementation team to talk through what a project built around your business, rather than a generic template, would actually look like.
Frequently asked questions
Why do ERP implementations fail?
Most failures trace back to unclear scope, poor data migration, or a lack of ongoing support after go-live, rather than the software itself. The platform is rarely the problem. The planning, the data, and the people around it usually are.
What is the ERP implementation failure rate?
ERP projects can exceed their original budget, timetable or fall short of their intended business outcomes. However, reported failure rates vary because studies use different definitions, including abandonment, delay, budget overrun and failure to achieve the original business case. The more useful question is where implementation risk can be reduced through better scope, data, governance and user adoption.
What should be on an ERP implementation checklist?
At minimum, your checklist should cover clear success metrics, a data migration and cleansing plan, a change management plan for affected teams, a realistic budget with contingency built in, and a defined post-go-live support arrangement. Missing any one of these is where projects typically start to slip.
How much does ERP implementation cost?
Costs vary widely depending on business size and scope, but the biggest overruns tend to come from underestimating data migration, customisation, and training, not from the base licensing fee. Budgeting realistically for these areas up front avoids most of the nasty surprises later.
How do you manage change during an ERP implementation?
Involve affected staff early, communicate clearly what’s changing and why, and train in a way that fits shift patterns and multi-site operations rather than relying on a single desk-based session. The businesses that manage this well treat change management as a workstream in its own right, not an afterthought bolted onto go-live.