---
title: "SYSPRO Exit Checklist: What to Do Before Your Licence Expires"
slug: syspro-exit-checklist-before-licence-expiry
date: 2026-10-26
author: Raajshekhar Rajan
categories: [SYSPRO, Checklist, ERP]
excerpt: "A 10-step checklist for IT teams leaving SYSPRO before the 2026 licence expiry dates. Covers the data export request, data audit, extraction, retention, cutover and validation."
tldr: Your SYSPRO licence expires on 31 October 2026 outside the US or 31 December 2026 in the US. This 10-step checklist runs from raising the data export with your account manager to decommissioning SYSPRO after go-live.
canonical: https://clonepartner.com/blog/syspro-exit-checklist-before-licence-expiry
---

# SYSPRO Exit Checklist: What to Do Before Your Licence Expires


If your SYSPRO licence expires in 2026 and you have decided not to sign the new subscription, this is the checklist to work through. It covers ten things your team must finish, in order, before your access ends.

SYSPRO's formal notice, dated 15 July 2026, ends the Initial and Annual Licence Fee model. From now on SYSPRO is available only as a named-user subscription ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). A customer who does not sign a new subscription loses access to the software. The notice is clear: if you decide not to move to the subscription model, "you should plan to transition to an alternative solution before" your expiry date.

This checklist assumes you have already made that decision.

## What are the SYSPRO licence expiry deadlines?

SYSPRO's formal notice sets two dates ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)):

- **31 October 2026** for customers located outside the United States. Access ends from 1 November 2026.
- **31 December 2026** for customers located in the United States. Access ends from 1 January 2027.

After your expiry date, "you will no longer be able to access Syspro" unless you enter a new subscription agreement. The notice also says an Initial License Fee "does not carry forward as a perpetual right to access the software after your expiry date." The notice describes no read-only mode and no grace period after expiry. It does not say how long the export process stays available.

Every item on this checklist must be finished before your expiry date. If you are outside the US, that date is 31 October 2026, so start with Step 1 and the running-out-of-time list at the end of this post. If you are in the US, you have until 31 December 2026.

For the full breakdown of the licensing change, see [SYSPRO Licence Change 2026: 31 Oct & 31 Dec Deadlines Explained](https://clonepartner.com/blog/blog/syspro-licence-change-2026-deadlines-explained).

## Step 1: Confirm your decision and request the data export

Before you touch a single table, get two things in writing.

- [ ] **Internal sign-off.** Confirm that your organisation is not subscribing, signed off by the executive who owns the budget, with a date.
- [ ] **Data export request.** SYSPRO's formal notice says: "On cessation of your current licence, you have the right to export your data" and "Syspro will provide a straightforward process for this on request" ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). The notice asks customers to raise this with their account manager ahead of the expiry date. Do it now, in writing.

The notice does not describe what format the export produces, how long the process stays available, or any read-only period after expiry. Assume you will have no access at all after your expiry date, and plan to have your own extract in hand before it. For what the notice does and does not promise, see [What Happens to SYSPRO Data After Licence Expiry](https://clonepartner.com/blog/blog/what-happens-to-syspro-data-after-licence-expiry).

## Step 2: Audit your SYSPRO data estate

You cannot migrate what you have not listed. SYSPRO 8 stores its data in Microsoft SQL Server, with one database per company and a single system-wide database for information that is not specific to any company ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf)). A multi-company installation has several databases, each with its own tables.

You do not need every table. A migration focuses on master data, open transactions and supporting reference data. Map the business entities you need to their SQL tables. These core tables are named in SYSPRO's documentation:

### Financial and account data

