Switching from Microsoft Dynamics AX to Dynamics 365 F&O

Microsoft Dynamics AX has served enterprise and upper mid-market customers since 2002 (originally Axapta from Damgaard). Microsoft's product strategy has consolidated AX into Dynamics 365 Finance and Operations (D365 F&O) — the cloud-native successor with continuing functional depth. AX 2012 R3 mainstream support ended in October 2021; extended support continued through 2026 for those still operating it. For DACH AX customers, migration to D365 F&O is increasingly necessary rather than optional.

End-of-support pressure

The AX-to-F&O migration timeline is partly regulatory: AX 2012 R3 mainstream support ended October 2021; extended support ended October 2023 with custom-support extensions available; security-only support ends in 2026. Beyond that, customers operating AX face increasing risk: no Microsoft-provided security patches, no compliance updates, no ISV-platform support. Migration to D365 F&O has become operationally mandatory for most AX customers. Microsoft offers Dynamics 365 F&O Migration as a structured programme with conversion tooling and partner-led services. Customers delaying migration face accumulating risk; the runway to safe operation narrows continuously.

What changes in F&O versus AX

D365 F&O is conceptually familiar to AX users with significant architectural changes. Cloud-native deployment: hosted on Microsoft Azure as SaaS with continuous updates. Modern UX: web-based interface replacing the AX rich client. X++ continues: customisation language evolves; existing AX X++ code may need adaptation but the foundation continues. Power Platform integration: tight integration with Microsoft Power Platform for low-code extensions, Power BI for analytics, Power Automate for workflows. Common Data Service (Dataverse): integration layer with other Microsoft business applications. Continuous updates: F&O receives monthly platform updates and twice-yearly application updates; AX customers used to multi-year upgrade cycles face significant operational change. AI capabilities: Microsoft Copilot for Dynamics 365 brings AI assistance increasingly to F&O operations.

Migration methodology

Three migration paths. (1) Greenfield: fresh F&O deployment with process redesign; AX data migrated selectively. Highest transformation value, longest implementation. (2) Brownfield (uses Microsoft Data Migration Tool): AX data migrated to F&O while preserving customisations and process patterns. Faster, lower transformation value. (3) Hybrid: process redesign for some areas (typically financials, where F&O Best Practices justify change); brownfield approach for areas with extensive Sage-specific customisation. Microsoft Fasttrack and partner-led methodologies support all three approaches. Implementation duration: 12-30 months typical depending on complexity and approach. Cost: 1-10+ million EUR for upper mid-market AX customers.

Practical considerations

Three patterns. (1) Review customisation extensively: AX customers typically accumulated decade-plus of X++ extensions. The migration is the right time to retire unused customisations and re-platform critical ones to Power Platform where appropriate. (2) Plan for continuous-update operations: F&O's monthly platform updates require regression-testing discipline that AX-era operations rarely needed. Build the operational model for ongoing change. (3) Choose the right edition: F&O comes in different deployment options (Cloud, Cloud and Edge, Premium). Match the choice to specific operational requirements; many AX customers do not need the most-expensive tier. Microsoft pricing has structured tiers from Activity to Operations to Premium — understand the differences during contract negotiation.

Also consider:Microsoft Dynamics 365 Business Central · Microsoft Dynamics 365 F&O

Häufig gestellte Fragen

When does support for Dynamics AX 2012 R3 finally expire?

Mainstream support for Microsoft Dynamics AX 2012 R3 already ended on 12 October 2021, and extended support with security-only hotfixes expired on 10 January 2023. Microsoft therefore no longer delivers regular updates or security patches for AX 2012 R3; help is only available through paid custom support agreements. Older versions such as AX 2009 or AX 2012 R2 have been out of support for even longer, so practically all AX users need to act. For regulated or security-critical environments, running without patches is an increasingly serious risk.

Can you upgrade directly from AX 2012 to Dynamics 365 Finance & Operations, or is a new implementation required?

Microsoft supports a direct upgrade path exclusively from Dynamics AX 2012 R2 and R3 to Dynamics 365 Finance & Operations; for AX 2009, only a data migration via the Data Migration Tool is provided, or alternatively a two-stage upgrade first to AX 2012. For lightly customised installations, the database can largely be lifted technically with Microsoft's tools, which is faster and cheaper. For heavily customised setups that have grown over years, many partners instead recommend a new implementation (greenfield), because it reduces technical debt and makes the modern F&O functions cleanly usable. The right choice depends on customisation volume, data quality and strategic goals, and should be decided in a fit-gap analysis at the start of the project.

How much X++ code can be carried over to F&O automatically?

The code upgrade service in Microsoft Dynamics Lifecycle Services (LCS) handles part of the conversion automatically but by no means fixes everything itself; according to widely shared partner experience, roughly 80 to 85 per cent of customer-specific X++ code and a significantly higher share of the system code are converted automatically, while Microsoft itself guarantees no fixed percentages. Developers must rework the rest manually, especially API calls, data model changes and the shift from direct code editing to the new extension-based model. As a rough rule of thumb, partners calculate several weeks of migration and testing effort per 100,000 lines of code. A code inventory in the Discover phase is therefore mandatory, because the actual custom code volume often forms the largest single item in the project.

What does a Dynamics 365 Finance & Operations licence cost compared with AX maintenance?

A full Dynamics 365 Finance or Supply Chain Management licence is in the range of around 210 US dollars per user per month on Microsoft's current price list (Finance and Supply Chain combined around 240 US dollars), and a premium variant with Copilot credits around 300 US dollars; cheaper Activity users (approx. 70 USD) and Team Member licences (approx. 8 USD) cover lighter usage profiles. These ongoing cloud licence costs are generally significantly higher than the former AX on-premise maintenance. In return, you no longer need your own server infrastructure, manual updates and part of the operating effort, which must be offset in a total-cost-of-ownership analysis. Since Microsoft has tightened licence enforcement from early 2026, the licence structure should be planned early and realistically.

How long does an AX-to-F&O migration take and what does the duration depend on?

For classic corporate group setups, total durations of about 18 to 36 months are realistic, and 24 to 48 months for multi-country structures with multiple subsidiaries. Pure technical upgrades of lightly customised systems, by contrast, can succeed in around 10 to 14 months. The main drivers of the duration are the X++ code volume, the number of interfaces and ISV add-ons, the complexity of the multi-company structures, and the training and testing effort. A phased rollout with a pilot subsidiary, followed by waves for the remaining entities, reduces risk in large, internationally distributed rollouts.

Should smaller AX users switch to Business Central instead of F&O?

Dynamics 365 Business Central is designed for small and medium-sized companies, typically up to around 500 employees, while Finance & Operations is Microsoft's enterprise solution for larger organisations with complex, multi-entity structures. AX users with a manageable scope (often under about 200 users) may therefore find Business Central the leaner and more cost-effective choice. Classic AX corporate groups with extensive customisation, multiple legal entities and international requirements, by contrast, are better served by F&O. What matters is not headcount alone but the depth of processes, functional needs and internationality, which is why the decision should be assessed individually.