Microsoft Dynamics AX Upgrade & Support Guide for Australian Businesses

Microsoft Dynamics AX was the go-to ERP for larger Australian businesses that needed something more powerful than Dynamics NAV/GP but didn't want SAP. Manufacturing, distribution, retail, and professional services organisations across Perth, Melbourne, and Sydney invested heavily in AX implementations. Many still run AX 2009 or AX 2012 today.

The challenge is that Microsoft has moved on. Dynamics 365 Finance & Operations (F&O) replaced AX as the strategic product in 2016. It runs on Azure, gets continuous updates, and follows a fundamentally different architecture. If you're still on AX, you need a plan - either migrate to D365 F&O, move to a different ERP, or make a conscious decision about how long you'll maintain your current system.

The Dynamics AX Timeline

Understanding where each AX version sits helps frame your decisions:

• Dynamics AX 4.0 (2006) - Long gone from any support. If you're still on this, an upgrade is overdue.
• Dynamics AX 2009 - End of extended support has passed. No more security patches from Microsoft.
• Dynamics AX 2012 - The last on-premise version. AX 2012 R3 had mainstream support until 2021. Extended support runs until January 2023. Some organisations got custom support extensions.
• Dynamics 365 for Finance & Operations (2016+) - Cloud-based, runs on Azure. This is the successor to AX. Continuously updated by Microsoft with version updates roughly every month.

Migration Path: AX to D365 Finance & Operations

Microsoft provides a supported upgrade path from AX 2012 R3 to D365 F&O. The process is substantial - this isn't a simple version bump.

1. Code Upgrade

The biggest change is architectural. In AX 2012, customisations were done through "overlayering" - you'd modify Microsoft's base code directly. In D365 F&O, you must use "extensions." This means:

• Every overlayered customisation needs to be refactored to an extension pattern
• X++ code carries forward but the way it integrates with the base application changes
• Microsoft provides code upgrade tools in Lifecycle Services (LCS) to automate parts of this, but manual rework is always needed
• ISV solutions (third-party modules) need to be available in extension-based versions for D365

2. Data Upgrade

Moving your data from AX 2012 to D365 F&O involves:

• Database schema conversion - D365 F&O has a different database structure
• Data entity mapping for any custom tables and fields
• Historical transaction data migration (how much history do you bring across?)
• Master data cleanup - this is a good time to clean up customers, vendors, items that have accumulated over years
• Microsoft provides data upgrade scripts through LCS, but custom data structures need manual handling

3. Integration Rebuild

Integration architecture changes significantly in D365 F&O:

• OData endpoints replace the old AIF services. External systems that connected via AIF need to be reconfigured for OData or custom web services.
• Azure Service Bus handles async messaging patterns that were previously managed through AIF queues.
• Power Automate / Logic Apps provide low-code integration options that didn't exist with AX.
• Dual Write synchronises data between D365 F&O and Dataverse (the platform behind D365 Sales/Customer Service).

4. Testing and Training

D365 F&O looks and works differently from AX 2012. Users need retraining, and your team needs time to validate that everything works:

• Functional testing of all business processes in the new system
• Performance testing with realistic data volumes
• Integration testing with connected systems
• User acceptance testing with key stakeholders from each department
• Training materials and sessions for end users - the web-based UI is quite different from the AX rich client

Still on AX? What About Ongoing Support?

Not every organisation is ready to migrate to D365 F&O immediately. If you're staying on AX for now, here's what you need to manage:

Infrastructure

• Keep your Windows Server and SQL Server instances patched and current
• Monitor AOS (Application Object Server) performance and restart schedules
• Maintain your batch processing schedules and alert configurations
• Ensure backups are running and tested - including both database and AX model store

Customisation Maintenance

• Document your X++ customisations if they aren't already. When you eventually migrate, you'll need to know what every modification does.
• Fix bugs and performance issues as they arise. Don't add new overlayered customisations unless absolutely necessary - they'll just add to the migration effort later.
• Consider converting some AX customisations to external services now, which makes the eventual D365 migration easier.

Security

Without Microsoft security patches, you need to compensate:

• Restrict network access to AX servers - no direct internet exposure
• Use network segmentation to isolate AX infrastructure
• Monitor access logs and implement proper role-based security within AX
• Keep the underlying OS and database patched even if AX itself can't be

Common Dynamics AX Problems

1. Performance degradation - AX systems slow down over time as data volumes grow. Number sequences, batch jobs, and inventory closings are common bottlenecks.
2. Undocumented customisations - Multiple consultants and developers have worked on the system over the years. Nobody has a complete picture of what's been changed.
3. ISV solution lock-in - Third-party solutions that were installed in AX may not have D365 F&O equivalents, creating migration blockers.
4. Talent shortage - Finding developers who know AX 2012 X++ is increasingly difficult. The talent pool is migrating to D365 F&O skills.
5. Environment management - Managing dev, test, and production AX environments with proper code promotion and database refresh processes.
6. Reporting complexity - A mix of SSRS, Management Reporter, Excel-based reports, and possibly Power BI, built by different people at different times.

How HELLO PEOPLE Can Help

We're a Perth-based software company with 18+ years of experience in enterprise systems across Australia - Perth, Melbourne, Sydney, Brisbane, Adelaide, and regional areas.

Frequently Asked Questions

Is Microsoft still supporting Dynamics AX?

AX 2012 R3 is past mainstream support and in extended support with limited patches. Microsoft's investment is entirely in D365 Finance & Operations. If you're on AX 2009 or earlier, you're completely unsupported.

How much does an AX to D365 migration cost?

It varies enormously. A simple AX 2012 with few customisations might migrate for $150K-$300K. A heavily customised enterprise implementation with ISV solutions, complex integrations, and large data volumes can run $500K-$2M+. The customisation complexity is the biggest cost driver.

Can I migrate straight from AX 2009 to D365?

Not directly using Microsoft's standard upgrade tools. You typically need to upgrade to AX 2012 first, then migrate to D365. Alternatively, a "greenfield" reimplementation on D365 with data migration from AX 2009 can sometimes be more efficient than a stepped upgrade.

What happens to my X++ code?

X++ is still the development language in D365 F&O - so the language skills transfer. But the development model changes: overlayering is replaced with extensions, Visual Studio replaces MorphX as the development tool, and deployment happens through packages in Lifecycle Services rather than model stores.

Should I consider a different ERP instead of D365 F&O?

It's worth asking the question. D365 F&O is a good platform but it's complex and expensive. If your needs have changed since you first implemented AX - maybe you've simplified your operations or no longer need manufacturing modules - a lighter platform like NetSuite or Dynamics 365 Business Central might be a better fit. Talk to us and we'll help you evaluate.

Summary

Dynamics AX served Australian businesses well for years, but the clock is ticking. Microsoft's future is D365 Finance & Operations on Azure, and the AX talent pool is shrinking. Whether you migrate to D365 F&O, choose an alternative ERP, or need support to keep AX running while you plan the transition, having a clear strategy is essential.

If your Dynamics AX environment is becoming harder to maintain, your customisations are undocumented, or you're not sure which direction to take - book a free assessment with our team.