Cloud archive for Dynamics AX 2012, AX 2009 and AX 4.0. Parquet on S3 or Azure Blob, SQL query layer, REST APIs, DocuRef attachments, hot/warm/cold tiering, retention rules per legal entity (SOX 7yr, IRS 7yr, HGB 10yr, HMRC 6yr), full SOX evidence chain.
Keeping AX 2012 running for retention purposes after Fusion go-live costs six figures annually and creates a growing unpatched-vulnerability surface area. Archive once; decommission cleanly.
Customers retiring Dynamics AX after migrating to Fusion (or to D365 F&O, or after a divestiture or shutdown of an AX-running legal entity) face a retention problem: SOX requires 7 years of financial records, HMRC requires 6 years of VAT substantiation, German HGB requires 10 years of financial books and supporting documents, and sector overlays (PCI DSS, FDA, IFRS) impose additional minimums. The temptation is to keep AX running 'just in case auditors ask'. The cost is brutal: Microsoft Premium Support extended-licence on AX 2012 (through 2026), SQL Server Enterprise per-core licensing, server hardware or VM costs, OS licensing, AX application administration labour, security patching against a platform that is no longer receiving feature updates. Mid-market deployments routinely spend $180K–$420K annually on this 'just in case' posture.
Dynamics ax data archival inverts the equation. Syntra ETL extracts every byte that retention requires — financial transactions, subledger detail, master data, document attachments, Financial Dimension combinations — lands it as Parquet on cloud object storage (S3 or Azure Blob), and exposes it through a SQL query layer (Athena, Synapse, Snowflake) and REST APIs. The same archive that costs $4K–$18K annually answers every audit, every tax inquiry, every legacy lookup faster than the live AX system did. AOS decommissioned. SQL Server licence cancelled. X++ skills retired. 95%+ cost reduction starts the month after cutover.
And the archive is built for the next decade, not just the next audit. Hot tier for the first 12 months of active query, warm tier for years 2–3, cold tier (S3 Glacier or Azure Cool/Archive) for older partitions where access is rare. Retention rules per legal entity per data domain auto-expire records past retention with audit logging. Legal-hold overrides pause expiration on flagged records during litigation. The archive is a product, not a one-time data dump.
What makes the AX archive a proper enterprise archive rather than a forgotten Parquet dump on S3.
S3 or Azure Blob, partitioned by fiscal year and legal entity (DataAreaId). Columnar format means SQL queries scan only the columns they need — fast and cheap regardless of partition size.
AWS Athena, Azure Synapse Serverless, Snowflake or BigQuery exposes the archive as queryable tables. Anyone with SQL can query — no AX login, no AOS, no X++ skills.
Financial Dimension combinations decoded into readable (dim-name, dim-value) columns in the archive schema. No 3-table JOIN to know what cost-center a journal line posted to.
Documents preserved with original filenames, content-types, hash signatures, DocuRef cross-reference keys. Retrievable by REST API or direct link from the query layer.
Active query tier for recent partitions, warm for 12–36 months, cold (Glacier/Archive) for older partitions. Cost optimised for the full retention window.
Per-legal-entity, per-data-domain retention rules enforce SOX/HGB/HMRC/IRS/PCI minimums. Auto-expiry with audit logging. Legal hold pauses expiration during litigation.
From extracting the last byte of AX to a queryable, immutable cloud archive — and the AOS decommissioned.
Per-legal-entity retention rules defined (SOX 7yr US, HMRC 6yr UK, HGB 10yr DE, IRS 7yr tax, sector overlays). Data domains scoped (GL, AP/AR, inventory, sales, purchase, documents). Archive target selected (S3 + Athena or Azure Blob + Synapse).
Full historical extract from AX 2012/2009/4.0 via SQL Server direct plus AIF SOAP. All in-scope tables, all in-scope fiscal years, all legal entities, all DocuRef attachments. Output staged as Parquet plus original documents in object storage with hash signatures.
EDTs flattened to native SQL types in the archive schema. Financial Dimension combinations decoded into readable columns. Number Sequences preserved. Custom field overlays from CUS/USR layers preserved with origin annotation.
Athena/Synapse/Snowflake configured against the archive. SQL query catalog published with business-glossary descriptions per table and column. REST APIs exposed for document retrieval and structured record lookup. BI tool connectors validated.
Final reconciliation pack (AX TB vs archive query result per period per legal entity to the cent, document count and hash chain). Sign-off by finance, audit, tax, IT. AOS shut down, SQL Server licence cancelled, physical infrastructure decommissioned.
Archive operates as a managed service. Hot/warm/cold tiering automatic. Retention enforcement automatic. Legal hold managed through audit-facing console. Query usage monitored, costs tracked, quarterly compliance attestation issued.
The archive is not a forensic dump. It's a working compliance and operational tool with daily users.
Statutory tax audits (IRS, HMRC, Bundesfinanzbehörden, DGFiP) requesting VAT-registered vendor invoice detail, sales-tax-collected reports, cross-border transaction substantiation for periods that AX was the system of record.
SOX 404 IT-general-controls walkthroughs, financial-close substantiation, journal-line-to-original-document tracing for periods that fell under AX. One query returns the journal line plus every linked DocuRef attachment.
Post-cutover finance close questions — 'what was the cost-center allocation on this 2019 invoice?' — answered through SQL query against the archive in seconds, no AX login, no IT ticket, no AOS spin-up.
M&A diligence, contract dispute discovery, regulatory subpoena response. Legal hold engine flags affected records, pauses expiration, captures audit log of access for the duration of the hold.
Sales/support teams looking up historical orders for long-tenured customers, warranty claims against discontinued products, supplier-quality reviews referencing 5-year purchase history.
Divestiture or carve-out scenarios where the buyer needs N years of historical data for the acquired entity. Archive partition for that legal entity exported as a clean, signed package.
Dynamics ax data archival is the process of preserving historical AX data — GL transactions (LedgerJournalTrans), AP/AR subledger (VendInvoiceJour, CustInvoiceJour), inventory movements (InventTrans), sales/purchase orders, customer/vendor master, document attachments (DocuRef/DocuValue) — in a queryable, immutable cloud archive after the live AX system is decommissioned. Syntra ETL's AX archive lands data as Parquet on S3 or Azure Blob with hot/warm/cold tiering for cost control, a query layer (Athena/Synapse) for SQL access, REST APIs for application access, and an audit-grade retention engine enforcing SOX 7-year, IRS 7-year, German HGB 10-year, UK HMRC 6-year and sector-specific retention rules per legal entity.
Three reasons. First, cost: AOS server licensing, SQL Server Enterprise per-core licensing, OS licensing, hardware/VM/storage and the Microsoft Premium Support contract that extended support on AX 2012 through 2026 add up to six figures annually for a typical mid-market AX 2012 deployment. Dynamics ax data archival in cloud Parquet retires all of that. Second, skills: X++ developers and MorphX administrators are increasingly hard to hire as the platform ages. Third, audit risk: keeping a 2026-end-of-extended-support system running for retention purposes after the new Fusion ERP goes live creates an unpatched-vulnerability surface area that grows every quarter. Archive once; retire AX cleanly.
Everything required for SOX/statutory retention plus everything finance, audit and operations might ever need to look up. Financial: full LedgerJournalTrans by period/legal entity, General Journal Account Entries, AP subledger (VendInvoiceJour, VendTrans, settlements), AR subledger (CustInvoiceJour, CustTrans, settlements), trial balances per period per legal entity, Financial Dimension combinations decoded into readable tuples. Operational: SalesTable/SalesLine including closed sales history, PurchTable/PurchLine including closed purchase history, InventTable, InventTrans, InventSum, BOMs and production orders. Master: CustTable, VendTable, InventTable, employees, sites, warehouses, currencies, tax codes. Documents: DocuRef/DocuValue attachments with original file content and hash signatures. Customizations: AOT inventory and X++ object catalogue preserved as metadata for forensic reference.
By using SQL — not X++. The archive lands as Parquet on cloud object storage (S3 or Azure Blob) with a query layer (AWS Athena, Azure Synapse Serverless, Snowflake or BigQuery) exposing the data as queryable tables. Anyone who can write SQL can query the archive — no AX login, no AOS running, no MorphX expertise, no X++ knowledge. EDTs are flattened to native SQL types in the archive schema, Financial Dimension combinations are pre-decoded into readable (dim-name, dim-value) columns, and a query catalog documents every table and column with business-glossary descriptions. Finance, audit, tax and operations can self-serve through SQL clients or BI tools (Power BI, Tableau, Looker) for the full retention period.
Yes. Document attachments from DocuRef (the AX attachment reference table) paired with DocuValue (the actual document storage) are first-class citizens in the archive. Each document is preserved with its original filename, content-type, hash signature and the DocuRef cross-reference key intact. Documents land in cloud object storage indexed by the DocuRef key so they can be retrieved by API or by direct download link from the query layer. Signed time-stamped read-access logs are captured for every retrieval, satisfying SOX evidence-integrity and HGB/HMRC audit requirements. Multi-TB DocuValue archives are routine — the largest single tenants we have archived exceeded 18 TB of document content.
Retention rules are configurable per legal entity per data domain. Common patterns: US legal entities run SOX 7-year on financial records plus IRS 7-year on tax records; UK legal entities run HMRC 6-year on VAT records and Companies House 6-year on financial records; German legal entities run HGB 10-year on financial records and 6-year on operational; French legal entities run PCG 10-year. Sector overlays apply (PCI DSS for retail card data, FDA 21 CFR Part 11 for pharma manufacturing batch records if AX was running pharma workflows). The retention engine enforces immutability for the retention window (records cannot be modified or deleted), auto-expires records past retention with audit logging, and supports legal-hold overrides that pause expiration on flagged records during litigation.
Yes — and they do. The query layer exposes the AX archive as SQL tables that finance, audit, tax and operations query directly through SQL clients or BI tools. Common use cases: tax auditor asks for all VAT-registered vendor invoices in 2018 across the UK legal entity (5-second Athena query against the archive), finance asks for a year-over-year cost-center comparison for a discontinued product line (Power BI dashboard over the archive), internal audit asks for the full document attachment chain for a specific GL journal line during a SOX walkthrough (one API call returns the journal line plus every linked DocuRef document). No AX login needed. No AOS running. No X++ skills required.
Dramatically lower. A typical AX 2012 mid-market deployment costs $180K–$420K annually to operate (Microsoft Premium Support extended-licence, SQL Server Enterprise per-core, server hardware/VM/storage, application admin labour, security patching labour). The same data archived as Parquet on S3 with Athena query layer typically costs $4K–$18K annually depending on data volume and query frequency, with cold-tiered older partitions costing less still (S3 Glacier or Azure Cool/Archive tier). 95%+ savings is the norm, materialising in the first month after AX decommission and continuing for the full retention period.
Send us your AX version, legal-entity list, retention requirements per jurisdiction and an estimate of document attachment volume. We will return an archive scope, cost model (live AX vs archived) and timeline — typically within 5 working days. AOS retirement begins the day archive sign-off completes.