Dynamics AX Data Migration
Migrate to D365, Business Central, NetSuite, Odoo, or a Xero/MYOB multi-app stack.

Yes. AX 2009 extended support ended October 2018. AX 2012 RTM ended October 2021. AX 2012 R2 ended October 2023. AX 2012 R3 ends January 11, 2028. If you are on anything other than R3, you are already operating without vendor support — no security patches, no compliance updates. If you are on R3, you have less than two years before the same situation applies. The version determines how urgently migration planning needs to start.

No. It is the official Microsoft path and the closest functional match for complex AX environments, but it is not the only option. Business Central is worth evaluating if your AX implementation was relatively straightforward. NetSuite is worth evaluating if you are open to leaving the Microsoft ecosystem. The right answer depends on what you actually use AX for, how complex your customisations are, and your budget. We can help assess the options before you commit to a platform selection.

They need to be assessed individually. AX used overlayering — you could modify base application code directly. D365 does not allow this. Every X++ customisation needs to be either retired (because D365 now covers the requirement natively), rebuilt as a D365 extension, or replaced by a different approach. A significant proportion of X++ customisations in most AX environments can be retired because D365 F&O has added functionality that AX lacked. The rest need rebuilding.

For a mid-complexity AX environment, 12 to 18 months is a realistic project timeline. Simple environments can move faster. Heavily customised AX installations with many integrations and large data volumes take longer. The X++ assessment and customisation rebuild is usually the longest phase, followed by data migration and integration reconstruction. We scope from your actual environment after an audit rather than estimating from staff count.

No. AIF does not exist in D365 Finance & Operations or Business Central. All AIF integrations need to be rebuilt using the target platform's integration model: OData endpoints and Data Entities for D365 F&O, REST APIs for Business Central. Direct SQL integrations into the AX database also need rebuilding since the AX SQL schema has no equivalent in D365. The integration rebuild is often the most underestimated part of an AX migration.

SSRS reports in AX often use X++ data providers for complex calculations, which means they are tightly coupled to the AX platform. They need to be rebuilt for the target system. We rebuild SSRS reports as Power BI dashboards using the certified D365 connector for most operational and management reporting. Reports with highly complex logic are rebuilt as custom reporting tools. The end result is typically better than the original — live data instead of point-in-time snapshots.

For D365 Finance & Supply Chain Management, yes. The core ERP configuration — chart of accounts, workflows, modules, and D365 setup — is typically handled by a certified Dynamics 365 implementation partner. We work alongside them to handle data migration, X++ customisation rebuild, AIF integration replacement, and SSRS report migration. Most ERP partners prefer to have a specialist handle the data and integration layer rather than trying to manage it themselves.

Yes. We often do the AX environment audit and customisation assessment before an ERP partner is engaged. That documentation makes the partner selection process better — you go into partner conversations knowing exactly what your environment contains and what needs to be handled, rather than relying on estimates. It also helps you scope the ERP implementation more accurately, which leads to more comparable quotes from different partners.