Migration and upgrade
Dynamics NAV to Business Central migration
Short answer
MS Dynamics Guys helps companies move from Dynamics NAV to Microsoft Dynamics 365 Business Central. We review the NAV version, custom code, data and connected systems, then plan a supported upgrade or a fresh implementation. The scope can include C/AL-to-AL conversion, extension development, trial data loads, reconciliation and cutover. If your partner already leads the migration, our specialists can join that team.
Start with the NAV system you actually run
A NAV migration starts with an inventory. The version matters, but custom objects, reports, add-ons and integrations often determine the work. MS Dynamics Guys records what must move, what standard Business Central can replace and what the business can retire.
| Review | Why it matters | First output |
|---|---|---|
| NAV version and deployment | Establishes the supported route and environment requirements | Source-system inventory |
| C/AL customizations | Code may need conversion or replacement | Keep, replace, rebuild or retire register |
| Add-ons and reports | Publishers and formats may change | Compatibility and ownership list |
| Data and history | Full history and selected data lead to different plans | Agreed data scope |
| Integrations | SQL access and legacy connections may not fit online | Interface replacement plan |
| Finance and operations | Totals and critical workflows must remain correct | Reconciliation and acceptance checklist |
Upgrade or reimplement?
An upgrade carries existing data and selected customizations through a supported route. Reimplementation configures Business Central around the processes you want now and moves the agreed data. MS Dynamics Guys compares both options before recommending a path.
- Upgrade may fit: useful history, processes that still fit, manageable custom code and compatible add-ons.
- Reimplementation may fit: old processes you want to redesign, extensive obsolete customizations, or a deliberate choice to move selected records and balances.
These are planning criteria, not a promise that either route is available for every installation. Confirm the exact source version and dependencies first.
What happens to C/AL customizations?
Business Central extensions use AL. A move from customized NAV requires a decision for each customization: replace it with a standard feature, use a supported app, rebuild it as an extension, or remove it. MS Dynamics Guys documents that decision and the test that will prove the replacement works.
Microsoft documents different NAV upgrade and migration paths. Its guidance includes an intermediate Business Central on-premises stage and distinguishes full migration from reimplementation. Use the route for your exact version; do not assume NAV can move straight into Business Central online.
Deliver the move in testable stages
Assessment
Inventory the system and agree the business reasons for the move.
Design
Choose the target, migration route, retained history and extension scope.
Build
Convert or rebuild agreed code, reports and interfaces.
Rehearse
Run trial migrations and test critical processes on realistic data.
Reconcile
Compare balances, open documents, stock and required record counts.
Cut over
Follow an agreed freeze, final-load and go/no-go plan.
Stabilize
Track issues, transfer documentation and agree ongoing support.
Your process owners approve acceptance and reconciliation. The cutover plan states when rollback remains possible and what changes after users begin processing in the new system.
Outsource the migration or add specialists
Choose a scoped migration project when you want MS Dynamics Guys to own agreed deliverables. Choose staff augmentation when your internal team or Microsoft partner already owns the program and needs AL developers, functional consultants or data migration engineers. The product scope and responsibilities stay explicit in either model.
What determines the cost and timeline?
The main drivers are the source version, custom object count, add-on compatibility, data quality, required history, integrations and the time your team needs for testing. A migration estimate should separate assessment, code, data, testing, cutover and support. Microsoft licenses and third-party app charges should be listed separately.
Send the version, company count, approximate database size, major add-ons, integration list and target date. If these are unknown, start with the inventory.
NAV migration questions
Can we keep using NAV while the migration is prepared?
Migration preparation normally uses separate environments. MS Dynamics Guys agrees the data refresh, change-control and final cutover plan so work on the old system does not silently invalidate the migration. The exact freeze and downtime depend on the tested route.
Will every customization move unchanged?
No. Some customizations can be replaced by standard Business Central features. Others need AL development or a compatible app. Review each item before estimating the work.
Can MS Dynamics Guys work with our existing partner?
Yes. We can add specialists or deliver an agreed technical work package. Agree who owns architecture, functional decisions, licensing, cutover and final acceptance before work starts.
Do we need to move all transaction history?
That is a business and data-scope decision. Compare operational reporting needs with the cost and feasibility of migration. An archive can remain part of the plan where appropriate.
Partner-led NAV-to-Business Central staffing
The Ardent / Halden NAV-to-Business Central engagement was partner-led. MS Dynamics Guys supplied a C/AL developer and a separate data migration engineer.
Your next step
Plan your NAV to Business Central move
Share your NAV version, customizations and target date. MS Dynamics Guys will help define the next assessment or specialist role.
Product documentation referenced on this page
- Microsoft Learn: Migrate Dynamics NAV to Business Central online Microsoft Learn, checked October 29, 2026