Skip to main content

Time to Say Good Bye to Dynamics 365 Business Central 13.

Hi Readers,

If you are surprized after reading the title please don't be, its true based on Modern Lifecycle Policy.

Every product which is released comes up with a Mainstream Support. When the product is changing it also comes up with change in Release and Mainstream support End Dates.

Business Central 13 was the first version in the Future Journey of the Product. This version Marked the Era of Modern Client and New Name of Product aka "Business Central".

BC13 you will be remembered always. "You were the first milestone toward Journey of SaaS ."

What Does that Means? Read here.

MSDN - Fixed Lifecycle Policy.

If you are currently using Business Central 13 its time to plan for your next upgrade which will be not a big deal.

Mainstream Support End Dates - Read Here for Other Versions.

Below is the list of currently Supported Version - 
  1. Dynamics NAV 2016.
  2. Dynamics NAV 2017.
  3. Dynamics NAV 2018.
  4. Dynamics 365 Business Central on-premises April 2019 (14.X).
  5. Dynamics 365 Business Central on-premises October 2019 (15.X).
  6. Dynamics 365 Business Central 2020 Wave 1 (16.X).

What are my options?

You can still do a quick upgrade to Business Central 14.

OR

If you worked with your partner during last upgrade about eventing your customs then check what is the % Eventing completed. And based on that % you can decide your future version.

Here are some scenarios - 

Eventing Completed 100% & All your addons are available as Extension.
Upgrade to Business Central 2020 Wave 1 (16.x) on Prem or BC SaaS Online.
Eventing Completed ~100%, Only Custom Pending are around Option Fields & All your addons are available as Extension.
Upgrade to Business Central 2020 Wave 1 (16.x) on Prem or BC SaaS Online.

Eventing Completed 100% & Any addons is not available as Extension.
Upgrade to Business Central 14 and Check when Addon will be available as Extension.
Eventing < 100 % & All your addons are available as Extension.
A Preparade Project for completing eventing and then 
Upgrade to Business Central 2020 Wave 1 (16.x) on Prem or BC SaaS Online.

Eventing < 100 % & Addons are not available as Extension.
Upgrade to Business Central 14 and Check when Addon will be available as Extension.

So in Summary we have two dependencies for Upgrade after Business Central 14 -

  1. All Custom Code Evented.
  2. All Addons are available as Extension.

** You can modify base app (on-Prem) and upgrade to 16, but its not recommended.


Links that can help you plan your next upgrade - 

1. Free Upgrade Quote.

2. Upgrade Subscription.

3. Upgrading to Business Central.

4. Free eBook about Upgrades.

Hope you find this information useful. Let me know your views as comment to this article.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.