You’ve already invested time, money, and patience in Business Central. Changing partners can feel like risking that investment all over again.
But changing your partner and replacing your implementation are separate decisions. Before committing to either, establish what works, what needs attention, and what your business needs next.
You need a clearer way forward, not an automatic recommendation to start again.
Do you need a different partner, a different setup, or both?
Perhaps support requests go unanswered. The same issues keep returning. Or your business has outgrown the expertise available.
You might also be looking ahead: stronger integration support, ongoing enhancements, clearer service commitments, or access to specialist resources.
None of those needs automatically means your implementation has failed.
A useful review separates three things:
- The relationship: Communication, availability, accountability, and support.
- The environment: Configuration, data, integrations, extensions, and documentation.
- The requirement: What your organization needs Business Central to do.
If the environment meets your requirements but support does not, the next step is different from a situation involving unfinished or unsuitable work.
If you are unsure which situation applies, start with our guide on how to tell configuration, training, functionality, and partner-support issues apart.
What happens to the work you’ve already paid for?
Existing work needs to be understood before anyone recommends retaining or replacing it.
In one partner-switching enquiry received by 360 Visibility, an organization had paused its implementation after modifications had been developed and training had begun. The initial discussion identified gaps in specifications and design documentation.
That enquiry illustrates an important point: “The development is done” does not tell you whether the work is ready to support the business.
A review needs to establish what the modifications were intended to achieve, what has been demonstrated, and what remains uncertain.
Missing documentation is a reason to investigate. It is not, on its own, proof that everything needs rebuilding.
If key work was never finished, read how to recover a stalled Business Central implementation. If the project is live but your team still works around the system, see what to do when Business Central is live but not working properly.
What should a takeover recommendation explain?
Look for a clear distinction between:
What can be retained
Existing work that appears suitable for continued use, with an explanation of that conclusion.
What needs investigation
Areas that cannot yet be assessed confidently, and the work needed to resolve the uncertainty.
What needs changing
Corrections or replacements, why they are recommended, and what depends on them.
How support will work
Ownership of issues, improvements, decisions, and ongoing service.
Be cautious about either extreme: “Everything needs replacing” or “Nothing needs changing.”
You need reasoning you can understand, not reassurance you have to take on trust.
Define what a better partnership should deliver
Changing partners is not the outcome. Better support and a system that serves the business are the outcomes.
Be specific about what you need: resolving existing problems, maintaining integrations, delivering improvements, or providing a more dependable support model.
If you are already live, document the recurring workarounds and their business impact. If the project remains unfinished, establish what is complete, untested, blocked, or still unclear before agreeing to another timeline.
That gives the next conversation a practical starting point.
A different partner shouldn’t mean another leap of faith
You don’t have to commit to switching before understanding your options.
Our Business Central rescue service starts with your existing environment and what needs to change. We’ll discuss whether a scoped assessment is the right next step.
Request a Business Central Rescue Review to understand what can be retained, what needs investigation, and what a partner transition would involve.