Retiring Dynamics AX 2012 means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise company-specific postings, financial dimensions and inventory context. 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 a read-only AX 2012 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 AX 2012 environment is not a single server. Keeping it reachable means keeping all of this alive:

  • The AOS, the SQL Server database and SSRS, all on Windows Server and SQL Server versions that are ageing out of support alongside AX 2012 itself.
  • The AX client on remote desktop servers, with its own configuration, because the data is only intelligible through it.
  • X++ and AX know-how. Getting a historical inventory value or a production variance out of AX often means a developer, not a report.
  • Security patching and access reviews for a system holding vendor bank accounts, worker data and pay statements.
  • Licence and support contracts for software that nobody is allowed to post in.

Assess each cost separately: shutting down AOS does not automatically end shared infrastructure costs or contractual commitments.

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 Dynamics AX 2012

AX 2012 is unusually normalised, and ArchiveHub keeps it that way. The general ledger is held as GeneralJournalEntry (one header per posted voucher), GeneralJournalAccountEntry (one line per ledger account) and SubledgerVoucherGeneralJournalEntry (the link back to the subledger voucher). Ledger dimension combinations come from DimensionAttributeValueCombination, the chart of accounts from MainAccount, and the fiscal calendar from FiscalCalendarYear and FiscalCalendarPeriod. Posted journal batches sit in LedgerJournalTable and LedgerJournalTrans.

Where the AX 2012 upgrade renamed the old AX 2009 ledger table to DEL_LedgerTrans, ArchiveHub keeps it too, so ledger history that predates AX 2012 still has a home.

The subledgers keep their transaction and settlement structure: CustTrans and CustSettlement, VendTrans and VendSettlement, with CustTable, VendTable and DirPartyTable for the global address book. Inventory is held as InventTrans, InventTransOrigin, InventDim, InventSum and InventBatch. Production keeps ProdTable, ProdBOM, ProdRoute, ProdCalcTrans and ProdTableJour. Procurement and sales keep their posted journals (VendPackingSlipJour, VendInvoiceJour, CustPackingSlipJour, CustInvoiceJour). Fixed assets come with AssetTable, AssetBook and AssetTrans, payroll with PayrollPayStatement and its lines, HR with HcmWorker and HcmEmployment, and the system TransactionLog shows who posted what and when.

AX stores enum values as integers. ArchiveHub carries the enum labels (from SRSAnalysisEnums) with the data, so a status reads "Invoiced" rather than "3". In the demonstrated scope, each field keeps its AX name and description, so DataAreaId, Voucher and ItemId still mean what they meant in ad-hoc queries.

Explore the demonstration

Posted Journals list in ArchiveHub Posted Journals: AX 2012 general and payment journal batches, filterable by company, journal name and date. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Posted journal detail page in ArchiveHub Posted Journals detail: a single archived AX 2012 journal batch opened from the list. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Customer Aging in ArchiveHub Customer Aging: open customer transactions aged by due date at the archive cut-off. 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

  • Posted Journals: reference workflow: General ledger > Journals, General journal and payment journal batches (LedgerJournalTable)
  • Voucher Transactions: reference workflow: General ledger > Inquiries > Voucher transactions (GeneralJournalEntry, GeneralJournalAccountEntry)
  • Trial Balance: reference workflow: General ledger > Reports > Trial balance, by company and fiscal period
  • Main Accounts: reference workflow: General ledger > Common > Main accounts (chart of accounts)
  • Budget vs Actual: reference workflow: Budgeting > Reports, Actual vs. budget by main account and department (BudgetTransactionLine)
  • Ledger Reconciliation: reference workflow: the reconciliation of ledger balances to the subledgers at fiscal year end, including the inventory-to-ledger reconciliation
  • Ledger History FY2020: reference workflow: the ledger transactions kept from AX 2009 (LedgerTrans, renamed DEL_LedgerTrans at the AX 2012 upgrade)
  • Sales Tax Settlements: reference workflow: General ledger > Periodic, Sales tax payments and Posted sales tax (TaxTrans, TaxReportVoucher)
  • Transaction Log: reference workflow: System administration > Inquiries > Database > Transaction log (TransactionLog), including AOS batch jobs

Accounts receivable

  • Customers: reference workflow: Accounts receivable > Common > All customers (CustTable, DirPartyTable)
  • Customer Transactions: reference workflow: Accounts receivable > Inquiries, Customer transactions and settlement history (CustTrans, CustSettlement)
  • Customer Aging: reference workflow: the Customer aging report (CustAgingReport) at the archive cut-off, by due date

