7 Signs Your Business Central Implementation Needs a Rescue
Business Central projects rarely fail in one dramatic moment. They drift: a date slips, a requirement gets deferred, a workaround becomes permanent. By the time leadership calls it a problem, the budget is spent and the team is tired.
Here are seven signs we look for when a company asks us to assess a struggling Business Central implementation, before or after go-live.
1. The go-live date has moved more than once
One slip can be reasonable. Repeated slips usually mean the scope was never fully understood, key design decisions are still open, or data migration is not ready. Ask what specifically is blocking go-live and whether anyone owns each blocker.
2. Nobody can show you the solution design
Every implementation should have a written design that explains how your processes will run in Business Central: posting setup, dimensions, inventory and warehouse flows, approvals, integrations and reports. If the design lives only in the consultants' heads, decisions get remade every time someone new joins the project.
3. Change orders keep growing
A steady stream of change orders often means requirements were missed during discovery, or that standard functionality was not explored before custom development was proposed. Both are fixable, but only if someone steps back and re-baselines the scope.
4. Users are back in Excel
If people are maintaining spreadsheets alongside Business Central to track inventory, approvals or project costs, the system is not doing its job. Workarounds are a symptom: the underlying setup, training or process design needs attention.
5. Month-end does not close cleanly
After go-live, the first few closes are the real test. Common symptoms of setup problems include inventory valuation that does not reconcile to the general ledger, unexplained balances in interim accounts, missing or wrong dimensions on postings, and adjust cost routines that take hours. These usually trace back to posting groups, costing methods or item setup decisions made early in the project.
6. Customizations are breaking with every update
Business Central online receives major updates twice a year. Extensions built without following Microsoft's extensibility model, or without automated tests, tend to break on upgrade. If every update triggers a scramble, the customization approach needs review.
7. The team has lost confidence
This is the hardest one to measure and the most important. When finance, operations and leadership stop believing the project will deliver, adoption suffers even after the technical issues are fixed.
What a rescue looks like
A rescue is not about blame. It is a structured reset:
- Assess. Review the design, configuration, data, customizations and open issues. Interview the people doing the work.
- Stabilize. Fix the issues that block daily operations or the month-end close first.
- Re-plan. Agree on a realistic scope, owners and dates for what remains.
- Deliver. Work through the plan with clear weekly progress and decisions written down.
Often the fastest path is to use more standard Business Central functionality, not less, and to remove customizations that were built to replicate the old system.
Get an independent view
If several of these signs sound familiar, an outside assessment can save months. Learn more about our Business Central implementation rescue service, or talk to an architect. We typically start with a short assessment and give you a written findings report and recovery plan.
