Business Central Support: What a Good Partner Must Actually Deliver (2026)

Key takeaways

• BC support is more than ticketing: a good partner knows your installation, responds quickly, and prepares release waves proactively — before they go live.
• Microsoft release waves (April & October) are the most common source of unplanned incidents. A support partner tests your extensions against the preview in a sandbox first.
• SLA model comparison: hour budgets (cheap but reactive), retainers (predictable, named contact) and flat-rate (rarely sensible for BC). For most mid-sized businesses, a retainer model is the best fit.
• 8 questions to ask any BC partner before you sign a support contract.

What 'Business Central support' actually means

The word 'support' sounds like a helpdesk. In the ERP context it is considerably broader. Business Central support covers the reactive part — fixing errors, answering key-user questions, unblocking stuck postings — but also the proactive side: preparing release waves, monitoring interfaces, applying small adjustments and keeping master data clean.

The difference between these two dimensions separates good BC partners from poor ones. A partner who only reacts to tickets is cheaper per hour — but more expensive per year, because with every update you have to find out for yourself what has changed.

• Reactive support: error fixes, key-user questions, posting blockages, permission issues
• Proactive support: release-wave preparation, interface monitoring, small customising adjustments
• Strategic support: licence optimisation, roadmap advice, prioritising new requirements

The 5 most common mistakes in ERP support

Most support problems in day-to-day ERP operations don't arise from system errors but from structural weaknesses in the support model itself. Here are the five most common:

• 1. No named contact: every ticket lands with a different consultant who has to understand your installation from scratch. Result: diagnosis time doubles, issues recur.
• 2. Purely reactive, no monitoring: interfaces fail silently — nobody notices until accounting sees empty bank statements the next morning.
• 3. Release waves come as a surprise: Microsoft's April and October updates are not tested beforehand in a sandbox. Extensions break; go-live day becomes crisis day.
• 4. No clear escalation path: when production goes down, nobody knows who to contact or within what time frame to expect a response.
• 5. Support and development are separate: the support partner knows the application, not the code. Small adjustments take weeks because a third provider has to be brought in.

Release waves in April and October: what must happen beforehand

Microsoft automatically updates Business Central Online twice a year — in April and in October. The preview version is typically available 6–8 weeks earlier. In this window a good support partner must complete the following:

First: test extensions against the preview version. Every AL extension, every AppSource add-on and every interface must be checked for compatibility. Incompatible extensions are disabled by the system — this is the most common cause of support emergencies after a release update.

Second: identify breaking changes. Microsoft publishes 'What's New' documentation for every release wave. A structured partner filters the changes relevant to your installation and discusses the impact with your key users — before the update goes live.

Third: communication plan for your users. What changes in the UI? Which reports look different? Which new features can you use immediately? This prevents confusion and callbacks on the first day after the update.

Business Central SLA models compared

There are three common models for Business Central support contracts. None of them is automatically right — it depends on your operations.

• Hour budget (pay-as-you-go): you buy a block of consultant hours. Cheap for low support demand. Downside: no named contact, no proactive element, release-wave preparation costs extra.
• Retainer model (monthly flat fee): you pay a fixed monthly fee for a defined service package — named contact, agreed response times, release-wave support included. For most mid-sized businesses this is the most sensible model.
• Flat-rate (all-inclusive): all requests and adjustments at a fixed price. Rarely economically sensible, because in this model the partner has an incentive to minimise effort rather than fully process your requirements.

8 questions to ask every BC partner

Before signing a Business Central support contract, ask these questions — and insist on concrete answers:

• 1. Who is my named contact — and what happens when that person is on holiday?
• 2. What response times are contractually guaranteed — for critical errors and for normal requests?
• 3. How is preparation for Microsoft release waves handled — and is that included in the price?
• 4. Do you have experience with our specific industry or customisation context?
• 5. How is a production outage escalated — and by when can I expect an initial diagnosis?
• 6. Can you also handle small adjustments and reports during live operation — or do I need to place a separate order for that?
• 7. What does onboarding look like — how long until you genuinely know my installation?
• 8. Are there reference customers with a comparable installation I can speak to?

Frequently asked questions

How much does Business Central support cost per month?

That depends on the model and the size of your installation. An hour budget starts at a few hours per month; a retainer model with a named contact, defined response times and release-wave support typically costs more but is predictable and includes the proactive element. Contact us for a concrete assessment — after a brief initial call we can give you a realistic range.

Can I switch my existing BC partner?

Yes. A partner change in Business Central Online is technically straightforward: the new partner is registered as the responsible CSP partner in the Microsoft admin portal. The real work lies in the knowledge transfer: at the start we take time to thoroughly document your installation, extensions and open issues — so no context is lost.

What is the difference between Business Central support and a maintenance flat fee?

'Maintenance flat fee' is often an older term from the on-premises era, primarily describing system operations (server updates, database upkeep). In the cloud world this part falls away — Microsoft takes over infrastructure and updates. What remains, and what Business Central support means today, is professional and functional care: user questions, adjustments, release waves, interfaces, permissions.

How long does onboarding take with a new BC support partner?

Realistically 2–4 weeks to a complete picture of your installation. In this phase we inventory all extensions, interfaces, permission structures and open issues and conduct a handover with your previous partner or IT team. After that we can handle support requests without having to ask about your system history.

Does Central Solution also offer support for heavily customised Business Central installations?

Yes — that is our focus area. We are AL developers ourselves and know the complexity of custom extensions from our own project experience. With heavily customised installations, standard helpdesk support quickly reaches its limits because it doesn't know the custom logic. We can deliver support and further development from a single source.