mas500 upgrade to 2024

Started planning for mas500 upgrade from V7.3 to V2022.

Are intermediate upgrades required?  

If so, what are the intermediate versions required? e.g., V7.3 to V7.4 and V7.4 to V2024

Where can I get upgrade tasks or plan?  Going to new servers, both sql database and terminal server client.  Basically, replicating current environment with new hardware and updated operating systems.

Have approximately 40 users.

Thanks!

  • 0
    SUGGESTED

    When upgrading, technically you have to go through each version after the one you have.  However, each DB Utilities supports upgrades from the two previous versions.  So if you have 7.30, you would need the 7.50 version of the DB Utilities to bring it up to 7.50.  After that you would need to use the 7.70 version of the DB utilities to upgrade from the 7.50 to 7.70, etc.

    Depending upon your current SQL Server version, you would possibly need to upgrade it along the way too.  The current minimum SQL Server version supported by Sage 500  is 2012, although most would upgrade to a version beyond that.  You would possibly need to apply SQL Server upgrades while upgrading the database as, for example,  7.30 does not know about SQL Server version 2019 or 2022.

    You may be able to download the installs from Sage 500 version 2016+ from the Sage Customer Portal.  Versions prior to that (7.50 for you) can probably be had by contacting a longer term partner, or by contacting Sage support if you are on plan.  While I know Sage has the various installs on its internal systems, I do not know the Sage policy on supplying those. 

    If your system contains customizations beyond the customizer module (partner or third party customizations) then that is another issue.  7.30 is quite old (circa 2010 or so) and it will be an effort to get it up-to-date.  If your team is qualified to address the various issues then perhaps you can get it done without partner help.  You may wish to contact a qualified Sage partner to get an idea of what it will take and what sort of migration plan is feasible given any downtime restrictions and any test environments needed. 

    For reference, shown below are the version since your version:

    7.30

    7.40

    7.50 (2013) <-

    --

    7.60 (2014)

    7.70 (2016) <-

    --

    7.80 (2017)

    7.90 (2018) <-

    --

    8.00 (2019)

    8.10 (2021) <-

    --

    8.20 (2023)

    8.30 (2024) <-

    Hope this helps with what might be needed,

    Ramon

  • +1
    verified answer

    This is a potentially very large undertaking and I would suggest you not try this on your own. In fact, unless you have archived copies of the database utilities for some of the intermediate versions, you won't be able to upgrade all the way up to Sage 2024, although Support might be able to get them for you. The upgrade path is also dependent on your Sage 500 functional deployment, level of customization or add-ons, as well as the internal support you have available for the existing and proposed environments.

    I believe version 7.30 was released in 2010, so across those 14 years between 7.30 and 2024, there have been a significant number of changes in the application code, SQL engines and operating systems. The upgrade process across this many versions might be very nearly the equivalent of implementing a new ERP system.