Retiring Sage X3 means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise folder and company context, lot genealogy and quality evidence. 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 Sage X3 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.

An X3 environment kept "only for inquiries" still brings its whole stack with it:

  • The technology stack. Sage X3 runs on SQL Server or Oracle, with the Syracuse web server and its supporting components. Every one of them has to stay on a supported, patched and mutually compatible version.
  • Licences and maintenance. Annual maintenance or subscription fees, often for a full user count, just to keep reading history.
  • Upgrades you cannot skip. Operating system and database end-of-support dates do not care that the folder is read-only, and each forced move means a technical project on a system nobody is improving.
  • Specialist knowledge. Navigating X3's functions and folders, and knowing which inquiry answers which question, is a skill that leaves with the people who used it every day.
  • Security and audit access. Supplier bank details, customer data and payroll history sit on a system that still needs users, roles and passwords maintained for occasional auditors.

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 Sage X3

ArchiveHub archives Sage X3's own tables under their native names. Fields keep their X3 names with descriptions, so the vocabulary of X3 consultants and power users still works in the ad-hoc query builder.

Representative tables in the archive:

  • Financials: GACCENTRY and GACCENTRYD journal entries and lines, GACCENTRYA analytical lines, and GACCDUDATE open items. Balances are in BALANCE, budgets in BUD, and the structure tables behind them are GACCOUNT, GCOA, GLED, GJOURNAL, GTYPACCENT, CACCE and GDIE dimensions, FISCALYEAR and PERIOD.
  • Cash and bank: PAYMENTH and PAYMENTD payments and receipts, BANREC bank reconciliation statements, RELBANK statement lines and the BANK accounts.
  • Business partners: BPARTNER, BPCUSTOMER, BPSUPPLIER, BPADDRESS and BPCARRIER.
  • Sales: SORDER / SORDERP / SORDERQ, SDELIVERY / SDELIVERYD, and SINVOICE / SINVOICED / SINVOICEV.
  • Purchasing: PORDER / PORDERP / PORDERQ, PRECEIPT / PRECEIPTD with internal and supplier lots, and PINVOICE / PINVOICED.
  • Stock and traceability: STOCK, STOLOT and STOLOTFCY, the STOJOU stock journal, STOTRK traceability, and STOTRKWRK with every lot descended from a selected lot. Quality control is in STOQLYH / STOQLYD; any additional technical-sheet results require source mapping validation.
  • Manufacturing: BOM / BOMD, ITMCOST, MFGHEAD / MFGITM / MFGMAT / MFGOPE work orders, and MFGHEADTRK / MFGITMTRK / MFGMATTRK production tracking.
  • Products and sites: ITMMASTER, ITMFACILIT, ITMMVT, ITMBPS, ITMCATEG, FACILITY, WAREHOUSE and COMPANY.
  • Fixed assets: FXDASSETS, DEPREC, FXDMVT and FASFAM.
  • Payroll: HISTOPAYE payroll history by employee, period and heading, RUBRIQUE payroll headings, and EMPLOID and EMPLOCTR for civil status and contracts.
  • Audit and tax: AUDITH / AUDITL audit trail, SVCRVAT document tax, and TABVAT / TABRATVAT tax codes and rates.

Explore the demonstration

Journal Entries list in ArchiveHub Journal Entries: posted GACCENTRY documents by company, journal, type and date, as in GESGAS. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Journal Entries detail page in ArchiveHub Journal Entries detail: one entry with its GACCENTRYD lines, accounts and amounts. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Bank Reconciliation list in ArchiveHub Bank Reconciliation: BANREC statements by bank account, with statement lines from RELBANK. 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.

Finance

  • Journal Entries: reference workflow: Financials > Journal entries, GESGAS (GACCENTRY / GACCENTRYD).
  • Trial Balance: reference workflow: Financials > Inquiries > Account balances, CONSBAL, and the trial balance report (BALANCE).
  • Budget vs Actual: reference workflow: Financials > Budgets > Budget inquiry (BUD against BALANCE).
  • Tax Register: reference workflow: the tax journal by document behind the VAT return and sales tax reports (SVCRVAT).
  • Fixed Assets: reference workflow: Fixed assets > Assets, GESFAS (FXDASSETS / DEPREC / FXDMVT).
  • Subledger to GL Reconciliation: reference workflow: control-account justification (Justification of balances): AR, AP, stock, WIP, GRNI, assets, bank and payroll by department against the general ledger.

Cash and bank

  • Bank Reconciliation: reference workflow: A/P-A/R accounting > Bank reconciliation statement (BANREC), with statement lines (RELBANK).
  • Payments and Receipts: reference workflow: A/P-A/R accounting > Payments > Payment entry, GESPAY (PAYMENTH / PAYMENTD).

Receivables and Payables

  • Customer Aged Balance: reference workflow: A/P-A/R accounting > Inquiries > Customer aged bal. to date (CONSBAH) and the aged balance report (BALAGE), at the archive cut-off.
  • Supplier Aged Balance: reference workflow: A/P-A/R accounting > Inquiries > Supplier aged bal. to date (CONSBAHF) and the aged balance report (BALAGE), at the archive cut-off.

