Upgrade Path Planner

SYSPRO ERP upgrade path planner: SYSPRO 6.1 and 7 to SYSPRO 8 2026

Pick the SYSPRO release you run today and the SYSPRO 8 release or SYSPRO Cloud ERP you are moving to. The planner lays out the documented route (ISAM to SQL, SYSPRO 7 Update 1, the SYSPRO 8 Readiness Check, database conversion, then release updates through the SYSPRO Installer Application), what changed in every release you cross, and a risk score, effort range and regression test plan sized to your VBScripts, e.net integrations, reports and companies.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 30 cited sources.

1Releases
Verify with vendorRelease year not verified. The conversion brings databases to the latest Update 1 level, 7.0.1.0007.
CurrentYear from the release name. Help is published for 2026 R1 and 2026 R2.
2Landscape
What to count in SYSPRO
customizations:
VBScripts on forms, custom form fields, Customize Application changes, Application Designer apps, custom COBOL programs called from DFM, eSignatures, triggers or workflows, custom SQL tables.
integrations:
e.net business object callers through WCF or web services, OData Service readers, Document Flow Manager, tax connectors, third-party add-ons.
interfaces:
EDI and B2B XML imports, EFT bank files, Bulk Insert loads, scheduled SQL extracts.
reports:
SRS documents and reports on SAP Crystal, Reporting Services designs, GL Report Writer layouts, Embedded Analytics dashboards.
sites:
Companies in SysproAdmin. Each one is converted and updated, and each needs its own reconciliation.
Modules in use
Integration types
SYSPRO 7 Update 1 on SQL ServerSYSPRO 8 2026 R1 and R2 (current)

SQL sources: upgrade version by version to SYSPRO 7 Update 1, pass the SYSPRO 8 Readiness Check, run Conversion of Databases to SYSPRO 8 Format, then update to the target release.

