Microsoft doesn't implement Business Central for you. A partner does. Here's what a Business Central partner actually does, what to ask before you commit, and how to find one matched to your industry, size and budget.
A Business Central partner is a Microsoft-accredited organisation licensed to sell, implement and support Dynamics 365 Business Central. For the vast majority of small and mid-sized businesses, Microsoft does not deliver the project itself. It licenses the software and relies on a partner network to handle everything that turns that licence into a working finance and operations system.
In practice, that means the partner is responsible for scoping your requirements, configuring the chart of accounts and dimensions, migrating historical data from your existing system, building or sourcing any extensions you need, integrating Business Central with the other tools you run, training your team, and supporting the platform once it is live.
Because the software itself is identical whoever you buy it from, the partner is the variable. Two organisations can run the same Business Central licences and have wildly different experiences of it, entirely because of how it was set up and who supports it. That is why the partner decision matters more than the product decision.
Scope varies by engagement, but a competent partner covers all of the following, either directly or through a named specialist in their team.
Understanding how your finance and operations processes actually run today, where the pain sits, and which of those processes Business Central should change rather than replicate. Weak discovery is the single most common cause of a disappointing implementation.
Advising on Essentials versus Premium, how many full users you genuinely need against Team Members licences, and what the total cost looks like across licensing, services and year-two support.
Setting up the chart of accounts, dimensions, VAT, approval workflows and user permissions, then mapping and migrating opening balances and historical transactions from Sage, Xero, QuickBooks or a legacy NAV instance.
Connecting Business Central to the systems around it, from Power BI reporting and Microsoft 365 through to ecommerce platforms, payroll, warehouse tools and industry-specific applications from Microsoft AppSource.
Getting your finance team, budget holders and approvers confident in the system before go-live, and supporting them through the first close. Adoption is where most of the promised efficiency is either realised or lost.
Handling day-to-day queries, managing Microsoft's twice-yearly release waves, and continuing to develop the platform as your business changes. This is a long-term relationship, not a one-off project.
Most organisations shortlist partners on price and Microsoft credentials. Both matter, but neither predicts whether the implementation will go well. The stronger signals are industry familiarity, the seniority of the people who will actually be on your project, and how the partner behaves when you push back.
Ask who is delivering the work, not who is selling it. It is common for an experienced consultant to run the sales conversation and a much more junior team to deliver the project. Ask for the names, the split of their time, and whether the consultant in the room will still be involved at go-live.
Ask for references in your sector and at your size. A partner with deep manufacturing experience may be an awkward fit for a professional services firm billing time against projects, and a partner used to 200-user enterprises will often price and staff a 15-user rollout badly. Sector fit shows up in how quickly they understand your process without you having to explain it.
Ask what they would not do. A partner willing to tell you that a requested customisation is a bad idea, or that a standard Business Central process should replace one of your existing workarounds, is usually the one that keeps your total cost of ownership down. Partners who agree to everything tend to build expensive, fragile systems.
Finally, look at what happens after go-live. Ask about the support model, response times, who you contact, whether support hours roll over, and how release-wave updates are tested. Support is where most of the relationship lives, and it is the part most often glossed over during the sales process.
These separate partners quickly, and the answers are easy to compare side by side.
Names, roles and how much of their time is allocated to you. Confirm whether the consultant leading the sales conversation stays involved through to go-live and beyond.
Ask for two references at a similar size in a similar industry, and ask to speak to the finance lead rather than the project sponsor who signed it off.
Total licensing, support retainer and expected change requests. Implementations are quoted; the ongoing cost is often not, and it is where budgets get caught out.
Microsoft ships two major updates a year. Ask how the partner tests them against your configuration and any extensions before they reach your live environment.
Response times, escalation, named contacts, and whether training questions count against your support hours or sit outside them.
A partner who can name a requirement they would challenge, and explain why, is thinking about your total cost of ownership rather than the size of the statement of work.
There are two separate costs and they are often conflated. Microsoft sets the licence price per user per month, split across Essentials for core finance, sales, purchasing and inventory, and Premium which adds service management and manufacturing. Team Members licences cover light users who need to read data, approve, or enter timesheets, and cost a fraction of a full licence.
Partner fees sit on top and cover the implementation itself. A finance-only rollout for a small team migrating from Xero or QuickBooks, with clean data and standard processes, sits at the lower end. Costs rise with the number of entities, currencies and warehouses, the volume of historical data to migrate, the number of integrations, and any custom development.
The variable most people underestimate is their own data. Time spent cleaning suppliers, customers, stock codes and opening balances before migration reduces the partner's hours and improves the result. Time spent arguing about it during the project inflates both.
Budget for year two as well as year one. Licensing recurs, support is usually a monthly retainer or a block of hours, and most organisations make further changes within twelve months as they find things they want to automate. Read our breakdown of what to expect in the guide to Business Central pricing.
We work with the Microsoft partner community across the UK and can help match you to a partner suited to your sector, size and the shape of your project. That means understanding your requirements first, then pointing you towards the partners genuinely equipped to deliver them, rather than the ones with the largest sales team.
If you are earlier in the process and still weighing whether Business Central is the right platform, it is worth reading how it compares to the accounting tools most organisations outgrow, and how it applies in your industry. Both help you arrive at a partner conversation with a clearer brief, which almost always produces a better quote and a better project.
Tell us about your business, your current finance system and what you need Business Central to do. We'll help you shape the brief and point you towards partners equipped to deliver it.
A Business Central partner is a Microsoft-accredited organisation licensed to sell, implement and support Dynamics 365 Business Central. Microsoft does not sell or implement Business Central directly to most small and mid-sized businesses, so the partner handles licensing, configuration, data migration, training and ongoing support.
You can buy licences directly, but almost every organisation works with a partner for the implementation. Business Central is an ERP rather than a plug-and-play accounting tool, and the value comes from how it is configured around your chart of accounts, approvals, stock and reporting.
Licensing is set by Microsoft and charged per user per month across Essentials and Premium tiers. Partner fees are separate and cover implementation, data migration, customisation, training and support. A finance-only rollout for a small team is a few thousand pounds of services; a multi-entity or manufacturing implementation with integrations costs considerably more.
A straightforward finance-first rollout for a single entity typically runs six to twelve weeks. Multi-entity, multi-currency or manufacturing projects with significant integration work commonly take four to six months. Data quality and the availability of your own team are usually the biggest factors in the timeline.
Yes. Your licences and your data belong to you, and the partner relationship can be transferred. It is worth checking during procurement whether any custom extensions are owned by you or licensed from the partner, as that affects how clean a transfer is.
Most implementations are delivered remotely, so location matters less than sector experience and support quality. UK-based partners do bring an advantage on VAT, Making Tax Digital and local payroll integration, which is worth weighing if your finance processes are UK-specific.
A partner is the accredited organisation that can supply licences and take contractual responsibility for delivery. A consultant is an individual with Business Central expertise, who may work for a partner or independently. Independent consultants are useful for reviews and optimisation, but you will still need a partner for licensing.
