3 Reasons Business Central Implementations Fail

Believe it or not, nearly half of ERP implementations fail to meet expectations that is a staggering statistic and one that can make business leaders nervous about starting a new project.

However, Business Central itself is stable, well-documented, and proven in thousands of midsize professional services firms.

The problem usually lies in three connected areas: change management, scope control and data readiness. Each requires a realistic understanding of the effort involved and the impact an implementation will have on the business.

This is especially true for a Business Central implementation, where the business impact depends as much on adoption and data as on configuration.

The Three Reasons

Most implementation failures trace back to three root causes. Surprisingly, none of them are technical.

User Adoption

Your Business Central implementation will fail because of change management or a lack of change management.

When teams resist the new system, they:

• Keep using spreadsheets alongside Business Central
• Skip data entry or enter it inconsistently
• Work around the system instead of through it
• Lose confidence because they have not been properly trained

The result is a costly and underwhelming adoption rate that delivers little to no value.

Scope Control

The fastest way to derail a Business Central implementation is to try to make it work exactly like your old system.

Scope creep usually starts small:

• “Can we just add this one custom field?”
• “We need this workflow to match our current process.”
• “Let’s add this module while we’re at it.”

Each request feels reasonable in isolation. Together, they:

• Extend timelines by months
• Inflate budgets by 30–50% in many projects
• Increase testing before go live
• Customisation that can break during updates

The objective is not transporting old workflows and processes into a new system. For a successful project it’s best to prioritise out of the box functionality and only customise where it is genuinely business critical.

Data Readiness

Dirty data migrated into a clean system is one of the biggest implementation risks.

The majority of leaders think data migration will take a few weeks. In reality, it often takes eight or more because:

• Conversion of legacy data
• Chart of accounts, customer records, documents and vendor lists are inconsistent, incomplete, or duplicated
• Historical transactions don’t reconcile with opening balances
• No one internally owns the data cleansing effort

The consequence: go-live is delayed, users lose confidence in the system from day one and the finance team spends months fixing what should have been addressed before migration.

Avoiding Failure

The three failure points are easier to manage when they are identified early. The following areas deserve particular attention during partner selection, planning, configuration, testing and go-live preparation.

Partner Selection

Your partner agrees to everything you ask. A good partner will push back on unnecessary customisation and explain why out-of-the-box is better.

They do not have a structured methodology. Implementation should follow defined phases: discovery, fit-gap, design, data migration, testing, training, go-live and aftercare.

They cannot provide references from similar firms. If they have not implemented Business Central for professional services before, you are their learning project. There is nothing wrong with that but be aware.

They focus on features, not outcomes. The conversation should be about business processes and decision-making, not just “what reports do you need?” For professional services firms, that often means prioritising project accounting, margin visibility and role-based reporting.

A strong partner should be willing to challenge assumptions, explain trade-offs and connect the implementation to measurable business outcomes.

A strong partner should be willing to challenge assumptions, explain trade-offs and connect the implementation to measurable business outcomes.

Timeline and Budget

Go-live is planned in under 12 weeks for a full implementation. Realistic timelines for midsize professional services firms are typically 4–9 months, depending on scope.

Data migration is allocated less than 20% of project time. It should be one of the largest workstreams, not an afterthought.

There is no contingency budget. A 10–20% contingency is standard for ERP projects. If the budget is fixed with no flexibility, you are being set up for failure.

Requirements and Testing

Requirements were not documented and signed off. If you cannot point to a written scope document, you do not have a project; you have a wish list.

Testing was limited to “happy path” scenarios. Real testing should include edge cases, integrations and failure scenarios.

End users were not involved in testing. If only the project team tested the system, you are going to discover adoption gaps at go-live.

There is no regression testing plan. When customisations are added, existing functionality should be re-tested. If this is not happening, defects can appear.

Managing Change

Change management is the difference between a system that gets used and one that gets abandoned. Here’s what it looks like in practice.

