It looks like there is an error in the document.

Upgrade from Prior Versions
Consider the following when upgrading to the current version.
• If you are upgrading from version 7.4 through 7.8, you must first upgrade to version 2013 and then upgrade to version 2023.
• If you are upgrading from version 2013, 2014, 2016, 2017, 2018, or 2019
you can upgrade directly to version 2023.
• Only three prior versions can be directly upgraded to the current version.

The third bullet point is accurate.  The first two are inaccurate and in conflict with the third bullet point.  So you would need to get to 2018 before going to 2023 (there was no version 2020).  Sorry, but I am not familiar with the intricacies of a large upgrade, but perhaps someone else can comment, or you can contact your trusted partner or Sage support.

Thank you Ramon. I could not find the download link of Sage 500 ERP 2013 (retired) at Sage portal. Can you share the downloads if possible? Regards, Jackie Q

Thank you Ramon. I could not find the download link of Sage 500 ERP 2013 (retired) at Sage portal. Can you share the downloads if possible? Regards, Jackie Q

What version will the upgrade be performed?  I believe the 2016 (7.7) upgrades will go back from 7.4.  After that, perhaps 2018 (7.9).  Then finally, 2023 (8.2).

If your upgrades starts with 7.3 or older, I do not believe  the upgrades files are available on the portal.

There may have been an issue in multiple version upgrades along the way, I don't recall where.  The safest thing to do once you get to 2016, is to do each of the subsequent versions in order (2017 - 2018 - 2019 - 2021 - 2023)  My recollection was that around 2017 to 2019 there may have been a multiple version issue on some systems.

Thank you Ramon. I have 7.4 installed. Need to upgrade to 2023. It looks it needs to upgrade to 7.5(2013) firstly. Regards

From the docs in 2016, it looks like the 2016 upgrades should work for you.7.4 was within the 3 releases back support claim.  So if you wanted, you should be able to use the 2016 upgrades to go from 7.4 to 7.5 (2013) upgrade.

Thank you Ramon. Unfortunately, Sage just provides 2019, 2020 and 2021 versions to be downloaded.  Regards

This is a little odd.  I logged onto the Customer Portal and the Sage 500 ERP 2016 Download Page .  From there, I found the 2016 database utilities.  When I tried to use them, I got an authorization error.

Every year, they come to the 500 team and ask them what is expiring and to give us the opportunity to extend things.  I had made it a point to extend Sage 500 ERP 2016 specifically as an upgrade path.  The permissions issue could be because I use a special account to get to the customer portal.

First of all, when you search the knowledgebase for "Sage 500 2016", do your results include  Sage 500 ERP 2016 Download Page?  If so, can you click the link and see all the 2016 download options?  If those options then throw a permission error for you too, then I will look into why this happens.  

Also keep in mind that upgrading can be a simple process, but it can also be a troublesome process in some cases.  Most quality partners can deal with these issues with experience, and may have the tools one would need to do this, especially when there is a need to upgrade many versions at one time.

Ramon, thank you so much for your help. Same error - the download file was removed. I will ask others to see if could find the version at backups. Regards, 

I will work on getting the customer portal updated.  Until then, you can try:

Sage 500 ERP 2016 Client

Sage500ERP2016Client.exe

https://dlm.esd.sage.com/d.aspx?_C=4f1a514f-3e3b-4050-8ac1-60d453dc26ea

or

https://cdn-dlm.esd.sage.com/Sage500/20469/Sage500ERP2016Client.exe

Sage 500 ERP 2016 Database

Sage500ERP2016Database.exe

https://dlm.esd.sage.com/d.aspx?_C=f681952e-7302-4700-abd7-b6f3c71a8505

or

https://cdn-dlm.esd.sage.com/Sage500/20470/Sage500ERP2016Database.exe

Please recall that all upgrades should be tested on a non-production environment first, and that you backup any production environment before deploying.

Hope this helps,

Ramon