Adaptors / Dynamics AX

Dynamics AX adaptor

Legacy source adaptor for Microsoft Dynamics AX (Axapta). Extraction patterns, mapping templates, and deterministic validators for migration to modern platforms.

Book a 15-min triage call Request adaptor details

The Dynamics AX adaptor provides proven extraction patterns for legacy AX estates, covering standard and customised tables. It handles the complexity of AX's data model, including financial dimensions, inventory dimensions, and heavily customised modules, producing governed outputs ready for deterministic transformation and loading into modern target platforms.

What it accelerates

Proven AX extraction patterns: pre-built queries covering standard AX tables and common customisation patterns
Financial dimension handling: templates for extracting and transforming AX's complex dimension framework
Inventory dimension mapping: extraction patterns for AX's inventory dimension groups and tracking dimensions
Customisation awareness: base templates extended during the Decide phase to handle client-specific table modifications
Reconciliation at source: validators confirm extraction completeness against AX source totals before transformation begins

How it works with elfware

The controlled non-determinism model applied to Dynamics AX:

1Human decisions: consultants map the AX estate, identify customisations, define scope, and determine which data domains migrate
2AI-assisted optioning: surfaces common AX-to-target mapping patterns and highlights customisations that need human judgement
3Governed specs: locked decisions cover extraction queries, transformation rules, and target mappings
4Deterministic generation: code-printing produces extraction scripts, transformation logic, and load files from the governed spec
5Deterministic validators: source-side checks confirm extraction completeness; target-side checks confirm transformation accuracy
6Rehearsal and cutover: proven rehearsal chain provides confidence in timing and data accuracy

AI boundary: AI never processes customer data; it supports mapping and delivery configuration only. When AI assists with code generation, the output is reviewed, QA'd, and verified in test runs before deployment to any system.

Source vs target usage

As a legacy source

Extraction from Dynamics AX estates for migration to D365, Oracle Retail, or other modern platforms. Covers standard tables and common customisation patterns.

Product master: InventTable, EcoResProduct, product dimensions, bar codes, Inventory Management, Product Information Management, Accounts Receivable, Accounts Payable, Procurement and Sourcing, Warehouse Management
Customer/supplier master: CustTable, VendTable, addresses, contacts, payment terms
Financial data: LedgerJournalTable, subledger entries, financial dimensions, budgets
Inventory: InventTrans, InventSum, warehousing, batch/serial tracking
Sales and purchasing: SalesTable/SalesLine, PurchTable/PurchLine, open orders, history
Reference data: units, currencies, number sequences, organisation hierarchies, location code mapping required

As a target

Dynamics AX is not supported as a target. This is a source-only adaptor for migrating data out of legacy AX estates to modern platforms such as D365 F&O or Oracle Retail.

Typical artefacts delivered

Extraction templates

Pre-built SQL extraction queries for standard AX tables with handling for common customisation patterns and financial dimensions.

Mapping templates

Source-to-target mapping documents translating AX data structures to target platform entities, with transformation rules and defaults.

Deterministic validators

Source-side validators confirm extraction completeness; transformation validators check data accuracy before loading.

Reconciliation / evidence pack

Row counts, value totals, and cross-reference checks reconciling AX source data against transformed outputs and target loads.

Cutover rehearsal playbook

Runbook covering AX extraction timing, transformation windows, and load sequencing for rehearsal and cutover execution.

Interfaces and data domains

Domain	Typical entities	Cadence	Notes
Products	InventTable, EcoResProduct, dimensions, bar codes, categories	Full + delta	InventTableModule join required; DISTINCT applied to resolve dimension combinations
Customers	CustTable, addresses, contacts, payment terms, credit limits	Full + delta	Address enrichment required; store customers extracted separately
Suppliers / vendors	VendTable, addresses, contacts, payment terms, agreements	Full + delta	Bank accounts and opening balances extracted separately
Financials	LedgerJournalTable, subledger, dimensions, budgets	Full + history	Dimension framework mapping
Inventory	InventTrans, InventSum, batch/serial, warehousing	Snapshot + delta	Dimension groups critical
Sales	SalesTable, SalesLine, returns, delivery schedules	Open + history	Open orders only; DocumentState filter required
Purchasing	PurchTable, PurchLine, receipts, invoices	Open + history	Open status filter; location code mapping required
Reference data	Units, currencies, number sequences, org hierarchies	Full	Foundation dependency

Common risks and how we mitigate them

Heavy customisation of standard tables

Base extraction templates are extended during the Decide phase to cover custom fields, tables, and relationships specific to each AX estate.

Financial dimension complexity

Adaptor includes dedicated dimension extraction and transformation patterns that map AX's dimension framework to target platform structures.

Inventory dimension group variations

Templates handle different inventory dimension group configurations (batch, serial, site, warehouse, location) with validators to confirm completeness.

Data volume and extraction performance

Extraction queries are optimised for large AX databases with partitioned execution, checkpointing, and parallel extraction where possible.

Missing or incomplete documentation

Data profiling and automated discovery tools identify customisations and data quality issues before extraction templates are finalised.

Cross-company data in shared AX instances

Extraction templates include company filtering and validators confirm data isolation across legal entities.

Frequently asked questions

What do you need to start?

Access to the AX database (or representative data extracts), documentation of customisations, and clarity on the target platform. We can work from data dictionaries and sample files initially.

How do validators reduce risk?

Validators check every extracted record against source totals and cross-references, then validate the transformed output against target constraints before loading. Objective pass/fail evidence is produced at every rehearsal.

Do you support history builds?

Yes. The AX adaptor supports progressive history builds for transactional data including sales orders, purchase orders, inventory transactions, and financial journals.

How do adaptors evolve over time?

Each AX migration engagement adds new extraction patterns, customisation handling, and validators. These are folded back into the reusable library for future programmes.

What about AX customisations?

AX estates are frequently heavily customised. The adaptor provides a base extraction layer for standard tables, and we extend it during the Decide phase to cover client-specific customisations.

Which AX versions do you support?

The adaptor covers Dynamics AX 2009, AX 2012, and AX 2012 R2/R3 estates. Earlier Axapta versions (3.0, 4.0) are supported with additional mapping effort.

Ready to de-risk your migration?

Book a 15-min triage call Get your migration risk score

Same-day response (Mon-Fri)