What Happens to Your SYSPRO Data After Your Licence Expires (2026)

Your data does not disappear when your SYSPRO licence expires, but your access to SYSPRO does. SYSPRO's formal notice dated 15 July 2026 states that after your expiry date "you will no longer be able to access Syspro" (syspro.com). The same notice says: "On cessation of your current licence, you have the right to export your data." It adds: "Syspro will provide a straightforward process for this on request" (syspro.com). That is all the notice says about data after expiry. It says nothing about the format, the window or the process.

SYSPRO is ending its Initial and Annual Licence Fee model. From now on SYSPRO is available only as a named-user subscription. If you do not sign a new subscription agreement, your access to SYSPRO ends on your expiry date. This is not an end-of-support milestone. It is a hard cutoff.

This guide covers the deadlines, your export right, where your data physically sits, how to extract it, and what your retention obligations look like after the switch.

For a full pre-departure list, see the SYSPRO exit checklist.

When does SYSPRO access end?

SYSPRO's formal notice sets two expiry dates (syspro.com):

• "your individual expiry date, being 31 October 2026 for customers located outside the U.S."
• "31 December 2026 for customers located in the U.S."

The new terms apply "from your expiry date (that is, from 1 November 2026 for customers located outside the U.S. and 1 January 2027 for customers located in the U.S.)" (syspro.com).

Until your expiry date, "Everything you have paid for continues as normal" and "Your access, your support, and your entitlements are unchanged through to that date" (syspro.com). After it, "To continue using Syspro after that point, you will need to enter a new subscription agreement with us."

If your agreement 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). The notice states no subscription price. It does not say that existing licences convert automatically, or that past licence fees are credited against a subscription.

If you paid an Initial License Fee, it "does not carry forward as a perpetual right to access the software after your expiry date" (syspro.com).

What does the notice actually say about your data?

The notice makes two data-related statements (syspro.com):

1. "On cessation of your current licence, you have the right to export your data."
2. "Syspro will provide a straightforward process for this on request."

It also asks you to raise the export with your account manager ahead of your expiry date.

That is the complete statement. The notice does not describe:

• A read-only mode or grace period after expiry
• How long the export process stays available
• What format the export produces
• Whether the process differs for on-premise and cloud customers
• What happens to your data if you do not request an export

You have a stated right, but no published mechanism, timeline or format. If you assumed your upfront payment gave you indefinite, read-only access to your history, the notice says otherwise. Once your expiry date passes, you cannot log in to run historical reports, check old inventory movements, or audit past financial years through SYSPRO.

So your IT team should own the extraction and run it before your expiry date. Relying only on a vendor export requested at the last minute puts your migration timeline at risk.

Where does your SYSPRO data physically live?

SYSPRO 8 stores its data in Microsoft SQL Server. "SYSPRO supports multiple companies where each company's data is contained within a single database. In addition, a single system-wide database is used to store information that is not specific to any individual company." A site running one company therefore has two databases (help.syspro.com).

Where those databases sit depends on your deployment model.

On-premise: the database is on your hardware

If you run SYSPRO on-premise, the SQL Server databases are on servers you own or lease. The database files stay on disk after your expiry date, and you can still back up your own servers. What the notice ends is your access to SYSPRO. It says nothing about whether you may read the database after expiry, so do not plan on it. Take your backup and run your extract before your expiry date, while every route is open.

Cloud ERP: you do not own the infrastructure

The picture is different if SYSPRO hosts you. For SYSPRO's Private Hosting model, "Full access to the SQL Server database is allowed in line with your access control protocols" (trust.syspro.com). For customers who leave, SYSPRO's trust site says "there is an off-boarding process that is followed" and "There is a download cost associated with transferring a backup of the database to you" (trust.syspro.com).

On Syspro Cloud ERP, the platform "doesn't allow direct database access by any application or personnel" (help.syspro.com). The only data-access route is the Syspro OData Service. If your licence expires before you extract your data, you depend on SYSPRO's off-boarding process.

What data is at risk?

Everything in the company databases and the system-wide database. SYSPRO's database guide says "Each SYSPRO 8 company database contains approximately 1000 tables" (help.syspro.com). For a manufacturer, the core of it looks like this:

