Upgrade Path Planner
SyteLine upgrade path planner: versions 7, 8 and 9 to SyteLine 10
Pick the SyteLine release you run today and the version 10 build or Infor cloud tenant you are moving to. The planner lays out the documented route (upgrade.exe to the version 10 base, database validation, Uplift), what changed in every release you cross, and a risk score, effort range and regression test plan sized to your customizations, integrations and reports.
Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 20 cited sources.
Direct upgrade: upgrade.exe takes any previous SQL release (7, 8 or 9) to the version 10 base, then Uplift brings it to the current build. No intermediate release is documented.
- 1PreparationDocumented
Build a test copy of production and back up every database
Infor upgrade guidance is to run the upgrade first on a test environment that mirrors production, to work out issues and to time the run, and to back up the databases before you start.
- 2PreparationDocumented
Check customizations against the version 10 rules
Version 10 restricts several AppColumn and AppTable settings: next key generators must use one of the allowed formats and additional keys must be columns in the base table, so NextKeyPreGenerate logic from an earlier version may need to be reimplemented. Custom columns on SyteLine tables must be nullable or have a default, and no extra constraints or unique indexes may be added to SyteLine tables.
- 3UpgradeDocumentedlands on SyteLine 10, 2018 to 2020 builds
Run upgrade.exe to the version 10 base (Database Level 0)
upgrade.exe takes a previous SQL version of SyteLine to the version 10 base, Database Level 0 (DL 0), and merges the Forms, Application, Objects and Templates databases into one all-in-one database.
- 4UpgradeDocumented
Run each approved third-party product upgrade
Third-party products approved for Single Version ship their own upgrade. Be on the product's latest pre-Single Version release before running it, and confirm approved products with Infor.
- 5ValidationDocumented
Validate and remediate with the Database Validation and Prep Tool
The tool compares schema and objects with the Single Version manifest, reports unapproved customizations and missing schema, and confirms the databases are consolidated. Run Remediate, fix what it cannot by hand, and rerun Validate until it passes. The Single Version Installer, which includes DBValidatorUI.exe, is on the Download Center.
- 6UpliftDocumented
Uplift to the current build
A database at the version 10 base is not a working database until it is uplifted. Uplift brings it to the current build, which carries the fixes and features released since that base. Version 10 has no separate patches; changes arrive through uplifts.
- 7ConversionDocumented
Choose the route for custom reports
Version 10 produces standard reports with Mongoose Reporting and does not require SSRS. Custom SSRS reports that still need to run require SSRS on the reporting server until they are converted to Mongoose reports.
- 8ConversionDocumented
Move users from the Smart Client to the browser client
The Smart Client is being phased out in favour of the HTML5 browser client. Under the Infor OS framework the browser client is the only option.
- 9ConversionDocumented
If you use Infor Document Management: update IDM content
Back up document types, ACLs and bundling rules, import IDM_Configuration.xml, confirm your custom document types, attributes and ACLs survived, activate feature RS8485 in Feature Management, then review active IDM workflows and re-add your workflow changes.
- 10PreparationDocumented
Review features delivered behind feature keys
Some version 10 features ship switched off and are activated in Feature Management. Decide which to turn on and add them to the test scope.
- 11CutoverVerify with vendor
Rehearse, freeze and cut over
Time the full run on the test copy at least once with production-sized data, agree a freeze window, post or close open transactions as the upgrade guide for your source release requires, then run, validate and reconcile key balances before users return.
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 SyteLine upgrade planner
- 1
Pick your releases
Choose your current SyteLine release and the target: a SyteLine 10 build on-premises or hosted, or multi-tenant CloudSuite Industrial.
- 2
Describe your landscape
Enter counts for customizations, integrations, file and EDI interfaces, custom reports, data size, users and sites, then tick the modules and integrations you use.
- 3
Read the path and the drivers
Review each upgrade step with its source, the changes in every release you cross, and the drivers behind the risk score and effort range.
- 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
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 SyteLine?
SyteLine 10. Infor moved SyteLine to a single version model with version 10: there are no new major versions, and changes ship as builds numbered 10.0.0.x, labelled by year and month (for example 2020.09 was build 10.0.0.487). Infor publishes the documentation per year, such as 2026.x. On-premises customers download and apply builds; multi-tenant cloud tenants receive them automatically.
Can I upgrade from SyteLine 8 or 9 directly to SyteLine 10?
Yes. Infor documents upgrade.exe as the tool that takes a previous SQL version of SyteLine to the version 10 base (Database Level 0), merging the Forms, Application, Objects and Templates databases into one. You then run the Database Validation and Prep Tool and an Uplift to the current build. No intermediate 9.01 hop is documented. From version 7 you first create the Objects and Templates databases in version 10 with InforDBCL.
How do I upgrade from SyteLine 6 or earlier?
SyteLine 5 and 6 run on Progress, so it is a migration rather than an upgrade. Infor's 8.03 installation guide covers Progress migration in its own chapters and states that the SQL database upgrade utility does not upgrade from version 6 or earlier. Confirm the current landing release with Infor, then follow the version 10 route from there.
What happens to our custom SSRS and Crystal reports in SyteLine 10?
Version 10 produces standard reports with Mongoose Reporting and does not need SSRS. If you have custom SSRS reports that still need to run, Infor's Guide to Technology says to install SSRS on the reporting server until they are converted. Count custom reports separately in the planner: each one needs a keep or rewrite decision.
Which customizations block the upgrade to SyteLine 10?
The Database Validation and Prep Tool checks that custom columns on SyteLine tables are nullable or have a default, that no extra constraints or unique indexes were added to SyteLine tables, that all SyteLine schema is present, and that the databases are consolidated. Version 10 also restricts next key generator formats, so NextKeyPreGenerate logic may need to be rebuilt. Moving to the multi-tenant cloud removes source code changes altogether.
How long does a SyteLine 10 upgrade take?
It depends mostly on customizations, integrations and reports. One Infor partner, Veits Group, puts it at about 4 months for a straightforward upgrade with few customizations to over a year when customizations are extensive. The planner shows a person-day range with the formula behind it so you can see which inputs move the number.
How should we test a SyteLine upgrade, and what should we automate?
Run a full regression on a copy of production: platform tests (sign-in, roles, background tasks, custom forms and IDO methods, reports), the business modules you use, and every integration with saved production files. Because version 10 changes arrive through repeated Uplifts, the tests marked for automation pay back on every build. The planner generates this list and flags tests as critical where your path changes that area.
Should we stay on-premises or move to CloudSuite Industrial?
On-premises or hosted SyteLine 10 keeps your database-level customizations, subject to the version 10 rules. Multi-tenant CloudSuite Industrial needs all sites in one database, no intranet licensing, and no source code changes, so heavily modified systems carry more rework. Run the planner with both targets and compare the risk drivers.
Sources
- Infor: CloudSuite Industrial (SyteLine) 9.01 now available
- CIMdata: next generation of Infor CloudSuite Industrial (SyteLine), January 2017
- Nucleus Research: Infor releases SyteLine 9 (November 2013)
- Computer Business Review: Infor launches ERP SyteLine 8.01 (May 2009)
- Infor10 ERP Business (SyteLine) 8.03 Installation Guide
- IndustryWeek: Frontstep to offer .NET edition of ERP package (SyteLine 7)
- Logistics IT: Infor SyteLine 7 gains momentum (2005)
- Infor CloudSuite Industrial 10 Guide to Technology, release 10.0.0.404+
- Infor CloudSuite Industrial (SyteLine) roadmap, February 2021
- Infor SyteLine Release Notes for 2021, release 10.00
- Infor docs: upgrading on-premises SyteLine to the version 10 base
- Infor docs: Database Validation and Prep Tool prerequisites
- Infor docs: validations for moving to Single Version
- Infor docs: SyteLine Database Validation and Prep Tool overview
- Infor docs: upgrading Document Management features
- Guide Technologies: CloudSuite Industrial October 2024 release
- Visual South: what is new in CloudSuite Industrial/SyteLine 10
- Quartess: Infor CloudSuite Industrial version 10 (September 2018)
- ERP Advisors Group: Infor SyteLine product support lifecycle
- Veits Group: upgrading SyteLine to version 10 (2023)
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.