Business Central upgrade planned around your extensions
We assess your environment, fix extension compatibility, rehearse the data upgrade in a copy of production and support the cutover, so moving to a current version is a scheduled event, not a scramble.
The challenge
Upgrades go wrong at the edges: an extension that depends on an obsoleted object, an integration that assumed an old API, a report layout nobody documented. On-premises customers choose when to upgrade; SaaS customers face updates on Microsoft's schedule. Either way, preparation decides the outcome.
Technology we use
How we approach it
The same four steps apply whether the project is a rollout, an integration or a fix. Only the depth changes.
Assess
Versions, extensions, dependencies, integrations, reports and data volume are inventoried, and the supported upgrade path is confirmed.
Prepare the code
Extensions are updated for platform and application changes, obsolete objects and changed events.
Rehearse
The upgrade is run against a copy of production data, and users test real scenarios.
Cut over
A dated cutover plan with a rollback option, followed by support through the first working days.
What is included
- Upgrade path confirmation and readiness assessment
- Extension compatibility review and code updates
- Sandbox upgrade rehearsals with production data
- Integration and API compatibility testing
- Report layout and permission set review
- User acceptance testing support
- Production cutover and rollback planning
- Post-upgrade support
What you get from it
- Predictable downtime and a rehearsed cutover
- Extensions and integrations verified before users depend on them
- Access to current features and security fixes
- A cleaner extension set after obsolete code is removed
Related pages
Related services
Read more
NAV to Business Central Migration: Upgrade, Cloud Migration or Fresh Start?
Three realistic routes off Dynamics NAV, how to choose between them, and what to check before you commit.
Business Central SaaS vs On-Premises: How to Choose
The real trade-offs between Microsoft-hosted and self-hosted Business Central, and the questions that decide it.
Frequently asked questions
How often does Business Central update?
Microsoft ships two major release waves a year, in spring and autumn, plus regular monthly updates. SaaS customers receive updates on Microsoft's schedule with some control over timing. On-premises customers install updates themselves and choose when to move versions, within Microsoft's support lifecycle.
Can we skip versions when upgrading?
Upgrade paths are defined by Microsoft. Some direct jumps are supported and others need intermediate steps. We confirm the supported path for your exact version before planning.
Can NAV be upgraded to Business Central?
Yes, through supported upgrade paths or by migrating data into a new Business Central setup. See our NAV to Business Central migration page for how we compare the options.