Query historical AX 2012, AX 2009 and AX 4.0 records years after AOS shutdown. SQL, REST, Parquet, browser viewer — finance, tax, audit, e-discovery, customer service self-serve. Full Financial Dimension context, original attachments, every read logged for SOX and HGB audit.
The data outlives the application. The SOX 7-year clock, the HGB 10-year clock and the IRS lookback period all keep ticking long after AX 2012 mainstream support has ended.
When the Dynamics AX environment moves to read-only or gets fully decommissioned, the operational use case ends but the access use case is just beginning. Finance still needs to defend prior-year balances to external auditors. Tax still needs to respond to HMRC and IRS information requests reaching back six or seven years. Internal audit still tests control evidence from the AX era. Legal e-discovery still pulls invoices, purchase orders and sales orders for litigation matters and contractual disputes. Customer service still answers 'why was I billed this amount in 2017?' calls. Vendor management still defends payment timing for SOX 404 testing.
Doing that against a live AX 2012 instance is expensive and risky — extended Microsoft support runs out in 2026, the Windows Server estate falls out of support, SQL Server CU drift introduces incompatibilities, and the in-house pool of AX/X++/MorphX skill shrinks every year as people retire or rotate. The right answer is to lift the historical dataset off AX, land it in cheap object storage as columnar Parquet, expose it through SQL/REST/viewer interfaces consumers already know, and let the AX infrastructure go.
That is what Syntra ETL's dynamics ax legacy data access tier delivers. The same extractors used for migration (SQL Server direct, AIF SOAP, DocuRef/DocuValue attachments, Financial Dimension catalogue) populate the archive with the full historical record, signed and indexed. Consumers get four query paths matched to their skill level and use case. SOX, HGB, HMRC and IRS audit evidence is built in.
The same hash-signed Parquet archive serves every consumer through the right query path for their skill level.
Athena, BigQuery, Snowflake, Trino or Spark against tables mirroring the AX schema — LedgerJournalTrans, CustTable, VendTable, SalesTable, PurchTable, InventTrans. Finance writes the SQL they used to write against the AX database.
Programmatic access from case management, GRC and e-discovery platforms. Search by vendor, customer, voucher, invoice number, date range, attachment hash. Returns JSON with full Financial Dimension context.
Non-technical users — customer service reps, AP clerks, vendor management — get a search interface with vendor/customer/invoice/voucher lookup, attachment download, RBAC-scoped per legal entity.
Columnar files in S3, Azure Blob or GCS — for data scientists, ML pipelines, bulk regulatory submissions. Hash-signed manifests prove integrity for SOX and HGB.
PDF/Excel outputs from SSRS, Management Reporter and MorphX captured at decommissioning, indexed by date/entity/report-name, searchable in the viewer.
DocuRef/DocuValue file content preserved with original file names and content hashes. Bound to source records so audit trails resolve from GL → AX journal → invoice → PDF scan.
From live AX to a queryable archive in 8–12 weeks. Often run in parallel with the Fusion migration.
Per-legal-entity retention windows mapped (SOX 7yr, HGB 10yr, HMRC 6yr, IRS 7yr, jurisdiction-specific extensions). Data domains classified: financial transactions, master data, attachments, Number Sequences, Financial Dimensions, persisted reports. RBAC role map drafted.
SQL Server direct extraction of LedgerJournalTrans, CustTrans, VendTrans, InventTrans, SalesTable, PurchTable, CustTable, VendTable, InventTable across all in-scope fiscal years. AIF SOAP extraction where document-class logic needs preserving. AOT metadata, EDT catalogue and Financial Dimension catalogue extracted alongside.
DocuRef/DocuValue document attachments extracted with file content and hashed. SSRS report definitions and persisted historical runs extracted from ReportServer. Management Reporter row/column/tree definitions and historical statements extracted. MorphX legacy report metadata extracted from AOT.
Every record hashed with stable schema-aware hash. Manifests signed and timestamped. Indexes built for search (vendor, customer, voucher, invoice, date range, dimension combination, attachment hash). Parquet partitioned by fiscal year and legal entity for query performance.
SQL engine (Athena/BigQuery/Snowflake/Trino) pointed at the Parquet dataset. REST API deployed with auth. Browser historical viewer deployed. RBAC roles wired to identity provider (Okta, Entra ID, Ping). Read-logging streamed to append-only audit log.
Sample queries from finance, audit, tax, customer service rehearsed against the archive. Reconciliation pack vs live AX. Sign-off from finance, internal audit, IT security. AX moves to read-only or full decommission per the decommissioning runbook. Dynamics ax legacy data access becomes the system of record for historical inquiry.
No bespoke archive — a productised, governed archive layer refined across dozens of AX environments.
Tables named and shaped to mirror AX — LedgerJournalTrans, CustTable, VendTable, SalesTable, PurchTable — so analyst muscle memory carries across from live AX to the archive.
DimensionAttribute and DimensionAttributeValueCombination preserved alongside transactions so analytical splits stay queryable years later.
Active sequence definitions with scope, format mask and statutory significance preserved for documentary evidence of issued invoice numbers.
CustTable and VendTable expanded to party + site shape so customer service and vendor management lookups work intuitively.
DocuRef/DocuValue → source record → GL → Fusion — auditable end-to-end at any level.
Every query logged with user, timestamp, query text, rows returned. Quarterly access-review reports auto-generated for SOX 404.
Dynamics ax legacy data access is the ability for finance, tax, internal audit, external audit, legal e-discovery, customer service and regulator-facing teams to query historical AX 2012, AX 2009 or AX 4.0 records after the live AX environment has been retired or moved to read-only archive mode. Once AOS is shut down, MorphX is gone, SSRS reports stop running, and ad-hoc Management Reporter queries against the AX SQL Server are no longer possible — but you still need to answer 'show me every invoice the German entity issued to ACME in fiscal 2019' for SOX, HMRC, HGB or IRS inquiries for years after cutover. Syntra ETL's dynamics ax legacy data access layer exposes the full historical AX dataset (LedgerJournalTrans, VendInvoiceJour, CustInvoiceJour, SalesTable, PurchTable, InventTrans, plus original document attachments from DocuRef/DocuValue) through SQL, REST and Parquet endpoints so the right consumers can self-serve without the live AX environment.
Read-only AX still requires AOS, the SQL Server licence, the Windows Server estate, and the in-house AX skills to navigate MorphX, run SSRS reports and decode AOT artefacts. It is expensive (mid-six-figures annually for a typical 2-AOS production setup) and fragile (Windows Server patching, SQL Server CU drift, lapsed AX skills as people retire). Dynamics ax legacy data access via Syntra replaces all of that with object storage (S3, Azure Blob or GCS), columnar Parquet files, a SQL query endpoint (Athena, BigQuery, Snowflake or Trino against the same Parquet), a REST search API, and a browser-based historical record viewer. No AOS, no SQL Server licence, no MorphX. 95%+ cost reduction with stronger audit posture because every read is logged.
Four interfaces, all reading the same underlying Parquet dataset. (1) SQL via Athena, BigQuery, Snowflake, Trino or Spark — finance and audit can write the same kind of ad-hoc SQL they used against the AX database, against tables named CustTable, VendTable, LedgerJournalTrans etc. mirroring the AX schema. (2) REST API — programmatic access for integration with case management, GRC and e-discovery platforms. (3) Browser historical viewer — non-technical users (customer service reps, AP clerks responding to vendor queries) get a search interface with vendor/customer/invoice/voucher lookup and attachment download. (4) Parquet files directly — for data scientists, ML and bulk extracts. Every access path is governed by RBAC and every read is logged for SOX, HGB and HMRC audit evidence.
Yes — that traceability is the whole point. Syntra ETL preserves the audit chain end-to-end: a Fusion GL balance → Fusion GL journal line → migration source reference → original AX LedgerJournalTrans record → original AX subledger document (VendInvoiceJour, CustInvoiceJour, SalesTable, PurchTable) → original attachment (PDF invoice scan, supplier confirmation, dispatch note) from DocuRef/DocuValue, with cryptographic hash signatures at every hop and timestamps. External auditors (Big Four, statutory auditors in EU jurisdictions, internal audit, IRS/HMRC inspectors) can follow the trail from a current-year Fusion balance back to a 2014 AX-era source document without anyone reaching for the original AOS instance.
Retention windows depend on jurisdiction and record type, but the typical envelope is 7–10 years for financial records and longer for specific employment, environmental, product safety and contract data. SOX requires 7 years for material financial records. IRS and HMRC require 6–7 years (HMRC 6 years plus current). German HGB requires 10 years for invoices, books and balance sheets. French PCG mandates 10 years. Italian and Spanish frameworks similarly require 10 years for primary accounting documents. Healthcare-adjacent and contract records can extend to 15–25 years depending on jurisdiction. Syntra ETL's dynamics ax legacy data access is configured per legal entity to enforce the longest applicable retention with auto-expiry workflows that meet each statutory minimum without retaining longer than legally permitted (GDPR data minimisation).
Yes. The Parquet-resident historical dataset preserves Financial Dimension combinations exactly as they were posted in AX — DimensionAttribute, DimensionAttributeValueCombination, default account rules — so analytical splits that depended on dimension combinations remain queryable. A finance analyst can write SQL against the archive that says 'sum LedgerJournalTrans.AmountMST where Period = 201912 and Dimension.CostCenter = CC100 and Dimension.Department = DEPT_FINANCE' exactly as they would have done against live AX. The dimension metadata catalogue ships with the archive so dimension IDs resolve to dimension names without out-of-band lookup.
Two-track preservation. (1) Historical report runs already produced and persisted (PDF, Excel, fixed-format outputs from Management Reporter financial statements, SSRS scheduled reports, year-end audit packs) are extracted from the SSRS ReportServer database and Management Reporter store, hash-signed, indexed by date/legal-entity/report-name and made searchable in the historical viewer. (2) The report definitions themselves (RDL files from SSRS, MR row/column/tree definitions, MorphX report metadata from AOT) are archived as metadata for reference but not re-executable — the original SSRS/MR runtime is no longer available. New analytical questions go via SQL/REST against the archived raw data, not by re-running old report definitions.
Defense-in-depth. (1) RBAC: roles defined per legal entity and per data domain (finance reads everything, customer service reads CustTable+CustTrans+attachments only, etc.), enforced at the SQL and REST layer. (2) Server-side encryption at rest (KMS/Azure Key Vault) and TLS in transit. (3) Every read logged with user, query text, rows returned, timestamp — replicated to an append-only audit log for SOX evidence. (4) GDPR: right-to-erasure workflows handle personal-data deletion from the archive with cryptographic proof of deletion, while preserving statutory financial records (HGB, HMRC) per the lawful-basis exemption. (5) Quarterly access-review reports for SOX 404 testing. The dynamics ax legacy data access tier passes external SOC 2 / ISO 27001 audits as a standard compliance posture.
Book a 30-minute discovery call. We will walk through your AX version, retention obligations by jurisdiction, attachment volume and audit-trail requirements — and give you a concrete archive design and timeline. Get the data off AX before extended support ends in 2026.