Business Central support after go-live
Hypercare through your first close, then an ongoing helpdesk, release management and enhancement service — without a lock-in that stops you leaving.
The first two weeks: hypercare
Every implementation includes a two-week hypercare window from go-live. This is not a phone number — it is our consultants working alongside your team through the first live transactions and, critically, the first period close. Most of what a new ERP user needs to learn only becomes visible under real closing pressure.
Ongoing support
| Service | What it covers |
|---|---|
| Helpdesk | User questions, transaction troubleshooting, posting errors and permission issues, handled by consultants who know your configuration. |
| Month-end assistance | Support during close — reconciliation queries, accrual handling, report variances and the statutory pack. |
| Release management | Microsoft ships two major Business Central waves a year. We test your configuration and extensions against each one before it reaches your production tenant. |
| User training | Onboarding for new staff and refresher sessions when roles change — the single biggest determinant of whether an ERP investment holds its value. |
| Enhancements | New reports, additional workflows, further Power Platform apps, and scope you deliberately deferred at go-live. |
| BIR change management | Configuration and process updates when BIR requirements change — including EIS rules and CAS amendment filings. |
Why release management matters more than clients expect
Business Central is a cloud service on a fixed release cadence. Microsoft's two annual waves land whether you are ready or not. An unmanaged tenant discovers a broken report or a changed permission behaviour during month-end close — the worst possible moment. Testing in a sandbox first turns that from an incident into a scheduled task.
No lock-in
You own your Microsoft tenant, your data and your configuration. Business Central is standard software, and any Microsoft partner can take over support. We do not hold your licences, and we do not build proprietary layers that only we can maintain.
Clients stay because leaving is easy and staying is better. That is the only retention model we are interested in operating.
Taking over someone else's implementation
We support Business Central tenants we did not build. The engagement starts with a configuration review — posting setup, permissions, extension inventory, and how far the tenant has drifted from a supportable baseline. You get the findings in writing before you commit to anything ongoing.
Frequently asked questions
What is included in hypercare?
Do you support Business Central tenants you did not implement?
What happens when Microsoft releases an update?
Are we locked in to your support?
Running Business Central without proper support?
We will review your tenant configuration and tell you what needs attention — in writing, before you commit to anything ongoing.