Domain	Key tables	What you lose access to
Customers & AR	ArCustomer, ArCustomerGroup, ArInvoice	Customer master records, groups, invoice history
Suppliers & AP	ApSupplier, ApBank, ApInvoice	Supplier records, banks, payable history
Inventory	InvMaster, InvWarehouse, InvMovements	Stock codes, warehouse balances, movement history
Sales orders	SorMaster, SorDetail	Order headers and line items
Purchase orders	PorMasterHdr, PorMasterDetail	PO headers and line items
Manufacturing	WipMaster, WipJobAllMat, WipJobAllLab, BomOperations, BomWorkCentre	Jobs, material allocations, routing steps, work centres
General ledger	GenMaster, GenTransaction	Chart of accounts, journal entries
Lot & serial	LotDetail, InvSerialHead	Traceability records
Currency	TblCurrency, TblCurrDatedRates	Exchange rates, dated rates
Custom fields	Plus tables (e.g. [InvMaster+])	Any custom form data your team added

These table names come from SYSPRO's published documentation (help.syspro.com, help.syspro.com). Custom form data sits in a separate table per form type, named after its parent table with a "+" suffix (help.syspro.com).

An extract has to keep the relationships between these tables. For example, SorDetail lines must stay joined to their SorMaster headers so the target ERP can rebuild complete sales orders.

Data outside the SQL database

Beyond the tables, check for data on the file system: notes, multimedia and files attached to records. Where these live depends on how your site was set up, so ask your SYSPRO administrator. Your extraction plan needs to cover them.

Archived and purged data

SYSPRO's archiving copies purged data to XML files rather than keeping it in the live SQL tables. If your team routinely purges old records, the live database does not hold your complete history.

"Within SYSPRO, you can archive the following: Sales orders, Jobs, ECC bill of materials." But "No 'additional' attached information (such as custom forms, multimedia, notes, etc) is archived" (help.syspro.com, SYSPRO 7 Update 1 help). Archive files are named Xyynnnnn.XML, where X is the company ID, yy is the archive type (SO for sales orders, JB for jobs, BO for bills of materials) and nnnnn is the archive number (help.syspro.com).

The lot Purge and Archive program copies lot transactions and inspection records to an archive file, and deletes the transaction details for completed lots from the live tables. "The header record is never deleted from the lot master table; only the lot transactions are deleted and archived" (help.syspro.com). On SYSPRO 7, the lot Purge and Archive output "is stored in C-ISAM format in the data directory, regardless of the company database format" (help.syspro.com).

Before the final migration, your team must find these archive files, parse them, and merge them with the live SQL data so history is unbroken. For how to keep that history, see how to archive SYSPRO history before switching ERP.

Technical methods for extracting SYSPRO data

The right method depends on your deployment model, your access and your data volume.

1. Direct SQL Server access (one-off, read-only)

Reading the company database with SQL is the most complete way to extract history. It reaches every table, including the plus tables. For large tables such as GenTransaction or InvMovements, it is the only practical bulk route.

SYSPRO's best-practice guide warns: "Connecting to the SYSPRO databases directly using SQL drivers is not advised" (help.syspro.com). That warning is about live integrations. A migration extract runs once and reads only. Use a read-only login, and ideally run it against a restored copy of the database.

This route is open to on-premise customers and Private Hosting customers with SQL access. It is not available on Syspro Cloud ERP.

2. Syspro OData Service

The Syspro OData Service is read-only. It "lets you connect securely to SYSPRO data without direct SQL access" (help.syspro.com). SYSPRO says it "is the only mechanism available when applications need access to SYSPRO data in the Syspro Cloud ERP environment" (help.syspro.com).

It has a hard limit: "SYSPRO OData is a light data gathering solution. Therefore, we limit to 5000 rows under the Microsoft best practice guidelines for performance and fair use." Larger extracts page with $top and $skip (help.syspro.com). For bulk extraction, direct SQL is faster where you have it.

3. Business Activity Queries (BAQ)

"SYSPRO Business Activity Queries are SQL views that are created in the relevant company databases." "Any SQL user with db_datareader permissions can retrieve data using the views" (help.syspro.com). SYSPRO documents no row limit for BAQs. The Business Activity Query Export program moves query definitions between environments. It does not export data, so you still need SQL or OData to pull the results.

4. SYSPRO e.net business objects

