Skip to content
Bitta Apps
Implementation & migration

NAV to Business Central Migration: Moving Customizations

Microsoft's upgrade path, a rebuild, replace or retire decision for each customization, how C/AL maps to AL extensions and events, and how to test the data upgrade.

Business Central Report Layouts with an obsolete report highlighted, beside the headline Rebuild, replace or retire
On this page

A NAV to Business Central migration carries customizations forward only as AL extensions, because Business Central online runs extensions only. Microsoft's full-migration route goes through Business Central 14 on-premises, then version 25 or later, then the cloud migration tool. Dynamics NAV 2017 extended support ends January 11, 2027. Before any data replicates, each C/AL customization should be retired, replaced by a standard feature or app, or rebuilt as an extension.

For finance, operations and IT leaders and developers running customized Dynamics NAV, this guide covers the NAV to Business Central upgrade path, customization decisions, AL conversion, custom data and testing. Sources were checked on 2026-11-10.

Plan your NAV migration. Book a free discovery call to discuss your NAV version, customizations and practical next steps. Detailed assessment is agreed separately. Use the short form on the Business Central partner page, or call (626) 766-9732.

Why NAV customizations decide the migration

A NAV migration combines process review, data migration, application upgrades and extension design. Carrying every old modification forward preserves complexity the business may no longer need.

Microsoft's customization migration guide sets the rule plainly: Business Central online runs extensions only, and retained C/AL customization code must become AL extensions before full migration. It adds two planning constraints:

  • Data from tables with code customizations can't be carried forward from Dynamics NAV unless an extension installed both on-premises and online handles it.

  • Breaking schema changes, such as removing or renaming fields, prevent extension synchronization and can cause data loss.

The Business Central online upgrade overview also notes that technical upgrades are not a concept in Business Central online. Microsoft manages the updates. A customization has to be built to survive them.

The clock matters too. Microsoft's 2027 end of support list shows Dynamics NAV 2017 leaving extended support on January 11, 2027, and the 2028 end of support list shows Dynamics NAV 2018 leaving on January 11, 2028, both in Pacific Time. Earlier NAV versions are already out of support: extended support for Dynamics NAV 2016 ended on April 14, 2026.

The NAV to Business Central upgrade path

No NAV version uses the standard cloud migration route without an on-premises upgrade. Microsoft's Migrate Dynamics NAV to Business Central online article documents these routes:

Starting version

Route Microsoft documents

NAV 2015, 2016, 2017 or 2018

Business Central 14 on-premises, then version 25 or later on-premises, then Business Central online

NAV 2013 or 2013 R2

NAV 2018, then version 14, then version 25 or later, then online

NAV 2009 SP1 or 2009 R2

NAV 2013 or 2015, then NAV 2018, then version 14, then version 25 or later, then online

Version 14 is the hinge. It is the last version that supports C/AL, and the supported upgrade paths page states that the path from NAV 2015 to 2018 to Business Central 2026 release wave 2 (version 29) runs through version 14 and version 25, and requires converting the application from C/AL to AL. Since version 26, a direct upgrade from version 14 to the latest release isn't supported. The cloud migration prerequisites then require Business Central 25.0 or later. SQL Server sources need SQL Server 2016 SP1 or later and compatibility level 130 or higher; Azure SQL Database is also supported.

Microsoft also documents a Business Central 14 reimplementation tool. It moves master data, open orders, opening balances, setup and a defined subset of posted history from version 14, without the climb to version 25. Legacy C/AL customizations and their data are not migrated by default, and Microsoft labels the tool a preview feature that isn't meant for production use. Confirm its status at project start. Dynamics GP has its own cloud migration path, covered in the Dynamics GP end of support and migration timeline.

Build the customization inventory first

Microsoft's guide makes the inventory the first checkpoint: catalog all modified objects, ISV add-ons and integrations, and classify each by complexity. In practice the list is wider than the object designer shows. Include:

  • Modified and new tables, pages, codeunits, reports, XMLports and queries

  • ISV add-ons, with the publisher and whether a compatible Business Central version exists

  • Integrations, file drops, job queue entries and scheduled tasks

  • Permission sets, control add-ins and .NET assemblies

  • Data held in custom tables or added fields

Map each item to a business owner, actual usage, compliance need and operational dependency. Usage evidence matters. A modified report that nobody has run for two years should not get the same treatment as a posting rule required by contract.

