# SYSPRO Upgrade Checklist: Plan, Test and Go Live

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

## Short answer

A phased checklist for upgrading SYSPRO: scoping, backup, customisations, test cycles and cut-over.

## Category

erp-operations

## Erp

SYSPRO

## Region

South Africa

## Audience

- SYSPRO administrator
- IT manager
- Project manager

## Tool

**Kind:** checklist

**Scoring Note:** Critical items are the ones where a miss can stop go-live or cause data loss. Close them first and keep evidence of each.

**Groups:**

#### Planning and scope

**Items:**

**Text:** Target version and release notes read by the project team

**Critical:** true

Business sponsor and project lead named

Inventory of installed modules, add-ons and bespoke programs

**Text:** Licence and support status confirmed with your supplier

**Critical:** true

Upgrade window agreed outside month end and stock take

Business reasons for the upgrade written down

#### Environment and backups

**Items:**

**Text:** Full backups of every company database and system database taken and restore tested

**Critical:** true

**Text:** Test environment built from a recent copy of live data

**Critical:** true

SQL Server version and operating system supported by the target release

Client machines meet the minimum requirements

Disk space and server capacity checked for the upgrade

**Text:** Rollback plan written with a decision point and owner

**Critical:** true

#### Customisations and integrations

**Items:**

Custom forms, reports and Crystal or SSRS layouts listed and retested

**Text:** Third party add-ons confirmed compatible by their vendors

**Critical:** true

e.net and API integrations retested with sample transactions

Scheduled imports, exports and EDI jobs listed with owners

Operators, roles and security settings reviewed

#### Testing

**Items:**

**Text:** Test scripts cover order to cash, procure to pay, MRP, jobs and period end

**Critical:** true

Key users from each department sign off their own scripts

Printing, label and document layouts verified on real printers

Performance checked with realistic users and data volumes

Defects logged, prioritised and retested

**Text:** A full dress rehearsal of the live upgrade completed with timings

**Critical:** true

#### Go live and after

**Items:**

Users warned of downtime and the cut-over timeline

**Text:** Final backup taken immediately before the upgrade

**Critical:** true

Post upgrade smoke tests run before users are let in

Extra support cover arranged for the first week

Lessons learned captured and documentation updated

## Content

**Intro:** SYSPRO upgrades go smoothly when custom items, add-ons and backups are handled before the window opens, and badly when they are discovered during it. This checklist breaks the work into planning, environment, customisations, testing and go live.

**Sections:**

#### How to use the checklist

**Body:** Assign each group to an owner and tick items as evidence is collected, such as a restore log, a signed test script or a vendor email. Treat the critical items as gates: do not move to the next phase until they are done. Use the printed version in project meetings so open items are visible. Reuse the same list for each future upgrade and improve it each time.

#### Where upgrades usually fail

**Body:** The common failure points are untested restores, add-ons that are not yet compatible, custom forms or reports that break after the update, and integrations that depend on behaviour that changed. A full dress rehearsal on a copy of live data exposes most of these and gives you a realistic downtime estimate, which users appreciate. Without it, the go-live window is a guess.

#### Testing that counts

**Body:** Test the processes the business cannot live without: take a sales order through to invoice, receive a purchase order, run MRP, issue material to a job and close a period. Use real users and real data volumes. A tester who is not the daily user will miss the awkward cases. Record the outcome of each script so the sign-off is auditable.

#### Common mistakes

**Body:** Teams skip the test restore, plan the upgrade for the week of a stock take, forget to retest scheduled jobs, or leave users out of testing. Another mistake is upgrading and changing processes at the same time, which makes problems hard to trace. Upgrade first, improve later.

**Cta:** If you want help analysing custom forms and integrations before an upgrade, Netray can review the code and data flows and flag what is likely to need rework.

**Faq:**

#### How long does a SYSPRO upgrade take?

**Answer:** The live cut-over often takes hours to a weekend, but the preparation takes weeks. Time depends on database size, number of companies, customisations and testing depth. A dress rehearsal gives the most reliable estimate for your environment.

#### Do I need a test environment?

**Answer:** Yes. Upgrading live without a rehearsal on a copy of production data exposes you to avoidable risk. A test copy lets you verify custom items, integrations and timings before the real window.

#### What happens to custom forms and reports?

**Answer:** Some survive unchanged and others need adjustment. List them all, retest each in the test environment, and ask your SYSPRO partner or the form author to confirm which need rework before the live upgrade.

#### Can I roll back after upgrading?

**Answer:** Only if you have a verified backup taken immediately before and a documented rollback decision point. After users have posted new transactions, a rollback means losing them, so decide early and set a time limit.

## Search terms

syspro upgrade, syspro upgrade checklist, syspro 8 upgrade, syspro version upgrade plan, syspro custom forms upgrade, syspro add-on compatibility, erp upgrade test plan

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