- [ ] **`GenMaster`**: general ledger accounts (chart of accounts)
- [ ] **`GenTransaction`**: general ledger transactions
- [ ] **`ArCustomer`**: customers (Accounts Receivable)
- [ ] **`ArCustomerGroup`**: customer groups
- [ ] **`ArInvoice`**: customer invoices
- [ ] **`ApSupplier`**: suppliers (Accounts Payable)
- [ ] **`ApInvoice`**: supplier invoices
- [ ] **`ApBank`**: banks
- [ ] **`TblCurrency`** and **`TblCurrDatedRates`**: currencies and dated exchange rates, if you trade in more than one currency ([help.syspro.com](https://help.syspro.com/syspro-8-2024/topics/dated-exchange-rates/dated-exchange-rates-ovr.htm))

### Inventory and supply chain

- [ ] **`InvMaster`**: inventory master (stock codes)
- [ ] **`InvWarehouse`**: inventory per warehouse
- [ ] **`InvMovements`**: inventory movements
- [ ] **`InvSerialHead`**: serial numbers
- [ ] **`LotDetail`**: lot detail for lot-traceable items

### Sales and purchasing

- [ ] **`SorMaster`**: sales order headers
- [ ] **`SorDetail`**: sales order lines
- [ ] **`PorMasterHdr`**: purchase order headers
- [ ] **`PorMasterDetail`**: purchase order lines

### Manufacturing and WIP

- [ ] **`WipMaster`**: work in progress jobs
- [ ] **`WipJobAllMat`**: materials allocated to a job
- [ ] **`WipJobAllLab`**: labour (operations) allocated to a job
- [ ] **`BomOperations`**: bill of materials operations (routing steps)
- [ ] **`BomWorkCentre`**: work centres

### Custom form fields (the plus tables)

SYSPRO stores custom form data in a separate table per form type. SYSPRO's database guide says "custom form data associated with the customer table 'ArCustomer' is stored in a table named 'ArCustomer+'", and that each table "typically has the same name as its primary associated table with a '+' character as a suffix" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf)). If your team added custom fields to customers, stock codes or sales orders, audit the matching plus tables. If you skip them, you lose those values.

### Attachments and documents

File attachments, report templates and other documents can live outside the SQL database. Find where they are stored and put them in your migration or archive scope.

- [ ] Count the records in each table now. Compare these counts with the counts on migration day. This is your validation baseline.

> [!TIP]
> Do not skip the plus tables. Custom fields on the customer form live in `[ArCustomer+]`, not in `ArCustomer`. SYSPRO advises square brackets around these names in SQL. Miss them and you lose data you did not know you had.

## Step 3: Separate what you archive from what you migrate

**Archiving** and **migration** are two different scopes. They have different targets and different retention rules.

- [ ] **Migration scope** is the data your new ERP needs on day one: open sales orders, open purchase orders, open invoices, current inventory balances, active customers and suppliers, the current chart of accounts, and the history your finance team agrees to bring across.
- [ ] **Archive scope** is everything else that must be kept for audit, compliance or reference but does not need to live in the new ERP: closed jobs, older GL transactions, completed sales orders, and lot records for products still in the field.

Separate these scopes early. Loading years of closed purchase order lines and `GenTransaction` history into a new system makes mapping and testing harder. Archive that history to a queryable store, such as a SQL database or a structured file export with an index, and keep the migration lean.

For the archive side, see [How to Archive SYSPRO History Before Switching ERP](https://clonepartner.com/blog/blog/how-to-archive-syspro-history-before-switching-erp).

## Step 4: Choose your extraction method

How you extract the data decides how fast and how complete the migration is. The right method depends on whether you run SYSPRO on-premise, with SQL Server access, or on Syspro Cloud ERP.

| Method | Best for | Limitations |
|---|---|---|
| **Direct SQL (one-off, read-only)** | Full extraction of an on-premise company database | Needs SQL Server access and schema knowledge. SYSPRO's best-practice guide says connecting directly with SQL drivers "is not advised" ([help.syspro.com](https://help.syspro.com/syspro-8-2023/resources/pdfs/2023-release/technical/syspro-8-best-practices-for-connecting-to-syspro.pdf)), so use a read-only login, ideally against a restored copy |
| **Business Activity Queries (BAQ)** | SQL views SYSPRO creates in the company database | "Any SQL user with db_datareader permissions can retrieve data using the views" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/2022-release/topics/syspro-8-business-activity-queries-reference-guide.pdf)). Still a SQL read, so the same caution applies |
| **OData Service** | Syspro Cloud ERP, or wherever SQL is not possible | Read-only. SYSPRO limits it to 5,000 rows "under the Microsoft best practice guidelines for performance and fair use", with paging through `$top` and `$skip` ([help.syspro.com](https://help.syspro.com/syspro-8-2021-r2/topics/insights-and-reporting/syspro-odata/syspro-odata.htm)) |
| **e.net business objects** | Integration and targeted lookups | Query objects such as `ARSQRY`, `INVQRY` and `SORQRY` return XML for one record or a filtered set. They suit integration, not bulk extraction |
| **Report Writer** | Small, ad-hoc exports | Can send a report to an ASCII file or to spreadsheets ([help.syspro.com](https://help.syspro.com/syspro-7-update-1/_repovr.htm)). Not practical for a full extract |

**On-premise, we use a one-off, read-only SQL extract first.** It reaches every table, including the custom form plus tables. SYSPRO's warning about direct SQL is about live integrations. A migration extract is a single read, so run it with a read-only login, ideally against a restored copy of the database, and remove the connection when you finish. BAQs are a useful complement where a view already joins the tables you need.

In Syspro Cloud ERP, the OData Service "is the only mechanism available when applications need access to SYSPRO data in the Syspro Cloud ERP environment" ([help.syspro.com](https://help.syspro.com/syspro-8-2025/topics/insights-and-reporting/syspro-odata/syspro-odata.htm)). If that is you, plan for paged extraction and allow extra time for large tables.

Every method, with its limits, is covered in [How to Export Data from SYSPRO: Methods, API Limits and Portability](https://clonepartner.com/blog/blog/how-to-export-data-from-syspro-methods-api-limits-portability).

> [!WARNING]
> **SYSPRO Harmony is not an API.** It is a collaborative social platform inside SYSPRO ([help.syspro.com](https://help.syspro.com/syspro-8-2024/topics/harmony/harmony-ovr.htm)). Do not build an extraction plan around it.

## Step 5: Map integrations and downstream dependencies

SYSPRO rarely runs alone. Before you switch it off, list every system that reads from or writes to it:

- [ ] **EDI feeds**: customer and supplier connections that post orders or send ASNs
- [ ] **E-commerce platforms**: inventory sync, order import, pricing feeds
- [ ] **CRM systems**: customer sync, quote-to-order handoffs
- [ ] **Payroll and HR**: if labour costing feeds from SYSPRO WIP
- [ ] **Warehouse management**: barcode scanning, pick, pack and ship
- [ ] **BI and reporting**: dashboards, Power BI connections, report packs
- [ ] **Banking and payments**: AP payment files, bank reconciliation imports
- [ ] **Third-party add-ons**: ISV apps and custom automation

For each integration, record the direction of data flow, the connection method (SQL, e.net business object, file drop, OData), the frequency (real-time, hourly, nightly) and the owner who will reconnect it to the new system.

Your new ERP's implementation partner rebuilds these integrations. But *you* own the list. If a nightly CSV feed to your 3PL breaks on day one because nobody wrote it down, that gap belongs to the exit checklist, not the implementation plan.

## Step 6: Handle compliance and retention requirements

Manufacturers and distributors often have retention obligations that outlast any ERP. Your auditor or legal team sets the retention periods. They run from the date of each transaction, not from the day you switch SYSPRO off.

Before you decommission SYSPRO, confirm:

- [ ] **Tax and financial records**: GL transactions, AP and AR records, and bank reconciliation data are kept for the period your auditor sets.
- [ ] **Lot and serial traceability**: if you make products that can be recalled, your `LotDetail` and `InvSerialHead` records are compliance records, not optional extras. SYSPRO's lot Purge and Archive program may already have moved older lot transactions to archive files, so check for them before extraction ([help.syspro.com](https://help.syspro.com/syspro-8-2024/g_programs/lot/lotp01/lotp01.htm)).
- [ ] **Contractual retention clauses**: customer contracts may say how long you keep order history, pricing or delivery records.
- [ ] **GDPR and data minimisation**: if you hold personal data on EU customers, contacts or staff, keeping everything forever is itself a risk. Keep what you must and delete what you should.

Document which records are kept, for how long, and where they will live after SYSPRO is switched off. If the archive sits outside the new ERP, make sure people can query it. A folder of CSV files nobody can search is not an archive.

ClonePartner holds SOC 2 Type II and ISO 27001. We purge staging data within 30 days of project close.

## Step 7: Map data to your target ERP

**Data mapping** defines how each field in SYSPRO matches a field in your target system, and what transformation sits in between.

This is where ERP migrations break. SYSPRO has its own conventions: stock codes in `InvMaster`, customer groups in `ArCustomerGroup`, dated exchange rates in `TblCurrDatedRates`. Your target ERP has its own schema, required fields and validation rules.

Common mapping problems in a SYSPRO exit:

- [ ] **Unit of measure**: if the target handles unit of measure conversion differently, you need transformation logic, not just a column rename.
- [ ] **Multi-warehouse inventory**: `InvWarehouse` holds quantities per warehouse. If the target has a different warehouse or location hierarchy, restructure the data instead of copying it.
- [ ] **Custom form fields**: plus-table data must map to custom fields in the target. If the target has no equivalent, archive the data or lose it.
- [ ] **GL account structure**: the `GenMaster` chart of accounts may not match the target's segment structure. Your implementation partner makes that design decision, but the migration team needs the mapping before extraction starts.
- [ ] **Open document status codes**: what SYSPRO treats as an open sales order or PO may not match the target's status model. Map every status value.

For the target you have chosen, see the pair pages for [SYSPRO to Microsoft Dynamics 365 Business Central](https://clonepartner.com/blog/migrate/syspro-to-microsoft-dynamics-365-business-central), [SYSPRO to SAP Business One](https://clonepartner.com/blog/migrate/syspro-to-sap-business-one) and [SYSPRO to Epicor Kinetic](https://clonepartner.com/blog/migrate/syspro-to-epicor-kinetic).

## Step 8: Plan the cutover window

The cutover is the period between freezing SYSPRO and going live on the new system. Keep it short, and finish it before your licence expiry date.

The approach we use:

1. Run the bulk data load in the days before go-live, while SYSPRO stays live.
2. Freeze SYSPRO before Monday's working day starts.
3. Run a final delta of changed records only: new orders, updated stock levels, recent invoices. The delta takes about 30 minutes.
4. Go live on the new ERP that Monday morning.

**Go live on a Monday, never on a Friday.** A Monday go-live gives you a full working week, with business users at their desks, to catch problems in real transactions. A Friday go-live leaves issues building up over a weekend with nobody to check them.

Cutover planning items:

- [ ] **Freeze date and time**: when does SYSPRO stop taking transactions? Tell every department.
- [ ] **Open transaction cutoff**: decide which orders, POs and invoices should be closed in SYSPRO before the freeze. Anything still open gets migrated.
- [ ] **Delta scope**: which tables changed between the bulk load and the freeze? The migration must handle inserts and updates, not just the first load.
- [ ] **Rollback plan**: if validation fails, how do you go back? SYSPRO is only a fallback until your expiry date. After that you have no access, so schedule go-live with time to spare.

> [!NOTE]
> **Two clocks, not one.** The data migration, moving records from SYSPRO to the new ERP, takes days. Most data migrations finish within 1 to 5 business days, depending on data volume, complexity and API rate limits. Under 10,000 records can finish in under 24 hours. The ERP implementation (selecting, configuring, testing and rolling out the new system) takes months and is a separate project run by your implementation partner or the vendor. ClonePartner handles the data migration. We do not implement ERPs.

## Step 9: Validate the migration

Validation is not a single pass. It starts with sample migrations and continues after go-live.

- [ ] **Record-count parity**: the number of records extracted from SYSPRO matches the number loaded into the target. Run counts on every table, every time, and compare them with your audit baseline.
- [ ] **Field-level checks**: check critical fields such as customer balances, stock quantities, open order values and GL balances. Did the plus-table custom fields land in the right custom fields in the new system?
- [ ] **Referential integrity**: do sales order lines (`SorDetail`) point at their headers (`SorMaster`), valid customers and valid stock codes (`InvMaster`)? Do PO lines point at valid suppliers? Broken references mean broken workflows.
- [ ] **Financial reconciliation**: run a trial balance in SYSPRO and compare it with the trial balance in the new ERP after the sample load. Period-end balances, aged AR and AP totals, and bank reconciliation figures should agree to the cent.
- [ ] **User acceptance testing**: business users run real scenarios on migrated data. Can they find a customer and see the right order history? Can they receive a PO that was open in SYSPRO?

Never run a big-bang migration without testing. We run unlimited sample migrations before the full run, until the data is right.

## Step 10: Decommission SYSPRO

Once the new ERP is live and validated, shut SYSPRO down properly:

- [ ] **Final backup**: take a full SQL Server backup of every SYSPRO company database and the system-wide database. Store it in at least two places. This is your last-resort archive.
- [ ] **Licence documents**: keep your original SYSPRO licence agreement, the formal notice, and your correspondence with your account manager about the data export, for the audit trail.
- [ ] **Integration shutdown**: disable every feed, scheduled task and API connection that pointed at SYSPRO. A dormant connection to a retired server is a security risk.
- [ ] **Server retirement**: if SYSPRO ran on its own hardware, follow your standard retirement process and wipe or destroy storage media under your data destruction policy.
- [ ] **Sign-off**: confirm in writing to finance, operations and compliance that SYSPRO is switched off, that data is archived to the retention schedule, and that the new ERP is the system of record.

## What to do if you're running out of time

If you are outside the US, your date is 31 October 2026. If you are in the US, it is 31 December 2026. If time is short, this is the list:

1. **Raise the data export with your SYSPRO account manager today**, in writing, ahead of your expiry date.
2. **Take a full SQL Server backup** if you run SYSPRO on-premise. A complete backup of every SYSPRO database keeps your options open.
3. **Extract master data and open transactions first.** Customers, suppliers, stock, open orders and current GL balances are what the new ERP needs on day one. History can come from the backup or the archive later.
4. **Bring in a migration specialist.** Under 10,000 records can finish in under 24 hours. Larger data sets take longer, but the data migration is measured in days, not months.
5. **Keep the two clocks apart.** If your new ERP is not configured yet, the data migration can still be scoped, mapped and staged. We move the data. Your implementation partner builds the system.

For how each deadline works, see [SYSPRO Licence Change 2026: 31 Oct & 31 Dec Deadlines Explained](https://clonepartner.com/blog/blog/syspro-licence-change-2026-deadlines-explained).

## The bottom line

A SYSPRO exit is a project, not a crisis, but the expiry dates do not move. Raise the export with your account manager, audit your data, separate archive from migration, pick the right extraction method, map to the target, validate every load, go live on a Monday before your expiry date, and decommission cleanly.

ClonePartner is a vendor-neutral, engineer-led data migration service. We do not resell ERPs and we are not a SYSPRO partner. We move the data out of SYSPRO into whichever system you have chosen, and we validate it with record-count parity, field-level checks and reconciliation reports. One fixed price per project, starting at $500 ([clonepartner.com](https://clonepartner.com/pricing)). No hourly billing and no per-record metering.

> Book a free 30-minute scoping call and get a fixed-price proposal for your SYSPRO data migration before your licence expires.
>
> [Talk to us](https://clonepartner.com/talk-to-us?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### What happens to my data when my SYSPRO licence expires?

SYSPRO's formal notice says you will no longer be able to access SYSPRO after your expiry date (31 October 2026 outside the US, 31 December 2026 in the US) without a new subscription agreement. The notice confirms you have the right to export your data on cessation and says SYSPRO will provide a process on request. It does not describe a read-only mode after expiry or say how long the export process stays available, so raise the export with your account manager ahead of your expiry date.

### What is the best way to extract bulk data from SYSPRO?

For an on-premise migration, a one-off, read-only SQL extract of the company database, ideally against a restored copy, reaches every table, including the custom form plus tables. SYSPRO advises against direct SQL connections for live integrations, so do not leave the connection in place. Where SQL is not possible, use the read-only OData Service, which SYSPRO limits to 5,000 rows per call. In Syspro Cloud ERP, OData is the only route.

### How long does a SYSPRO data migration take?

The data migration itself, moving records from SYSPRO to the new ERP, takes 1 to 5 business days, depending on data volume, complexity and API rate limits. Under 10,000 records can finish in under 24 hours. The ERP implementation is a separate project that takes months and is run by your implementation partner or the vendor.

### Should I archive SYSPRO data or migrate everything to the new ERP?

Separate the two scopes. Migrate what your new ERP needs on day one: open orders, active master data, current balances and the history your finance team agrees to bring across. Archive everything else, such as closed jobs, older GL transactions and completed orders, to a queryable store outside the new ERP.

### Do I need to keep SYSPRO data after my licence ends?

Usually yes. Retention periods for financial, tax and traceability records are set by your auditor or legal team, and they run from the transaction date, not from the day SYSPRO is switched off. Before your licence expires, make sure your archive covers tax records, lot and serial traceability, contractual retention clauses and personal data rules, and document what is kept and where.