Products reach the end of their Product Life Cycle for a number of reasons. These reasons may be due to market demands, technology innovation, and development driving changes in the product, or the products simply mature over time and are replaced by functionally richer technology.
While this is an established part of the overall product life cycle, NETRONIC Software recognizes that end-of-life milestones often prompt companies to review the way in which such end-of-sale and end-of-life milestones impact the usage of their NETRONIC Software products in their companies. With that in mind, we have set out below NETRONIC Software's end-of-life policy to help customers better manage their end-of-life transition and to understand the role that NETRONIC can play in helping to migrate to alternative NETRONIC offerings.
The following milestone definitions apply to all EOL policies:
Announcement milestone – the date on which NETRONIC Software announces via website and blog posting, that a specific product has reached his EOL. The EOL announcement provides dates by which time Marketing, Sales, development, and overall maintenance/support will end for the affected product.
The date until which – after the EOL – customers and prospects still can purchase new and upgrade licenses for the respective product; as well as they can agree new maintenance period until the end of the service period (EOS). As a general rule, the EOSM period following the EOL announcement will be a minimum of 3 months, if NETRONIC still observes a reasonable market demand for that product. During this period, the product will no longer get functionally enhanced. However, NETRONIC Software will provide bug fixes for reported bugs of the most current version at the EOL announcement. NETRONIC Software also will eventually publish Service Releases of the most current product version.
The final date for support via maintenance contracts. As a general rule, the period between EOL and EOS will be a minimum of 2 years, but could also be much longer (or shorter in exceptional cases). In the period between EOSM and EOS, no new software licenses of the affected products are available. NETRONIC Software will provide bug fixes for reported bugs of the most current version at the EOL announcement. NETRONIC Software also will eventually publish Service Releases of the most current product version.
In December 2021, we decided to align our product lifecycle management with Microsoft's (modern) lifecycle.
Read this blog post to learn all the details of this decision.
As a consequence of this decision, the following milestone dates apply.
| NAV version | End of product development | End of Marketing & Sales | End of support |
| NAV 2009 R2 | Dec 21 | Mar 22 | Jun 22 |
| NAV 2013 | Jun 22 | Jun 22 | Dec 22 |
| NAV 2013 R2 | Jun 22 | Jun 22 | Dec 22 |
| NAV 2015 | Jun 22 | Jun 22 | Jun 23 |
| NAV 2016 | Jun 22 | Dec 22 | Dec 23 |
| NAV 2017 | Jun 22 | Jun 23 | Jun 24 |
| NAV 2018 | Jun 22 | Dec 23 | Dec 24 |
| BC fall 2018 update, v. 13.x | Jun 22 | Dec 22 | Dec 23 |
| BC spring 2019 update, v. 14.x | Jun 22 | Dec 22 | Dec 23 |
| NAV version | End of product development | End of Marketing & Sales | End of support |
| NAV 2013 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2013 R2 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2015 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2016 | Dec 21 | Mar 22 | Jun 23 |
| NAV 2017 | Dec 21 | Mar 22 | Dec 23 |
| NAV 2018 | Dec 21 | Mar 22 | Dec 23 |
| BC fall 2018 update, v. 13.x | Dec 21 | Mar 22 | Dec 23 |
| BC spring 2019 update, v. 14.x | Dec 21 | Mar 22 | Dec 23 |
| NAV version | End of product development | End of Marketing & Sales | End of support |
| NAV 2013 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2013 R2 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2015 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2016 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2017 | Dec 21 | Mar 22 | Dec 22 |
| NAV 2018 | Dec 21 | Mar 22 | Dec 22 |
| BC fall 2018 update, v. 13.x | Dec 21 | Mar 22 | Dec 22 |
| BC spring 2019 update, v. 14.x | Dec 21 | Mar 22 | Dec 22 |
In December 2021, we decided to align our product lifecycle management with Microsoft's (modern) lifecycle.
Read this blog post to learn all the details of this decision.
As a consequence of this decision, the following milestone dates apply.
| Business Central version | End of product development | End of Marketing & Sales | End of support |
| BC spring 2019 update, v14.x | Dec 21 | Oct 23 | Oct 23 |
| BC 2019, release wave 2, v15.x | Apr 20 | Apr 21 | Apr 21 |
| BC 2020, release wave 1, v16.x | Apr 21 | Apr 22 | Apr 22 |
| BC 2020, release wave 2, v17.x | Apr 21 | Apr 22 | Apr 22 |
| BC 2021, release wave 1, v18.x | Oct 21 | Oct 22 | Oct 22 |
| BC 2021, release wave 2, v19.x | Apr 22 | Apr 23 | Apr 23 |
| BC 2022, release wave 1, v20.X | Oct 22 | Oct 23 | Oct 23 |
| BC 2022, release wave 2, v21.X | Apr 23 | Apr 24 | Apr 24 |
| Product | VARCHART JGantt |
| EOL | 01 December 2022 |
| EOSM | 30 March 2023 |
| EOS | 31 December 2024 |
| Product | Resource Scheduling Module for VARCHART XGantt |
| EOL | 31 December 2020 |
| EOSM | 1 January 2021 |
| EOS | 31 December 2022 |
| Product | VARCHART XGantt/ XNet / XTree ASP.NET Edition |
| EOL | 7 December 2018 |
| EOSM | 7 December 2018 |
| EOS | 31 December 2020 |
| Product | GRANEDA Dynamic |
| EOL | 18 December 2012 |
| EOSM | 30 June 2013 |
| EOS | 31 December 2016 |
