How to sell Microsoft Business Central as an MSP (without building a BC team)

Selling Microsoft 365 to a growing SME client is straightforward. You know the product, you know the licensing model, and the conversation runs on familiar ground. Selling Microsoft Dynamics 365 Business Central to the same client is structurally different, even though it sits in the same Microsoft ecosystem. The licence side looks like Microsoft 365 with a few extra steps. The delivery side does not.

This is the post that explains both halves. If you run an MSP and you have clients on Microsoft 365 who are starting to outgrow their accounting software, Business Central is the natural upsell in your ecosystem. The question is whether you can deliver it without hiring BC consultants you cannot yet afford. That is what this guide is for.

Why MSPs are well placed to sell Business Central

Business Central is Microsoft's mid-market financials and operations platform. It is designed for businesses that have outgrown QuickBooks, Xero, or Sage but are not large enough for a tier-one ERP like NetSuite or SAP Business One. Most successful deployments sit in the £5m to £30m revenue band.

If you are an MSP, you already have several structural advantages with this audience that a generic BC consultancy does not.

You have the relationship. Your finance manager contact at a growing manufacturer or wholesaler trusts you with their systems. When they start to feel the pain of running their business out of Xero and a stack of spreadsheets, you are the person they will ask first, not a BC consultancy they have never heard of.

You already sell Microsoft. You are signed up to the Microsoft AI Cloud Partner Program, you have a Microsoft Partner ID, and you transact Microsoft 365 licences through the Cloud Solution Provider programme. Business Central rides on the same partner infrastructure.

You think in recurring revenue. The MSP business model is built on monthly subscriptions and ongoing service contracts. Business Central is a per-user-per-month licence with similar economics. It fits how you already price and deliver, structurally if not operationally.

You understand the Microsoft stack. Business Central integrates natively with Microsoft 365, Power BI, Power Automate, Power Apps, and Azure. You already manage the surrounding environment. The client does not have to choose between vendors.

The barrier is not whether you can sell Business Central. It is whether you can deliver it once the contract is signed.

What the licence side looks like (the easier half)

If you are already a Microsoft partner, the licensing route to Business Central is well-trodden. There are three things to set up.

Cloud Solution Provider enrolment

You need to be enrolled in the CSP programme if you are not already. The CSP programme has two routes.

Indirect Reseller is the lower-barrier path. You sit underneath an Indirect Provider (a distributor like Pax8, Sherweb, or Crayon) who handles the relationship with Microsoft, manages billing, and provides technical and operational support. You sell to the end customer; the provider sells to you. This is how most smaller MSPs operate.

Direct Bill means you have a direct relationship with Microsoft for billing and licence management. The bar is higher, with revenue thresholds, support requirements, and more operational overhead. It is generally only worth it for MSPs doing significant Microsoft volume.

For Business Central specifically, both routes work. If you are already a CSP Indirect Reseller for Microsoft 365, you can sell Business Central licences through the same distributor without changing your model.

Business Central licensing tiers

Business Central has two main user licences.

Essentials is the standard licence, covering finance, sales, purchasing, basic inventory, project costing, and the standard reporting layer. It is the licence the majority of users will hold.

Premium adds service management and manufacturing modules. Most SMEs only need Essentials, and you can always upgrade users to Premium later if the business case appears.

There is also a Team Member licence, which gives limited read and light-write access for users who only need to view records, approve documents, or log time. A typical BC deployment mixes a small number of full Essentials licences for finance and operations users with a larger number of Team Member licences for everyone else. The licence mix is one of the things that makes the commercial case work at SME scale.

The Partner Center setup

Once you are in CSP and want to start transacting Business Central licences, you set up the customer relationship in Partner Center. You request a reseller relationship with the customer, they accept, and licences flow from there.

If you want to be able to access the customer's Business Central environment to provide support, you set up delegated administrative privileges. This is what Microsoft calls DAP, or GDAP for more granular control. It lets your technicians log into the customer's BC tenant without needing separate licences, which keeps your operational costs sensible.

That is the licence side. None of it is hard, none of it is novel for an MSP, and most of it is the same plumbing you already have for Microsoft 365.

What the delivery side looks like (where it gets hard)

This is where the gap usually shows up. You have sold the licence. The customer is excited. The contract is signed. Now you have to move them from their current system to Business Central, and Business Central is not Microsoft 365.

Here is what a typical Business Central onboarding involves.

Data migration from the source system

The customer is on QuickBooks, Xero, Sage 50, Dynamics GP, or sometimes a homegrown spreadsheet setup. Their data lives in that system. You need to get it into Business Central without breaking the running business.

Business Central has built-in migration assistants for some sources (QuickBooks being the cleanest path). For Xero, Sage, and others, the official route is Microsoft's RapidStart Services, which means hand-mapping data through CSV files. Experienced BC partners typically build their own migration tooling to handle this faster, but that tooling does not exist if you are starting out.

Migration is also not just moving the data. It is reconciling the data. The chart of accounts in QuickBooks rarely maps cleanly to a Business Central chart of accounts. Customer and supplier records often have duplicates. Item master data needs categorising. Opening balances need cutting over at a specific date with reconciliation against the source system.

This is the bit where projects go wrong. It is also the bit MSPs are least equipped for, because the work is finance-domain work, not IT work.

Chart of accounts and posting setup

