# How to update SYSPRO (and how to check the latest version) > Source: https://netray.co/erp-help/how-to-update-syspro-latest-version > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SYSPRO 8 ships as named releases (for example 2022 R1 style names) plus later updates, and the current release is listed on the SYSPRO partner and customer portals, not on a fixed public page. To update, back up, test the new build on a copy of your data, then update the server, services and clients in a planned window. ## Kind how-to ## System syspro ## Erp SYSPRO ## Module Installation / Updates ## Query how to update syspro ## Alternate Queries - what is the latest version of syspro - current syspro version - syspro 8 update steps ## Applies To SYSPRO 8 on Windows Server with SQL Server. Release names and media change over time, so confirm the latest build with your SYSPRO partner or the SYSPRO support portal. ## Steps ### Update a SYSPRO installation safely **Items:** - Find the installed version: in the SYSPRO client use Help, About, and note the release and build. Record the same for the server and each client. - Ask your SYSPRO partner or check the SYSPRO support portal for the current release and the release notes for every release between yours and the target. - Back up SysproAdmin, every company database, the SYSPRO base folder, custom forms, reports and any e.net or integration configuration. - Restore the backup into a test environment and install the target release there first. Do not test only on a blank database. - Run the data conversion for each company in the test environment and time it, so you can size the production window. - Regression test the processes that matter: order entry, purchasing receipts, WIP issue and completion, invoicing, GL posting, month end, and every integration. - Schedule the production window, stop e.net and scheduled jobs, take a final backup, install and convert, then update clients. - Keep the previous build installers and backups until a full period close has passed on the new release. ## Sections ### Finding the version you are on **Body:** The version appears in the client About dialog and in the SYSPRO administration tools. Record both the release name and the build number, because support and release notes refer to both. Check that every client matches the server, as mismatched clients are a common cause of odd logon errors. For the latest version, do not rely on third party pages that go stale. SYSPRO publishes release information through its partner and customer channels. If you have no direct access, your reseller can confirm the current release and whether it is generally available or an early release. ### Release, update and conversion are different things **Body:** A release is a new set of features and often includes a database conversion. An update or service pack on the same release usually carries fixes and a smaller change set. The effort differs: a release needs conversion testing and user training, an update mainly needs regression testing. Plan the conversion carefully. It touches every company, runs for a time that depends on data volume, and cannot be undone except by restoring the pre-update backup. Size the window from the test run, not from guesses. ### Customisations and integrations **Body:** Custom forms, reports, VBScript and any code that uses e.net business objects can break on a new release if an XML schema or a field changes. List them before the project and test each against the target release. Third party add-ons often need their own matching version. Confirm compatibility with each vendor before you commit to a date. If you are moving from SYSPRO 7, read the separate upgrade planning page as well. ## Pitfalls - Upgrading production without a restored copy test, so the conversion time and failures are a surprise. - Updating the server but leaving clients on an older build. - Forgetting scheduled jobs and e.net callers that run overnight during the window. - Deleting old backups straight after go-live, before a period end has run cleanly. - Assuming add-ons and reports carry over unchanged. ## Ai Angle Before an update, an assistant over your own SYSPRO environment can list which custom reports, forms and integrations touch changed business objects, and draft the regression checklist from your transaction history. Netray runs this privately on your infrastructure so no schema or data leaves your network. ## Faq ### What is the latest version of SYSPRO? **Answer:** SYSPRO 8 is the current product line, delivered as named releases. The exact newest release changes over time, so confirm it with your SYSPRO partner or the SYSPRO support portal rather than a static web page. ### Can I update SYSPRO without downtime? **Answer:** Not for a release with a database conversion. Plan a maintenance window sized from a test conversion. Smaller updates may be quicker, but still need services stopped while files are replaced. ### Do I need to update every client? **Answer:** Yes. Clients should match the server build. Mismatched clients cause logon and runtime errors. Use a managed install or a published client package to keep them aligned. ### Can I go back after a failed update? **Answer:** Only by restoring the backups taken before the update. That is why the final backup and a tested restore matter more than any other step. ## Search terms how to update syspro, latest version of syspro, current syspro version, syspro 8 update, syspro upgrade steps, syspro release notes, check syspro version, syspro service pack --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json