Steps
18
1 to confirm
Releases crossed
6
SYSPRO 8
Risk
53 / 100
Moderate
Effort
85-225 d
about 4-11 person-months
  1. 1
    PreparationDocumented

    Build a separate test environment from a production copy

    SYSPRO describes migrating SYSPRO 7 Update 1 ISAM data to SQL on a separate environment before running the SYSPRO 8 Readiness Check. Use the same copy to time the conversion of every company and to run the regression tests before the production run.

    Source 22
  2. 2
    PreparationDocumented

    Fix collation, compatibility level and auto close on every SYSPRO database

    ISAM data is case sensitive, so stock codes ABC and abc collide in InvMaster on a case-insensitive database. Change the system-wide and company databases to a case-sensitive (_CS) or binary (_BIN2) collation, for example Latin1_General_CS_AS or Latin1_General_BIN2; a T-SQL collation change does not apply to existing tables and columns. Set the compatibility level to 100 or higher and make sure auto close is off.

    SQL Server Management StudioSource 22Source 23
  3. 3
    ConversionDocumented

    Convert custom form data to the '+' table format in SYSPRO 7

    SYSPRO 8 removed the single table that stored all custom form data; custom form data must use separate tables per master table. The conversion stops when IMPACT.INI has the blank entry IMPCFM=. Migrate the format with the Custom Form admin tool before converting.

    Source 22Source 23
  4. 4
    ConversionDocumented

    Replace technologies SYSPRO 8 does not support

    Removed in SYSPRO 8: ODBC DSN connections to SQL Server (use a connection string, SQLSSN in IMPACT.INI), CCI client-server communication (use the SYSPRO Communications Service on WCF), legacy HTML web-based applications, SAP Crystal 2008, ISAM data, Preactor integration (SYSPRO MOM is the stated replacement) and direct calls to Encore.dll over COM or DCOM (use the SYSPRO 8 e.net Communications Load Balancer service; web services still work).

    Source 22Source 23
  5. 5
    ConversionDocumented

    Recode VBScripts that use enetguid, and check third-party products

    VBScripts that invoke e.net business objects through the legacy enetguid variable must be recoded to use CallBo. From SYSPRO 8 only authorized operators can call the Custom Form Query business object (COMQFM) directly. Confirm each third-party product has a SYSPRO 8 compatible version and licence before you start.

    Source 22
  6. 6
    ValidationDocumented

    Run the SYSPRO 8 Readiness Check from SYSPRO 7 Update 1

    A diagnostic program run on the SYSPRO 7 Update 1 SQL databases (be on port 36 for the latest version of the check). It lists the system-wide database and one row per company read from the ADMCTL control files in WORK. Critical items block conversion: SQL Server older than 2008 R2, database compatibility level below 100, case-insensitive collation (_CI), legacy custom form data format, ISAM files that need re-indexing, existing tables with names reserved for the conversion, and custom COBOL programs (not defined in IMPPRG.IMP) called from Document Flow Manager, Electronic Signatures, Task Items, Events, Triggers or Workflows.

    SYSPRO 8 Readiness CheckSource 22
  7. 7
    PreparationDocumented

    Post, balance and freeze SYSPRO 7

    Post all pending transactions to the General Ledger, get all modules into the same period, run the Balance function in every module and keep the reports, print distribution reports and At a Glance for all modules, then log out operators and e.net users, stop the SYSPRO services and block logins until migration is complete. Make sure no documents are queued in Document Flow Manager.

    Source 22
  8. 8
    PreparationDocumented

    Back up databases and the WORK and DATA folders

    Re-index ISAM files, run the SQL Server Diagnostic program on tables, indexes and columns, back up the system-wide and company databases plus any related third-party databases, and back up every folder that holds data or customization, including WORK and DATA, which hold the ISAM files migrated during conversion.

    Source 22
  9. 9
    UpgradeDocumented

    Install SYSPRO 8 with the SYSPRO Installer and a new licence

    Install with a SYSPRO Administrator login and a SQL Server admin login that can create and drop databases, tables and columns and issue BULK INSERT. The new SYSPRO 8 licence must cover the modules you use. Services are reinstalled: keep the SYSPRO 7 port numbers to reuse firewall rules and endpoints, or update calling applications to the new ports.

    SYSPRO InstallerSource 22Source 21
  10. 10
    ConversionDocumented

    Run Conversion of Databases to SYSPRO 8 Format

    The wizard starts from the SYSPRO 8 login when IMPACT.INI shows a migration is due. It writes encrypted SQLADM and SQLSTD logins plus SQLBLK and SQLCPG to IMPACT.INI, renames the company cross-reference table to SysproAdmin, brings each database to the latest SYSPRO 7 Update 1 level (7.0.1.0007), creates the SYSPRO 8 tables, bulk-inserts ISAM data and moves each file to ISAM_ARCHIVE, updates tables and columns, and rebuilds foreign keys. Audit data can only be converted now; archives (Lots, Sales Orders, Jobs, ECC Structures) can be converted later. The log is base\settings\SYSPRO8_Conversion_Log.txt.

    Conversion of Databases to SYSPRO 8 FormatSource 23
  11. 11
    ConversionDocumented

    Convert archived lots, sales orders, jobs and ECC structures

    Archive data is not available in SYSPRO 8 until it is converted. Convert it during the conversion or later with the Archiving Migration program. Lot archive files that need re-indexing are critical before conversion.

    Archiving MigrationSource 23Source 22
  12. 12
    ConversionDocumented

    Restore SYSPRO 7 custom form fields with IMPCFC CONVERT

    SYSPRO's current update guides warn that custom form fields added in SYSPRO 7 Update 1 may not display after conversion and changes may not save. Run IMPCFC CONVERT from the Run a program window to convert the ADMPRO file in \Base\Settings on the application server.

    IMPCFC CONVERTSource 7Source 3
  13. 13
    PreparationDocumented

    Bring servers and clients to the target platform

    Only 64-bit operating systems are supported from 2021 R2. For 2025 and 2026 the application server needs Windows Server 2022 or later, SYSPRO Runtime 10, the Microsoft Core 3.1.12 Windows Hosting Bundle, .NET Desktop Runtime 8.0.10 (x64 and x86) and .NET Framework 4.8.1 for the e.NET Communications Load Balancer; SQL Server must be 2019 or later and clients Windows 11.

    Source 12Source 7Source 3
  14. 14
    PreparationDocumented

    Get the licence the target release requires

    The 2025 update needs a new SYSPRO licence on the application server. For 2026 a new licence is not needed when updating from 2025 but is needed from 2024 or earlier. SYSPRO is also ending the Initial and Annual License Fee model (1 November 2026 outside the U.S., 1 January 2027 in the U.S.) in favour of a named-user subscription; a new subscription agreement is needed to keep using the software after the expiry date.

    Source 7Source 3Source 24
  15. 15
    ConversionDocumented

    Choose Reporting Services or Legacy Reporting (Crystal)

    The installer asks for the reporting engine: Reporting Services (cloud-first, server only, web designer) or Legacy Reporting with SAP Crystal Reports 2020 (SP4 server side, SP35 client side). If the Reporting Host Service is installed, the installer checks the reporting software version and you fix it on the Reporting Software screen. Additional Reporting Software 2013 and 2016 are not available for new installations from January 2024. Legacy list reports removed in 2025 must be rebuilt in Reporting Services.

    Source 7Source 12Source 5
  16. 16
    UpliftDocumented

    Log in as Administrator to run the database update for every company

    The first Administrator login runs the database update on system-wide and company tables for every company in SysproAdmin, not only the one you log in to. Duration depends on record counts. The release shows at the bottom left of the main menu afterwards.

    Source 7Source 3Source 9
  17. 17
    ValidationDocumented

    Retest customizations in the Windows client and the Web UI (Avanti)

    Most customization and Power Tailoring work unchanged, but SYSPRO recommends testing because customizations may not have been built version independent. Customizations that use .NET components such as a .NET user control do not run in Avanti, which uses HTML5 and JavaScript; test both interfaces where both are used. The scripting engine now supports C#.

    Source 22Source 27Source 6
  18. 18
    CutoverVerify with vendor

    Rehearse, cut over and reconcile against the balance reports

    Time the full run on the test copy with production-sized data, agree a freeze window, then run, compare the Balance function and At a Glance output with the reports kept before the upgrade, and release users.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the SYSPRO upgrade planner

  1. 1

    Pick your releases

    Choose your current SYSPRO release, including whether SYSPRO 6.1 or 7 still runs on ISAM, and the target SYSPRO 8 release or SYSPRO Cloud ERP.

  2. 2

    Describe your landscape

    Enter counts for customizations, e.net integrations, EDI and file interfaces, custom reports, data size, users and companies, then tick the modules and integrations you use.

  3. 3

    Read the path and the drivers

    Review each step with its SYSPRO source, the changes in every release you cross, and the drivers behind the risk score and effort range.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV. Critical tests are flagged where your path changes that area.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.

