Service · Upgrades and cloud moves
Whether you are on an old NAV build, an on-premises Business Central, or heading to the cloud, we plan each hop, review every customisation, rehearse the cutover and keep your data intact. Most upgrade problems are data problems, so we test the data first.
What is included
Upgrade assessment and impact analysis
Customisation review: convert, replace or retire
Data integrity checks before every hop
Test environments and validation cycles
A written, repeatable upgrade manual
What you get
- A route plan with a risk list for each hop
- Cutover rehearsed on a copy of your own data
- Post-upgrade support and an update cadence
Best for
Companies on NAV, older Business Central versions, or on-premises installs planning a move to the cloud.
Try it
Plan your route, hop by hop.
Each hop gets its own data checks, test run and rollback point, so a failure is small and recoverable.
Ask for a path reviewHop 1: BC14 to BC18
Extension-first. Direct changes to base code are no longer an option.
Watch for: Data problems, such as broken default dimensions, tend to stop upgrades here.
Hop 2: BC18 to BC25
The on-premises target used in this planner.
Watch for: Check the SQL edition, memory and lock settings before the upgrade window, not during it.
Hop 3: BC25 to Cloud
A hosted tenant. Extensions only, no direct database access, and updates arrive continuously.
Watch for: Integrations and reports that read the database directly must be redesigned.
In practice
Related case studies
Tell us where your system is today.
Share your version, your goal and your deadline. You get a straight first view of the route and the risks, from someone who has done it.