Then separate data from behavior, as Microsoft recommends. Customizations that carry data, such as custom tables and added fields, must be handled as extensions before full migration, or their data will not be carried into online. Behavior-only changes, such as page layouts, are easier to defer or retire.

Rebuild, replace or retire: decide per customization

Decide whether the business still needs each outcome and which supported approach can provide it.

Decision

Use it when

Target

Retire

The process is unused, duplicated or no longer required

No replacement; archive documentation and data as required

Adopt standard

Current Business Central now provides the outcome

Configuration, training and process change

Replace

A supported Microsoft or Microsoft Marketplace (formerly AppSource) app meets the need

App evaluation, data conversion and a support agreement

Rebuild

The requirement is differentiating and not covered safely

Customer-owned AL extension or integration

Defer

Value is uncertain and the first go-live can operate without it

Prioritized post-go-live backlog with an owner

Check current standard functionality before scoping a rebuild. For retained customizations, Microsoft's guide recommends choosing per-tenant or Microsoft Marketplace distribution early. The comparison of per-tenant extensions vs Marketplace apps covers ownership, updates and support for both models.

How to migrate NAV customizations to Business Central

Microsoft's guide maps each NAV object type to an AL approach:

C/AL object type

AL approach

Tables

Table extensions for added fields and keys; custom tables become new AL tables

Pages

Page extensions for base pages; custom pages become new AL pages

Codeunits

AL codeunits that subscribe to integration and business events instead of modifying base code

Reports

AL reports, or report extensions where available

Option fields

AL enums where possible

XMLports and queries

Reimplemented as AL objects

.NET add-ins

Redesigned, because .NET interop isn't available online; use control add-ins, Azure Functions or external APIs

The conversion workflow

The documented workflow exports the C/AL objects with the Export-NAVApplicationObject cmdlet and the ExportToNewSyntax flag, generates initial AL files with the Txt2Al tool, and finishes the code in Visual Studio Code with the AL Language extension against a development database. The Txt2Al conversion tool ships only with version 14, and Microsoft states it is no longer available from version 21. The on-premises conversion procedure is in code conversion from C/AL to AL.

Txt2Al gives a starting point, not an extension design. Refactor retained base-code changes into supported extension points, including event subscribers; field and layout changes use table and page extensions.

From modified code to events

Microsoft's events overview explains the model: a publisher declares an event, the application raises it, and a subscriber in your extension runs your logic, without modifying the original code. Three NAV patterns need specific attention, according to the upgrade considerations: Codeunit 1 is retired and replaced by system codeunits and events, V1 extensions must be converted, and MenuSuite no longer controls search.

When the event a customization needs does not exist, do not recreate the fork. Microsoft retired ALAppExtensions on 2026-10-19. Extensibility requests, including new integration events and option-to-enum changes, now belong in BCApps. Our guide to event subscriber patterns in AL covers how to keep subscribers small and testable.

Plan the data upgrade for custom tables and fields

For full migration, install data-carrying extensions online and keep each table's ReplicateData property true, the default, as explained in Microsoft's cloud migration planning guide. Install each data-carrying extension on both sides, with at least one permission set.

Where names or structures change, migration table mapping can rename a table during migration or move a set of fields into a table extension. Moved fields must keep the same name and type; differently named fields are ignored. Renamed tables require matching keys and ReplicateData set to true. Two source tables can't map to the same destination table.

Some data is excluded. The on-premises to online migration overview states that most system tables, users, permissions and record links are not migrated. It also warns that once the data upgrade succeeds, replication can't be run again from the earlier version.

For each custom dataset, define:

  • Source and target table and field mapping

  • Data owner and retention rule

  • Conversion and validation rules

  • Expected row counts and financial control totals

  • The reconciliation report business owners will sign

  • Whether history must stay transactional or can be archived read-only

Later extension versions use upgrade codeunits when data needs transformation. The guide to AL extension upgrade strategies explains how to ship new versions without losing data.

Test the migration before cutover

Microsoft's customization guide calls for a pilot conversion of a representative subset of objects, then regression testing in a sandbox with key business users. The NAV migration article asks for at least one full sandbox dry run; the planning guide recommends two, plus a runbook with owners, durations, decision gates, change freeze timing and rollback options.

Install required extensions before replication. Rehearse the source freeze, final replication, data upgrade when required, permissions, integrations, reports, user acceptance, reconciliation and go or no-go decision. Time each step and record manual fixes. The Business Central sandbox vs production guide helps users distinguish test and live environments.

