The Complete Guide to Moving Your Business Central Partner

Changing your Business Central partner is a decision most organisations agonise over far longer than they need to. The reality is that the process is straightforward, the risk is low and the impact on your day-to-day operations is minimal. If your current partner is not delivering the service you need, staying put is almost always the more expensive option.

This guide covers why organisations change partner, what the transition involves, what to look for in a replacement and what your first 90 days should look like.

Why Organisations Change Partner

In our experience, the decision to move partner rarely stems from a single event. It builds over months, sometimes years, as small frustrations compound into a pattern of dissatisfaction. The most common triggers we see are:

• Poor communication. Support tickets disappear into a queue. Updates are infrequent. You chase more than you are chased. When you do get a response, it comes from someone unfamiliar with your system.
• Slow response times. A five-minute configuration change takes a week. Critical issues are not treated with urgency. Your business waits while your partner works through a backlog.
• Lack of industry knowledge. Your partner treats every client the same. They do not understand your sector's regulatory requirements, operational rhythms or commercial pressures. You spend more time explaining your business than receiving advice.
• Overly junior teams. The senior consultant who sold you the project is nowhere to be seen. Your day-to-day contact is a junior analyst who escalates every question. You are paying premium rates for entry-level service.
• Hidden costs. Every conversation leads to a change request. Every change request leads to an invoice. The total cost of ownership bears no resemblance to the figure you were quoted during the sales process.

If three or more of these sound familiar, it is time to explore your options.

What the Transition Actually Involves

The most common reason organisations delay switching is a belief that the process is complex, risky or disruptive. It is none of these things. Here is what actually happens:

CSP transfer. Your Business Central subscription is managed through Microsoft's Cloud Solution Provider programme. Transferring to a new CSP partner is an administrative process that Microsoft facilitates. It does not affect your data, your configuration or your users. The system continues to run exactly as before.

Partner authorisation. Your new partner needs delegated admin access to your Business Central tenant. This is a standard Microsoft process that takes minutes to set up. You control what level of access to grant.

Data and documentation handover. Your outgoing partner should provide any project documentation, configuration notes, custom development specifications and support history. In practice, many partners hold limited documentation, which is one reason you may be leaving in the first place. A competent new partner will conduct their own system audit regardless.

No downtime. At no point during a partner transfer is your system unavailable. Your users continue working as normal throughout the entire process. There is no migration, no data movement and no reconfiguration required simply because you have changed partner.

What to Look for in a New Partner

Not all Business Central partners are equal. The market ranges from large consultancies with thousands of clients and tiered support structures to specialist firms with deep expertise and direct access to senior consultants. When evaluating a new partner, consider:

• Industry expertise. Do they have clients in your sector? Can they demonstrate understanding of your industry's specific requirements? A partner who knows your vertical will deliver faster, more relevant implementations and support.
• Track record. How long have they been implementing Business Central? What is their project success rate? Ask for references from clients of a similar size and sector.
• Transparent pricing. Can they give you a clear price for your implementation or support before you commit? If the answer involves phrases like "it depends" without any indicative figures, proceed with caution.
• Own extensions. Partners who develop their own BC extensions demonstrate a depth of technical capability that resellers of third-party add-ons cannot match. It also means a single support relationship rather than multiple vendors.
• Responsive support. Ask how their support model works. What are typical response times? Who will handle your requests? Will you deal with senior consultants or a first-line helpdesk?

The First 90 Days with a New Partner

A good partner will not simply pick up where your previous one left off. The first 90 days should follow a structured approach:

Weeks 1-2: System audit. Your new partner should conduct a thorough review of your Business Central environment. This covers configuration, customisations, extensions, integrations, user setup, permissions and data quality. The audit identifies any technical debt, security gaps or configuration issues that need addressing.

Weeks 3-4: Relationship building. The partner should invest time understanding your business processes, pain points and priorities. This is not a box-ticking exercise. It requires conversations with your finance team, operations team and any other key users. The output should be a prioritised list of improvements.

Weeks 5-8: Quick wins. Based on the audit and discovery, your new partner should deliver a set of quick wins. These are changes that deliver immediate, visible value: fixing long-standing issues, improving report layouts, streamlining workflows or enabling features that were not previously configured. Quick wins build confidence and demonstrate competence.

Weeks 9-12: Roadmap. By the end of the first quarter, you should have a clear roadmap for the next 12 months. This covers planned improvements, upcoming Business Central updates that are relevant to your business and any larger projects such as new integrations or process redesigns.

Common Concerns Addressed

Will I lose data? No. Your data resides in your Microsoft tenant. Changing partner does not affect your data in any way. Your new partner accesses the same system, the same database and the same configuration.

Will there be downtime? No. A partner transfer is an administrative change, not a technical migration. Your system remains fully operational throughout.

What about in-flight projects? If your current partner is midway through a project, you have options. You can ask them to complete the project before you transfer, or your new partner can take over the work. If custom development is involved, ensure you have access to the source code or that the code is deployed as an extension in your environment.

What if my current partner is also my CSP? This is common and easily resolved. Your new partner can become your CSP, or you can purchase licences directly from Microsoft and use your new partner solely for implementation and support services.

Will my current partner make the transition difficult? Professionally run partners facilitate smooth transitions. If your current partner is obstructive, that tells you everything you need to know about whether you made the right decision to leave.