7 signs your Business Central implementation is in trouble
ERP projects rarely fail all at once. They drift: one slipped date, one workaround, one unanswered question at a time. The good news is that the warning signs are predictable, and most of them are fixable if you act early.
1. The go-live date keeps moving
One delay can be reasonable. Two or more usually means the plan was never grounded in a clear scope, or that problems are being discovered later than they should be. Ask what changed each time. If the answers are vague, that's the real problem.
What to do: separate what must work on day one from what can follow, and re-baseline against that smaller list.
2. Finance can't close the month or trust the numbers
If month-end close takes longer than it did on your old system, or balances need manual adjustments to tie out, the issue is almost always configuration: posting groups, dimensions, costing setup or migrated opening balances.
What to do: trace each recurring variance to its source before more transactions pile on top of it.
3. Integrations fail quietly
Orders that don't sync, payroll entries that need re-keying, an e-commerce feed that "usually works." When staff routinely fix integration errors by hand, the true failure rate is hidden and the cost is real.
What to do: every integration needs error handling, logging, and a named owner who's alerted when it fails.
4. Users are drifting back to spreadsheets
Workarounds are the most honest feedback a project gets. When people keep parallel spreadsheets, it's because the system doesn't support how they work, wasn't set up correctly, or they were never properly trained.
What to do: ask users why. The answers will tell you whether you have a setup, process or training problem.
5. Change orders keep arriving
A steady flow of change orders usually points to requirements that were never pinned down. Each one may look small; together they signal that the design is being worked out during the build.
What to do: compare open change orders against the original design document. If there isn't one, that's the first gap to close.
6. Nobody can explain the customizations
Extensions written to avoid hard process decisions become fragile, expensive to change, and a risk every time Microsoft releases an update. If no one can tell you what each customization does and why it exists, you have a maintenance problem waiting to happen.
What to do: inventory every extension, its purpose and its owner. Retire what standard Business Central now handles.
7. The people doing the work aren't the people you met
Senior consultants win the deal; less experienced staff deliver it. That gap shows up first in design decisions, which are the most expensive mistakes to undo later.
What to do: make sure someone with deep experience owns the architecture, and that you can talk to them directly.
How many did you recognize? One or two is common and manageable. Three or more usually means the project needs an independent senior review before more time and budget go in.
Can a troubled project be saved?
Usually, yes. Most struggling implementations have a sound core with specific problems in data, setup, customizations or integrations. Starting over is rarely necessary. The key is an honest diagnosis: what to keep, what to fix and what to remove, followed by a plan that stabilizes daily operations first.
Your Business Central environment, data and licenses belong to you. If you've lost confidence in your partner, switching mid-project is more manageable than most companies expect.