Retiring SYSPRO means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise lot and serial relationships, job records and financial history. Compare required reports and documents with source evidence, test permissions and obtain business acceptance before scheduling shutdown.

This guide covers the retirement questions, a mock-data ArchiveHub demonstration and the validation work needed to define a project scope.

What keeping SYSPRO "read-only" really costs

Cost categories are a discovery checklist, not a guaranteed savings calculation. Verify support status, deployment, shared infrastructure and contract terms for the actual installation.

  • The server and database stack. A Windows server and SQL Server instance that still need patching, backup and licences, often on versions near or past the end of support.
  • SYSPRO licences and support. Annual maintenance or a subscription for a system that no longer posts transactions.
  • Client installs and partner time. Every lookup needs a working SYSPRO client and someone who knows which query program to run. That often means a call to the reseller.
  • Fading expertise. The people who knew the Lot Traceability Query, the GRN Suspense report or the WIP Valuation by heart are moving on.
  • Audit and quality access workarounds. Auditors and quality teams receive exports and screenshots, with no controlled, logged way to view the source data.

Switching SYSPRO off removes these lines. The savings depend on your licensing and infrastructure, so we keep them qualitative.

Scope, versions and evidence

This is an illustrative workflow, not a customer case study. Confirm the source release, deployment, modules, customisations and extraction permissions before using the mappings below. Tables and report labels describe the demonstration catalogue; native-report equivalence has not been independently certified. Use agreed source reports and representative records for acceptance testing.

An archive is not a replacement for every operational feature of the retired ERP. Document required historical tasks, excluded functions and any archive-derived calculations.

Historical data to scope for SYSPRO

ArchiveHub keeps the SYSPRO data model with its native table names. The module prefixes (Gen, Ap, Ar, Inv, Wip, Bom, Lot, Sor, Por, Csh, Pay, Asset) still point where they always did:

  • General Ledger: GenMaster for the chart of accounts, GenJournalCtl with one row per posted journal, GenTransaction for the journal detail lines, GenHistory for beginning-of-year and closing balances by period, and GenBudgets.
  • Accounts Payable: ApSupplier, ApInvoice with outstanding balance, ApPayRunHdr and ApPayRunDet for payment runs by cheque or EFT, and GrnDetails for goods received notes and GRN matching.
  • Accounts Receivable and sales: ArCustomer, ArInvoice, ArInvoicePay, ArTrnDetail for sales analysis lines, and SorMaster and SorDetail for sales orders.
  • Purchasing: PorMasterHdr and PorMasterDetail.
  • Inventory: InvMaster for stock codes, InvWarehouse with quantities and cost per warehouse, and InvMovements for every receipt, issue, sale and adjustment.
  • Manufacturing: WipMaster, WipJobAllMat and WipLabJnl for jobs, material and labour, and BomStructure, BomOperations and BomWorkCentre for structures and routings.
  • Traceability: LotDetail and LotTransactions, and InvSerialHead and InvSerialTrn for serialised stock codes.
  • Cash Book, Assets, Payroll and Tax: ApBank and CshTransactions, AssetMaster and AssetHistory, PayEmployee and PayHistory, and AdmTax and AdmTaxReturn.

In the demonstrated scope, each field keeps its SYSPRO column name and gets a description, so users can query the archive in SYSPRO terms. A few snapshots are rebuilt by ArchiveHub and labelled as archive-derived, not native SYSPRO tables: the quarter-end AP and AR aged analyses and the quarter-end inventory valuation.

Explore the demonstration

GL Journals list in ArchiveHub GL Journals: posted SYSPRO journals by year, period and source, from the journal control file. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

GL Journals detail page in ArchiveHub GL Journals detail: one posted journal with its GenTransaction lines by GL code. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Subledger to GL Reconciliation in ArchiveHub Subledger to GL Reconciliation: AR, AP, inventory, WIP, GRN, cash book, assets and payroll movements against the GL control accounts by period. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Explore the report reference catalogue

These mappings identify intended business workflows, not certified one-for-one equivalents. Confirm availability, source coverage, filters, currencies, dates and calculations for the selected release and implementation.