Questions

What is the latest version of SYSPRO?

SYSPRO 8 2026 R2, per the SYSPRO help site, which lists SYSPRO 8 releases from 2018 R1 to 2026 R2. SYSPRO 8 ships named releases (2018 R1 and R2 through 2021 R1 and R2, then 2022, 2023, 2024, 2025, and 2026 R1 and R2) with hotfixes in between, delivered through the SYSPRO Installer Application.

Can I upgrade from SYSPRO 7 directly to SYSPRO 8?

Only from SYSPRO 7 Update 1 with every company on SQL Server. Run the SYSPRO 8 Readiness Check in SYSPRO 7 Update 1, fix the critical items (SQL Server 2008 R2 or later, compatibility level 100 or higher, case-sensitive collation, custom forms in the '+' table format, custom COBOL programs), install SYSPRO 8 and run Conversion of Databases to SYSPRO 8 Format. Earlier SYSPRO 7 databases are skipped until they reach Update 1.

How do I upgrade from SYSPRO 6.1 or an ISAM system?

Version by version. From SYSPRO 6.1 SQL you upgrade to SYSPRO 7 Update 1 SQL, then to SYSPRO 8. From 6.1 ISAM you either upgrade to SYSPRO 7 Update 1 ISAM and migrate to SQL there, or migrate to 6.1 SQL first and then upgrade. SYSPRO 8 does not read ISAM files.

