Microsoft Dynamics NAV (Navision) and Business Central (the 2026 upgrade)
Microsoft Dynamics NAV (Navision) support dates, upgrade paths by version and costs. Cloud moves start at Business Central on-premises version 14.
Key takeaways
- Microsoft Navision, Dynamics NAV, Dynamics Navision, and Microsoft Dynamics NAV Navision are names for the same on-premises ERP line.
- Microsoft describes Dynamics NAV 2018 as a complete enterprise resource planning (ERP) software solution for mid-sized organizations.
- Searchers who type microsoft navision, dynamics nav, or erp microsoft nav are usually deciding whether Business Central is a new name for the system they already run.
- The application model changed.
Dynamics NAV vs Business Central
Searchers who type microsoft navision, dynamics nav, or erp microsoft nav are usually deciding whether Business Central is a new name for the system they already run. It is the successor product. The move still passes through a specific on-premises release, and custom C/AL in the base application has to be handled before data in those tables can move.
The table uses the final NAV release, NAV 2018, against Business Central online as of October 2026. Version numbers and the version 14 gate come from Microsoft's migrate-nav and upgrade-paths pages. List prices come from the US and Canada pricing pages. Support dates come from the Microsoft lifecycle pages for each NAV release.
| Dimension | Dynamics NAV (on-premises) | Business Central (online) |
|---|---|---|
| What buyers call it | Microsoft Navision, Dynamics NAV, Dynamics Navision | Dynamics 365 Business Central |
| Customization | C/AL in the base application, plus add-ons | AL extensions. Data in tables that still have code customizations cannot move forward from NAV. |
| Cloud route | No direct migration to Business Central online | Start at on-premises version 14, then version 25 or later, then online |
| Code conversion tool | C/AL objects | txt2al.exe ships only with version 14 and is deprecated from version 21 |
| How you buy it | Historic perpetual license files (.flf) on many estates | Cloud Solution Provider only. Named types include Essentials, Premium, Team Members, and External Accountant. |
| US list price, paid yearly | Not a current online list price | Essentials $80, Premium $110, Team Members $8 per user per month as of October 2026 |
| Canada list price, paid yearly | Not a current online list price | Essentials CAD 108.50, Premium CAD 149.20, Team Members CAD 10.90 per user per month, plus tax |
| Support still open as of October 2026 | NAV 2017 extended support through 11 January 2027. NAV 2018 extended support through 11 January 2028. | Current online tenant. Version 14 itself is only a stepping-stone for the upgrade. |
What changed from NAV to Business Central
The application model changed. Dynamics NAV let partners and customers change C/AL objects in the base application, which is why older upgrades were code merges. On the way to a current Business Central release, that application has to be converted from C/AL to AL. Extensions V1 are not supported on Business Central on-premises and must be converted to extensions V2 before the upgrade. Codeunit 1 ApplicationManagement from Dynamics NAV is retired.
The version gate changed with it. Business Central Spring 2019 is version 14, the last version that supports C/AL. The txt2al.exe converter that turns C/AL objects into .al files ships only with version 14. Microsoft deprecated that tool starting with 2022 release wave 2 (version 21), and it is not available in later releases. If the conversion is still ahead of you, the work happens on a version 14 database, before you climb to a current release.
The commercial model changed for the online product. Business Central online licenses are bought only through a Cloud Solution Provider. A self-service evaluation includes a 30-day trial company. Premium includes Essentials plus service management and manufacturing. Team Members is limited access to read data, approve workflows, and create or update selected information. Read-only Microsoft 365 access is available when the tenant already has at least one Business Central license.
A Device license exists for shared devices such as point of sale, shop floor, or warehouse. Users in the security group named exactly Dynamics 365 Business Central Device Users share the purchased device licenses concurrently. The public US and Canada pricing pages do not list a Device price or an External Accountant price, so those two seats need a quote from the CSP rather than a figure from this page. Our Business Central licensing guide covers how Essentials, Premium, and Team Members sit together once the seat mix is known.
When Dynamics NAV support ends
As of October 2026, several NAV releases are already past extended support. Dynamics NAV 2016 extended support ended on 14 April 2026. Mainstream support for NAV 2016 had ended on 13 April 2021. Dynamics NAV 2015 extended support ended on 14 January 2025. Dynamics NAV 2013 extended support ended on 10 January 2023. Dynamics NAV 2009 R2 extended support ended on 14 January 2020. Running those releases means you are outside the published security-update window for that product.
Two releases are still inside extended support. Dynamics NAV 2017 mainstream support ended on 11 January 2022, and extended support ends on 11 January 2027. Dynamics NAV 2018, which started on 1 December 2017, had mainstream support through 10 January 2023, and extended support ends on 11 January 2028, under the Fixed Lifecycle Policy. Extended support is the window you have left on those two versions, and it is shorter for 2017 than for 2018.
Version 14 is a different clock. Mainstream support for Business Central version 14 ended in October 2023, and minor updates are no longer available. New customers cannot use version 14 in production. Microsoft documents it only as a stepping-stone for upgrading. Existing version 14 customers remain under the Fixed Lifecycle Policy. Plan the hop through version 14 as project work, then leave that database for version 25 and a current release.
Older versions also add hops, which is why the support date and the version number should be read together. NAV 2015 through NAV 2018 can reach version 14 in one product hop. NAV 2013 and NAV 2013 R2 add a hop through NAV 2018 first. NAV 2009 SP1 and NAV 2009 R2 add a further hop through NAV 2013 or NAV 2015, then NAV 2018, then version 14. A 2009 database that lost extended support in January 2020 can still be upgraded on the documented route, and the route is longer.
Supported upgrade paths by NAV version
There is no direct migration from Dynamics NAV to Business Central online. Both the full-migration path and the reimplementation path start by upgrading to Business Central on-premises version 14. From there, the cloud route for a full migration continues to Business Central on-premises version 25 or later, then to Business Central online.
On the on-premises matrix, Microsoft Dynamics NAV 2015 is version 8, NAV 2016 is version 9, NAV 2017 is version 10, NAV 2018 is version 11, Business Central October 2018 is version 13, and Business Central Spring 2019 is version 14. Those sources cannot jump straight to 2026 release wave 2 (version 29). The documented path is version 14, then 2024 release wave 2 (version 25), then version 29, and it requires converting the application from C/AL to AL.
Starting in 2025 release wave 1 (version 26), a direct upgrade from Business Central 2019 (version 14) to the latest release is not supported. The supported path goes through 2024 release wave 2 (version 25). A project plan that says "version 14, then the current cloud tenant" is missing that hop. Budget the version 25 database as its own environment, with a backup and a test pass, before the move to version 29 or to online.
Use the table as the scope checklist. The version you read on the NAV server is the input. The number of product hops is the output your partner should put on the timeline before anyone talks about a cutover weekend.
| Starting version | Route |
|---|---|
| NAV 2015, 2016, 2017, or 2018 (versions 8 to 11) | Business Central on-premises version 14, then on-premises version 25 or later, then Business Central online |
| NAV 2013 or 2013 R2 | Dynamics NAV 2018, then version 14, then version 25 or later, then Business Central online |
| NAV 2009 SP1 or 2009 R2 | NAV 2013 or NAV 2015, then NAV 2018, then version 14, then version 25 or later, then Business Central online |
| Business Central October 2018 (version 13) or Spring 2019 (version 14) | Version 14 if you are not there yet, then version 25, then version 29 for the current on-premises release. Cloud migration continues from version 25 or later. |
Stay on NAV, move to Business Central on-premises, or go online
There are three places to land. You can stay on NAV 2017 or NAV 2018 until extended support ends, move to Business Central on-premises, or move to Business Central online. Only the first is a code-neutral choice, and it has a dated exit: 11 January 2027 for NAV 2017 and 11 January 2028 for NAV 2018.
Business Central on-premises does not avoid the code work. Microsoft's upgrade-paths page states that the route from NAV 2015 through 2018 to a current release requires converting the application from C/AL to AL, with Business Central Spring 2019 (version 14) as the first stop and 2024 release wave 2 (version 25) as the second. The choice between on-premises and online is about where the database runs, who patches it, and what the code is allowed to touch.
On-premises Business Central follows Microsoft's Modern Lifecycle Policy, which dates every release. As Microsoft lists them on 24 October 2026, 2026 release wave 2 (version 29) runs from 1 October 2026 to 6 April 2028, version 28 runs to 13 October 2027, and version 27 runs to 6 April 2027. Each release is supported for roughly 18 months, so an on-premises database needs a version upgrade about that often to stay supported. Microsoft's 2026 end-of-support list shows version 25 ended on 4 April 2026 and version 26 ended on 13 October 2026, so both are now outside servicing.
That last date matters for the cloud route. Microsoft's NAV migration page still names version 25 or later as the on-premises source for the online replication, and the upgrade path from version 14 still goes through version 25. Because version 25 and version 26 are both outside servicing, ask your partner which target version they will replicate from and which one they will keep as the waypoint. Do not accept a plan that treats version 25 as a place to stay.
Online removes the hosting and upgrade cadence, at the price of the customization limits in the table: extensions only, no .NET add-ins, and no direct SQL Server access. The Business Central online licenses are sold through a Cloud Solution Provider. For product scope and seat types, see our Business Central guide.
| Option | Customization | Database and hosting | Support clock | Fits when |
|---|---|---|---|---|
| Stay on NAV 2017 or NAV 2018 | C/AL stays as it is | Your SQL Server and servers | Extended support ends 11 January 2027 (2017) and 11 January 2028 (2018) | You need a bridge of a year or two with a dated exit and a funded plan |
| Business Central on-premises (version 29) | AL extensions, after C/AL is converted | Your SQL Server and servers, with direct database access | 1 October 2026 to 6 April 2028, then the next release | Reports, integrations, or hosting rules still need direct SQL access |
| Business Central online | AL extensions only. .NET add-ins are not available. | Microsoft-hosted tenant, no direct SQL access | Current online release, updated by Microsoft | You want the hosting and upgrade cadence off your team and can run on extensions and APIs |
Full migration or reimplementation
After version 14, Microsoft documents two ways to reach Business Central online. A full migration carries data and customizations only after C/AL customizations are converted to AL extensions and the database is upgraded to a current version. Data in tables that still have code customizations cannot move forward from Dynamics NAV. That rule is why a code inventory comes before a data-migration estimate.
The alternative is the Business Central 14 reimplementation tool, which moves essential data and does not require converting extensions. Microsoft's 23 May 2026 documentation marks that tool as a preview feature. The same page says it is not meant for production use. Treat a plan that depends on it as a pilot until Microsoft changes that status. It is a documented option for what to carry, and it is not a shortcut you can put a live company on while the label still says preview.
When the tool runs, it migrates master data (customers, vendors, items, G/L accounts, dimensions), open sales and purchase orders, opening balances, and setup. Legacy C/AL customizations are not migrated. Only a defined subset of posted history is included, for example posted G/L entries and posted sales invoices.
Choose a full migration when the custom logic still matches how the company ships, bills, or manufactures, and when finance needs more than opening balances plus a thin set of posted documents. Choose a reimplementation when the object list is mostly old modifications, the business will adopt standard Business Central processes, and history can live in a read-only archive. The choice is a process decision with the finance lead and the operations manager, because each path keeps a different set of numbers. Our ERP upgrade guide sets this choice next to other Dynamics 365 and Odoo upgrades.
| Decision factor | Full migration | Reimplementation tool (version 14) |
|---|---|---|
| Status | Supported route once C/AL is AL and the database is current | Marked preview on 23 May 2026 documentation, not for production use |
| Customizations | C/AL must become AL extensions before customized table data can move | Legacy C/AL is not migrated. Extension conversion is not required. |
| Data carried | Companies and data you scope, after the technical upgrade | Master data, open sales and purchase orders, opening balances, setup, and a defined subset of posted history |
| Version hops | Version 14, then version 25 or later, then online | Reach version 14, then use the reimplementation tool toward online |
| Fits when | Custom business logic and a broader history are still required | Standard processes are acceptable and history can be archived outside the new tenant |
What breaks when custom NAV code meets Business Central
List modified objects, including objects nobody on the current team wrote, before estimating the migration. Microsoft's rule is narrower than a slogan: data from tables that still contain code customizations cannot be carried forward from Dynamics NAV until those customizations are handled by extensions. If a custom field holds a price, a route, or a lot attribute you still post, that field needs an AL table extension before the cloud replication, or the value stays on the old database.
Three platform retirements show up on almost every NAV estate. Codeunit 1 ApplicationManagement is retired, so trigger logic that lived there has to move to event subscribers. Extensions V1 are not supported on Business Central on-premises and must be converted to extensions V2 before the upgrade. The txt2al converter itself exists only on version 14, so a team that starts on a later AL-only release cannot run that conversion step there.
Other breaks that Microsoft's customization migration guidance has long flagged still decide the budget. .NET add-ins are not available in Business Central online, so assemblies called from C/AL need a redesign before cutover. MenuSuite navigation has to be rebuilt on AL pages. Reports and integrations that read SQL Server tables directly have to move to APIs, query objects, or page objects, because the online tenant does not give you that database. Breaking schema changes, such as removing or renaming a field, can block extension synchronization.
A practical test during discovery: list every object your users touch in a close, a shipment, and a shop-floor receipt. Mark each one as still required, replaceable by standard Business Central, or unused. If most of the list is unused, the reimplementation path is the one to price. If the shipment and the close depend on modified codeunits, the full migration's AL conversion is the critical path, and the cutover date should sit behind that conversion.
Converting C/AL customizations to AL extensions
On a full migration, conversion is the long task. Export the C/AL objects and run txt2al.exe from the Business Central version 14 installation, the last version that supports C/AL. Compile the .al files and repair what the converter could not express. Because the tool is deprecated from 2022 release wave 2 (version 21) and is absent later, do not plan to do this step on version 25 or version 29.
Microsoft's object treatment is consistent even when the converter output is rough. Pages become page extensions or new AL pages. Tables become table extensions or new AL tables. Codeunits move to AL codeunits that subscribe to events, which is also how Codeunit 1 logic is replaced. Reports, XMLports, and queries are reimplemented as AL objects. .NET add-ins are not available in Business Central online and need a redesign before cutover.
Keep the conversion in a sequence the business can see. Inventory modified objects, add-ons, and integrations first, and tag which ones store data. Convert a small set that includes one posting routine and one document the warehouse uses every day. Regression-test that set in a sandbox. Freeze further C/AL changes before the final replication so new work is written as AL. Our BC extensions guide explains how per-tenant extensions sit on the base application once that freeze is in place.
Add-ons need the same inventory. An ISV object that has a Business Central online successor can stay on the project plan. An add-on with no successor is either rebuilt, replaced by a standard process, or left in the archive with the old database. That decision changes both the timeline and the license conversation, because some replacements are separate apps with their own subscription.
| C/AL object | AL approach | Project note |
|---|---|---|
| Pages | Page extensions or new pages | Base pages stay intact. Layout changes live in the extension. |
| Tables | Table extensions or new tables | Custom fields that hold live data must exist as extensions before that data can move. |
| Codeunits | AL codeunits on events | Codeunit 1 is retired. Subscribe instead of editing the base codeunit. |
| Reports, XMLports, queries | AL objects | Rebuild the layouts finance and the warehouse still run. |
| Extensions V1 | Convert to extensions V2 | V1 is not supported on Business Central on-premises. |
| .NET add-ins | Redesign | .NET add-ins are not available in Business Central online and need a redesign before cutover. |
Inventory objects on the version you run
Record the NAV build, then list modified objects, ISV add-ons, and integrations. Split data-carrying changes from layout and report changes. This list is what makes a full migration estimate different from a reimplementation estimate.
Convert on version 14
Reach Business Central on-premises version 14 and run txt2al.exe there. Repair the output in AL. Do not leave this until version 25 or later, where the converter is gone.
Pilot, then stop C/AL changes
Convert one posting path and one operational document, and test them in a sandbox with the people who run that work. After the pilot, new requirements ship as AL so the final replication has a stable source database.
How the cloud cutover moves the data
Cloud cutover replication is started from the online Cloud Migration Management page. Business Central online calls Azure Data Factory and the replication pipeline. A self-hosted integration runtime copies table data, using Azure Blob storage as a regional temporary store. The on-premises database you replicate from has to be a supported version: version 25 or later on the full-migration route, after the version 14 and C/AL work.
Before migration, Microsoft says the on-premises SQL Server compatibility level must be 130 or higher. Check that level on the NAV or Business Central database early. Raising it is a database change with its own test, and it should not be left for the cutover weekend. Clean obsolete companies and oversized logs before the first replication so the pipeline is moving data you still need.
Microsoft also recommends at least one full dry run in a sandbox before production cutover. Use that run to time the copy, to compare customer, vendor, item, and G/L balances, and to let finance open a known invoice. A second company, if you have one, should follow the same schedule so the production weekend is a repeat of a measured run. The surrounding project phases, including who signs off, are laid out in our Business Central implementation guide.
The dry run is also where license and access questions become concrete. Internal people who only need to read data may fit Team Members, or Microsoft 365 read-only access when the tenant already has at least one Business Central license. People who post shipments, production orders, or service orders need the full seat that matches the work. Settle that list before you buy a year of the wrong mix.
What drives the effort and cost of a NAV upgrade
Cost follows the same short list on every NAV estate, in the US or Canada. The subscription is priced from Microsoft's list. The services effort depends on the drivers below, which is why two companies of the same size can receive quotes that differ several times over. Written down before the quote, they let you compare firms on the same assumptions.
The data work sits inside these drivers rather than beside them. How many companies replicate, how much history comes along, and how many dry runs the plan allows decide the migration weeks. Our ERP data migration guide covers cleansing and reconciliation that apply to any source system.
| Driver | What to count | Effect on effort |
|---|---|---|
| Version hops | NAV release and the hop list to version 14, then version 25 | Each extra product hop adds an upgrade and a test pass |
| Modified objects | Count of changed pages, tables, codeunits, reports, and XMLports | Largest driver on a full migration, because each becomes AL |
| ISV add-ons | Each third-party object and whether a Business Central version exists | Missing successors mean a rebuild, a replacement, or an archive |
| Integrations and SQL access | Reports, links, and tools that read the database directly | Move to APIs, queries, or pages before an online cutover |
| Companies and data volume | Company batches, obsolete companies, oversized log tables | More batches mean more dry runs and reconciliations |
| Posted history | How much history finance needs inside the new tenant | A full migration carries more, and reimplementation carries a defined subset |
| Localization and reports | Tax, regulatory, and statutory reports | Local logic must exist as an online localization or an extension |
| Users and roles | Seat mix, permission sets, training groups | Sets the subscription and the change-management load |
What a Dynamics NAV upgrade to Business Central costs in Texas
As of October 2026, public records do not show a Texas award or a statewide package price for a Dynamics NAV upgrade to Business Central. A Texas services number has to come from a scoped quote. Keep two bills separate: the Microsoft subscription, which has a public list price, and the partner services fee, which is quoted per estate.
On the US pricing page, paid yearly, Business Central Essentials is $80 per user per month, Premium is $110 per user per month, and Team Members is $8 per user per month. Premium is the seat that includes service management and manufacturing. Canada list prices on the same basis are CAD 108.50, CAD 149.20, and CAD 10.90 per user per month, plus applicable tax. These October 2026 list prices are the subscription. A Texas services quote sits on top of them.
Worked subscription, stated assumptions: a Texas manufacturer with 25 people who post transactions and 10 people who only approve and look up orders. Manufacturing requires Premium. At US list, paid yearly: 25 times $110 times 12 equals $33,000, and 10 times $8 times 12 equals $960, so the subscription is $33,960 per year before tax. The same 25 users on Essentials would be 25 times $80 times 12, or $24,000, which is $9,000 a year less and omits manufacturing and service management. If that company were buying on the Canada list, the Premium math is 25 times CAD 149.20 times 12, or CAD 44,760, plus 10 times CAD 10.90 times 12, or CAD 1,308, for CAD 46,068 per year plus tax. Device seats and External Accountant seats are excluded because Microsoft does not publish those prices on the US or Canada pages.
Services ranges published by two firms do not agree, and they should not be averaged into one US or Texas cost. 365 Vanguard, on a page updated 24 September 2026, publishes NAV-to-BC services at about 50 to 70 percent of a new Business Central implementation: EUR 8,000 to 18,000 for a clean NAV 2016 to 2018, EUR 18,000 to 40,000 as its typical band, and EUR 45,000 to 60,000 or more for complex multi-entity work, with durations from 8 weeks to 9 months. Those euro figures are that firm's published bands. A Texas company still needs its own services quote, and the Microsoft subscription is priced from the US list above.
OmniLogic Solutions, on a 28 April 2026 page, publishes mid-market project ranges of USD 60,000 to 350,000 overall, reimplementation USD 60,000 to 200,000, lift-and-shift USD 80,000 to 350,000, and hybrid USD 250,000 to 800,000 or more, over 3 to 9 months for 30 to 150 users. That page is not Texas-specific. The same page's subscription figures of about USD 70 for Essentials and about USD 100 for Premium disagree with Microsoft's live list of USD 80 and USD 110, so use the Microsoft pages for licenses and treat OmniLogic's numbers as a services band only.
Duration follows the hops and the code, in Texas and in every other state. A clean NAV 2016 to 2018 estate with few modifications can sit toward the shorter end of those published bands. NAV 2013 or NAV 2009 adds the intermediate product hops in the route table, and a large C/AL inventory adds conversion time on version 14 before Azure Data Factory runs. Flectic sets the timeline for a first phase in the written scope, with a fixed price, before work starts. Ask any firm to map its quote to your NAV version, your object count, and whether the price assumes a full migration or a reimplementation.
Choosing a US firm for a NAV-to-Business Central upgrade
People searching for the best Microsoft partner for a NAV-to-Business Central upgrade in the USA will not find a Microsoft ranking. Microsoft does not publish a best-partner list for this upgrade. Licenses for Business Central online are sold only through a Cloud Solution Provider, so the firm you hire has to be able to transact the subscription, or it has to work with a CSP that can. A directory listing is not evidence that the firm has taken your NAV version to version 14 and then to version 25.
Score the shortlist on the version you are leaving, on C/AL-to-AL evidence, on US localization, and on a sandbox dry run. Ask which NAV builds they have upgraded in the last two years, and whether those databases were 2018, 2016, 2015, 2013, or 2009. Ask to see how they run txt2al on version 14, how they replace Codeunit 1, and how they convert extensions V1 to V2. Ask which US tax and payment localizations the online tenant will use, and whether your state and local reports are in that set or in a custom extension.
Ask for one full sandbox dry run in the statement of work, because Microsoft recommends at least one before production cutover. The proposal should name the SQL compatibility check (level 130 or higher), the company batch, and who signs the balance comparison. If the firm quotes the Business Central 14 reimplementation tool as the production method, the proposal should also say that Microsoft marked that tool as a preview on 23 May 2026 and said it is not for production use.
Flectic scopes this work for companies of 20 to 100 people in the US and Canada. The scoping call starts from your NAV version, a first pass of modified objects, and whether manufacturing or service management means Premium seats. Flectic is an independent consultancy. Book that call from the Business Central page.
Choosing the NAV to Business Central path
Three inputs settle the path: the NAV version on the server, the share of custom objects you still post with, and how much posted history finance will accept in an archive. Price the subscription from the Microsoft list, then price services only after those three inputs are written down.
Read the version before you read a feature list
NAV 2015 through 2018 take one hop to version 14. NAV 2013 and 2013 R2 pass through NAV 2018 first. NAV 2009 SP1 and 2009 R2 pass through NAV 2013 or NAV 2015, then NAV 2018, then version 14. From version 14, a current release goes through version 25. Version 14 is a stepping-stone, and new customers cannot run it in production.
Pick full migration when the code still runs the business
If shipments, manufacturing, or invoicing depend on modified codeunits and custom fields, convert C/AL to AL on version 14 and carry the data forward only after those extensions exist. Plan version 25 before the online cutover. Keep txt2al on the version 14 environment, because later releases do not include it.
Pick reimplementation when the code is residue
If the object list is old, undocumented, and unused in the current close, move master data, open orders, opening balances, and setup, and archive the rest. Remember the reimplementation tool's May 2026 preview status before you put a go-live date on it. Posted history in the new tenant will be the subset Microsoft documents, such as posted G/L entries and posted sales invoices.
Put the support dates on the same page as the quote
NAV 2016 extended support ended on 14 April 2026. NAV 2015 extended support ended on 14 January 2025. NAV 2013 extended support ended on 10 January 2023. NAV 2009 R2 extended support ended on 14 January 2020. NAV 2017 extended support ends on 11 January 2027. NAV 2018 extended support ends on 11 January 2028, under the Fixed Lifecycle Policy. A quote that ignores an already ended support window is missing the reason many of these projects start.
Pre-migration checks before you book a cutover
Run these checks before you buy a year of licenses or reserve a cutover weekend. Each one is a Microsoft prerequisite or a choice that changes the quote. A firm that skips the version map and the object inventory will mis-state both the fee and the calendar.
For a company of about 20 to 100 people, the useful output is a one-page scope: NAV version, hop list, full migration or reimplementation, seat mix at the October 2026 list price, and a date for the sandbox dry run. That page is what finance can approve. The replication tooling comes after it.
| Check | What to record | Why it changes the project |
|---|---|---|
| NAV version | Exact release: 2018, 2017, 2016, 2015, 2013, 2013 R2, or 2009 SP1 / R2 | Sets the hop count to version 14 |
| Support date | Whether extended support has ended or the end date still ahead | NAV 2017 extended support ends 11 January 2027. NAV 2018 extended support ends 11 January 2028, under the Fixed Lifecycle Policy. Extended support has ended for NAV 2016 (14 April 2026), NAV 2015 (14 January 2025), NAV 2013 (10 January 2023), and NAV 2009 R2 (14 January 2020). |
| C/AL inventory | Modified objects, extensions V1, Codeunit 1 usage, .NET add-ins | Decides full migration versus reimplementation, and blocks data in customized tables until extensions exist |
| SQL compatibility | Compatibility level 130 or higher | Microsoft requires this before migration |
| Version 14 plan | Where txt2al will run, and that version 14 is not the production destination | The converter exists only on version 14. New customers cannot use version 14 in production. |
| Version 25 hop | A planned stop at 2024 release wave 2 before a current release or online full migration | From version 26, version 14 cannot upgrade directly to the latest release |
| Seat mix | Essentials, Premium, and Team Members counts at US or Canada list | Manufacturing or service management requires Premium at $110 or CAD 149.20 |
| Dry run | One full sandbox replication with balance sign-off | Microsoft recommends at least one before production cutover |
| Data preparation | Archive obsolete history, shrink oversized transaction and log tables, and design company batches | Microsoft advises cleaning technical debt before the first replication |
| Localization | Required localization apps for your country, and tax or reporting logic converted to AL extensions | Country functionality arrives as localization apps online and is usually managed by the partner |
A NAV to Business Central plan based on your version and your code
Flectic is an independent ERP and CRM consultancy for companies of 20 to 100 people in the US and Canada. We implement Microsoft Dynamics 365 Business Central and Odoo. On a Navision or Dynamics NAV estate we start with the version, the support date, and the modified objects, then say whether the first phase is a full migration through version 14 and version 25 or a reimplementation of essential data.
The written proposal sets the timeline and a fixed price for each phase before work starts. The delivery method is designed to deliver up to 3x faster on suitable engagements. Bring the About-page version, a rough object count, and whether you manufacture or run service management. We will price the Microsoft subscription from the current US or Canada list and separate that number from the services scope, including a Texas company that needs a quote rather than a statewide package.
How Flectic can help
Flectic migrates finance teams off Dynamics NAV onto Dynamics 365 Business Central and reconciles the opening balances before go-live. We also set up the general ledger, payables and receivables, and Power BI dashboards. We work alongside your team through the first month-end close on the new system. Book a free discovery call with Flectic to check your NAV version and custom code against the Dynamics 365 implementation scope.
Sources
On 7 May 2002 Microsoft announced an agreement to acquire Navision, valued at about USD 1.3 billion (about EUR 1.4 billion / DKK 10.8 billion), at 300 DKK per share. Navision sold through about 2,400 partners and had sold more than 136,000 solutions. Product lines named: Navision Axapta, Navision Attain / Navision Financials, and Navision XAL. Headquarters were Vedbaek, Denmark.
news.microsoft.comChecked 2026-10Microsoft's Business Central product page tells NAV customers "What's next after NAV?" and describes Business Central as ERP for small and midsize businesses, trusted by 55,000 companies.
microsoft.comChecked 2026-10There is no direct migration from Dynamics NAV to Business Central online. Both paths start at Business Central on-premises version 14. Cloud route from NAV 2015, 2016, 2017, or 2018: version 14, then on-premises version 25 or later, then online. NAV 2013 and 2013 R2 add a hop through NAV 2018. NAV 2009 SP1 and 2009 R2 add a hop through NAV 2013 or NAV 2015, then NAV 2018, then version 14. SQL Server compatibility level must be 130 or higher. Microsoft recommends at least one full sandbox dry run. A full migration carries data and customizations only after C/AL is converted to AL and the database is current. Data in tables that still have code customizations cannot move forward from Dynamics NAV. Data preparation: archive obsolete history, shrink oversized transaction and log tables, confirm SQL Server compatibility level 130 or higher, and design company batches early. Localization: country functionality is delivered as localization apps online, and locally customized tax or reporting logic must be converted to AL extensions. Page dated 23 May 2026.
learn.microsoft.comChecked 2026-10NAV 2015 is version 8, NAV 2016 is version 9, NAV 2017 is version 10, NAV 2018 is version 11, Business Central October 2018 is version 13, and Business Central Spring 2019 is version 14. Path to 2026 release wave 2 (version 29) is version 14, then 2024 release wave 2 (version 25), then version 29, and requires C/AL to AL. From version 26, a direct upgrade from version 14 to the latest release is not supported. Version 14 mainstream support ended in October 2023, minor updates are no longer available, new customers cannot use version 14 in production, and existing version 14 customers remain under the Fixed Lifecycle Policy.
learn.microsoft.comChecked 2026-10The Business Central 14 reimplementation tool moves essential data and does not require converting extensions. Documentation dated 23 May 2026 marks it as a preview feature, not meant for production use. It migrates customers, vendors, items, G/L accounts, dimensions, open sales and purchase orders, opening balances, and setup. Legacy C/AL is not migrated. Only a defined subset of posted history is included, for example posted G/L entries and posted sales invoices.
learn.microsoft.comChecked 2026-10Cloud cutover replication starts from the Cloud Migration Management page. Business Central online calls Azure Data Factory and the replication pipeline. A self-hosted integration runtime copies table data, using Azure Blob storage as a regional temporary store.
learn.microsoft.comChecked 2026-10txt2al.exe ships only with Business Central version 14, the last version that supports C/AL. The tool is deprecated starting with 2022 release wave 2 (version 21) and is not available in later releases.
learn.microsoft.comChecked 2026-10Extensions V1 are not supported on Business Central on-premises and must be converted to extensions V2 before the upgrade. Codeunit 1 ApplicationManagement from Dynamics NAV is retired.
learn.microsoft.comChecked 2026-10Customization migration guidance: .NET add-ins are not available in Business Central online; MenuSuite navigation moves to AL pages; direct SQL access is replaced by APIs, queries, or page objects; breaking schema changes can block extension synchronization. Object treatment moves pages, tables, codeunits, reports, XMLports, and queries into AL extensions or new AL objects.
learn.microsoft.comChecked 2026-08Business Central online licenses are bought only through the Cloud Solution Provider program. Online does not use classic Dynamics NAV .flf files. Named license types include Essentials, Premium, Team Members, and External Accountant, plus read-only Microsoft 365 access when the tenant already has at least one Business Central license. A self-service evaluation includes a 30-day trial company. A Device license covers shared devices such as point of sale, shop floor, or warehouse. Users in the security group named Dynamics 365 Business Central Device Users share purchased device licenses concurrently. The licensing page does not publish the Device price.
learn.microsoft.comChecked 2026-10US list prices as of October 2026, per user per month, paid yearly: Essentials USD 80, Premium USD 110 (Essentials plus service management and manufacturing), Team Members USD 8. Team Members is limited access to read data, approve workflows, and create or update selected information. The page does not list a Device license price. Worked Texas subscription of 25 Premium users and 10 Team Members equals USD 33,960 per year before tax (25 x 110 x 12, plus 10 x 8 x 12). The same 25 users on Essentials equal USD 24,000 per year.
microsoft.comChecked 2026-10Canada list prices as of October 2026, per user per month, paid yearly, plus applicable tax: Essentials CAD 108.50, Premium CAD 149.20, Team Members CAD 10.90. Worked example of 25 Premium users and 10 Team Members equals CAD 46,068 per year plus tax (25 x 149.20 x 12, plus 10 x 10.90 x 12).
microsoft.comChecked 2026-10Dynamics NAV 2018 started 1 December 2017. Mainstream support ended 10 January 2023. Extended support ends 11 January 2028, Fixed Lifecycle Policy.
learn.microsoft.comChecked 2026-10Dynamics NAV 2017 mainstream support ended 11 January 2022. Extended support ends 11 January 2027.
learn.microsoft.comChecked 2026-10Dynamics NAV 2016 mainstream support ended 13 April 2021. Extended support ended 14 April 2026.
learn.microsoft.comChecked 2026-10Dynamics NAV 2015 extended support ended 14 January 2025.
learn.microsoft.comChecked 2026-10Dynamics NAV 2013 extended support ended 10 January 2023.
learn.microsoft.comChecked 2026-10Dynamics NAV 2009 R2 extended support ended 14 January 2020.
learn.microsoft.comChecked 2026-10365 Vanguard, page updated 24 September 2026, publishes NAV-to-BC services at about 50 to 70 percent of a new Business Central implementation: EUR 8,000 to 18,000 for a clean NAV 2016 to 2018, EUR 18,000 to 40,000 typical, and EUR 45,000 to 60,000 or more for complex multi-entity, with durations from 8 weeks to 9 months. These are that firm's ranges, not Microsoft or Texas prices.
365vanguard.comChecked 2026-10OmniLogic Solutions, 28 April 2026, publishes mid-market NAV-to-BC ranges of USD 60,000 to 350,000 overall, reimplementation USD 60,000 to 200,000, lift-and-shift USD 80,000 to 350,000, and hybrid USD 250,000 to 800,000 or more, over 3 to 9 months for 30 to 150 users. The page is not Texas-specific. Its subscription figures of about USD 70 and USD 100 disagree with Microsoft's list and are not used here.
omnilogicsolutions.comChecked 2026-10Microsoft Dynamics NAV 2018 is described as a complete enterprise resource planning (ERP) software solution for mid-sized organizations. The archived documentation points to Business Central for current documentation. Dynamics NAV 2018 content is no longer maintained by Microsoft.
learn.microsoft.comChecked 2026-10Dynamics NAV 2013 R2 follows the Fixed Lifecycle Policy. Start 30 December 2013, mainstream support ended 9 January 2018, extended support ended 10 January 2023. NAV 2013 started 19 December 2012 with the same end dates. NAV 2015 started 17 December 2014, mainstream ended 14 January 2020. NAV 2016 started 3 January 2016. NAV 2017 started 27 October 2016. NAV 2009 R2 started 15 March 2011, mainstream ended 13 January 2015.
learn.microsoft.comChecked 2026-10Business Central on-premises (Modern Policy) release dates: 2026 release wave 2, version 29.x, 1 October 2026 to 6 April 2028. Version 28.x to 13 October 2027. Version 27.x to 6 April 2027.
learn.microsoft.comChecked 2026-10Microsoft's Ending Support in 2026 list: Business Central on-premises (Modern Policy) version 25.x end of servicing 4 April 2026, version 26.x 13 October 2026. The same list gives 14 April 2026 as the end of support for Dynamics NAV 2016. Extended Support includes security updates at no cost and paid non-security updates and support. After end of support there are no new security updates, non-security updates, or assisted support options.
learn.microsoft.comChecked 2026-10Microsoft's Ending Support in 2027 list gives 11 January 2027 as the end of support for Dynamics NAV 2017. Its Ending Support in 2028 list gives 11 January 2028 for Dynamics NAV 2018. The lifecycle pages for the same releases print the end as 6:59:59 AM on 12 January.
learn.microsoft.comChecked 2026-10Microsoft's Ending Support in 2028 list: Dynamics NAV 2018 end of support 11 January 2028 under the Fixed Policy.
learn.microsoft.comChecked 2026-10
Frequently asked questions
What is Navision?
Navision was a Danish ERP company, based in Vedbaek, that Microsoft agreed to acquire on 7 May 2002 for about USD 1.3 billion. The announcement named three product lines: Navision Axapta, Navision Attain / Navision Financials, and Navision XAL. In everyday use, Microsoft Navision now means the Dynamics NAV product companies still run on-premises. Microsoft's Business Central page points those customers to Business Central as what comes after NAV.
Is Microsoft Navision the same as Dynamics NAV?
Yes for the ERP most finance teams still have installed. Microsoft Navision, Dynamics NAV, Dynamics Navision, and Microsoft Dynamics NAV are search names for that product line, including releases such as NAV 2018, NAV 2017, NAV 2016, NAV 2015, NAV 2013, and NAV 2009. The 2002 company also sold Navision Axapta and Navision XAL as separate lines in the acquisition announcement. This guide does not treat those two lines as Business Central.
Is Business Central just the next version of NAV?
Business Central is the cloud successor to Dynamics NAV. There is no direct migration from Dynamics NAV to Business Central online. Both the full migration and the reimplementation start at Business Central on-premises version 14, and a current on-premises release then passes through version 25 before 2026 release wave 2 (version 29). C/AL customizations become AL extensions, or you leave them behind and move essential data only.
How do I upgrade Dynamics NAV to Business Central?
Upgrade to Business Central on-premises version 14 first. NAV 2015 through 2018 can do that in one hop. NAV 2013 and 2013 R2 go through NAV 2018 first. NAV 2009 SP1 and 2009 R2 go through NAV 2013 or NAV 2015, then NAV 2018, then version 14. Convert C/AL to AL on version 14 if you need a full migration, continue to version 25 or later, then replicate to Business Central online with the cloud migration setup. The SQL compatibility level must be 130 or higher, and Microsoft recommends a full sandbox dry run before production.
What is the best Microsoft partner for a NAV-to-Business Central upgrade in the USA?
Microsoft does not publish a ranked best-partner list for a NAV-to-Business Central upgrade in the USA. Online licenses are sold only through a Cloud Solution Provider. Score firms on the NAV versions they have upgraded to Business Central, on C/AL-to-AL work done with txt2al on version 14, on US localization, and on a written sandbox dry run. Flectic scopes that upgrade for US and Canadian companies of 20 to 100 people. The next step is a scoping call, not a partner directory.
What does a Dynamics NAV upgrade to Business Central cost in Texas?
No public Texas award or package price was available as of October 2026. The Microsoft subscription is separate from services. US list, paid yearly, is $80 per user per month for Essentials, $110 for Premium, and $8 for Team Members. A Texas manufacturer with 25 Premium users and 10 Team Members pays $33,960 per year in subscription before tax, at those rates. Published services bands from two firms (about EUR 8,000 to 60,000 or more, and about USD 60,000 to 350,000, with hybrid projects published up to USD 800,000 or more) are not Texas prices and should not be averaged. A Texas services figure needs a scoped quote.
Will my C/AL customizations survive?
They survive a full migration only after they are converted to AL extensions. Data in tables that still have code customizations cannot move forward from Dynamics NAV. txt2al.exe, the converter that emits .al files, ships only with Business Central version 14 and is deprecated from version 21. Extensions V1 must become extensions V2, and Codeunit 1 is retired. The reimplementation tool does not migrate legacy C/AL, and Microsoft marked that tool as a preview in May 2026 documentation.
Can I move NAV straight to Business Central online?
You cannot. Microsoft states there is no direct migration from Dynamics NAV to Business Central online. The database has to reach Business Central on-premises version 14, and a full migration then needs version 25 or later before the online replication. Replication is started from Cloud Migration Management. Business Central online calls Azure Data Factory, and a self-hosted integration runtime copies table data, with Azure Blob storage as a regional temporary store.
When does Dynamics NAV support end?
As of October 2026, Dynamics NAV 2016 extended support ended on 14 April 2026, and Dynamics NAV 2015 extended support ended on 14 January 2025. Dynamics NAV 2013 extended support ended on 10 January 2023, and Dynamics NAV 2009 R2 extended support ended on 14 January 2020. Dynamics NAV 2017 mainstream support ended on 11 January 2022, and extended support ends on 11 January 2027. Dynamics NAV 2018 mainstream support ended on 10 January 2023, and extended support ends on 11 January 2028, under the Fixed Lifecycle Policy.
Should I upgrade technically or reimplement?
Upgrade technically, meaning a full migration, when custom logic still posts your orders and you need that data in the new tenant. That path converts C/AL to AL and climbs from version 14 through version 25. Reimplement when you can live on master data, open orders, opening balances, setup, and a defined subset of posted history such as posted G/L entries and posted sales invoices. The version 14 reimplementation tool is still marked as a preview and is not meant for production use, so confirm its status before you schedule a go-live on it.