Business Central uses a structured chart of accounts with posting groups that link customers, suppliers, and items to general ledger accounts. The customer's existing chart of accounts may have grown organically over years and need rationalising before it goes into BC. The posting groups have to be designed before any transactions can flow.

This is bookkeeper-and-accountant territory. The work is not technically difficult, but doing it badly leads to a system the finance team will resent for years.

Configuration and dimensions

BC has a concept called Dimensions, which lets you slice transactions by department, project, location, cost centre, and other categories. Setting these up well at the start is the difference between a system that gives the customer real visibility and one that reproduces their old spreadsheet pain in a different shape.

This is consulting work, not IT work. It requires sitting with the finance team, understanding how they want to report, and translating that into a BC configuration.

Go-live cutover

The cutover from the old system to BC has to happen at a specific point in time, typically month-end or period-end. Sub-ledgers have to balance. Opening balances have to be loaded and reconciled. The team has to be ready. There is usually a parallel running period where transactions go into both systems while the team builds confidence in BC.

If anything is missed in cutover, the customer is doing manual reconciliations for weeks or months. The finance manager remembers this. They also remember who handled it.

Training and post-go-live support

The finance team has to know how to use Business Central to do their day job from go-live day one. That means training before go-live, not after. It means realistic walk-throughs of their processes in BC, not generic product training. It means a support model where the finance manager can call someone who knows what they are doing during the first month.

Once the customer is live, support is not "have you tried turning it off and on again." It is "the bank reconciliation is not matching, can you look at it." The MSP support model is built for infrastructure issues; the BC support model has to handle finance-domain questions. The skills required are different.

None of this is impossible. None of it requires you to be a chartered accountant. But it does require BC product knowledge, finance domain knowledge, and a delivery process that handles all of the above. That is what an MSP starting out does not have.

Three ways MSPs typically handle this gap

There are three credible routes, and the right one depends on how much BC business you expect to do.

Route 1: Build a BC delivery team internally

Hire one or two BC consultants. Train your existing support team. Build internal process for migration, configuration, and post-go-live support. Develop the playbook over time.

This is the right route if you expect to do meaningful BC volume (sustained, more than five or six deployments a year) and you are willing to invest twelve to eighteen months building the capability before it pays back. The downside is the upfront cost and the risk. BC consultants in the UK are expensive, the market for talent is competitive, and a junior team learning on real customer projects produces variable outcomes.

Route 2: Refer to a Microsoft BC partner

Pass the customer to a traditional BC partner once the conversation gets serious. You keep the Microsoft 365 relationship. The BC partner runs the BC engagement.

This is the path of least resistance, but it has a real cost. You give up the Business Central licence margin (which is the most lucrative part of the deal), you lose visibility into the customer for the duration of the BC project, and you risk the BC partner replacing you in the trusted-advisor seat. The customer's loyalty starts to move toward whoever solves their biggest current problem, and during a six-month implementation, that is the BC partner.

Route 3: Partner with a wholesale BC delivery layer

This is the route that works for MSPs who want to sell BC at smaller deal sizes profitably, without building internal capability and without losing the customer to a referral partner.

In this model, you keep the client relationship, the contract, the invoicing, and the recurring revenue. You sell the BC licence through your existing CSP. A wholesale partner handles the delivery work behind you: data migration from QuickBooks, Xero, Sage, or GP; chart of accounts and posting setup; BC configuration; cutover planning; training; and post-go-live support. All of which can be branded as your firm if you want to white-label the customer experience.

You can be as involved or as hands-off in the delivery as you want. The work can be partner-led, where you deliver using the wholesale platform's tooling. It can be wholesale-led, where the platform handles delivery end-to-end and you bring the client. Or it can be client-led, where the customer self-serves through a portal with you and the platform in the background.

The commercial model is wholesale. The platform charges you a per-deployment fee. You bill the customer whatever you choose. The difference is your margin. You retain the licence margin separately through your CSP.

Where this leaves you as an MSP

If you have read this far, you are probably in one of three places.

You have customers asking about Business Central and you have been turning them away or referring them out because you have no delivery capability. In which case, the wholesale partner route is built for you.

You are doing one or two BC deployments a year, you are losing money on them because they take too long, and you cannot justify a full BC hire. The wholesale partner route again.

You are doing serious BC volume and considering whether to build internal capability. The wholesale partner route can bridge you while you decide, or you go all-in on building a team. Either is defensible.

The reason this article exists is that the third option, partnering with a wholesale BC delivery layer, did not really exist as a serious commercial proposition for MSPs until recently. The traditional BC partner ecosystem is built around larger implementations at tier-one consultancies. The wholesale partner-platform model is new. It exists because the unit economics of BC delivery at SME scale only work with a different operating model, and the partners who succeed in it understand that the customer relationship is the asset, not the delivery skill.

A practical next step

Qwyk is the wholesale BC delivery layer described above. We have a partner pack written for exactly this audience. It walks through the model, the commercial structure, the migration capability, and what working together looks like. You can also get more information on our partner page.

If you want to skip the pack and talk to someone, you can book a thirty-minute partner conversation through the same page. There are no slides, just a walk-through of the platform on a real example and an honest assessment of whether it fits your delivery model.

Business Central is a meaningful upsell opportunity for any MSP serving growing SMEs. The licence side is easy. The delivery side is where most MSPs hit the wall. That wall does not have to be there.