SYSPRO Upgrade Checklist: Plan, Test and Go Live
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.
0 of 28 items complete
9 critical items still open - these are the highest-risk gaps.
Planning and scope
Environment and backups
Customisations and integrations
Testing
Go live and after
Critical items are the ones where a miss can stop go-live or cause data loss. Close them first and keep evidence of each.
Upgrade risk review
Optional: we can review your custom items and integrations and list the likely rework.
Optional. The tool and every export work without this. No spam.
How to use the checklist
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
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
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
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.
Frequently Asked Questions
How long does a SYSPRO upgrade take?
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?
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?
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?
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.
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.
Related Tools
SYSPRO MRP Checklist
A checklist of the master data, parameters and review steps that decide whether SYSPRO MRP output can be trusted.
Developer ToolsSYSPRO SQL Query Generator
Generate read-only SQL Server queries against common SYSPRO tables. Fill in database and filters, then copy the code.
ERP Migration & SelectionSage Pastel to Cloud ERP Migration Assessment
Ten questions that score your readiness to move from Sage Pastel to a cloud ERP and point to the gaps to close first.
ERP Migration & SelectionSouth Africa Manufacturer ERP Selection Scorecard
Weight your criteria, score up to three ERP candidates from 1 to 5, and see weighted totals out of 100. Exports to Excel.