General Ledger

  • GL Transactions: reference workflow: the GL Query: transaction detail by GL code and period (GenTransaction, GenMaster)
  • GL Journals: reference workflow: the GL Journal Query and GL Journal Listing / audit trail of posted journals (GenJournalCtl, GenTransaction)
  • GL Accounts: reference workflow: the GL Structure / GL Code Query: chart of accounts with yearly history (GenMaster, GenHistory)
  • Trial Balance: reference workflow: the GL Trial Balance (GENP20) by year and period from GL history (GenHistory), with P&L accounts opening at zero after the SYSPRO year end
  • Budget vs Actual: reference workflow: the GL Budget Query / budget versus actual report (GenBudgets, GenHistory)
  • Subledger to GL Reconciliation: reference workflow: the GL Reconciliation reports: AR, AP, Inventory, WIP, GRN, Cash Book, Assets and Payroll movements against the GL control accounts by period
  • Tax Report: reference workflow: the tax report / VAT and sales tax return by tax code and period (ArTrnDetail, ApInvoice, AdmTax, AdmTaxReturn)

Accounts Payable

  • Suppliers: reference workflow: the Supplier Query (APSPEN) and supplier maintenance (ApSupplier)
  • AP Invoices: reference workflow: the AP Invoice Query, with GRN matching and payment history (ApInvoice, GrnDetails, ApPayRunDet)
  • AP Payment Register: reference workflow: the AP Payment Run / cheque and EFT register (ApPayRunHdr, ApPayRunDet)
  • AP Aged Analysis: reference workflow: the AP Aged Analysis (APSP21) at quarter-end dates, rebuilt from ApInvoice and ApPayRunDet
  • GRN Suspense: reference workflow: the GRN Suspense report / GRN Query: goods received not yet invoiced and GRN matching (GrnDetails)

Accounts Receivable

  • Customers: reference workflow: the Customer Query (ARSPEN) and customer maintenance (ArCustomer)
  • AR Invoices: reference workflow: the AR Invoice Query and Document Print reprint (ArInvoice, ArTrnDetail, ArInvoicePay)
  • AR Payments: reference workflow: the AR Payments and Adjustments journal / cash receipts (ArInvoicePay, CshTransactions)
  • AR Aged Analysis: reference workflow: the AR Aged Analysis / AR Trial Balance (ARSP30) at quarter-end dates, rebuilt from ArInvoice and ArInvoicePay

Sales

  • Sales Orders: reference workflow: the Sales Order Query (SORQRY), with lines, dispatches and invoices (SorMaster, SorDetail)
  • Sales Analysis: reference workflow: the Sales Analysis Query / Sales History by customer and stock code, with gross profit (ArTrnDetail)

Purchasing

  • Purchase Orders: reference workflow: the Purchase Order Query (PORQRY), with lines and goods received (PorMasterHdr, PorMasterDetail, GrnDetails)

Inventory

  • Stock Codes: reference workflow: the Inventory Query (INVPEN): stock code, warehouse quantities and cost (InvMaster, InvWarehouse)
  • Inventory Movements: reference workflow: the Inventory Movements Query (InvMovements): receipts, job issues, sales, take-on and stock take adjustments
  • Inventory Valuation: reference workflow: the Inventory Valuation report (INVP25) at quarter-end dates, rebuilt from the movement ledger (InvMovements)

Manufacturing

  • Job Query: reference workflow: the WIP Job Query (WIPPEN): job header, material allocations, labour postings, lots consumed and serials produced (WipMaster, WipJobAllMat, WipLabJnl)
  • WIP Valuation: reference workflow: the WIP Valuation report (WIPPWV): open jobs with material, labour and overhead to date at the archive date (WipMaster)
  • Bill of Materials: reference workflow: the Bill of Materials Query (BOMPEN): structure and routing per parent part (BomStructure, BomOperations, BomWorkCentre)
  • Lot Traceability: reference workflow: the Lot Traceability Query (LOTPEN), searching down from a lot to jobs and serials (LotDetail, LotTransactions)
  • Serial Tracking: reference workflow: the Serial Tracking Query and the traceability search up from a serial to its job and component lots (InvSerialHead, InvSerialTrn, LotTransactions)

Cash Book

  • Cash Book: reference workflow: the Cash Book Query and Bank Reconciliation (CSHPEN) (ApBank, CshTransactions)

