Why ERP Projects Fail (and Why I Still Trust Business Central)

Reading Time: 3 minutes

After 30 years implementing ERP systems in factories and warehouses across Greece, the UK, and the rest of Europe, I’ve come to a conclusion that usually surprises people:

Most ERP projects do not fail because the software is bad.

They fail because companies try to change too much, too fast, while still running a real business every day.

I’ve seen this happen more times than I can count. Management gets excited, consultants promise a “digital transformation,” and suddenly the company decides that from Monday morning everything will work differently. New ERP, new processes, new approvals, new reports, new screens, new rules.

Three months later the warehouse is back on Excel, salespeople are keeping customer notes in Outlook, and finance is exporting half the data into spreadsheets because nobody fully trusts the numbers yet.

And honestly? I understand why that happens.

People can only absorb so much change at once.

The Biggest Trap: the “Big Bang” Implementation

The projects that usually go wrong are the ones trying to do everything in one shot.

I once worked with a company that spent months redesigning workflows, approval chains, dashboards, KPIs, everything. By the time they went live, the staff were already exhausted before they had even posted the first real transaction.

The funny part is that some of the old processes they were trying so hard to preserve were already broken before the ERP arrived.

That’s another thing people don’t always want to hear: sometimes the software is not the problem. Sometimes the company process itself needs to change.

Too many ERP projects become exercises in copying old habits into a newer and more expensive system.

Why I Still Like Business Central

This is one of the reasons I stayed with NAV and later Business Central for so many years.

Business Central works well for mid-sized companies because it allows you to breathe a little during implementation. It doesn’t force you to redesign the entire company overnight.

And maybe this sounds simple, but it matters: people are less afraid of BC because it feels familiar.

It looks like Microsoft. It works with Excel. It lives inside Teams and Outlook.

For many users, especially in manufacturing or distribution environments, that familiarity removes a huge amount of resistance.

My usual approach is very simple: find the process causing the biggest pain today and fix that first.

Not ten processes. One.

Maybe inventory accuracy. Maybe production planning. Maybe customer invoicing.

Once people see one area actually working properly, confidence starts building naturally.

That’s the point where ERP projects usually succeed or fail. Not technically, but psychologically.

What Successful Projects Usually Have in Common

After all these years, the successful projects almost always follow the same pattern:

They stabilise the core data first instead of chasing fancy dashboards.

They avoid heavy customisation early on.

They accept that some old habits probably need to disappear.

And most importantly, they roll things out at a speed the staff can realistically absorb.

If the warehouse still writes quantities on paper because they don’t trust the scanners yet, this is probably not the moment to start talking about AI forecasting and advanced automation.

One step at a time works better.

A Bit of Honest Advice

If your ERP project already feels overwhelming, simplify it.

Seriously.

You do not need to climb the whole mountain in one afternoon.

I’ve seen companies make more progress in six weeks with a small, focused rollout than other companies made in two years with giant transformation programmes.

Business Central is not magic. No ERP is.

But what I still trust about BC after all these years is that it gives companies room to grow gradually instead of forcing perfection from day one.

And in the real world, gradual progress usually beats ambitious chaos.

I’d genuinely love to hear your own experiences because every consultant who has been around long enough has a few ERP horror stories.

What was the moment where your ERP project started going wrong, or finally started going right?