--- title: "SYSPRO Licence Expires 2026: Subscribe, Stay or Move" slug: syspro-licence-expires-2026-subscribe-stay-or-move date: 2026-10-26 author: Roopendra Talekar categories: [SYSPRO, ERP, Migration Guide] excerpt: "SYSPRO ends its Initial and Annual Licence Fee model. Licences expire 31 Oct 2026 outside the US and 31 Dec 2026 in the US. Here's what subscribe, stay, and move to another ERP each mean in practice." tldr: "SYSPRO is ending its Initial and Annual Licence Fee model. Existing licences expire on 31 October 2026 outside the US and 31 December 2026 in the US. Sign a new named-user subscription, or export your data and move to another ERP before your access stops." canonical: https://clonepartner.com/blog/syspro-licence-expires-2026-subscribe-stay-or-move --- # SYSPRO Licence Expires 2026: Subscribe, Stay or Move Every SYSPRO licence on the old fee model expires this year. A formal notice dated 15 July 2026 confirms that SYSPRO is discontinuing the Initial License Fee (ILF) and Annual License Fee (ALF) model and moving to named-user subscription licensing only ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). The hard deadlines: **31 October 2026** for customers outside the United States and **31 December 2026** for US customers. After your respective date, SYSPRO's notice says, "you will no longer be able to access Syspro" without a new subscription agreement. This is not an optional upgrade. The notice says the change "applies to all customers", so every SYSPRO customer has a decision to make about their ERP. You have three options: sign the subscription, export your data and leave, or let the deadline pass and lose access to the software. This guide breaks down what each option means in practice — including how to get your data out if you choose to replatform. For a deep-dive on the dates themselves, see [SYSPRO Licence Change 2026: 31 Oct & 31 Dec Deadlines Explained](https://clonepartner.com/blog/blog/syspro-licence-change-2026-deadlines-explained). ## What exactly is SYSPRO changing? **SYSPRO is discontinuing the Initial License Fee and Annual License Fee model.** From now on, SYSPRO software is available only "under a named-user, subscription-based platform model". The old model is ending for all customers, not offered as an option alongside the new one ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). Under a named-user model, you count the people who use SYSPRO. The notice gives no prices and no user tiers. SYSPRO's notice says the subscription includes "access to the full Syspro module entitlement, not just the modules in your current licence" ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). That means modules you never licensed are included. The notice also states that any ILF you previously paid "does not carry forward as a perpetual right to access the software after your expiry date" ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). > [!WARNING] > SYSPRO publishes no subscription pricing. Third-party estimates vary widely. Do not plan your budget around published ranges — get a direct quote from your SYSPRO account manager or certified partner. ## Option 1: Sign the new SYSPRO subscription If you are satisfied with SYSPRO's manufacturing and distribution capabilities and want continuity, the subscription is the path of least disruption. No data migration. No re-training. No re-implementation. **What you gain:** - Full module entitlement — the notice promises "the full Syspro module entitlement, not just the modules in your current licence" - No migration project, so no change to how your team works today **What you need to evaluate:** - **Named-user count.** Audit your active directory and SYSPRO user logs to determine exactly how many unique individuals access the system. Count every operator across every shift. - **Cost delta.** Compare your current ALF to the proposed subscription. This is a direct conversation with your account manager — no public pricing is available. - **Contract terms.** Read the subscription agreement's term, renewal and termination clauses before signing. ## Option 2: "Stay" on SYSPRO — what that actually means There is no option to stay on the old licensing model. SYSPRO's notice is clear: the ILF/ALF model is being discontinued. "Staying" on SYSPRO after 31 October 2026 (outside the US) or 31 December 2026 (US) **means subscribing**. The notice dates the change "from your expiry date": 1 November 2026 outside the US and 1 January 2027 in the US. From then, "you will need to enter a new subscription agreement" ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). The notice does not describe a grace period or a read-only mode after expiry. If your agreement has no fixed expiry date, the notice says it "constitutes formal written notice that Syspro is terminating your agreement under that provision". Termination takes effect on the same dates ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). This is not an optional upgrade you can decline while continuing on the old terms. Some customers may interpret "stay" as delaying the decision — running the software until the deadline and dealing with it later. That approach carries real risk. After the expiry date, SYSPRO says you lose access. If you haven't signed a subscription or exported your data by then, you are locked out of the application, and getting your data depends on an export process the notice does not describe. SYSPRO does acknowledge your ownership of your historical data. The notice states: "On cessation of your current licence, you have the right to export your data." It further notes that "Syspro will provide a straightforward process for this on request", and asks you to raise it with your account manager ahead of your expiry date ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). Our post on [what happens to SYSPRO data after licence expiry](https://clonepartner.com/blog/blog/what-happens-to-syspro-data-after-licence-expiry) covers this in more detail. > [!CAUTION] > **What the notice does not promise:** SYSPRO does not describe a read-only mode after expiry, nor does it state how long the export process remains available after the deadline. Do not let the deadline pass without a signed subscription or a completed data export. ## Option 3: Move to a different ERP If the subscription economics don't work, or if SYSPRO's functional fit no longer matches your business, the licensing change is a forcing function to re-evaluate. You are not the only team asking this question — the change applies to every SYSPRO customer globally. ### Which ERPs do SYSPRO customers move to? SYSPRO serves mid-market manufacturers and distributors, so the natural alternatives target the same segment: The usual shortlist for this segment is Microsoft Dynamics 365 Business Central, Epicor Kinetic, SAP Business One, Acumatica and Oracle NetSuite. Each vendor's licensing model and manufacturing depth changes from release to release, so take both from the vendor's own pages and a demo on your own data. Get each vendor's current pricing from the vendor or its partner. For a side-by-side view, see our [SYSPRO alternatives comparison](https://clonepartner.com/blog/blog/top-syspro-alternatives-2026-tco-features-migration-paths). Our migration pages cover moving SYSPRO data into [Business Central](https://clonepartner.com/blog/migrate/syspro-to-microsoft-dynamics-365-business-central), [Epicor Kinetic](https://clonepartner.com/blog/migrate/syspro-to-epicor-kinetic) and [Acumatica](https://clonepartner.com/blog/migrate/syspro-to-acumatica). For broader ERP comparison context, see [NetSuite vs Dynamics 365 Business Central: Which ERP Wins in 2026?](https://clonepartner.com/blog/blog/netsuite-vs-dynamics-365-business-central-which-erp-wins-in-2026). ### What makes a SYSPRO exit harder than other ERP migrations? SYSPRO's architecture creates specific extraction and mapping challenges that trip up teams who treat it like a generic SQL lift-and-shift: - **SQL Server company databases.** SYSPRO keeps each company's data in its own SQL Server database, plus one system-wide database ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf)). Table names are module-prefixed (e.g., `InvMaster` for inventory, `ArCustomer` for customers). This is well-structured for extraction but requires careful mapping to the target ERP's entity model. - **Plus tables for custom fields.** Custom form fields in SYSPRO are stored in "plus tables" — a separate table per form type, named after its primary table with a `+` suffix (e.g., `[ArCustomer+]` for customer custom fields) ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf)). A migration that skips plus tables loses every custom field your business added. A bulk extraction script must join the core tables to their respective plus tables to ensure no custom data is left behind. - **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](https://help.syspro.com/syspro-8-2021-r2/topics/distribution/lots/lots-ovr.htm)). Not every target ERP supports the same depth. If you're in a regulated industry (food, pharma, medical devices), verify the target platform's traceability model before committing. ## How do you get your data out of SYSPRO? SYSPRO's formal notice says you have the right to export your data on cessation of your licence and that "Syspro will provide a straightforward process for this on request" ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). But the notice does not describe what that process looks like, how long it remains available, or whether it provides access to a running SYSPRO instance or just a data dump. **Do not rely on a post-expiry export process you haven't seen.** Extract your data while your licence is still active and you have full access to the SQL Server databases. For a technical comparison of extraction methods, see [SYSPRO e.net Business Objects vs Direct SQL for Data Extraction](https://clonepartner.com/blog/blog/syspro-enet-business-objects-or-direct-sql-extraction). ### Direct SQL Server access **Direct SQL is the fastest and most complete way to extract data from SYSPRO.** By querying the SQL Server database directly, you bypass API rate limits and application-layer overhead. Any SQL tool — SSMS, Azure Data Studio, a scripted pipeline — works. SYSPRO uses one SQL Server database per company plus a single system-wide database, so a site with one company has two databases ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf)). To extract a complete picture, you must query each company database. Direct SQL is the most complete bulk route for custom fields. SYSPRO's custom form fields live in plus tables (e.g., `[ArCustomer+]`). A bulk extraction script must join core tables to their respective plus tables to ensure no custom data is left behind. ### Business Activity Queries (BAQs) **SYSPRO Business Activity Queries are SQL views created in the relevant company databases.** Any SQL user with `db_datareader` permissions can retrieve data using these views ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/2022-release/topics/syspro-8-business-activity-queries-reference-guide.pdf)). SYSPRO documents no row limit for BAQs. They are useful for structured, repeatable extracts, but they often require modification to ensure all necessary historical tables and plus tables are included in a full migration scope. ### SYSPRO OData Service **The SYSPRO OData Service is a read-only RESTful endpoint** that lets you connect to SYSPRO data without direct SQL access ([help.syspro.com](https://help.syspro.com/syspro-8-2025/topics/insights-and-reporting/syspro-odata/syspro-odata.htm)). SYSPRO notes this "is the only mechanism available when applications need access to SYSPRO data in the Syspro Cloud ERP environment." SYSPRO limits each OData call to 5,000 rows: "we limit to 5000 rows under the Microsoft best practice guidelines for performance and fair use" (same source). Paging with `$top` and `$skip` works, but it slows down large extractions compared to direct SQL. ### e.net business objects **SYSPRO e.net business objects are XML-based programmatic interfaces to SYSPRO's business logic.** Query objects like `ARSQRY` (Customer Query), `INVQRY` (Inventory Query), and `SORQRY` (Sales Order Query) return XML for one record or a filtered set. They pass through SYSPRO's business logic, but calling an e.net business object for every historical transaction in a 15-year-old database creates heavy overhead and long extraction times. Use them for integration and spot-checks, not bulk extraction. > [!TIP] > Our extraction preference for SYSPRO migrations is **Direct SQL first**, then the read-only OData service where SQL is not possible. OData is the only route on Syspro Cloud ERP. e.net business objects are for integration, not bulk extraction. On the loading side, we prefer API into the target ERP, with JSON or CSV as fallbacks. Direct SQL gives you the complete dataset, including custom plus-table fields that BAQs and business objects may not fully expose. ## What data should you actually migrate? Not everything in your SYSPRO database needs to move. Migrating 15 years of closed sales orders into a new ERP adds cost and complexity without operational value. **Always migrate (operational data):** - Chart of accounts and GL balances (trial balance at cutover date) - Customer and supplier master records with open balances - Inventory master with current quantities, costs, and lot/serial data - Open sales orders and open purchase orders - Bills of materials (active BOMs only, unless regulatory requirements demand full history) - Active pricing and discount structures **Migrate selectively (historical data):** - Closed transaction history — often better served by an archive or reporting database than by loading into the new ERP - Lot genealogy and traceability records — required for regulated industries, optional for others - Attachments and documents — migrate active ones, archive the rest **Leave behind:** - Superseded BOM revisions with no regulatory requirement - Purged or voided transactions - Temporary data (staging records, test companies) For a detailed framework, see [What Data Should You Actually Migrate to Your New ERP?](https://clonepartner.com/blog/blog/what-data-should-you-actually-migrate-to-your-new-erp). ## How long does a SYSPRO data migration take? **The data migration itself — extracting from SYSPRO and loading into the target ERP — typically completes within 1–5 business days**, depending on data volume, complexity, and API rate limits on the target platform. Small datasets under 10,000 records can finish in under 24 hours. **This is not the same as your ERP implementation timeline.** Selecting, configuring, and rolling out a new ERP — chart of accounts design, workflow configuration, user training, integration setup — takes months and is handled by your implementation partner or the ERP vendor. ClonePartner moves the data; we do not implement the ERP. These are two separate workstreams on two separate clocks. If you're planning to leave SYSPRO, your deadline is 31 October 2026 (outside the US) or 31 December 2026 (US). If that date is close, **raise the data export with your SYSPRO account manager now** and extract the data while you still have access. Your implementation partner can then configure the target system, and we can run sample migrations, validate field mappings, and schedule the final cutover. For a broader view of this distinction, see [ERP Data Migration vs Implementation: What's the Difference?](https://clonepartner.com/blog/blog/erp-data-migration-vs-implementation-whats-the-difference). ## Who owns SYSPRO On 13 August 2024, Advent International announced it would take a majority stake in SYSPRO ([adventinternational.com](https://www.adventinternational.com/news/advent-international-to-invest-in-syspro-a-global-provider-of-manufacturing-and-distribution-software-to-enhance-innovation-and-growth/)). The licensing notice does not mention the ownership change. SYSPRO's subscription model may deliver genuine value, such as full module access. Evaluate the economics with your own user count and a direct quote, not with assumptions about what the subscription "should" cost. ## How ClonePartner fits a SYSPRO exit ClonePartner is a vendor-neutral, engineer-led data migration service. We don't resell SYSPRO, and we don't resell whatever you're moving to. We move the data from point A to point B and validate the result. What that looks like in a SYSPRO migration: - **Extract** from SYSPRO's SQL Server company databases — including plus tables, lot/serial data, BOM structures, and GL history - **Map** SYSPRO's module-prefixed tables to the target ERP's entity model — GL accounts, warehouse structures, pricing models - **Load** into the target ERP via API (preferred), JSON, or CSV as a fallback - **Validate** with record-count parity, field-level checks, and reconciliation reports - **Cutover** with a bulk load before go-live while SYSPRO stays operational, then a final delta sync (~30 minutes) covering only changed records **Fixed pricing:** One fixed price per project, starting at $500 ([clonepartner.com](https://clonepartner.com/pricing)). No hourly billing, no per-record metering. The price scales based on data volume, custom fields, attachment size, and the platforms involved. **Unlimited sample migrations** are included in the paid price. We run subsets of your data into a sandbox environment until the field mapping, posting groups, and referential integrity are correct. **Dedicated engineering:** A dedicated migration engineer owns your project from start to finish — not a ticket queue. **Monday go-live:** We execute the bulk load in the days before go-live while SYSPRO stays operational. SYSPRO is frozen before Monday's working day starts, and we run a final delta sync to capture the last changes. We always go live on a Monday, never on a Friday. Our staging databases auto-purge no later than 30 days after project close, and we maintain SOC 2 Type II and ISO 27001 safeguards throughout. ## A realistic timeline for leaving SYSPRO The 2026 deadlines are hard stops. 31 October 2026 (non-US) and 31 December 2026 (US) represent the end of your current access rights. | Workstream | Owner | Typical duration | Notes | |---|---|---|---| | ERP selection and contract | Your team + ERP vendor | Variable (often already in progress) | ClonePartner does not perform this | | ERP configuration and setup | Your implementation partner | Months | ClonePartner does not perform this | | Data migration scoping | ClonePartner | Free 30-minute call | Produces a fixed-price proposal | | Data migration execution | ClonePartner | 1–5 business days (most migrations) | Depends on volume, complexity, API rate limits | | Final cutover and delta sync | ClonePartner + your team | ~30 minutes for the final delta | Go live on a Monday, never on a Friday | The data migration is the short part. The ERP implementation is the long part. If you haven't started the implementation yet, the data migration timeline is not your bottleneck — the implementation is. If you plan to subscribe to the new named-user model, begin auditing your user counts immediately to forecast the financial impact. If you plan to leave, start evaluating target ERPs now. The new system must be configured and ready to receive data well before your SYSPRO access is terminated. > Leaving SYSPRO before the deadline? Book a free 30-minute scoping call. We'll review your SYSPRO database structure, map the extraction path, and deliver a fixed-price proposal. > > [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 ### When does my SYSPRO licence expire in 2026? SYSPRO licences expire on 31 October 2026 for customers outside the US and 31 December 2026 for US customers. After the expiry date, SYSPRO's formal notice says you will no longer be able to access the software without a new subscription agreement. ### Can I keep using SYSPRO without switching to the subscription? No. SYSPRO is discontinuing the Initial License Fee and Annual License Fee model for all customers. From your expiry date, the notice says you need a new subscription agreement to keep using SYSPRO. Without one, you will no longer be able to access it. ### Can I export my data when my SYSPRO licence expires? Yes. SYSPRO's formal notice states that on cessation of your licence, you have the right to export your data and that SYSPRO will provide a straightforward process for this on request. However, the notice does not describe the process or how long it remains available. Raise the export with your account manager before 31 October 2026 (outside the US) or 31 December 2026 (US), and extract your data while your licence is still active. ### Which ERP systems can SYSPRO customers move to? ERPs aimed at mid-market manufacturers and distributors, such as Microsoft Dynamics 365 Business Central, Epicor Kinetic, SAP Business One, Acumatica and Oracle NetSuite. The best fit depends on your manufacturing depth requirements, user count, and whether you need multinational or multi-subsidiary capabilities. ### How long does a SYSPRO data migration take? The data migration itself — extracting from SYSPRO SQL Server and loading into the target ERP — typically completes within 1–5 business days, depending on data volume, complexity, and API rate limits. This is separate from the ERP implementation project, which takes months and is run by your implementation partner or the ERP vendor.