Services · Upgrade & migration
NAV to Business Central upgrade & migration
From any Dynamics NAV version to the current Business Central — code, data, integrations and people. Planned as fixed-price milestones, so the business case is clear before the work starts.
Scope
Everything a migration actually involves
An upgrade is more than converting code. All six workstreams below are part of the plan — and of the fixed price.
Upgrade assessment
Inventory of customisations, add-ons, integrations and data volume — resulting in a written migration plan with a fixed milestone quote.
C/AL → AL conversion
Customisations transformed into clean AL extensions: event-based, analyzer-clean and free of base-app modifications.
Data migration
Full-history upgrades along Microsoft's upgrade path, or lift-and-shift of master data and open entries — with reconciled trial runs.
Cloud & SaaS readiness
Universal Code compliance, replacement of .NET and file-system dependencies, tenant setup and environment strategy for BC online.
Integration re-platforming
Legacy interfaces rebuilt on API pages, OData and Azure services so they survive in the cloud and the next ten release waves.
Testing & go-live
Structured UAT with your key users, cutover plan, weekend go-live and hypercare in the weeks after.
Process
Five steps from NAV to Business Central
A migration succeeds on sequence and rehearsal: rationalise before you convert, convert before you migrate, and test everything twice before go-live weekend.
- 1
Assess
Object and usage analysis of your NAV database; keep / replace-with-standard / retire decisions per customisation.
- 2
Plan
Target platform choice (SaaS or on-prem), migration strategy, milestone plan with fixed prices and dates.
- 3
Convert
C/AL to AL transformation, extension refactoring, report rebuild and integration re-platforming.
- 4
Migrate & test
Trial data migrations, reconciliation, and user acceptance testing against real converted data.
- 5
Go live
Cutover weekend, final migration run, integration switch-over — then hypercare until the organisation settles.
Version coverage
Any starting point, one destination
Fifteen years across every NAV release means no archaeology surprises — classic client, RTC, C/AL, it has all been migrated before.
- NAV 2009 / R2
- NAV 2013 / R2
- NAV 2015
- NAV 2016
- NAV 2017
- NAV 2018
- BC 14 on-prem
- BC on-prem (any)
- → Business Central (current)
FAQ
Upgrades, answered
How long does a NAV to Business Central migration take?
A lightly customised single-company NAV 2016+ database typically reaches Business Central SaaS in eight to twelve weeks. Heavily customised, multi-company environments are four-to-six-month programmes. The assessment gives you a firm milestone plan before you commit to anything.
We are still on NAV 2009. Is that a problem?
No — older versions are routine. Very old databases are often better served by a lift-and-shift migration into a clean Business Central company than by a step-by-step full upgrade; the assessment compares both routes for your data.
Should we go to the cloud (SaaS) or stay on-premises?
Business Central online is the default for most mid-market organisations: no servers, automatic updates and the lowest long-term cost. On-premises remains valid for specific regulatory or integration constraints. We advise per case — and build cloud-compliant either way, so the door stays open.
What happens to our ISV add-ons?
Each add-on is checked for a Business Central successor. Where the vendor offers one, we migrate the data to it; where not, we replace it with standard functionality or a purpose-built extension. This is decided add-on by add-on in the assessment.
The assessment is a paid, fixed-price milestone on its own — if you stop after it, you still own a complete migration plan any partner could execute.
Ready to plan your Business Central migration?
Tell us your NAV version, company count and a rough idea of customisations. You will receive a proposal for a fixed-price assessment within one business day.