Accounts payable

  • Vendors: reference workflow: Accounts payable > Common > All vendors (VendTable, DirPartyTable)
  • Vendor Transactions: reference workflow: Accounts payable > Inquiries, Vendor transactions and settlement history (VendTrans, VendSettlement)
  • Vendor Aging: reference workflow: the Vendor aging report at the archive cut-off, by due date

Cash and bank

  • Bank Statements: reference workflow: Cash and bank management, bank account statements and reconciled bank transactions (BankAccountStatement, BankAccountTrans)

Inventory

  • Released Products: reference workflow: Product information management, Released products with cost price versions (InventTable, EcoResProduct, InventItemPrice)
  • Inventory Transactions: reference workflow: Inventory and warehouse management > Inquiries > Transactions with receipt and issue status (InventTrans, InventTransOrigin)
  • On-hand Inventory: reference workflow: the On-hand inquiry by site, warehouse and batch at the cut-off (InventSum, InventDim)
  • Inventory Journals: reference workflow: posted Counting and Profit/loss journals (InventJournalTable, InventJournalTrans)
  • Inventory Value: reference workflow: the Cost accounting Inventory value report by item at each fiscal year end (InventValueReport, per-item stock ledger)

Production

  • Production Orders: reference workflow: Production control > All production orders with production BOM, route, journals and price calculation (ProdTable, ProdBOM, ProdRoute, ProdCalcTrans)
  • Production Variances: reference workflow: production variances on ended orders, estimated vs realized cost (ProdCalcTrans, ProdTableJour)
  • Bills of Materials: reference workflow: Bills of materials and routes, BOM versions, lines and operations (BOMTable, BOMVersion, BOM, RouteOpr)
  • Batch Trace: reference workflow: Dimension tracking and Trace inventory dimensions by batch, covering output, shipments and consumption (InventBatch, InventDim, InventTrans)

Procurement

  • Purchase Orders: reference workflow: Procurement and sourcing > All purchase orders with product receipts and invoices (PurchTable, VendPackingSlipJour, VendInvoiceJour)

Sales

  • Sales Orders: reference workflow: Sales and marketing > All sales orders with packing slip and invoice journals (SalesTable, CustPackingSlipJour, CustInvoiceJour)

Projects

  • Capital Projects: reference workflow: Project management and accounting > All projects, investment projects with posted transactions (ProjTable, ProjCostTrans, ProjEmplTrans)

Fixed assets

  • Fixed Assets: reference workflow: Fixed assets > Common > Fixed assets and value models with transactions (AssetTable, AssetBook, AssetTrans)

Human resources

  • Workers: reference workflow: Human resources > Workers, employment and position assignments (HcmWorker, HcmEmployment, HcmPositionWorkerAssignment)
  • Pay Statements: reference workflow: Payroll pay statements by worker and department (PayrollPayStatement, PayrollPayStatementLine)

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.

Archived documents remain linked to their AX records. Vendor invoices, purchase orders and customer invoices carry their PDFs; production orders keep their travelers and batches their certificates; tax returns, projects, fixed assets, customers, vendors and workers keep their files. A batch recall question can be answered with the trace and the certificate side by side.

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 AX table, with AX field descriptions and suggested joins (for example InventTrans to InventDim on InventDimId).
  • Retention rules and purge with approval, applied per table, so pay statements and worker data can expire while the ledger stays.
  • Legal hold for product liability or tax disputes.
  • 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 into Excel, Power BI and SAP Analytics Cloud, to set AX history beside Dynamics 365 figures.

How an AX 2012 decommissioning runs

  1. Extract all legal entities (DataAreaId) from the AX database with table and field metadata and enum labels.
  2. Validate. Row counts per table, then balances that tie out: CustTrans and VendTrans to their summary accounts, inventory value to the inventory ledger accounts, asset books to the GL and the trial balance to the GeneralJournalAccountEntry totals for each fiscal period.
  3. Parallel read access. Finance, cost accounting and quality users run their usual inquiries in ArchiveHub while AX is still up.
  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.

Questions about Dynamics AX 2012 retirement

Should every AX table be treated as company-specific?

No. Identify shared versus company-specific data in the selected release and configuration. Preserve the keys required to interpret transactions and test company-level access explicitly.

What should inventory reporting acceptance include?

Agree valuation dates, costing scope and the movements required for each report. Compare selected inventory and ledger outputs and record adjustments or differences before sign-off.

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 Dynamics AX 2012 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 Dynamics AX 2012-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 Microsoft Dynamics 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 Dynamics AX 2012 retirement engagement

ArchiveHub offers a fixed-price engagement for Dynamics AX 2012 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 Dynamics AX 2012 retirement requirements with ArchiveHub

Microsoft Dynamics AX is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Microsoft.