# SyteLine 8 and 9 to SyteLine 10 Technical Upgrade Checklist

> Source: https://netray.co/tools/syteline-10-technical-upgrade-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

The technical steps for moving an on-prem SyteLine 8.x or 9.x system to SyteLine / CSI 10, from customisation inventory to rehearsal and rollback.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- ERP administrator
- SyteLine developer
- DBA

## Tool

**Kind:** checklist

**Groups:**

#### Inventory before the upgrade

**Items:**

**Text:** List customised forms with FormSync and record which are site, group or user level

**Critical:** true

**Text:** List IDO Custom Assemblies and locate the source code for every extension class assembly

**Critical:** true

**Text:** List EXTGEN_ procedures: SELECT name FROM sys.procedures WHERE name LIKE 'EXTGEN[_]%'

**Critical:** true

List custom triggers on application tables and their purpose

List Uf_ user fields and user extended tables in use

List custom event handlers and event actions

List custom Background Task Definitions and scheduled tasks

List custom reports (Crystal and SSRS) and their data sources

List replication rules and multi-site intranets

List BOD integrations and the ION flows that consume them

#### Databases

**Items:**

**Text:** Confirm the target SQL Server version and compatibility level are on the SyteLine 10 release's supported list

**Critical:** true

**Text:** Plan for the all-in-one database: if the source still has separate forms, objects and templates databases, the upgrade merges them into the application database

**Critical:** true

**Text:** Keep the database collation unchanged from the source system

**Critical:** true

Restore a current production copy for the rehearsal, not an old test database

Record database sizes and plan disk for the merged database and log growth during the upgrade

#### Customisations

**Items:**

**Text:** Use FormSync to carry WinStudio form changes forward (it covers form definitions only, not IDO or SQL objects)

**Critical:** true

Export and import IDO metadata changes with App Metadata Transport

**Text:** Recompile extension class assemblies against the new Mongoose DLLs and re-import them in IDO Custom Assemblies

**Critical:** true

**Text:** Compare each EXTGEN_ procedure with the new base stored procedure and re-apply the change

**Critical:** true

Revalidate custom triggers against changed table definitions

Revalidate event handlers and event actions

Check user extended tables and Uf_ fields survived and still appear on forms

#### Services and configuration

**Items:**

Recreate configurations in Configuration Manager pointing at the upgraded database

**Text:** Set up TaskMan, replication and event services in Service Configuration Manager

**Critical:** true

Confirm which database ION retrieves outbound BODs from in a multi-site setup

Check LogMonitor for errors while starting services and opening forms

#### Reporting and integrations

**Items:**

Decide which Crystal reports move to SSRS where the target uses SSRS

Check Report Options and the report server configuration

**Text:** Reconnect ION and verify the Replication Document Outbox is being read

**Critical:** true

Retest IDO REST clients and update any that call older REST endpoints

#### Rehearsal and cutover

**Items:**

**Text:** Run a timed rehearsal of the full upgrade on a production copy

**Critical:** true

**Text:** Take and verify a full backup of every source database before cutover

**Critical:** true

**Text:** Write rollback criteria and the time at which rollback is decided

**Critical:** true

Freeze customisation changes after the final rehearsal

Plan post-upgrade checks: login, key forms, a background report, a posting transaction

**Scoring Note:** Count the critical items still open. Any open critical item means the cutover date is at risk; non-critical items can be closed during the rehearsal cycle.

## Content

**Intro:** This checklist covers the technical path from SyteLine 8.x or 9.x to SyteLine / CloudSuite Industrial 10 on premises: inventory, databases, customisations, services, integrations and cutover. It is for the admins and developers doing the work, not the functional test plan.

**Sections:**

#### Start with the customisation inventory

**Body:** Every upgrade problem traces back to a customisation nobody listed. Use FormSync to list customised forms, IDO Custom Assemblies to list extension class assemblies, and sys.procedures to list EXTGEN_ procedures, which SyteLine uses to extend base stored procedures. Add custom triggers, Uf_ user fields and user extended tables, event handlers, Background Task Definitions, custom reports, replication rules and BOD integrations. For every item, record owner, purpose and whether it is still used. Retiring a dead customisation is the cheapest upgrade work you will do. If you cannot find the source code for an extension class assembly, flag it now: you will need to recompile it.

**Bullets:**

- FormSync: customised forms
- IDO Custom Assemblies: extension class DLLs
- EXTGEN_ procedures: extended base logic
- Uf_ fields and user extended tables

#### Database changes in SyteLine 10

**Body:** Older SyteLine releases kept forms, objects and templates in separate databases from the application data. SyteLine 10 uses the all-in-one (AIO) model, so if your source system still has separate databases the upgrade merges them into the application database. Plan disk and log space for that merge. Keep the collation identical to the source system: collation mismatches surface later as errors in temp tables and joins. Check the SQL Server versions and compatibility levels supported by your exact CSI 10 release in Infor's system requirements before you build servers, and do not assume the newest SQL Server is supported.

#### Carrying customisations forward

**Body:** FormSync merges WinStudio form customisations into the new form versions; it handles form definitions, not IDO metadata or SQL code. IDO metadata changes move with App Metadata Transport. Extension class assemblies must be recompiled against the Mongoose DLLs of the new release and re-imported, because they reference framework classes that change between versions. Each EXTGEN_ procedure was a copy of a base procedure with your change applied; the base procedure has changed, so diff the old base, your EXTGEN and the new base, then re-apply the change to a fresh copy. After services are configured in Configuration Manager and Service Configuration Manager, use LogMonitor while opening forms to catch broken references fast.

#### What this checklist does not cover

**Body:** This is the technical path only. Functional regression testing, test cases by process, belongs in the separate upgrade regression test checklist, and the question of whether your current version is near end of support belongs in the EOL risk assessment. Use all three together: the inventory here feeds the regression scope, and the rehearsal timings feed the cutover plan. Run at least two rehearsals: the first finds problems, the second proves the timings.

**Cta:** If you want an AI agent to inventory your SyteLine customisations and diff EXTGEN procedures against the new base on your own servers, we can set that up with SyteRay.

**Faq:**

#### Can I upgrade directly from SyteLine 8 to SyteLine 10?

**Answer:** Infor documents the supported upgrade paths per release, including which source versions can go directly to your target. Check the upgrade guide for your exact CSI 10 release before planning. The technical work is similar either way: inventory, database merge, form and IDO metadata carry-forward, assembly recompilation and EXTGEN review.

#### What does FormSync do in a SyteLine upgrade?

**Answer:** FormSync synchronises WinStudio form customisations from your old form definitions into the new release's forms, so site and group form changes are kept. It does not move IDO metadata, extension class assemblies, stored procedures or triggers; those need App Metadata Transport, recompilation and manual review.

#### What are EXTGEN procedures in SyteLine?

**Answer:** EXTGEN_ procedures are customer versions of base SyteLine stored procedures. When an EXTGEN_ procedure exists, SyteLine calls it in place of the base logic. After an upgrade the base procedure may have changed, so each EXTGEN must be compared with the new base and rebuilt, or the old logic silently overrides new fixes.

#### Is SyteLine 9 still supported?

**Answer:** Support status depends on Infor's lifecycle policy for each release and changes over time, so check Infor's support portal or ask your account team for the current dates for your exact version. Use the EOL risk assessment tool to weigh the risk of staying on 8 or 9 against the upgrade effort.

## Search terms

syteline upgrades, syteline 9, syteline 8, syteline version 10, syteline 9.00, syteline 10 upgrade, csi 10 upgrade checklist, syteline formsync

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json