Syspro 8 2026 R1 Update Guide
In this article, we delve into several key areas to ensure a smooth transition to the latest release. From the update process to important considerations, we provide comprehensive details to guide you through the Syspro 8 2026 R1 release update.
The main topics covered include:
-
Release prerequisites
-
Update process
-
Feature updates:
-
-
SaaS Gateway
-
Sub-Contract Lead Time Sequential Calculation
-
-
Maintenance updates:
-
Bill of Material | Removal of 99 Routes Limitation
-
-
Program, Business Object and SQL updates:
-
SQL Updates by Release
-
Program and Business Object Updates by Release
-
-
SYSPRO 7 upgrade considerations
Release Prerequisites
A new license was required for Syspro 8 2025. This is not required for Syspro 8 2026 R1. However, a new license must be obtained when upgrading to Syspro 8 2026 R1 from Syspro 8 2024 or earlier.
The following must be installed on the Application server:
-
SYSPRO Runtime 10
-
Windows Server 2022 or later
-
Microsoft Core 3.1.12 or higher Windows Hosting Bundle
-
.NET Desktop Runtime 8.0.10 x64 or higher
-
.NETDesktop Runtime 8.0.10 x86 or higher
-
Microsoft .NET Framework 4.8.1
This is required for the Syspro 8 e.NET Communications Load Balancer
The following must be installed on the Microsoft SQL Server:
-
Microsoft SQL Server 2019 or later
The following must be installed on the client machine:
-
Windows 11
-
SYSPRO Runtime 10
-
.NET Desktop Runtime 8.0.10 x86 or higher
Before commencing with an update to the latest release:
-
Ensure to check the sizes of your transaction log directories and shrink the transaction logs if required.
This will ensure that you have enough disk space available for the database updates when they occur. -
Ensure to uninstall any Diagnostic Hotfixes before attempting to update your release of Syspro 8.
-
As time progresses, certain products may become retired as they are replaced by newer capabilities. Therefore, if you have an installed product that has been retired in the latest release, the application will prompt you to uninstall the retired product before proceeding with the update.
Once you have successfully uninstalled the retired product, you can proceed with updating to the latest release.
Update Process
-
Run the Syspro Installer Application on the SYSPRO Application server.
-
Once connected to the Syspro Deployment Service, enter your Syspro Online Profile login credentials (and customer code if applicable). Ensure that you use the correct credentials as subsequent notifications rely on this information.
An OTP (one time pin) is emailed to you and must be entered at the Password field.
If you can't obtain the OTP, then you can use your InfoZone password.
-
From the home screen select the SYSPRO ERP Software option.
-
Identify the deployment group you want to update and select the Update button. This creates a text file (SYSPRO_Deployment_Release_Update.txt) in the same folder where the service is installed, providing details about the machines belonging to the group, as well as the software installed on each of those machines. Software updates must be applied to all machines in a group to complete the process otherwise the deployment group remains listed as Update in progress.
-
Select Syspro 8 2026 R1 as the release to update.
In this release, you have the option of installing either the Syspro Reporting Service or Legacy Reporting (Crystal) as your reporting engine.
-
Reporting Services
This installs SYSPRO's state of the art, cloud first, server only reporting solution that provides an intuitive web interface for designing and amending reports.
View the following feature topic for more information on the deployment, user-friendly report design and maintenance.
-
Legacy Reporting (Crystal)
This installs SAP Crystal Reports 2020 that was available from Syspro 8 2023 and includes Service Pack 4 (SP4) for server-side and Service Pack 35 (SP35) for client-side.
View the following article for details on the processes to follow when updating your reporting software:
-
If the Syspro 8 Reporting Host Service is installed, the app verifies if any version of the SYSPRO Reporting Software is also installed and if its supported by the selected release.
A system message is displayed if the app detects an installed version of SYSPRO Reporting Software that is not supported by the selected release (or if its unable to detect the current version).
Select the Reporting Software option to access the Reporting Software screen, from where you can uninstall your current Reporting Software and install the correct version as required.
Once you have ensured that you have the correct version of Reporting Software installed, enable the Reporting software updated, continue Release Update option within this message box and select the Continue function to proceed with the release update.
-
-
The products you have installed are preselected at the Product Updates available for Release screen and you can select the Continue option to proceed.
-
After accepting the license terms and conditions, a summary of all products to be installed is displayed.
-
Select Begin Install to proceed with the installation of all selected products.
-
Update any additional servers in your deployment group that require an update (listed as update in progress).
-
Log in to Syspro 8 as an Administrator. A minor database update is performed to your system-wide tables and to each company-specific table.
-
The duration of the minor database update depends on the number of records in the latest database.
-
This database update applies to all companies listed within the SysproAdmin table (i.e. not just the company selected for your login).
-
You will be able to see the version of SYSPRO that you are using in the bottom left of the main menu.
-
You are now ready to start using Syspro 8 2026 R1.
Feature Updates
We are currently working on this section and will be adding more information during the first month of General Availability. Please check back regularly for updates.
We added governed hierarchy and identifier fields to the ArCustomer table to create a centralized backbone for analytics and integration. Sales, finance, and partner teams can now work from a consistent view of who the customer is and who they roll up to, enabling confident pricing, credit, investment, and commissions.
The following fields were added to the ArCustomer table:
-
DefaultContainer - VarChar(20)
-
CorporateParentID - Customer
-
PartnerID - Customer
-
BrokerID - VarChar(50)
-
SalesManager - VarChar(50)
-
ShipToDUNS - VarChar(11) Mask 99-999-9999
-
BillToDUNS - VarChar(11) Mask 99-999-9999
-
Facility - VarChar(50)
-
BillingID - VarChar(50)
-
StoreNumber - VarChar(30)
-
CustomerRefID - VarChar(50)
The new container inventory table (WhmContainerInv) defines how stock codes relate to the container types they are stored in to determine the quantity and packing configuration for a stock code. This was done to accommodate the Container-Based Contract Selling Rules enhancement that will be made available in a subsequent release.
The WhmContainerInv table structure allows the user to set container definitions at stock code level to enforce order quantities through contracts. This ensures sales orders can only be raised in multiples of certain quantities, which reduces packing errors and aligns order fulfillment.
We added the Revalue when maintaining setup option (Setup Options > Preferences > Distribution > Purchase Orders that centrally controls the revaluation of purchase orders using foreign currencies.
When the Revalue when maintaining setup option is enabled, purchase orders are revalued when the exchange rate is updated.
The Deny revalue when maintaining preference in the Purchase Order Entry program takes precedence over this setup option. If the operator has permission for and enables the Deny revalue when maintaining preference, revaluation is prevented.
We updated electronic signatures for Bill of Materials change operations to ensure triggers execute and both header and detail logging is captured.
We updated the following eSignatures:
Controls access to the Change function for Operations in the Structures and Routings program.
Controls access to the maintenance of operations in the BOM Routing Maintenance business object.
We enhanced eSignatures within the Lot Traceability module that control changes to lot expiry dates. This secures the secures Lot Number Maintenance program and ensures that only authorized users can modify lot expiry dates while maintaining a full audit trail.
We updated the following eSignatures:
Controls access to the maintenance of lots in the following programs:
- Browse on Lots
- Lot Number Maintenance
Controls access to the update of operations in the Lot Maintenance business object.
Maintenance Updates
We optimized SQL in Transfer BOM Costs to Warehouse Costs to accelerate cost updates and lower load as data grows. This enhancement improves execution efficiency through targeted SQL optimization techniques. The goal is to reduce processing time, lower system load, and ensure consistent performance as data volumes grow.
We have improved how the Transfer BOM Costs to Warehouse Costs program interacts with the database to ensure queries run faster and it uses fewer system resources.
Program, Business Object and SQL Updates
The Syspro 8 2026 R1 List of Program Changes article provides a list of all program changes made in the Syspro 8 2025 release.
This article provides a list of all program changes made in the latest release.
This topic outlines the programs and business objects that have been added or deleted for each release of Syspro 8.
This topic outlines the table changes that have been made for each release of Syspro 8.
SYSPRO 7 Upgrade considerations
Take note of the following when upgrading to Syspro 8 2025 from Syspro 7 Update 1:
All custom form fields added in Syspro 7 Update 1 are no longer displayed in the programs after converting from Syspro 7 Update 1 to Syspro 8 2026 R1. When attempting to add existing or new custom form fields to programs in Syspro 8 2026 R1, the changes are not saved.
Follow these steps to restore custom form fields to programs after converting from Syspro 7 Update 1 to Syspro 8 2026 R1:
-
Select the SYSPRO button and choose the Run a program option from the menu.
The Run Program window is displayed.
-
At the Program name field enter IMPCFC CONVERT and select Run Program.
The ADMPRO file will be converted.
-
The custom form fields added to programs are saved in the ADMPRO file within the \Base\Settings folder on the application server.
-
Custom form fields added to programs are saved per program, system-wide and for all operators and roles.
-
Copyright © 2026 Syspro PTY Ltd.