Assets

  • Asset Register: reference workflow: the Asset Query and Asset Register report (AssetMaster, AssetHistory)

Payroll

  • Employees: reference workflow: the Payroll Employee Query and employee master (PayEmployee, PayHistory)
  • Payroll History: reference workflow: Payroll History and the Payroll GL Distribution report by department and period, tied to the wages GL code (PayHistory, GenTransaction)

Source documents stay attached

Document types below illustrate the intended scope. Include source attachments and external repositories explicitly, and test retrieval and record linkage before decommissioning.

ArchiveHub keeps archived documents linked to their records: AR and AP invoices, purchase orders, jobs, and the customer, supplier, employee and asset masters. A supplier query about a payment or a quality question about a job leads straight to the original paperwork. You don't need to search a file server.

Beyond the reports

Confirm these capabilities, configuration requirements and limits during the demonstration and scope review; the report catalogue alone does not validate them.

  • Ad-hoc query builder over all SYSPRO tables, with native field descriptions and suggested joins (for example LotTransactions to WipMaster to SorDetail).
  • Retention rules and purge with approval, so records leave the archive on schedule and only after sign-off.
  • Legal hold to freeze lots, jobs, customers or periods involved in a recall, claim or audit.
  • Personal-data governance: agree the lawful retention, access and deletion requirements with the responsible privacy and records teams. Product features alone do not establish regulatory compliance.
  • Access controls: define and test permissions for the required companies, records and sensitive fields. Do not assume that system-level roles reproduce the original ERP permissions, particularly for payroll and HR data.
  • OData feeds to Excel, Power BI and SAP Analytics Cloud.

How the decommissioning project runs

  1. Extract. Every SYSPRO company is extracted table by table, keeping native keys and names.
  2. Validate. Row counts are compared per table. The trial balance from GenHistory must tie to SYSPRO's. AR, AP, inventory, WIP, GRN suspense, cash book, assets and payroll must tie to their GL control accounts by period, and a sample of lots and serials is traced end to end.
  3. Parallel read access. Finance, quality and operations use ArchiveHub while SYSPRO is still running, and confirm that the answers match.
  4. Retire after acceptance. Obtain documented sign-off for data reconciliation, document retrieval, user access, retention and legal holds, recovery and remaining integrations. Retire only the approved components; shared infrastructure may still be needed. End or reduce subscriptions, licences and support only where the contract permits. Budget for archive operation and any residual costs.

Traceability without the old server

A recall query five years from now should take minutes, not a project to revive an old server. Move your SYSPRO history into ArchiveHub and retire the system.

Questions about SYSPRO retirement

How should a SYSPRO traceability test be designed?

Choose representative lots or serials and follow the required receipts, production and shipment relationships. Verify documents and exceptions independently of ledger reconciliation.

Can a reconstructed valuation be described as a native table?

No. Label archive-derived snapshots and describe their source data, cut-off and calculation basis. Compare them with the agreed source reports before relying on them.

What does this ArchiveHub demonstration prove?

The screenshots illustrate how selected records can be presented using mock data. They do not prove production completeness, customer outcomes or parity with every SYSPRO report. Request a demonstration against your own approved scope and acceptance cases.

Related retirement resources

For the broader project approach, see Legacy application retirement planning. To evaluate how users will find transactions, follow relationships and retrieve documents, explore archived data reporting. These resources complement this SYSPRO-specific scope rather than replace source-system validation.

Evidence and further reading

The report catalogue and screenshots originate from an internal mock-data demonstration. They are not vendor certification or customer implementation evidence.

Use SYSPRO release documentation to locate the documentation for the installed release. This is a documentation entry point, not verification of every table or report mapping in this article.

Fixed-price SYSPRO retirement engagement

ArchiveHub offers a fixed-price engagement for SYSPRO retirement and historical data access, based on an agreed scope, deliverables and acceptance criteria. Request a scoped proposal covering your source systems, data, documents, reporting and validation requirements. The proposal should specify included services, exclusions, ongoing platform or hosting charges, and how scope changes will be handled.

Discuss your SYSPRO retirement requirements with ArchiveHub

SYSPRO is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by SYSPRO.