Retired SYSPRO versions: upgrade to the current SYSPRO or move to ERPNext?
Short answer
SYSPRO’s own Release Lifecycle page (checked Nov 18, 2026) shows SYSPRO 7 and SYSPRO 7 Update 1 retired in July 2023, and the SYSPRO 8 2018 and 2019 releases (R1 and R2) retired in July 2024. The SYSPRO 8 2020, 2021, 2022, 2023 and 2024 releases are in the Legacy phase, 2025 is in Extended, and only SYSPRO 8 2026 R1 and R2 are Mainstream. In SYSPRO’s words, Legacy and Retired releases get no development work, no corrections and limited or very limited support. Your licence to use the software is not affected. If you run SYSPRO 7 or an early SYSPRO 8 release at a mid-size manufacturer or distributor, the default answer is to upgrade to the current SYSPRO 8 release: same vendor, same data model, same partner. ERPNext (open source, GPL-3.0, no licence fee) is worth pricing when the upgrade is effectively a reimplementation anyway, when you are leaving your SYSPRO partner, or when you want to own and host the system yourself. SYSPRO does not publish prices, so we give no SYSPRO estimate.
Contents
- Who this guide is for
- SYSPRO’s lifecycle, version by version
- What Mainstream, Extended, Legacy and Retired mean
- Check your add-ons too
- Your options
- When upgrading SYSPRO is the better call
- When ERPNext is worth pricing
- How SYSPRO concepts map to ERPNext
- Fit tests to run before you decide
- Getting data out of SYSPRO 7 or early SYSPRO 8
- Costs: what is published
- A 90-day decision plan
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, operations managers and IT leads at mid-size manufacturers and distributors that still run SYSPRO 7, SYSPRO 7 Update 1, or a SYSPRO 8 release from 2018 to 2022, on their own servers or with a hosting partner. We wrote it with sites in the UK, the US, South Africa and India in mind: companies that make or distribute physical products and have grown well beyond entry-level accounting software. A typical site runs inventory, sales orders, purchasing, bills of materials, jobs (work in progress), requirements planning, lot or serial traceability and the core ledgers, with a reseller that has looked after it for years.
We implement ERPNext, so read our view with that in mind. For most SYSPRO sites, the right next step is an upgrade to the current SYSPRO 8 release, and this guide says so plainly. It is written for the minority where that is not obvious: sites where the upgrade has been postponed for years, the customisations are heavy, the reseller relationship has ended, or the business has changed enough that a fresh implementation is on the table anyway.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. If you are comparing other mid-market manufacturing systems, our Epicor 10 and 9 guide and Infor VISUAL guide cover similar ground.
Sources, checked on Nov 18, 2026: the SYSPRO Release Lifecycle page (SYSPRO 8 2026 R2 help), the SYSPRO Product Lifecycle PDF (September 2025 edition) (which the series plan cited), the SYSPRO Product Portfolio Lifecycle page, the SYSPRO product page, the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.
SYSPRO’s lifecycle, version by version
SYSPRO publishes its release lifecycle in its own online help, and it is unusually clear. The table below is copied from the SYSPRO Release Lifecycle page (SYSPRO 8 2026 R2 help) as it stood on Nov 18, 2026. “Planned change” is SYSPRO’s own column: the date on which SYSPRO expects the status to change.
| Release | Original version | Status on Nov 18, 2026 | Planned change |
|---|---|---|---|
| SYSPRO 8 2026 R2 | November 2026 | Mainstream | September 2027 |
| SYSPRO 8 2026 R1 | June 2026 | Mainstream | March 2027 |
| SYSPRO 8 2025 | September 2025 | Extended | November 2026 |
| SYSPRO 8 2024 | August 2024 | Legacy | November 2026 |
| SYSPRO 8 2023 | September 2023 | Legacy | November 2026 |
| SYSPRO 8 2022 | February 2023 | Legacy | September 2025 |
| SYSPRO 8 2021 R2 | November 2021 | Legacy | September 2025 |
| SYSPRO 8 2021 R1 | April 2021 | Legacy | September 2025 |
| SYSPRO 8 2020 R2 | September 2020 | Legacy | September 2025 |
| SYSPRO 8 2020 R1 | March 2020 | Legacy | September 2025 |
| SYSPRO 8 2019 R2 | September 2019 | Retired July 2024 | None |
| SYSPRO 8 2019 R1 | March 2019 | Retired July 2024 | None |
| SYSPRO 8 2018 R2 | September 2018 | Retired July 2024 | None |
| SYSPRO 8 2018 R1 | July 2018 | Retired July 2024 | None |
| SYSPRO 7 Update 1 | April 2015 | Retired July 2023 | None |
| SYSPRO 7 | May 2014 | Retired July 2023 | None |
| SYSPRO 6.1 SP1 | June 2012 | Retired December 2015 | None |
| SYSPRO 6.1 | August 2010 | Retired December 2014 | None |
Two things to note. First, several Legacy releases show a planned change of September 2025, a date that has passed while the page still shows them as Legacy. We do not read that as “support ended in September 2025”, because SYSPRO has not said so; we read it as a status change that is due or overdue, and the next step after Legacy is Retired. Second, the September 2025 PDF edition that is still online listed SYSPRO 8 2024 as Mainstream and 2023 as Extended. The November 2026 page has moved both to Legacy. Lifecycle status moves on a regular rhythm, so always check the live page rather than a saved copy.
SYSPRO also says it intends to give “a minimum of 6 months notice of change in product lifecycle status”, and that changes will appear on that help page. If you are on 2023 or 2024, the planned change of November 2026 is now.
What Mainstream, Extended, Legacy and Retired mean
SYSPRO’s lifecycle page sets out what you get in each phase. This is the substance behind the labels:
| Support level | Mainstream | Extended | Legacy | Retired |
|---|---|---|---|---|
| Enhancements made to this version | Yes | Rarely | No | No |
| Corrections to reported problems | Yes | Discretionary | No | No |
| Product support (help with using the product) | Yes | Yes | Limited | Very limited |
| Technical support (help with technical issues) | Yes | Yes | Limited | No |
| Development support (for third-party developers) | Yes | Limited | Very limited | No |
| Annual licences issued | Yes | Yes | Yes | Yes |
| Can upgrade to the Mainstream product | Not applicable | Yes | Yes | Yes |
Source: SYSPRO Release Lifecycle page (SYSPRO 8 2026 R2 help). SYSPRO describes Legacy releases as having “no development work” and carrying “a risk that the latest technologies may cause this software not to run appropriately”. For Retired releases it says the risk is “fairly high”.
Equally important is what SYSPRO says does not change. Its FAQ says the lifecycle guidelines “only impact on new license availability and certain product support policies” and “in no way” affect your licence to use the product. It also says that if you run a Legacy or Retired release, “you do not have to do anything”. So SYSPRO 7 will not stop working on a date. What stops is the safety net: no fixes, no help with technical problems, and no changes when Microsoft ships a new Windows or SQL Server version. SYSPRO’s own example is exactly that: a new operating system or database may need SYSPRO changes that will only be made in the Mainstream release.
Check your add-ons too
A separate SYSPRO page, the SYSPRO Product Portfolio Lifecycle page, lists add-on products that SYSPRO is retiring and their recommended replacements. If your old SYSPRO site uses any of them, your upgrade plan has to cover them as well. Dates below are SYSPRO’s, checked Nov 18, 2026:
| Product | Recommended alternative (SYSPRO’s) | End of support | End of life |
|---|---|---|---|
| APS (Nexsys) advanced planning and scheduling | SYSPRO Manufacturing Operations Management (MOM) | 31 December 2026 | 31 December 2026 |
| AQM (UK) advanced quality management | SYSPRO Quality Management | 31 December 2026 | 31 December 2026 |
| SYSPRO Embedded Analytics | ZAP, Power BI or SYSPRO Torque | 31 December 2026 | 31 December 2026 |
| WebReports | SYSPRO Reporting Services | 31 December 2026 | 31 December 2029 |
| SYSPRO Harmony | SYSPRO Torque | 30 June 2026 | 31 December 2026 |
| Equator payroll (UK) | Industry payroll providers | 1 July 2028 | 1 July 2028 |
| Orchard WMS | SYSPRO WMS (Datascope WMS) | 31 December 2029 | 31 December 2029 |
| SYSPRO Espresso mobile platform | SYSPRO Mobile Warehouse (RiteScan) | 31 December 2029 | 31 December 2029 |
| ShopClock shop-floor time tracking | SYSPRO TimeTrack (RiteTime) | 31 December 2029 | 31 December 2029 |
The page also lists a UK Company Copy utility, a US credit card interface and a US customer portal. The practical point: if you planned to upgrade SYSPRO and keep Nexsys scheduling or Equator payroll as they are, that plan needs revisiting. It also means some sites face two changes at once, and that is often the moment the “upgrade or replace” question gets asked properly.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Upgrade to the current SYSPRO 8 release (2026 R1 or R2) | Same vendor and data model; your reseller runs the upgrade, retests customisations and reports | You are broadly happy with SYSPRO, customisations are modest and your reseller relationship is good |
| Stay on a Legacy or Retired release | Keep running, with limited or very limited support and no corrections | Short term only, while you plan; watch Windows and SQL Server changes |
| Reimplement SYSPRO from scratch on the current release | A new SYSPRO company, cleaned masters, redesigned processes | Your old setup no longer matches the business but SYSPRO still fits |
| Move to ERPNext | Open-source ERP with inventory, manufacturing, buying, selling and accounting; self-host or Frappe Cloud | You want to own the system and its code, avoid per-user licence growth, or you are reimplementing anyway |
SYSPRO does not publish licence, maintenance or upgrade prices on its SYSPRO product page or anywhere else we checked, so we give no SYSPRO estimate. Ask your reseller for a written quote that separates licence and maintenance, upgrade services, customisation rework, report rework and training. Then price ERPNext over the same five years with the same categories.
An honest default
If you are on SYSPRO 8 2020 to 2024 with light customisations, an in-family upgrade is almost always cheaper and less risky than changing ERP. This guide is not trying to talk you out of that. The case for ERPNext gets stronger the older and more customised your SYSPRO is.
When upgrading SYSPRO is the better call
- Your processes still fit. If inventory, jobs and requirements planning work the way your business works, a version upgrade preserves that.
- You rely on SYSPRO-specific functions. Sites that rely on SYSPRO-specific modules, such as its product configurator, or on local tax and payroll features, should check carefully whether anything else matches them.
- Your reseller is strong. A good SYSPRO partner who knows your data is a real asset. Starting again with someone new has a cost that does not show up in a licence quote.
- You are on a recent release. Moving from 2022, 2023 or 2024 to 2026 is a smaller step than moving from SYSPRO 7.
- You want the vendor accountable. SYSPRO provides product support on the Mainstream release; ERPNext support comes from Frappe’s paid plans or a partner, or your own team.
When ERPNext is worth pricing
- You are on SYSPRO 7 with heavy customisation. Every custom screen, report and integration has to be rebuilt or retested on SYSPRO 8. If that list is long, you are already paying for most of a reimplementation.
- You want to own and host the system. ERPNext is GPL-3.0. You can run it on your own servers or on Frappe Cloud, and change the code.
- User counts are growing. ERPNext has no per-user licence fee. Your costs are hosting, implementation and support.
- Your SYSPRO partner has gone. Picking a new partner is a reset either way; that is a fair moment to compare platforms.
- Retiring add-ons force change anyway. If Nexsys APS, AQM or Equator are being retired at your site, part of the business is changing systems regardless.
How SYSPRO concepts map to ERPNext
SYSPRO and ERPNext describe a manufacturer or distributor in similar terms. This is the starting map we use when scoping a SYSPRO move:
| In SYSPRO | In ERPNext | Notes |
|---|---|---|
| Stock codes and warehouses | Item (ERPNext Item documentation) and Warehouse (ERPNext Warehouse documentation) | Clean obsolete stock codes first; decide warehouse structure before loading |
| Bills of materials (structures and routings) | Bill of Materials (ERPNext Bill of Materials documentation) with Routing (ERPNext Routing documentation) and Operations (ERPNext Operation documentation) | Rebuild active BOMs only; scrap and process loss sit on the BOM |
| Work centres | Workstations (ERPNext Workstation documentation) | Working hours, hourly costs and production capacity |
| Jobs (work in progress) | Work Order (ERPNext Work Order documentation) and Job Card (ERPNext Job Card documentation) | Finish open jobs in SYSPRO where possible; start new ones in ERPNext |
| Requirements planning | Production Plan (ERPNext Production Plan documentation) and Material Request (ERPNext Material Request documentation) | Test with real demand before go-live |
| Sales orders, quotations | Sales Order (ERPNext Sales Order documentation), Quotation (ERPNext Quotation documentation) | Map order types and price lists |
| Purchase orders, requisitions | Purchase Order (ERPNext Purchase Order documentation) and Material Request | Map approval steps to Workflows (ERPNext Workflows documentation) |
| Customer and contract pricing | Price Lists and Pricing Rules (ERPNext Pricing Rule documentation) | The most common fit gap for distributors; test your real price structures |
| Lot traceability, serial tracking | Batch (ERPNext Batch documentation) and Serial No (ERPNext Serial No documentation) | Batches can carry expiry dates |
| Inspection | Quality Inspection (ERPNext Quality Inspection documentation) | Templates on the Item or Operation |
| General ledger, AR, AP, cash book | Chart of Accounts (ERPNext Chart of Accounts documentation), invoices, Payment Entry (ERPNext Payment Entry documentation) | Use accounting dimensions for branches or cost centres |
| Multiple companies | Multi-company with inter-company invoices (ERPNext inter-company invoices documentation) | Common for UK and South African groups |
| Foreign currency | Multi-currency accounting (ERPNext multi-currency accounting documentation) | Check revaluation and bank import formats |
The map is short because SYSPRO and ERPNext cover the same core. The work is in the detail: pricing structures, how jobs are costed, and which reports the business actually reads every week.
Fit tests to run before you decide
Do not decide from a demo. Run these five tests in an ERPNext trial with your own data:
Five fit tests for SYSPRO sites
- Pricing. Load your ten most complex customer price arrangements (contract prices, quantity breaks, promotions) as Price Lists and Pricing Rules. If a sales clerk can raise a correct order without overrides, pass.
- Jobs and costing. Rebuild three closed SYSPRO jobs as Work Orders with Job Cards. Compare the cost picture with the SYSPRO job valuation.
- Requirements planning. Run a Production Plan against a month of real sales orders and compare the suggested purchases and work orders with what SYSPRO suggested.
- Traceability. Trace one lot forwards to customers and backwards to suppliers. This must work on day one for regulated or food-grade sites.
- Month end. Close a trial month: stock valuation, GL reconciliation, aged debtors and creditors. Your finance team signs this off, not the project team.
If all five pass with configuration rather than code, ERPNext is a real candidate. If two or more need custom development, compare that effort honestly with a SYSPRO upgrade quote.
Getting data out of SYSPRO 7 or early SYSPRO 8
SYSPRO 8 runs on Microsoft SQL Server (SYSPRO’s lifecycle page ties each release to supported Windows and SQL Server versions), so the data is reachable with standard tools: your reseller or DBA can extract masters and open transactions to spreadsheets or CSV. If an older SYSPRO 7 site is not on SQL Server, ask your reseller for the extraction route before you plan anything else. Plan the move like this:
| SYSPRO data | ERPNext target | How |
|---|---|---|
| Stock codes, units of measure, customers, suppliers | Items, UOM conversions, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation) | Extract, clean, load with Data Import (ERPNext Data Import documentation) |
| Active bills of materials and routings | BOMs, Routings, Workstations | Only items you will make again |
| Open sales and purchase orders | Sales Orders, Purchase Orders | Freeze changes during cut-over week |
| Stock on hand by warehouse, lot and serial | Opening Stock Reconciliation (ERPNext Stock Reconciliation documentation) with batch and serial data | Count high-value and lot-controlled stock |
| Open receivables and payables | Opening invoices (ERPNext opening balance documentation) | Reconcile to aged reports |
| General ledger balances | Opening trial balance on the new chart of accounts | Keep SYSPRO read-only for history |
Do not plan to migrate years of closed jobs and invoices. Keep the old SYSPRO database available read-only, or export history to a reporting database, for audits, warranty questions and repeat orders. Agree the history cut-off with your auditor before the project starts.
If your SYSPRO has custom reports, triggers or a third-party add-on, list every one early and sort them into needed on day one, needed within a month, and probably unused. On old installations the third list is usually longer than people expect.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| SYSPRO licence, maintenance, upgrade services | Quote only; no estimate given | Quote only | SYSPRO product page |
| ERPNext software | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud, site plans | From $5 per month | About £3.79 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.33 (indicative) | Frappe Cloud server plans page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.79) and servers from $40 a month (about £30.33), checked on Nov 18, 2026. The GBP figures are indicative conversions, not Frappe prices.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3187 per £1 for 16 Nov 2026, the latest published figure when we checked on Nov 18, 2026. They are not official UK prices: Frappe does not publish a GBP list price for these plans, and your invoice currency, rate and VAT treatment may differ.
Hosting is rarely the deciding cost for either option. Implementation, data work, report rebuilding, training and the internal time of your finance and operations people dominate. Compare like for like over five years, and include the cost of standing still on a Retired release.
A 90-day decision plan
| Weeks | What to do | Output |
|---|---|---|
| 1 to 2 | Confirm your exact release on the live lifecycle page; list customisations, reports, integrations and add-ons | Inventory of what you run and its status |
| 3 to 4 | Ask your SYSPRO reseller for a written upgrade quote and plan to the current release | Upgrade quote with scope |
| 5 to 8 | Run the five ERPNext fit tests with your data | Pass, configure or develop, per test |
| 9 to 10 | Get an ERPNext implementation proposal with the same scope | Second quote |
| 11 to 12 | Compare five-year costs, risks and internal effort; decide | A board-level recommendation |
If you are on SYSPRO 7 and your servers or SQL Server version are also due for replacement, compress this plan. Infrastructure changes are where Retired releases tend to fail first, and SYSPRO says plainly that it will not change a Retired release to fix that.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| SYSPRO 8 2020 to 2024, light customisations | Upgrade SYSPRO | Smallest change; same data model and partner |
| SYSPRO 7, many custom screens and reports | Price both seriously | The upgrade is close to a reimplementation |
| Must self-host, own the code or avoid per-user fees | ERPNext | Open source, no licence fee |
| Retiring add-ons (Nexsys APS, AQM, Equator) in use | Plan the replacement either way | SYSPRO lists end-of-support dates for them |
| Complex configurator or local payroll inside SYSPRO | Upgrade SYSPRO, or ERPNext plus specialist tools | Check fit before you commit |
Best for, and wrong choice when
ERPNext is best for
Mid-size manufacturers and distributors on SYSPRO 7 or early SYSPRO 8 who are effectively reimplementing anyway, want to own and host their ERP, and have someone internal who will own the system after go-live.
Upgrading SYSPRO is best for
Sites on SYSPRO 8 2020 or later with modest customisations, a capable reseller, and processes that still fit how the business runs.
ERPNext is the wrong choice when
You need a go-live within a few months with no time for fit testing, you depend on SYSPRO-specific functions you have not tested elsewhere, or nobody in the business can own the system after the project ends.
Frequently asked questions
When did SYSPRO 7 support end?
SYSPRO’s Release Lifecycle page shows SYSPRO 7 (May 2014) and SYSPRO 7 Update 1 (April 2015) as Retired in July 2023 (checked Nov 18, 2026). Retired releases get no corrections and no technical support.
Which SYSPRO 8 releases are retired?
The SYSPRO 8 2018 R1, 2018 R2, 2019 R1 and 2019 R2 releases were retired in July 2024. The 2020 to 2024 releases are in the Legacy phase, 2025 is Extended, and 2026 R1 and R2 are Mainstream, per SYSPRO’s lifecycle page on Nov 18, 2026.
Can I keep using a retired SYSPRO release?
Yes. SYSPRO says the lifecycle guidelines do not affect your licence to use the product, and annual licences are still issued for Retired releases. You lose corrections, technical support and compatibility work for new Windows and SQL Server versions.
Did support for SYSPRO 8 2021 and 2022 end in September 2025?
SYSPRO’s page lists September 2025 as the planned change date for those releases but still shows them as Legacy on Nov 18, 2026. We do not treat that as a confirmed end-of-support date; check the live page or ask SYSPRO.
How much does a SYSPRO upgrade cost?
SYSPRO does not publish prices on the pages we checked. Ask your reseller for a written quote that separates licence, maintenance and services; we give no estimate.
What does ERPNext cost?
No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (about £3.79 and £30.33 at the Bank of England rate for Nov 16, 2026; checked Nov 18, 2026). Implementation is separate.
Should we migrate our SYSPRO history?
Usually not. Move masters, open orders, stock and balances, and keep SYSPRO read-only for closed jobs and invoices.