Microsoft Dynamics AX Migration
AX 2012 is end of life.
D365 Finance is not the only exit.
Dynamics AX 2009 and AX 2012 companies move to QuickBooks Enterprise or Intuit Enterprise Suite instead of funding a Dynamics 365 Finance and Operations re-implementation. Financial dimensions, ledger structures, and full posted history extracted from SQL and reconciled.
30-day standard timeline · 15,000+ migrations · Trusted by Intuit
The trigger
AX customers are not choosing to move. They are being moved.
Extended support has run out
AX 2012 R3 has passed extended support. You are running an unsupported ERP holding your general ledger, and that is now an audit conversation as much as an IT one.
D365 F&O is a re-implementation
It is not an upgrade path in any meaningful sense. New data model, new extensibility model, new licensing. The quote reflects that, and for a lot of AX customers it is out of proportion to the business it supports.
The X++ customizations are the cost
Years of X++ modifications and ISV layers do not carry across. Rebuilding them is where AX upgrade budgets go, and where AX upgrade timelines slip.
The AOS tier needs feeding
Application Object Server, SQL Server, SSRS, and a Windows estate to run them on. That infrastructure line is hard to justify for a mid-market finance function.
The business shrank or split
Divestitures and carve-outs leave AX sized for an enterprise that no longer exists. The remaining entity does not need a tier-one ERP.
AX skills have become scarce and expensive
The consulting market moved to D365. Finding someone who can safely touch an AX 2012 environment costs more every year.
The AX specifics
What makes a Dynamics AX migration its own problem.
Financial dimensions and account structures
AX 2012 replaced simple account numbers with a main account plus a configured dimension set and account structures that control valid combinations. Flattening that into a destination chart of accounts, without losing the reporting that the dimensions were carrying, is the core design work.
Ledger, subledger, and the general journal
AX posts through subledger journal entries that do not map one-to-one to a simple GL line. History is reconstructed from GeneralJournalAccountEntry and GeneralJournalEntry rather than from a summary report, so the migrated trial balance is auditable.
Legal entities and consolidation
AX holds multiple legal entities in one deployment with shared and company-specific data. Which entities migrate, which merge, and how intercompany balances resolve is decided in discovery.
Inventory costing models
Weighted average, FIFO, standard cost, and the recalculation and closing runs behind them produce valuations that will not reconcile from a stock-on-hand report alone. We tie to the inventory closing, then to the GL.
Production, projects, and service modules
Where AX is doing manufacturing, project accounting, or field service, the financial outcome migrates and the operational module is replaced with a fit-for-purpose system. Discovery makes that split explicit before you commit.
Number sequences and document references
AX number sequences carry meaning across entities and modules. Source document numbers are preserved as references on migrated records so audit trails survive the move.
Approach
Reconcile the ledger before you retire the server.
Discovery
AX version, legal entity list, dimension and account-structure configuration, module usage, customization and ISV inventory, and history depth. Written scope with a fixed cutover date.
SQL extraction
Extraction straight from the AX SQL database, at ledger-entry grain, so nothing depends on an AX report still running correctly.
Test conversion and sign-off
Trial balance by legal entity, AR and AP aging, inventory valuation, and dimensional reporting compared side by side until they tie. Your controller signs off.
Cutover and first close
Delta load at period end, AX retained read-only for retention and audit, and support through the first month-end.
FAQ
Dynamics AX migration questions.
Which AX versions can you migrate?
AX 2009, AX 2012, and AX 2012 R2 and R3. Dynamics 365 Finance and Operations is also supported where a company is moving back down from it.
Is QuickBooks really a destination for an AX customer?
For a lot of AX installs, yes, particularly after a carve-out or divestiture. Where the operational complexity is genuine, Intuit Enterprise Suite plus a purpose-built operational system is usually the right shape. If neither fits, we will tell you on the call.
What about our X++ customizations?
Inventoried in discovery, each with an explicit decision: replicate, replace with a destination capability, or retire. The financial impact of each is what we migrate.
Can we shut down the AX servers afterwards?
Keep an archived SQL backup and a documented restore path for your retention period. Most clients decommission the live AOS and SQL tier once the first close in the new system is complete.
Before You Decide, Read the Mechanics
Short field guides on the contract clauses and platform limits that usually decide this. Each one names a document or a report you already own.
Find the Escalator Before You Negotiate the Quote
A 6 percent discount erased by a 7 percent annual escalator, all three years priced out, and the three checks that change the answer.
Your Price Did Not Rise. Your Discount Expired.
Why a 20 percent introductory discount unwinds as a 25 percent increase, and the four things to do before you reply.
Put the AX exit next to the D365 quote.
Send us the AX version, the legal entity count, and the upgrade number you were given. Discovery will tell you what the alternative actually costs and what will migrate cleanly.
30-day standard timeline · Direct SQL extraction · Source system kept read-only