Dynamics AX Migration Assessment — Evidence-Driven Readiness

A dynamics ax migration assessment is a structured 2-4 week engagement that inventories your AX 2012, AX 2009 or AX 4.0 estate — every legal entity, every active AOS instance, every X++ customization across all 16 layers, every active Financial Dimension combination, every Number Sequence, every AIF integration port, every SSRS and Management Reporter report — and produces a concrete, costed, sequenced plan to move off AX onto Oracle Fusion before the 2026 extended-support cliff. Deliverables: instance scope register, X++ customization inventory with retire/replace/rebuild classification, AOT object catalogue, Financial Dimension to Fusion COA crosswalk draft, integration port map with Fusion rewiring plan, report inventory with OTBI/BI Publisher/Smart View replacement design, risk register, sized timeline (typically 14-20 weeks for full scope), budget envelope and decision pack ready for finance/IT/business sign-off.

Discovery workshops are interviews — people describe what they think exists. A dynamics ax migration assessment is evidence-driven — Syntra ETL's AOS-aware crawlers walk the actual AOT and produce the X++ customization inventory directly. SQL Server extractors pull row counts and active Financial Dimension combinations directly from LedgerJournalTrans and DimensionAttributeValueCombination. AIF endpoint introspection enumerates active integration ports directly. The artefact you get back is the ground-truth state of your AX environment, not someone's recollection of it. The implications are concrete: 'you have 47 active X++ customizations across CUS+USR, 31 of which appear to be functionally redundant under Fusion, 11 need rebuild as Fusion-native equivalents, 5 need redesign' — versus the discovery-workshop output 'we have lots of customizations and we'll need to inventory them in phase 1'.

Every layer: SYS, SYP, GLS, GLP, FPK, FPP, SLN, SLP, ISV, ISP, VAR, VAP, CUS, CUP, USR, USP. For each object (Table, EDT, Class, Form, Report, Menu Item, Number Sequence, Workflow definition) the assessment captures: source layer, last-modified date, last-modified user, dependent objects, business-purpose classification (validation rule, custom field, custom report, custom integration, regulatory requirement, vanity), Fusion-equivalent recommendation (native field, DFF, EFF, BIP report, AMX workflow, REST integration, retire). The inventory is reviewed object-by-object with the customer's AX functional leads in a workshop — most customers find 30-50% of customizations are functionally redundant under Fusion and can be retired, 30-40% need rebuild as Fusion-native, 10-20% need genuine redesign because the Fusion model differs.

Standard duration is 2-4 weeks elapsed time. Week 1: kickoff, scope confirmation, AOS/SQL Server access provisioning, initial crawler runs against AOT, SQL Server table inventory, AIF endpoint enumeration. Week 2: deep extraction — full X++ customization inventory, Financial Dimension combination extraction, SSRS/MR report enumeration, integration port mapping, attachment volume sizing. Week 3: review workshops with customer functional leads — X++ object retire/replace decisions, Financial Dimension to Fusion COA crosswalk draft, integration rewiring plan, report replacement design. Week 4: synthesis — risk register, sized timeline, budget envelope, sign-off pack. For very large estates (multiple AX 2012 instances across many countries, heavy X++ overlay) extends to 5-6 weeks.

Three things. (1) Read-only SQL Server access (a low-privilege login scoped SELECT on AX tables, plus dimension and AOT metadata tables) — no AOS changes, no schema modifications. (2) Read-only AIF SOAP endpoint access for environments where business logic in document classes (AxdCustomer, AxdVendor, AxdSalesOrder) needs introspecting. (3) Time from two functional leads (finance, supply chain) and one IT lead for review workshops — typically 3 half-day sessions in weeks 2-3. The assessment runs as a read-only client throughout — no changes to AX, no AOS restart, no production disruption.

Syntra ETL prices the assessment as a fixed-fee engagement scoped by AX instance count and customization profile. A single AX 2012 instance with moderate X++ overlay (20-50 active customizations) prices at $25-40k. Multi-instance estates with heavy overlay (multiple AX 2012 instances across countries, 100+ active customizations, complex AIF integration map) price at $50-90k. The assessment is structured to be self-funding — the budget envelope it produces is typically 40-60% lower than consultant-led discovery-workshop estimates because the X++ retire-rate becomes visible early. Customers commonly approve the full migration on the strength of the assessment's evidence pack.

Yes — and this is one of the highest-risk areas to leave for later. AIF (Application Integration Framework) in AX 2012 was the SOA layer; inbound and outbound document services connect AX to upstream sales channels, downstream warehouses, banks, tax authorities and trading partners. The dynamics ax migration assessment enumerates every active integration port (inbound + outbound), the document classes in use (AxdCustomer, AxdVendor, AxdSalesOrder, AxdPurchOrder, AxdLedgerJournal, AxdInventTransferOrder, custom AxdXXX), the endpoint types (file system, MSMQ, BizTalk, web service, custom), the cardinality (records/day, peak rates) and the upstream/downstream system. Output: integration port map plus Fusion rewiring plan (Fusion REST/SOAP endpoints, OIC integrations, FBDI batch substitutes, or retire-as-redundant-under-Fusion-native-feature).

Yes — and the assessment shape matters here. Carve-out scenarios involve one or more legal entities being separated from a group AX environment and migrated into a target Fusion tenant ahead of broader consolidation. The dynamics ax migration assessment for carve-outs adds: per-legal-entity transaction volume profile, shared-master-data analysis (customers, vendors, items shared across entities), Number Sequence scope analysis (shared sequences need careful disposition), inter-company elimination analysis, separation-of-duties analysis (X++ customizations that span entities), and a sequencing recommendation (full-entity vs phased-domain). The output supports the M&A transaction timeline — typically a 6-9 month window from Day-1 to operational independence in Fusion.