Sales

  • Sales Orders: reference workflow: Sales > Orders > Orders, GESSOH (SORDER / SORDERP / SORDERQ).
  • Deliveries: reference workflow: Sales > Deliveries > Deliveries, GESSDH (SDELIVERY / SDELIVERYD), with the lots shipped.
  • Sales Invoices: reference workflow: Sales > Invoices > Invoices, GESSIH (SINVOICE / SINVOICED / SINVOICEV).

Purchasing

  • Purchase Orders: reference workflow: Purchasing > Orders > Orders, GESPOH (PORDER / PORDERP / PORDERQ).
  • Purchase Receipts: reference workflow: Purchasing > Receipts > Receipts, GESPTH (PRECEIPT / PRECEIPTD), with internal and supplier lots.
  • Purchase Invoices: reference workflow: Purchasing > Invoices > Invoices, GESPIH (PINVOICE / PINVOICED).

Stock

  • Stock by Lot: reference workflow: Stock > Inquiries > Stock by lot, CONSSTO (STOCK / STOLOT / STOLOTFCY), at the archive cut-off.
  • Stock Transactions: reference workflow: Stock > Inquiries > Movements > Stock transactions, CONSSMV (STOJOU).

Traceability

  • Lot Traceability: reference workflow: Stock > Inquiries > Movements > Traceability, CONSSTK (STOLOT / STOTRK / STOTRKWRK), ascending and descending.
  • Recall Exposure: reference workflow: the descending Traceability inquiry (CONSSTK) down to customers: for an ingredient lot, every finished lot shipped and who received it (STOTRKWRK, SDELIVERYD).
  • Lot Expiry Monitor: reference workflow: Stock > Inquiries > Expiry of lots, with use-by and expiration dates of stock on hand (STOCK / STOLOT), at the archive cut-off.
  • Quality Control: reference workflow: Stock > Quality control > Analysis requests (GESSQH / STOQLYH / STOQLYD), with technical-sheet results and quality documents where their source and meaning have been validated.

Manufacturing

  • Work Orders: reference workflow: Manufacturing > Planning > Work orders, GESMFG (MFGHEAD / MFGITM / MFGMAT / MFGOPE).
  • Production Tracking: reference workflow: Manufacturing > Inquiries > Productions, CONSMKI (MFGITMTRK / MFGHEADTRK).
  • Formulas and BOMs: reference workflow: Common data > BOMs > Production BOMs, GESBOM (BOM / BOMD), with cost rollup (ITMCOST).
  • Yield and Cost Variance: reference workflow: Manufacturing > WIP costing > WO analysis (MFGANL): actual against standard cost and process yield for closed work orders.

Master data

  • Customers: reference workflow: Common data > BPs > Customers (GESBPC).
  • Suppliers: reference workflow: Common data > BPs > Suppliers (GESBPS).
  • Products: reference workflow: Common data > Products > Products (GESITM), with product-site records (GESITF).

HR and payroll

  • Payroll Journal: reference workflow: the Sage X3 People payroll journals (LIVREPAYE) from payroll history (HISTOPAYE), with civil status and contract (EMPLOID, EMPLOCTR).

Audit

  • Audit Trail: reference workflow: Usage > Audit > Audit inquiry (AUDITH / AUDITL): changes to customers, suppliers, products, accounts and users.

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.

In ArchiveHub, archived documents stay attached to the X3 records they belong to: customer invoices and customer credit notes, supplier invoices, supplier approval documents, batch records for production lots, certificates of analysis, fixed assets and employee files. When a quality investigation opens, the batch record and the certificate of analysis sit next to the lot genealogy they document.

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 the configured archived tables, with X3 field descriptions and suggested joins, for example SDELIVERYD to STOLOT to STOTRK.
  • Retention rules and purge with approval for each kind of record.
  • Legal hold to freeze records involved in a recall, claim or tax 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 the X3 tables from SQL Server or Oracle, folder by folder, keeping native names and descriptions.
  2. Validate. Row counts are checked per table. Balances must tie out: BALANCE has to agree with the trial balance X3 printed, and the customer, supplier, stock, WIP, GRNI, asset, bank and payroll control accounts must justify against the general ledger.
  3. Parallel read access. Finance, quality, supply chain and HR users answer their usual questions in ArchiveHub while X3 is still available.
  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.

The lot history outlives the system

Traceability questions can come years after a lot was shipped. With ArchiveHub, the answer is still there in X3's own terms, without paying to keep X3 running.

Questions about Sage X3 retirement

What should accompany an X3 lot-history record?

Include the agreed movements, production relationships and quality documents, with their source identifiers. Confirm whether COA means a certificate of analysis in that repository rather than assuming the abbreviation.

How should folder-specific differences be handled?

Inventory releases, folders, legislation settings and customisations before mapping. Test balances and lot workflows for the selected scope; a demonstration from one configuration does not validate another.

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 Sage X3 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 Sage X3-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.

For version-specific mappings, obtain the applicable vendor documentation and compare it with the installed system. No independently verified, release-specific mapping reference is supplied with this draft.

Fixed-price Sage X3 retirement engagement

ArchiveHub offers a fixed-price engagement for Sage X3 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 Sage X3 retirement requirements with ArchiveHub

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