+1 480 485 7373%22 d=%22M10.913 53.581h109.15c6.028 0 10.914 4.886 10.914 10.913v109.151c0 6.027-4.886 10.913-10.913 10.913H10.913C4.886 184.558 0 179.672 0 173.645V64.495C0 58.466 4.886 53.58 10.913 53.58%22%3E%3C/path%3E%3Cpath fill=%22%23fff%22 d=%22M94.208 95.125h-21.82v59.416H58.487V95.125H36.769V83.599h57.439z%22%3E%3C/path%3E%3C/svg%3E)
Microsoft Teams
Dynamics AX to Business Central migration when Finance and Operations is more than you need
A Dynamics AX to Business Central migration suits companies that run AX 2009 or AX 2012 but use only part of it. Many bought AX for growth that never needed its full depth, and now pay to keep servers, X++ code and specialist skills alive. Microsoft offers no upgrade path from AX to Business Central, so the move is a new implementation with selected data carried across, not an automatic conversion.
Is Business Central the right target for an AX company?
Microsoft's own path for AX 2012 leads to Dynamics 365 Finance and Supply Chain Management, which keeps much of the AX data model. Business Central is the better fit when the company trades in one country or a few, runs standard distribution or light manufacturing, and finds Finance and Operations licences and projects heavier than the business needs. Microsoft's lifecycle page shows that support for AX 2012 R3 has ended, so staying put carries growing risk.
If you rely on advanced warehouse management, many countries in one instance or complex process manufacturing, look at Dynamics AX to Dynamics 365 Finance first. If those features sit unused, Business Central is usually cheaper to license and quicker to change.
Where Dynamics AX structures land in Business Central
What data to bring from AX
- ✓Master data: customers, vendors, items, bank accounts and the chart of accounts, which we clean before loading.
- ✓Open documents: unpaid customer and vendor invoices, plus open purchase and sales orders.
- ✓Opening balances for the general ledger at the cutover date, by dimension.
- ✓Stock on hand by location and bin, with lot and serial numbers where they are used.
- ✓Fixed assets with their cost and accumulated depreciation.
- ✓History summarised by month for comparison reports, with full AX detail in a read-only archive.
How a Dynamics AX to Business Central migration runs
- 1
Process review
Walk through how each AX module is really used today, and list what can be dropped.
- 2
Design in Business Central
Set companies, dimensions, posting groups and locations to fit the new design, not to copy AX.
- 3
Data mapping and test loads
Extract from the AX SQL tables, transform, and load through configuration packages or APIs into a sandbox. Repeat until counts and balances match.
- 4
Testing with users
Key users run their processes on migrated data, and any gaps go back into the design.
- 5
Cutover
Freeze AX postings, load final balances and open documents, reconcile, and go live at the start of a period.
Questions about Dynamics AX to Business Central migration
Can Microsoft's cloud migration tool move AX data to Business Central?
Not as a standard source. Microsoft's migration documentation lists Business Central on-premises, Dynamics GP and Dynamics SL. AX data needs custom mapping, either as a custom migration or through configuration packages and APIs.
Can we convert our X++ code?
No. X++ and AL are different languages on different platforms. We review each customisation: some become AL extensions, some are replaced by AppSource apps, and many turn out to be covered by standard features.
Should we bring all of our AX history?
Usually not. Full history adds cost and storage. Most companies bring open items and balances, a summarised history for reports, and keep AX read-only or an export for audits.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.