Moving from NAV 2013 / R2 to Business Central 28 means 156 catalogued base changes, 22 of them high impact and 12 of them removals, reached over a 4-step upgrade path that Microsoft documents and that cannot be shortened. This page is a crawlable snapshot of the interactive NAV → BC delta tool, which adds filtering, tags, search, exports, and a printable migration briefing.
| Impact | Entries | What it means |
|---|---|---|
| High | 22 | Changes a process, removes something you rely on, or needs a decision before go-live. |
| Medium | 70 | Worth reviewing during design or UAT, but unlikely to change the project plan. |
| Low | 64 | Informational — new capability you can adopt later, or a change with no migration action. |
| Total | 156 | Base Business Central changes between NAV 2013 and BC 28, SaaS deployment. |
Open this comparison in the interactive tool →
Extended support for NAV 2013 / R2 ended on 10 January 2023 — 3 years 9 months ago. The system still runs, but it is unsupported: no fixes, no compliance or regulatory updates, and no Microsoft escalation path if something breaks.
Microsoft documents a 4-step route from NAV 2013 to BC 28. There is no supported single-step upgrade, and the intermediate versions are not optional — each one converts the database schema the next one expects. NAV 2013 is the harder case: it does not appear in any Business Central upgrade-path table, so the first hops happen entirely on the NAV side before Business Central will accept the database.
Every migration to BC 28 shares the risks below. These are the parts that apply to NAV 2013 and not to the other source versions on this site.
| Feature | Introduced | Impact | Status |
|---|---|---|---|
| UK Making Tax Digital (MTD) ongoing compliance | BC14 (2019 W1) (approx.) | High | New or changed |
| API-first integration model | BC14 (2019 W1) (approx.) | High | New or changed |
| AL programming language | BC14 (2019 W1) (approx.) | High | New or changed |
| Power BI embedded reporting | BC15 (2019 W2) (approx.) | High | New or changed |
| AppSource & per-tenant extensions | BC15 (2019 W2) (approx.) | High | New or changed |
| Environments & sandboxes | BC15 (2019 W2) (approx.) | High | New or changed |
| Monthly minor updates and biannual major waves | BC15 (2019 W2) (approx.) | High | New or changed |
| Windows desktop client removed | BC15 (2019 W2) | High | Removed / deprecated |
| C/AL and C/SIDE removed — AL extensions only | BC15 (2019 W2) | High | Removed / deprecated |
| G/L dimension correction tool | BC18 (2021 W1) | High | New or changed |
| Basic Auth (web service access keys) removed for SaaS | BC20 (2022 W1) | High | Removed / deprecated |
| VAT Date independent of Posting Date | BC21 (2022 W2) | High | New or changed |
| Financial Reports replacing Account Schedules | BC21 (2022 W2) | High | New or changed |
| Custom fields moved into extensions during migration | BC21 (2022 W2) | High | New or changed |
| Point-in-time environment restore and deleted-environment recovery | BC21 (2022 W2) | High | New or changed |
| E-Documents framework as a global capability | BC23 (2023 W2) | High | New or changed |
| Cloud migration path from v14 cut off | BC26 (2025 W1) | High | Removed / deprecated |
| Concurrent inventory and warehouse posting | BC26 (2025 W1) | High | New or changed |
| Cloud migration from any SQL Server database | BC27 (2025 W2) | High | New or changed |
| French e-invoicing mandate support | BC28 (2026 W1) | High | New or changed |
| Quality management for incoming goods and materials | BC28 (2026 W1) | High | New or changed |
| Employee expense management | BC28 (2026 W1) | High | New or changed |
Native MTD VAT submission to HMRC, including OAuth authentication, return submission, and obligation polling. Continually updated for HMRC API changes.
REST APIs (v2.0) cover most master and transactional data. OData v4 web services for custom endpoints.
AL (modern, VS Code based, Git-friendly, package-managed) replaces C/AL (old, monolithic, C/SIDE-locked). All BC customisation happens in AL.
Power BI reports embedded directly in role centres and list pages, with native data connectors for BC.
Customisations are deployed as AL extensions, either from AppSource or as per-tenant extensions. No more direct object modifications.
Tenants can have one production and multiple sandbox environments. Sandboxes can be copied from production for testing.
BC SaaS receives monthly minor updates plus two major waves per year (April, October). Major waves can be deferred up to 90 days but not skipped.
The classic Windows (RTC-style) client was removed in BC15 — from then on the browser client and mobile apps are the only clients. The interim UWP Windows app was itself retired in BC19 in favour of a web-wrapper app.
BC15 removed the C/SIDE development environment and C/AL language entirely. The base application became AL, and all customisation must ship as AL extensions — there is no in-database custom code from BC15 onward.
Posted G/L entries can have their dimensions corrected after the fact, with a full audit trail. Previously required reverse-and-repost or direct SQL fixes.
Web-service access keys (Basic Auth) were switched off for Business Central online in BC20. Integrations authenticate with OAuth 2.0 via Microsoft Entra ID from then on.
VAT Date is now a separate field on documents and entries, distinct from Posting Date. Allows VAT to be reported in a different period from the GL posting, with separate posting period controls (Allow VAT Date From/To).
Account Schedules renamed and rebuilt as Financial Reports, with row and column definition pairing, easier rendering to Excel and PDF, and better drill-down.
Fields added directly to base tables in the on-premises database can be mapped into an extension as part of cloud migration, instead of blocking the move.
Environments can be restored to a chosen point in time within the retention window, and recently deleted environments can be recovered, from the admin centre without raising a support request.
A general-purpose electronic document framework in the base application, handling inbound and outbound document exchange with pluggable formats and service providers, rather than a separate feature per country.
Direct cloud migration and data upgrade from Business Central Spring 2019 (v14) was removed in BC26 — older databases now need intermediate hops before they can reach current SaaS versions.
Multiple users can post inventory transactions at the same time, following the equivalent change for warehouse entries in the preceding wave.
The cloud migration tool accepts any SQL Server database as a source rather than only a supported NAV or BC on-premises install, so heavily modified or partially upgraded databases can be migrated without an intermediate version hop.
Electronic invoicing for France is delivered through the E-Documents framework, aligned to the French mandate's phased obligations.
A built-in capability to define quality specifications and record inspection results against incoming goods and materials, in preview from late 2025 and generally available April 2026.
Expense reports as a native capability, with mobile capture, an approval process, and travel requisitions arriving through 2026, working alongside the Expense Agent.
| Feature | Introduced | Impact | Status | What changes |
|---|---|---|---|---|
| Tell Me search bar | BC14 (2019 W1) (approx.) | Medium | New or changed | Universal search bar (Alt+Q) for finding pages, reports, and actions across the application. |
| Saved views on lists | BC15 (2019 W2) | Medium | New or changed | Users can save filtered, sorted views of any list page and share them with colleagues. Personal and shared views supported. |
| Power Automate connector for BC | BC15 (2019 W2) (approx.) | Medium | New or changed | First-class Power Automate connector for BC, enabling no-code automation across BC and other Microsoft 365 services. |
| Telemetry via Application Insights | BC15 (2019 W2) (approx.) | Medium | New or changed | Business Central emits operational telemetry to Azure Application Insights, queryable with KQL, alertable, and dashboardable. Environment-level telemetry applies from 2019 wave 2; per-extension telemetry was added in 2020 wave 2, and the set of available signals has grown in almost every wave since. |
| Automation API for tenant configuration | BC15 (2019 W2) (approx.) | Medium | New or changed | REST endpoints for managing tenant configuration: companies, users, permission sets, environment operations. |
| Personalisation and tenant customisation | BC15 (2019 W2) (approx.) | Medium | New or changed | Per-user personalisation, plus tenant-wide customisation (Designer mode) without writing AL code. Customisations survive updates. |
| Multiple windows / tabs | BC15 (2019 W2) | Medium | New or changed | Open multiple BC pages in separate browser windows or tabs — multitasking that was awkward in earlier BC. |
| Copy and paste rows from Excel | BC15 (2019 W2) (approx.) | Medium | New or changed | Copy a range from Excel and paste directly into list pages. Validates each row on paste. |
| Bank Data Conversion Service retired | BC15 (2019 W2) | Medium | Removed / deprecated | The NAV-era Bank Data Conversion Service was deprecated in BC15 in favour of the AMC Banking 365 Fundamentals extension — which Microsoft is in turn retiring from its Marketplace bundle in 2027. |
| Legacy best-price calculation replaced | BC16 (2020 W1) | Medium | Removed / deprecated | The old best-price logic was deprecated in BC16 and replaced by the new, extensible sales pricing experience. |
| Mobile approvals via Outlook & Teams | BC17 (2020 W2) (approx.) | Medium | New or changed | Approval requests reach approvers where they already are: the Business Central add-in in Outlook, and from BC17 the Business Central app in Microsoft Teams, with richer adaptive cards added in later waves. The approval engine itself is the NAV one. |
| Improved change tracking and audit trail | BC17 (2020 W2) (approx.) | Medium | New or changed | System audit fields (created and modified, by whom and when) were added to every table in 2020 wave 2, sitting alongside the change log and field monitoring for sensitive fields. Later waves added change log configuration telemetry, Microsoft Purview auditing, a printable Audit Trail report, and permission and approval auditing APIs. |
| VAT Group Management | BC17 (2020 W2) | Medium | New or changed | Members of a VAT group can submit returns to a group representative, who consolidates and files a single group return — including under UK MTD. |
| Edit in Excel (modern) | BC18 (2021 W1) (approx.) | Medium | New or changed | Edit in Excel opens a list page in Excel, edits are made there and published back. The capability is not new, but BC18 was the wave that made it reliable, and later waves extended it to more surfaces including recurring and intercompany journals, item journals, and warehouse worksheets. |
| Legacy web service protocols phased out (OData v3, SOAP) | BC18 (2021 W1) | Medium | Removed / deprecated | OData v3 endpoints were removed in BC18, and SOAP has been on a staged deprecation path since — Microsoft pages exposed as SOAP endpoints are disabled by default from BC26 and removed from 2026 wave 2. New development targets the OData v4 REST APIs. |
| VAT reporting in the W1 base | BC19 (2021 W2) (approx.) | Medium | New or changed | VAT return generation, submission, and audit-style reporting moved into the W1 base, replacing country-specific implementations for many jurisdictions. |
| Word and Excel layouts as first-class report formats | BC20 (2022 W1) (approx.) | Medium | New or changed | Reports can have Word or Excel layouts that non-developers can edit, alongside or instead of RDLC. |
| Shopify connector | BC20 (2022 W1) | Medium | New or changed | First-party Shopify connector for product, inventory, customer, and order sync. |
| Auto-save as you work | BC21 (2022 W2) | Medium | New or changed | Changes are saved as they are made, with the save state shown on the page, rather than depending on the user closing or committing a record. |
| Business Central embedded in Microsoft Teams | BC21 (2022 W2) | Medium | New or changed | Business Central pages can be embedded as tabs in Teams, alongside record sharing with previews and access for users with certain Microsoft 365 licences. |
| G/L Settlement (apply ledger entries) | BC22 (2023 W1) | Medium | New or changed | Bookkeepers can apply G/L entries against each other during reconciliation, similar to customer/vendor application. Useful for clearing suspense accounts and reconciliation accounts. |
| Statistical Accounts | BC22 (2023 W1) | Medium | New or changed | Non-financial numerical data (headcount, square footage, visitor numbers) can be entered against G/L periods and combined with financial data in account schedules and analyses. |
| Intercompany postings rebuild | BC22 (2023 W1) | Medium | New or changed | Intercompany setup, transaction routing, and reconciliation rebuilt. Less manual matching, better visibility on in-flight transactions across companies. |
| Approval workflows via Power Automate | BC22 (2023 W1) | Medium | New or changed | Approval flows can be designed in Power Automate using BC connectors, with custom routing logic, conditional approvers, and integration with non-BC systems. |
| Warehouse pick and put-away enhancements | BC22 (2023 W1) (approx.) | Medium | New or changed | A concentrated wave of warehouse workflow work: warehouse documents can be created with filters that control their content, bin and zone codes appear dynamically on the documents that need them, non-inventory items can be shipped and received on warehouse documents, and navigation between warehouse and inventory documents was reworked. |
| Warehouse Management module unification | BC22 (2023 W1) | Medium | New or changed | Inventory and warehouse modules increasingly unified: consistent terminology, fewer duplicate pages, clearer migration path between basic and advanced WHS configurations. |
| Permission sets and security groups overhaul | BC22 (2023 W1) (approx.) | Medium | New or changed | Security in Business Central was rebuilt across several waves: permission sets became AL objects deployed by extensions from version 18, security groups backed by Microsoft Entra arrived in 2023 wave 1, and legacy user groups were finally replaced in 2024 wave 2. |
| Financial consolidation improvements | BC23 (2023 W2) (approx.) | Medium | New or changed | Better consolidation reporting, FX handling on consolidation, dimension mapping between subsidiaries and consolidated entity. |
| List analysis mode (pivot/excel-like) | BC23 (2023 W2) | Medium | New or changed | Toggle on any list page into an Excel-like analysis view: pivots, summaries, cross-tabs, all in-app without exporting. |
| EDI / electronic invoicing improvements | BC23 (2023 W2) (approx.) | Medium | New or changed | Improved support for PEPPOL, e-invoicing mandates across multiple EU jurisdictions, OIOUBL and similar formats. |
| Include or exclude tables from cloud migration | BC23 (2023 W2) | Medium | New or changed | Administrators choose which tables take part in a cloud migration rather than moving the whole database, with the selection managed per run. |
| Directed pick and put-away suggestions in basic warehouse setups | BC23 (2023 W2) | Medium | New or changed | Guidance on where to pick from and put away to is available in basic warehouse configurations, not only in full directed put-away and pick. |
| Projects invoiced to multiple customers | BC23 (2023 W2) | Medium | New or changed | A single project can be invoiced to more than one customer, with planning lines directed to the relevant paying party. |
| Assemble to project | BC23 (2023 W2) | Medium | New or changed | Assembly orders can be linked directly to a project, mirroring the assemble-to-order flow used in sales. |
| General Ledger Allocations | BC23 (2023 W2) | Medium | New or changed | A dedicated allocations capability for distributing costs and revenue across accounts and dimensions on defined rules. |
| Intercompany transactions across environments | BC23 (2023 W2) | Medium | New or changed | Intercompany transactions flow between companies in different Business Central environments, not only between companies in one database, with intercompany general journals included in approval workflows. |
| Digital vouchers | BC23 (2023 W2) | Medium | New or changed | Rules requiring a supporting digital document to be attached to postings, with enforcement configurable by transaction type. |
| Payment practices and payment times reporting | BC23 (2023 W2) | Medium | New or changed | Reporting on how quickly suppliers are paid, for regimes that require large businesses to publish payment performance, extended with a dedicated Payment Practices feature in the UK localisation in 2026. |
| Reduced database locking | BC23 (2023 W2) | Medium | New or changed | Platform work to reduce lock contention in the database, alongside broader data stack performance improvements. |
| Sustainability module | BC24 (2024 W1) | Medium | New or changed | Native module for tracking emissions across scopes 1, 2, and 3. Sustainability Ledger entries integrate with G/L. Continued investment in subsequent waves. |
| Incoming documents: external OCR plus Copilot line matching | BC24 (2024 W1) (approx.) | Medium | New or changed | The Incoming Documents page carries over from NAV, and OCR itself remains a third-party service you contract for from Marketplace rather than something Microsoft ships. What Business Central added is AI assistance on the Business Central side of the process - Copilot mapping of e-document lines to purchase order lines from BC24 - alongside the E-Documents framework as the structured alternative to scanning paper at all. |
| Projects (formerly Jobs) modernisation | BC24 (2024 W1) | Medium | New or changed | The Jobs module was renamed to Projects in BC24, with a substantially rebuilt UX, modernised costing workflows, and improved time-sheet integration. |
| Automated reminders and collections | BC24 (2024 W1) | Medium | New or changed | The reminder process runs on automation: scheduled creation, issuing, and emailing of reminders with per-customer reminder terms and communication texts. |
| Dynamics 365 Field Service integration | BC24 (2024 W1) | Medium | New or changed | Native integration with Dynamics 365 Field Service: work orders flow to BC for invoicing, item availability is visible from Field Service, and the service module connects both ways (deepened through BC26). |
| Barcode scanning in the mobile app | BC24 (2024 W1) | Medium | New or changed | AL-controlled barcode scanning works across the mobile app — item lookup, inventory counts, and warehouse scenarios — without third-party scanning apps. |
| User groups replaced by security groups | BC25 (2024 W2) | Medium | Removed / deprecated | Legacy user groups were deprecated from BC22 and replaced by security groups plus composable permission sets, with the replacement completing in BC25. |
| Projects integrated with warehouse and replenishment | BC25 (2024 W2) | Medium | New or changed | Projects work with directed put-away and pick warehouses, items can be replenished for projects, and project items can be received through receipts and put-aways. |
| Customer-managed encryption keys | BC25 (2024 W2) | Medium | New or changed | Data at rest can be encrypted with a customer-managed key held in the customer's own key vault, rather than only with Microsoft-managed keys. |
| Job queue failure notifications | BC25 (2024 W2) | Medium | New or changed | Notifications when job queue entries fail, delivered both inside the product and to external channels, plus warnings about background processing problems. |
| Service-provider connectors for e-documents | BC26 (2025 W1) | Medium | New or changed | Connectors for third-party e-document service providers plug into the framework, covering access-point and document-exchange services across several markets. |
| German e-invoicing formats (XRechnung, ZUGFeRD) | BC26 (2025 W1) | Medium | New or changed | German e-invoicing formats are supported through the E-Documents framework, alongside the localised framework for Germany delivered in the preceding wave. |
| Production order lifecycle controls | BC26 (2025 W1) | Medium | New or changed | Finished production orders can be reopened, orders that already carry consumption can be cancelled, and items or variants can be blocked from production output. |
| Manufacturing costing accuracy and cost-adjustment control | BC26 (2025 W1) | Medium | New or changed | Improvements to how manufacturing costs are calculated and adjusted, together with better control and troubleshooting of cost adjustment runs. |
| Production output through warehouse put-aways and picks | BC26 (2025 W1) | Medium | New or changed | Production output can be handled with warehouse put-aways, overpicking is supported for production orders, and warehouse picks can be omitted for manual flushing methods. |
| RDLC report layout deprecation path | BC27 (2025 W2) | Medium | Removed / deprecated | Some legacy RDLC layouts are being phased out (deferral reports replaced with Word/Excel in BC27). Wider RDLC deprecation may follow. |
| Sales Order Agent (autonomous order-taking) | BC27 (2025 W2) | Medium | New or changed | An autonomous Copilot agent that monitors a mailbox, reads customer order emails, drafts sales quotes and orders, matches items, and routes everything through human review. Preview from BC25, generally available November 2025. |
| Payables Agent (automated vendor invoice capture) | BC27 (2025 W2) | Medium | New or changed | An agent that picks up vendor invoices from email, drafts purchase invoices, matches them to purchase orders, and flags its own confidence level for review. Generally available November 2025. |
| MCP server for AI agent integration | BC27 (2025 W2) | Medium | New or changed | Business Central exposes its data and actions to external AI agents through a Model Context Protocol (MCP) server, in preview from October 2025 and extended in BC28 with broader data access and an agent task pane to manage work from all agents in one place. |
| Power BI apps rebuilt (finance, sales, purchasing, inventory, manufacturing) | BC27 (2025 W2) | Medium | New or changed | The bundled Power BI apps were rebuilt on modern semantic models with dozens of ready reports per area, drill-back into BC, and open-sourced templates you can extend. |
| Export sandbox environment databases | BC27 (2025 W2) | Medium | New or changed | Sandbox databases can be exported from the admin centre, giving a downloadable copy of the environment's data. |
| Clearance model support in the E-Documents framework | BC27 (2025 W2) | Medium | New or changed | The framework supports clearance-model regimes, where invoices are submitted to a tax authority for validation before they reach the customer. |
| Excise, plastic, and sugar tax calculation | BC27 (2025 W2) | Medium | New or changed | Calculation of excise duties and of environmental levies such as plastic packaging and sugar taxes, delivered across the 2025 wave 2 and 2026 wave 1 releases. |
| Document attachments stored outside the database | BC28 (2026 W1) | Medium | New or changed | Document attachments can be stored in external Azure storage rather than the BC database. Reduces database size and backup duration. |
| Reimplementation projects in the cloud migration tool | BC28 (2026 W1) | Medium | New or changed | The migration tooling supports a reimplementation path \u2014 bringing master data and balances into a freshly configured environment \u2014 rather than only lift-and-shift of an existing database. |
| Payments handled within the E-Document framework | BC28 (2026 W1) | Medium | New or changed | The framework extends beyond invoices to payment documents, keeping payment exchange in the same pipeline as other electronic documents. |
| Subcontracting in production processes | BC28 (2026 W1) | Medium | New or changed | Dedicated subcontracting capabilities within production, covering the flow of material and operations out to and back from a subcontractor. |
| Self-billed invoices | BC28 (2026 W1) | Medium | New or changed | Native support for self-billing, where the buyer raises the invoice on the supplier's behalf. |
| Withholding tax on vendor transactions | BC28 (2026 W1) | Medium | New or changed | Withholding tax calculation for vendors in the base application rather than only in specific localisations. |
| Accelerated depreciation and investment allowances | BC28 (2026 W1) | Medium | New or changed | Accelerated depreciation methods for fixed assets, alongside support for investment-boost style first-year allowances, plus the ability to create multiple fixed asset cards at once. |
| Permission and approval auditing | BC28 (2026 W1) | Medium | New or changed | Auditing of user and group permissions across installed apps, with APIs for analysing permissions and approval workflows for auditors and IT staff. |
On Business Central online, Document Capture is an AppSource extension. NAV-era installs based on C/AL objects delivered as a FOB, and any C/AL customisation layered on top of them, have no path forward as code - Continia documents the conversion as a separate exercise from the Business Central upgrade itself.
Continia states it plainly: if you migrate to Business Central online, you can no longer use on-premises OCR. The locally installed ABBYY engine and the Continia File Service that feeds it are on-premises only, and recognition moves to the Continia Cloud OCR engine.
Structured document exchange over Peppol and equivalent national networks, using the Continia Delivery Network as the access point. Business Central documents are converted to and from XML, with validation before sending, order responses back from vendors, and localised formats including OIOUBL, PINT and PINT A-NZ, SimplerInvoicing, FA(3) for Poland, and the French plateforme agreee designation.
LS Nav was officially rebranded to LS Central in 2019, running on Business Central. LS Retail's product investment now happens almost exclusively in LS Central; LS Nav is in legacy support.
LS Central runs on BC SaaS. POS can be online or hybrid (online + offline fallback). Continued development and ISV ecosystem support.
LS Central's POS runs in the browser against the SaaS tenant, with LS Hardware Station installed locally to drive receipt printers, EFT terminals, scanners, scales, and cash drawers.
LS Pay is the unified payment integration layer with certified plugins for payment providers and terminals, replacing the bespoke EFT integrations typical of LS Nav sites.
Stores that must trade through connectivity loss can run offline POS with a local database, kept in sync with the SaaS head office through Azure Storage-based web replication.
No, and NAV 2013 is the harder case — it appears in no Business Central upgrade-path table at all. Microsoft's documented route is 4 steps: NAV 2013 → Dynamics NAV 2018 CU2, then the latest NAV 2018 CU → Business Central Spring 2019 → Business Central 2024 release wave 2 → Business Central 2026 release wave 1. The first hops run entirely on the NAV side, before Business Central will accept the database at all.
Extended support for NAV 2013 / R2 ended on 10 January 2023 — 3 years 9 months ago. The system still runs, but it is unsupported: no fixes, no compliance or regulatory updates, and no Microsoft escalation path if something breaks.
156 catalogued base changes: 22 high impact, 70 medium and 64 low, including 12 removals or deprecations. 125 of the 156 are verified against the Microsoft release notes cited on this page. A further 19 entries cover Continia Document Capture and LS Central add-ons.
They are rewritten. Microsoft attaches the same condition to every path off this version: it requires you convert your application from C/AL to AL. C/SIDE objects do not carry forward — customisations become AL extensions, and codeunit 1 is replaced by the system event model rather than migrated.
Not directly. Microsoft is explicit: if you are on a version of Dynamics NAV you must upgrade to Business Central on-premises first, then switch to Business Central online. The cloud migration tool has no NAV 2013 source path, so the on-premises route above is a prerequisite, not an alternative.
The NAV 2018 hop is two upgrades, not one. NAV 2013 and 2013 R2 are the only sources Microsoft routes through a specific cumulative update: a full application-and-data upgrade to NAV 2018 CU2, then a second full upgrade onto the latest CU. Budget two data upgrades for this step alone.
Yes. Business Central Spring 2019 (v14) is the mandatory bridge for anything on version 13 or earlier, and it is the only release that accepts a converted NAV database. Mainstream support for v14 ended in October 2023, so it is a staging point to move through quickly, not somewhere to sit.
NAV 2009 R2 → BC 28 (2026 W1) · NAV 2015 → BC 28 (2026 W1) · NAV 2016 → BC 28 (2026 W1) · NAV 2017 → BC 28 (2026 W1) · NAV 2018 → BC 28 (2026 W1) · BC 14 (2019 W1) → BC 28 (2026 W1)