Keep
$450/month
Keeps what we built working through every release wave.
- Upgrade testing every release wave
- Monitoring
- Fixes for anything we built that a Microsoft update breaks
- 2 hours a month of changes
- 3-business-day response
Home / Support & upgrades
Support & upgrades
Business Central support, built to survive upgrades.
Business Central gets two major updates a year plus smaller monthly ones. The worry we hear most is that the next one will break a customization and nobody will notice until Monday morning. Here is how the update cycle works, and what we do at each step so it doesn’t happen to you.
The April release waveOctober runs six months later
- Preview: March
- Update window: April to August
- Grace period: September
- Enforced: from October
The update cycle
How a Business Central update reaches your company.
Major updates, called release waves, arrive in April and October. Each one follows the same four stages. This is the April wave; the October wave runs six months later.
-
March · about a month ahead
Preview
Preview sandboxes open. Microsoft automatically tests per-tenant extensions for technical problems and emails your notification contacts if it finds any.
-
April to August · 5 months
Your update window
Your admin picks the update date. If an update fails, it is rolled back and tried again 7 days later.
-
September · 1 month
Grace period
The update can no longer be postponed. Your users may see warnings in Business Central about incompatible extensions.
-
From October
Enforced update
Microsoft can uninstall an extension that blocks the update. Its data is kept, but the feature is gone until a compatible version is installed, and it is not reinstalled automatically.
Microsoft only checks that an extension is technically compatible. Checking that it still does the right thing for your business is the developer’s job. If an extension blocks a critical security update, it may be uninstalled within 14 days.
Sources: Microsoft Learn, update cycles (updated October 2026) and maintaining apps and per-tenant extensions. The current wave, version 29, can be scheduled any time up to February 2027.
What we do
We find the break months before your update does.
Microsoft announces breaking changes at least a year ahead and publishes preview builds of each release. We use both, so by the time your update window opens, the work is already done.
All year
Every change is built and tested automatically
We use AL-Go for GitHub, Microsoft’s free, open-source build pipeline. Each time the code changes, it is compiled and its automated tests run, and the same pipeline also builds against Microsoft’s upcoming versions. A problem shows up as a failed check, not a phone call from your warehouse.
Preview
We test your extensions on the preview release
We install what we built for you in a preview sandbox, run the tests and walk through your key screens on desktop and phone. Anything that needs changing is fixed while there are still months to spare.
Update window
We tell you when it is safe to update
Once a verified version is ready, we agree on an update date with you and check your environment afterwards. Errors from our screens can be sent to Application Insights, Microsoft’s monitoring service, so we can see a problem before anyone reports it.
Telemetry goes to your own Azure Application Insights resource; we don’t store your business data.
Before the grace period
A written commitment on turnaround
On every plan, a compatible version of everything we built is ready before your grace period starts, so nothing we built is left blocking your update when enforcement begins. Day-to-day response times are written into each plan below.
Our commitments
Your code, your choice of developer.
Being tied to one developer is a fair fear with custom software. These hold whether or not you take a support plan.
You own the source code
It lives in a repository you can access, on GitHub or Azure DevOps, not only on our machines.
Clean AL
Written to Microsoft’s development guidelines, with prefixes and namespaces so new Microsoft fields can’t collide with ours, a classic cause of upgrade breaks.
Documentation
What each extension does, how it is set up and how it is deployed, written for the next person to read it.
No lock-in
Any competent Business Central developer can pick up our work. If you move on, you keep everything.
Extensions we didn’t build
We can adopt the extension you already have.
If your original developer has moved on, or updates keep catching you out, we can take over an existing Business Central extension. It starts with a code review, so you know what you have before you commit to anything.
Code review
We read the source, build it against the next Business Central release and look for obsolete code, name collisions with Microsoft’s fields, missing tests and slow add-ins.
Written findings and a quote
You get a plain-English report of what is at risk, what we’d fix first and what bringing it up to standard would cost.
On to a plan
Once it is up to standard, it is covered like anything we built: tested every release wave, monitored and fixed if an update breaks it.
We need the source code to support an extension. If you only have the installed app file, talk to us first and we’ll look at the options.
Support plans
One fixed monthly fee covers both release waves.
Every plan includes upgrade testing, monitoring and fixes when a Microsoft update breaks something we built. The difference is how much change time you get and how fast we respond.
Care
$1,100/month
For teams that keep improving their screens.
- Everything in Keep
- 6 hours a month of changes
- 1-business-day response
- Quarterly UX review
Run
$2,400/month
For businesses that run daily work on what we built.
- Everything in Care
- 15 hours a month of changes
- Same-business-day response for critical issues
- A named developer
Work outside your plan is $165 an hour. Prices in US dollars.
See all pricingFree Business Central UX review
Send us the screen your team hates most.
In 30 minutes we count the steps your team takes today and sketch the same task as one screen, on desktop and phone. You keep the written summary. No slides, no obligation.