Query (Q) business objects such as ARSQRY (Customer Query), INVQRY (Inventory Query) and SORQRY (Sales Order Query) return XML for one record or a filtered set. They apply SYSPRO's own logic, but they suit integration, not bulk extraction. SYSPRO notes that archived sales orders cannot be queried with SORQRY (help.syspro.com).

e.net runs over several bindings. The SYSPRO 8 e.net Communications Load Balancer hosts a REST binding alongside its net.tcp, basic HTTP and WS-HTTP bindings (help.syspro.com). The binding does not change the per-call nature of business objects.

For every export route and its limits, see how to export data from SYSPRO.

Your compliance obligations do not expire with your licence

Retention requirements are set by law and your auditors, not by your ERP vendor's licensing schedule. Tax authorities, auditors and regulators do not care that your SYSPRO licence ran out.

How long you must keep each type of record depends on your jurisdiction and industry. Your auditor or legal team sets the periods. The period runs from the transaction date, not from the date you stopped using SYSPRO. Losing access to SYSPRO does not satisfy a retention obligation. It creates a compliance gap.

What should you do before your expiry date?

The notice asks you to raise the data export with your account manager ahead of your expiry date. Do that, but do not treat it as your only plan.

1. Inventory everything in your SYSPRO databases

Catalogue every company database, the system-wide database, all plus tables (custom fields), archive files from past purges, and file-system attachments. If you run several SYSPRO companies, each has its own database.

2. Take a full SQL Server backup now

For on-premise installations, back up every SYSPRO database to a location you control. A .bak file is the simplest insurance. Even if you never restore it, you hold the data.

3. Extract what you need in a portable format

A one-off, read-only SQL extract against the company database is the fastest and most complete method. BAQs give you a structured layer. OData works but is limited to 5,000 rows per call. On Syspro Cloud ERP, start the OData extract and the export request now.

4. Validate the extract against the source

Check record counts, run field-level spot checks, and confirm parent-child links (SorMaster → SorDetail, PorMasterHdr → PorMasterDetail). Every sales order line should have a header. This is where mistakes surface.

5. Plan for read-only access to historical data

Your new ERP may not need every historical transaction in its live database. But finance, compliance or operations will need to look up old invoices, purchase orders or lot records. Plan a read-only archive that outlives the transition: a reporting database, a data warehouse or an archive tool. See read-only access to SYSPRO history after migration for the options.

6. Move now, whichever date applies to you

If you are outside the US, your expiry date is 31 October 2026. If you are in the US, it is 31 December 2026. Your ERP implementation takes months, and the data migration cannot run until the target system is ready to receive data. Securing a backup and an extract comes first.

The cutover process

A disciplined cutover follows these rules:

• Unlimited sample migrations run until the mapping is right. You review trial balances, inventory counts and open orders in the target system before approving the final run.
• The bulk load runs in the days before go-live, while SYSPRO stays live.
• SYSPRO freezes before Monday's working day starts.
• The final delta covers changed records only and takes about 30 minutes.
• Go-live happens on Monday, never on a Friday.

Target-specific detail is on our pair pages for SYSPRO to Microsoft Dynamics 365 Business Central, SYSPRO to Oracle NetSuite and SYSPRO to Acumatica.

What if you miss the deadline?

The notice gives you a right to export your data on cessation. It does not say how long that right or the process lasts. The notice asks you to raise the request ahead of your expiry date, so do not wait.

On-premise, the database files are still on your hardware after expiry. But the notice ends your access to SYSPRO and does not address reading the database afterwards. Talk to your account manager about the export process, and check your agreement before you touch the database after expiry.

For cloud customers the risk is higher, because you do not control the infrastructure. SYSPRO's trust site describes an off-boarding process with a "download cost" (trust.syspro.com). It does not say how long that process stays available after licence cessation.

The safe answer: do not miss the deadline. Export before it arrives.

How ClonePartner fits

ClonePartner is a vendor-neutral, engineer-led data migration service. We do not resell SYSPRO or the ERP you are moving to, and we are not a SYSPRO partner. We move the data out of SYSPRO, preferably with a one-off read-only SQL extract of the company database, and load it into whichever system you have chosen.

Every project includes unlimited sample migrations until the data maps correctly, at one fixed price per project starting at $500 (clonepartner.com/pricing), with no hourly billing and no per-record metering. Validation covers record-count parity, field-level checks and reconciliation reports. We are SOC 2 Type II and ISO 27001 certified, and we purge staging data within 30 days of project close.