What happens to our VBScripts, custom forms and e.net integrations?

SYSPRO states most customization and Power Tailoring work unchanged, but VBScripts that use the enetguid variable must move to CallBo, custom form data must be in the '+' table format, direct Encore.dll calls are replaced by the e.net Communications Load Balancer service, and .NET user controls do not run in the Avanti Web UI. Custom form fields added in SYSPRO 7 Update 1 may need IMPCFC CONVERT after conversion.

Does updating SYSPRO need a new licence, and what does SYSPRO cost?

The 2025 update requires a new licence, and 2026 requires one when coming from 2024 or earlier. SYSPRO is ending the Initial and Annual License Fee model on 1 November 2026 outside the U.S. and 1 January 2027 in the U.S., moving all customers to a named-user subscription with the full module entitlement. SYSPRO does not publish prices; get a quote from SYSPRO or your partner. The planner's effort range excludes subscription fees.

How should we test a SYSPRO upgrade?

Before the upgrade, post all transactions, run the Balance function and At a Glance in every module and keep the reports. Then regression test on a copy of production: sign-in and roles, VBScripts and custom forms in both interfaces, reports on the chosen reporting engine, every e.net caller and EDI or DFM flow, MRP and costing, and period end. The planner builds this list and flags critical tests for the areas your path changes.

Who does the upgrade and how do we train users?

SYSPRO sells and implements through its own team and partners in the Syspro Partner Pro program. Training runs on Syspro LearnIt Online and facilitated virtual workshops, with certifications issued as digital badges; SYSPRO does not publish exam names on its training page. Check that the people doing the work hold current SYSPRO 8 certifications.

Sources

  1. SYSPRO Help and Reference: SYSPRO 8 releases
  2. SYSPRO Roadmap Themes 2026 (2026 R1 and R2 highlights)
  3. SYSPRO: updating SYSPRO 8 to 2026 R1
  4. SYSPRO 8 SQL updates by release
  5. SYSPRO 8 program and business object updates by release
  6. SYSPRO 8 2025 feature highlights
  7. SYSPRO: updating SYSPRO 8 to 2025
  8. SYSPRO 8 2024 feature highlights
  9. SYSPRO: updating SYSPRO 8 to 2024
  10. SYSPRO 8 2023 feature highlights
  11. SYSPRO 8 2022 feature highlights
  12. SYSPRO: updating SYSPRO 8 to 2022
  13. SYSPRO 8 2021 R2 feature highlights
  14. SYSPRO 8 2021 R1 feature highlights
  15. SYSPRO 8 2020 R2 feature highlights
  16. SYSPRO 8 2020 R1 feature highlights
  17. SYSPRO 8 2019 R2 feature highlights
  18. SYSPRO 8 2019 R1 feature highlights
  19. SYSPRO 8 2018 R2 feature highlights
  20. SYSPRO 8 product overview (2018 R1 help)
  21. SYSPRO 8 reference guides (2018 R1 help)
  22. SYSPRO 8 Pre-installation - Upgrade (June 2018)
  23. SYSPRO 8 Data Conversion (June 2018)
  24. SYSPRO: formal notice, change to SYSPRO licensing
  25. SYSPRO: Cloud ERP and deployment options
  26. SYSPRO: Integration Framework
  27. SYSPRO Developer site
  28. SYSPRO: training and education
  29. SYSPRO: Partner Pro program
  30. SYSPRO home page

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.