Freeze C/AL development before the final cutover, as Microsoft's guide states, and do all new work in AL. The on-premises system remains the operative environment until migration is complete.

After go-live, Business Central online receives two major updates a year, in April and October. During enforced updates, Microsoft might uninstall blocking extensions, retaining their data for recovery with a compatible version. Test custom extensions against each release before it reaches production.

How Bitta Apps helps

Bitta Apps is a Microsoft Dynamics 365 Business Central partner and Microsoft Cloud Solution Provider. The migration readiness page lists the inventory to prepare for a NAV move. The paid Migration Readiness Assessment is published at $7,500, delivered seven business days after Bitta Apps has access; multi-entity or integration-heavy environments are quoted up to $12,500. As how it works describes, it covers a current-state review of NAV data and processes, a data-migration map of what migrates, what archives and what gets rebuilt, and a fixed-price migration proposal.

AL development covers C/AL to AL conversion and version-to-version upgrades with regression test plans, priced as fixed scope with a written proposal within five business days of the scoping call. Business Central implementation covers the migration project and go-live.

Keep the customization inventory current after go-live so future release testing covers the behavior the business still needs.

Next step. Bring your NAV version and customization list to a free discovery call to agree practical next steps. Detailed assessment is agreed separately. Use the short form on the Business Central partner page, or call (626) 766-9732.

FAQ

Frequently asked questions

How do I migrate NAV customizations to Business Central?

Inventory every modified object, add-on and integration, then decide for each one whether to retire it, adopt a standard feature, replace it with an app or rebuild it. Customizations you keep must be rewritten as AL extensions, because Business Central online runs extensions only. Microsoft's workflow exports the C/AL objects, generates starting AL files with the Txt2Al tool from version 14 and finishes the code in Visual Studio Code.

Can you upgrade NAV directly to Business Central online?

No. Microsoft's standard route takes NAV 2015 through 2018 to Business Central 14, then version 25 or later on-premises, before cloud migration. NAV 2013 and 2009 need earlier intermediate upgrades too. A separate BC14 reimplementation tool bypasses the version 25 step, but remains preview and is not intended for production.

What happens to C/AL code in Business Central?

Business Central online cannot run C/AL code. Retained base-code customizations must use AL extension points, including event subscribers; added fields and page changes use table and page extensions, while .NET interop needs redesign. Version 14 is the last version supporting C/AL.

Does custom table data migrate from NAV to Business Central online?

Only when an extension that owns the data is installed both on-premises and online. Microsoft states that data from tables with code customizations can't be carried forward otherwise. Migration table mapping can rename tables or move fields into a table extension, provided the moved fields keep the same name and type.

How long does a NAV to Business Central migration take?

It depends on the starting version, the number of customizations and integrations, data volume and how many dry runs the cutover needs. Microsoft's standard full migration from NAV includes upgrades to version 14 and to version 25 or later on-premises, plus the C/AL to AL conversion, before the cloud migration runs. A scoped assessment of the customization inventory is the reliable way to set a timeline.

What is the Business Central 14 reimplementation tool?

It is a Microsoft cloud migration option for companies already on Business Central 14 that want a fresh start. It moves master data, open orders, opening balances, setup and a defined subset of posted history, but excludes legacy C/AL customizations and their data by default. The tool is extensible for additional migration requirements. Microsoft still labels it preview and not intended for production use.

Sources

Claims in this article were checked against the following on Nov 11, 2026.

  1. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-nav-customization-playbook
  2. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-nav
  3. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths
  4. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-prerequisites
  5. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-bc14-reimplementation
  6. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-txt2al-tool
  7. github.com/microsoft/BCApps
  8. github.com/microsoft/ALAppExtensions
  9. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-plan-prepare
  10. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migration-table-mapping
  11. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-business-central-on-premises
  12. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/update-rollout-timeline
  13. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2017
  14. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2018
  15. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-to-business-central-online
  16. learn.microsoft.com/en-us/lifecycle/end-of-support/end-of-support-2027
  17. learn.microsoft.com/en-us/lifecycle/end-of-support/end-of-support-2028
  18. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2016
  19. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/devenv-code-conversion
  20. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-events-in-al

Written by

Mohammad Nour Itani

Founder & Senior Business Central Developer

Related services

Work with Bitta Apps on this

Next step

Talk to a senior Business Central consultant, not a sales rep.

Fixed-price proposal in writing within five business days of discovery.