CIO briefingSYSPROUpgrade / Platform

SYSPRO 7 to SYSPRO 8: What an IT Leader Should Plan Before Upgrading

Question

SYSPRO 7 to SYSPRO 8 upgrade what to plan

Also searched as

should we upgrade SYSPRO 7 to 8
SYSPRO 8 upgrade checklist
SYSPRO upgrade customisations integrations testing
SYSPRO upgrade project plan

Short answer

A SYSPRO 7 to 8 upgrade is mostly a customisation, integration and report inventory exercise rather than a data migration problem. List everything that touches SYSPRO, test each item in a copy of production, plan the user interface change for operators, and agree rollback. Check with your SYSPRO partner and current support terms for your version before deciding the timing.

Applies to: Sites on SYSPRO 7 planning a move to a SYSPRO 8 release, on-premise or hosted; confirm supported upgrade paths and platform requirements with SYSPRO or your reseller

Upgrade planning sequence

1Confirm the supported upgrade path, SQL Server and Windows Server requirements and your licence terms with your SYSPRO partner, in writing.
2Build an inventory of everything custom: custom forms, VBScript or macros, user-defined fields, customised reports, and any third-party add-ons.
3Build an inventory of integrations: e.net business object callers, EDI, web shops, CRM, scanners, Power BI or SSRS reports, and scheduled jobs.
4Restore a recent production backup to a test environment and run the upgrade there first, recording time taken and issues.
5Have each department test its real processes with its own data: order to cash, procure to pay, MRP, job costing, month-end close.
6Run MRP, costing and the month-end reports in test and compare results with production for the same period.
7Plan user training for the interface changes and the support load in the first weeks.
8Agree the cutover window, the freeze period and a rollback criterion, and rehearse the cutover once.

Where upgrades actually hurt

The data conversion itself is rarely the problem, since the vendor tooling is built for it. The pain is in the edges: a custom screen that depended on the old client, an integration that logs on in a particular way, a report built on a table that changed, or an add-on whose vendor has not certified the new release.

That is why the inventory comes before the date. A project that discovers its fifteenth undocumented integration in week eight is a project that slips.

Testing that finds real problems

Use real transactions, not the demo script. Replay a month of orders, receipts and job postings if possible, then compare costing, inventory valuation, WIP and ledger balances with production. A tolerance of zero on quantities and a clear explanation for any cost difference is the right bar.

Performance matters too. Test MRP and the heaviest reports at production volumes, because a restored copy on undersized test hardware can mislead in either direction.

Should we wait

Waiting is a legitimate choice if the current version is supported, stable, and not blocking anything you need. The costs of waiting are real, though: older platform dependencies such as the operating system and SQL Server version, reduced availability of partner skills, and compatibility with newer integrations or analytics tools.

Weigh the upgrade against other projects competing for the same people. An upgrade done during a year-end audit or an ERP-adjacent initiative such as a new MES is a risk multiplier. Put it in a quiet quarter and protect the test time.

People and cutover

Budget for the human side. Operators who know the old client by muscle memory will need training and floor support, and the first month-end on the new release deserves finance and IT in the same room. Keep the old environment available read-only for a defined period for comparison.

Common pitfalls

!Scheduling the upgrade without a customisation and integration inventory.
!Testing with demo data and discovering costing differences only in production.
!Underestimating training and floor support for operators and warehouse staff.
!Running the cutover across a month-end or audit period.
!Assuming third-party add-ons are certified for the target release without asking in writing.
!No rollback criterion agreed before the cutover starts.

How an ERP-grounded AI assistant handles this

An AI assistant grounded in your SYSPRO environment can help with the inventory step: reading customised reports, scripts and integration call logs to build the list of what touches SYSPRO, and summarising differences between test and production results for a given period. It does not replace a partner-led upgrade or user testing. For on-prem sites the work can run on local models so schema and transaction data stay inside your network.

See ERPray

Frequently asked questions

How long does a SYSPRO 7 to 8 upgrade take?

It varies mainly with customisations, integrations and testing depth rather than database size. Simple sites can finish in weeks; sites with many integrations and reports take longer. Ask your partner for an estimate based on your inventory, not a generic number.

Will our customised reports and forms still work?

Some will, some need rework, and you will not know without testing. Standard reports usually carry over. Custom forms, scripts and reports that depend on specific tables or the old client are the highest-risk items and should be tested first.

Do our e.net integrations need changes?

Often not many, but test each one. The business objects remain the supported integration path, yet XML structures and licensing behaviour can change between releases. Run each integration against the test environment with real payloads and compare results.

Is a staged upgrade by company possible?

That depends on your setup and licensing, and multi-company sites sometimes plan it. Companies often share administration data, so confirm with your partner whether a mixed-version estate is supported before you design the plan around it.

How-to

How to Create a SYSPRO Sales Order with the SORTOI Business Object

SORTOI is the SYSPRO e.net business object that enters sales orders from outside the SYSPRO client. You log on to get a session id, call the business object with a Parameter XML and a Document XML describing the order header and lines, then read the XML that comes back for warnings and the new sales order number. Always test in a non-production company first.

Advanced

SYSPRO SQL Query for Inventory On Hand by Warehouse

SYSPRO runs on SQL Server with one database per company, typically named like SysproCompanyA, and inventory is split between InvMaster for part-level data and InvWarehouse for quantities per warehouse. Join them on StockCode, filter, and read the quantity columns. Use a read-only login, never write to SYSPRO tables directly, and prefer e.net business objects for any change.

How-to

How to Run Requirements Planning (MRP) in SYSPRO

SYSPRO's MRP engine lives under Planning and Scheduling > Requirements Planning. Set planning parameters per warehouse, run the Requirements Calculation to net demand against supply, then review and release the resulting suggestions as purchase requisitions or work orders. A full regenerative run typically runs on a schedule, with net change runs in between to pick up new activity.

How-to

How to Create a Generic Inquiry in Acumatica

Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.

Error fix

Fix Odoo AccessError: You Are Not Allowed to Access Records

Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.

How-to

How to Void a Check in Sage 100

Sage 100 voids checks through Accounts Payable > Main > Check and Payment Voiding. Select the bank code, choose the check number, and Sage reverses the Cash Disbursements Journal entry and reopens the invoice it paid. A check that already cleared in Bank Reconciliation or falls in a closed period needs an extra step before it can be voided cleanly.

AI for ERP