Executive Sponsorship from Day One

Implementations stall when leadership is not visibly and actively committed. This means:

• The CEO or managing director communicates the “why” behind the change
• Leaders attend key project milestones and go-live support
• Resistance is addressed at the leadership level, not just delegated to the project team

Role-Based Training, Not Generic Demos

Training should be tailored to what users actually do:

• Finance teams need hands-on sessions on journals, reconciliations, and reporting
• Project managers need workflows for time entry, budget tracking, and billing
• Leadership needs dashboards and drill-through capabilities

Generic “here’s how Business Central works” demos don’t stick. Role-specific training does.

Communication That Overcomes Resistance

The best change management frameworks (like ADKAR — Awareness, Desire, Knowledge, Ability, Reinforcement) focus on:

• Awareness: Why are we doing this? What happens if we don’t?
• Desire: What’s in it for me? How does this make my job easier?
• Knowledge: How do I use the system for my role?
• Ability: Do I have the support and tools to succeed?
• Reinforcement: What happens if I don’t adopt? What recognition do I get if I do?

This isn’t soft stuff. It’s the difference between adoption and abandonment.

Aftercare and Continuous Improvement

The project doesn’t end at go-live. The first 30–90 days after go-live are critical:

• Aftercare support: Dedicated help desk, super-user network, daily check-ins
• Issue tracking: Log problems, prioritise fixes, communicate progress
• Adoption monitoring: Track login rates, transaction volumes, and data quality
• Continuous improvement: After the initial stabilisation, identify process enhancements and user-driven improvements

Projects that skip aftercare often see adoption collapse within the first quarter.

Once the system is stable, the focus shifts to using the data for faster, better decisions. Tools like Copilot and Power BI can help teams move from manual follow-ups to proactive insights.

Leadership Checklist

If you’re leading a Business Central implementation, these are the questions you should be asking at each phase.

Before the Project Starts

• What are our top three business objectives for this implementation?
• Who is our internal project sponsor, and do they have the authority to make decisions?
• Have we assigned a data owner to lead the cleansing and migration effort?
• What does success look like in 6 months? In 12 months?

During the Project

• Are we on track against our timeline and budget? If not, why?
• What customisations have been requested, and are they truly business-critical?
• Have end users been involved in testing, or is this just the project team?
• What’s our data migration status, and have we done a dry run?

At Go-Live

• What’s our aftercare plan for the first 30 days?
• Who are our super users, and how will they support their teams?
• What are our adoption metrics, and how will we track them?
• When is our first post-go-live review, and what will we measure?

Go-Live Readiness

Not every Business Central implementation problem is a reason to stop. But some are.

Hit Pause If:

• Data migration is failing repeatedly. If you can’t reconcile opening balances or migrate clean data, don’t go live.
• Key users are actively resisting. If department heads are undermining the project, address this before proceeding.
• Your partner is missing milestones consistently. One delay is understandable. A pattern is a red flag.
• Critical integrations aren’t tested. If you rely on integrations (e.g., payroll, CRM, time tracking), don’t go live until they are proven.

Push Through If:

• There are minor bugs that don’t block core processes. These can be fixed in aftercare.
• Some users are resistant but leadership is aligned. This is normal, address it with training and support.
• Timeline is slipping by 2–4 weeks due to scope additions. This is manageable if you control further creep.

The key is knowing the difference between a fixable issue and a fundamental risk.

FAQs

Assess Your Readiness

Business Central is a powerful platform for professional services firms that have outgrown tools like Xero. But it’s not a magic bullet.

To ensure a good outcome:

• Treat it as a business transformation, not just a software upgrade
• Invest in change management as much as configuration
• Prioritise data readiness and don’t cut corners on migration
• Work with partners who challenge you, not just agree with everything
• Plan for continuous improvement after go-live, not just a one-time project

If you’re evaluating Business Central implementation and want to avoid these pitfalls, we can help you assess your readiness.