SYSPRO Licence Change 2026: 31 Oct & 31 Dec Deadlines Explained

SYSPRO is ending its Initial License Fee and Annual License Fee model. A formal notice dated 15 July 2026 says existing licences expire on 31 October 2026 for customers outside the United States and on 31 December 2026 for customers in the US. From then on, SYSPRO software is available only under a named-user subscription (syspro.com).

If you run SYSPRO, this guide explains what each deadline means, what your options are, and how to get your data out if you decide to leave.

What is SYSPRO changing?

SYSPRO is discontinuing the Initial License Fee and Annual License Fee model. Going forward, SYSPRO software will only be available under a named-user, subscription-based platform model, and the notice says this applies to all customers (syspro.com).

If your agreement with SYSPRO has no fixed expiry date, the notice itself is the termination: it "constitutes formal written notice that Syspro is terminating your agreement under that provision" (syspro.com).

SYSPRO also says that under the new subscription "you get access to the full Syspro module entitlement, not just the modules in your current licence" (syspro.com). That is the upside SYSPRO offers.

What the notice does not say matters as much:

• It publishes no subscription price.
• It does not say existing licences convert to a subscription automatically.
• It does not say past licence fees are credited against a subscription.

What do the 31 October and 31 December 2026 deadlines mean?

The notice sets two expiry dates by customer location:

Until your expiry date, nothing changes. "Your access, your support, and your entitlements are unchanged through to that date" (syspro.com).

From your expiry date, the Annual License Fee model is no longer available. "To continue using Syspro after that point, you will need to enter a new subscription agreement with us." Without one, "you will no longer be able to access Syspro" (syspro.com).

The notice lists the SYSPRO contracting entities it covers: two in the UK, and one each in Canada, Australia, Singapore, Malaysia, the US and South Africa (syspro.com). So whichever region you license from, one of the two dates applies to you.

The change comes two years after Advent International agreed to take a majority stake in SYSPRO, announced on 13 August 2024 (adventinternational.com).

What happens if you don't sign a subscription?

The notice says customers who decide not to move to the subscription model "should plan to transition to an alternative solution" before their expiry date, because after it they "will no longer be able to access Syspro" (syspro.com). It does not describe a read-only period or an extension.

That leaves three scenarios:

1. Subscribe and stay on SYSPRO. Your data stays where it is, and you move to the named-user subscription.
2. Move to a different ERP. Export your data from SYSPRO and load it into the system you choose. That means two pieces of work: an ERP implementation and a data migration.
3. Do nothing. You lose access to SYSPRO on your expiry date, and your only route to the data is the export right described below.

We compare the first two in Your SYSPRO Licence Expires in 2026: Subscribe, Stay or Move.

What is your data export right?

The notice says: "On cessation of your current licence, you have the right to export your data. Syspro will provide a straightforward process for this on request." It asks customers to raise this with their account manager ahead of their expiry date (syspro.com).

The notice does not say what format the export takes or how long the process stays available after expiry. So do not make it your only plan. If you have access to your SYSPRO database today, run your own extraction before the deadline as well. Our SYSPRO data export guide compares the routes.

What does the change mean for cost?

SYSPRO publishes no subscription price list, and the notice states none. Your account manager or partner is the only source of a quote.

Two things from the notice shape the comparison. The subscription is named-user, so the count that matters is the number of people who need access. And the subscription includes the full module entitlement. If you only license core financials and distribution today, that may add value. If you already license most modules, it adds less.

When you compare a subscription quote with a move, count the data migration separately from the ERP implementation. We break down the migration side in What a SYSPRO Data Migration Costs in 2026.

How data comes out of SYSPRO

SYSPRO 8 stores its data in Microsoft SQL Server. Each company has its own database, and one system-wide database holds information that is not specific to a company (help.syspro.com).

There are three practical extraction routes:

1. Direct SQL Server access. Reading the company database directly reaches every table, including the custom form plus tables. It is the fastest and most complete route.
2. The Syspro OData Service. A read-only service that "lets you connect securely to SYSPRO data without direct SQL access" (help.syspro.com). In SYSPRO's Cloud ERP environment it is the only access mechanism (help.syspro.com).
3. e.net business objects. Six-character objects such as ARSQRY (Customer Query) return XML for a record or a filtered set. They suit integration, not a full-database extract. We compare them with SQL in SYSPRO e.net Business Objects or Direct SQL.

Here are the hurdles your migration team will meet.

Company and system-wide databases

A complete extraction covers every company database you use. If you run several SYSPRO companies, each one is extracted separately.

Custom form fields and the plus tables

SYSPRO keeps custom form data in separate tables named after the main table with a + suffix. Custom fields on customers, for example, sit in [ArCustomer+] (help.syspro.com). Every base table you extract needs its plus table joined in, or the custom data is lost. See Migrating SYSPRO Custom Form Fields and Plus Tables.

Lot traceability and serial tracking

SYSPRO's Lot Traceability system tracks an item "through the manufacturing process, providing full traceability at transactional level" (help.syspro.com). That history spreads across several tables, and SYSPRO's lot Purge and Archive program may already have moved completed lots' transactions to an archive file (help.syspro.com). Check for both before extraction. See SYSPRO Lot and Serial Traceability Migration.

SYSPRO Harmony is not an extraction route

The two clocks: data migration vs. ERP implementation

If you leave SYSPRO, keep two timelines apart.

The ERP implementation clock (months). Selecting, configuring and rolling out a new ERP takes months. Your implementation partner or vendor runs it. ClonePartner does not implement ERPs.

The data migration clock (days). Moving the data is fast. Most data migrations complete within 1–5 business days, depending on data volume, complexity and API rate limits. Small datasets under 10,000 records can finish in under 24 hours.

With a 31 December expiry, the implementation clock is the one that runs out. Start it first. For the difference in more detail, see ERP Data Migration vs Implementation: What's the Difference?

Go-live and cutover

We schedule an ERP cutover this way:

1. Go live on a Monday, never a Friday.
2. The bulk load runs in the days before go-live, while SYSPRO stays live.
3. SYSPRO freezes before Monday's working day starts, so nobody keeps entering data in the old system.
4. The final delta covers changed records only and takes about 30 minutes.

Every migration is checked with record-count parity, field-level validation and reconciliation reports. A dedicated migration engineer owns each project. Our infrastructure is SOC 2 Type II and ISO 27001 audited, and staging databases are purged no later than 30 days after project close.

What to do now

If you are outside the US: your expiry date is 31 October 2026. If you have not signed a subscription, talk to your SYSPRO account manager now and raise the data export at the same time, even if the date has passed.

If you are in the US: you have until 31 December 2026. Get subscription pricing, decide whether it works for you, and if it does not, start the ERP selection and the data migration as two separate workstreams. Our SYSPRO exit checklist lists the steps in order.

Wherever you are: export your data before your deadline, not after. The notice does not say how long the export process stays available after expiry.

If you are moving, the destination's pair page shows what maps and what does not. For example: SYSPRO to Business Central, SYSPRO to SAP Business One, SYSPRO to NetSuite and SYSPRO to Acumatica.