techone --guide=ax-to-fo
From Dynamics AX (Axapta) to Dynamics 365 Finance & Operations
Finance & Operations is a re-architected platform compared to AX, so the move is always a fresh start. You decide which of today's processes to keep and which to redesign around how the company works now.
TL;DR
- Who this guide is for
- Companies running some version of Microsoft Dynamics AX (Axapta) and deciding where to go next. Typically larger organizations with heavy customization.
- What it covers
- Why the move to Dynamics 365 Finance & Operations runs through a new system, what the financial data conversion involves, and how AI speeds up the whole approach.
- Support status
- No version in the AX line (2009, 2012, 2012 R2 or R3) is still supported; Microsoft no longer develops them. The whole line belongs on the migration plan.
- Recommended path
- Microsoft groups the finance and operations apps as the path forward: Dynamics 365 Finance, Supply Chain Management, Commerce and Project Operations. From AX 2012 and R2 the route runs through AX 2012 R3.
- How to start
- A current state analysis: scope of X++ customizations, data volume and quality, connected systems. The output is a clear brief on which customizations stay and which get rebuilt on the new platform.
Why It Belongs on Your Plan Now
With Dynamics AX the whole range is out of support and Microsoft no longer develops any version. Here is the picture by version.
Dynamics AX 2009
Long out of support, no longer developed by Microsoft. It belongs on the plan to move to Dynamics 365 Finance & Operations.
Dynamics AX 2012 and 2012 R2
Extended support has ended, so Microsoft no longer develops these versions. The official upgrade route from them runs through AX 2012 R3, so the move belongs in the plan rather than at the last minute.
Dynamics AX 2012 R3
Also out of support. It is the last version of the AX line. You cannot buy yourself another delay with a newer version, because there is no newer one in the old line.
What end of support means
With AX the entire range is out of support and Microsoft no longer develops any version. The finance core misses the modern capabilities that go into Dynamics 365 Finance & Operations: cloud, integrations, AI and continuous updates.
How the move works
Dynamics 365 Finance & Operations is a re-architected platform compared to AX. Microsoft groups the finance and operations apps together, covering Dynamics 365 Finance, Supply Chain Management, Commerce and Project Operations, and from AX 2012 and R2 the official route runs through AX 2012 R3. In practice this means a fresh start on a different platform, a real leap rather than a mechanical upgrade of the old installation. That sounds like more work, and up front it is. But your company has changed over the years, and the move is the one moment to align the processes with how you work today and leave years of customizations and workarounds behind, instead of carrying them forward.
Over the years AX accumulated X++ customizations, side procedures and processes that once made sense. You start fresh and make a deliberate decision on each of them: standard Dynamics 365 Finance & Operations covers it, it gets rebuilt, or the process is set up differently. That decision is no guess. It rests on a current state analysis. For what such an analysis looks like and what you get from it, see our guide to process analysis before an ERP implementation.
Rebuilding takes more work up front than the idea of an upgrade. In return you get a finance system on a current platform, not baggage transplanted from the previous decade.
What to Plan for in the Data Conversion
For a finance system, the data conversion is the part to get right. Some data comes across almost every time, while for the rest the scope is a project decision, not an automatic rule. It pays to sort this out before anything moves, so it is clear what you need live from day one and what is fine to archive.
Master data
Customers, vendors, items, chart of accounts. The backbone the new system needs to run at all. This is where the conversion is planned first.
Open items and balances
Unpaid documents, opening account balances and ledgers. The scope follows what has to sit in the general ledger ready for the first accounting day.
Long history
What happens to many years of document history is not a fixed rule. It is a decision: part into the live system, the rest into an archive you can reach. We make it based on how much history you genuinely need to look up.
Customizations and custom logic
X++ customizations do not come over on their own. Whatever should stay is rebuilt on the new platform, and the mapping between the old and new model has to be defined. This part tends to be the most labor-intensive.
The goal of the conversion is a clean start with data you can rely on, not moving everything wholesale. What actually comes across is confirmed by the analysis at the start of the project.
How AI Helps Us
The center of gravity in this move is the data itself: converting it off old AX, reconciling the general ledger, straightening out inconsistencies, and checking the closed periods. That work is done by tools we build for your specific data, and AI cuts down how long it takes us to build them.
The customizations live in X++ and the financial data is sensitive, so we keep a firm hand on the review. On top of the transfer layer we add the transformation, the checks and the conversion of customizations. AI saves us the most time across three areas:
Mapping and transformation
Tools that remap the financial data from old AX and convert it into the structure of the new model.
Consolidation and cleanup
Reconciling inconsistencies in the general ledger, merging duplicates and straightening code lists so the data enters the new system clean.
Validation and reconciliation
Checking that ledger balances and closed periods after the move match the source system across the full volume, not just a sample.
The faster we build those tools, the sooner you have a clean system without the legacy baggage.
Why Us
The move off Axapta stands on hands-on experience migrating a company off an aging finance system onto the current Dynamics 365 platform, in the same family that Finance & Operations belongs to.
For Tesil Fibres we handled the move from Oracle E-Business Suite to Dynamics 365 Finance, including data migration and Czech localization for VAT and Intrastat, coordinated with the parent company. Same kind of task and same platform: getting a company off an aging system onto current Dynamics 365 without losing data and in line with local legislation. How the implementation and the system integration carry on once the analysis is done is covered by our ERP integration service. For the step before the migration, see our guide to process analysis before an ERP implementation.
Frequently Asked Questions
Is it worth starting now, or waiting?
If the move is on your mind, an earlier start pays off. The AX line has no newer supported version to step onto in the meantime, so waiting only defers the same decision. Dynamics 365 Finance & Operations brings cloud, integrations, AI and continuous updates. The sooner you begin the analysis, the more calmly and with more options you decide, well before committing to anything. We begin with a no-obligation call about your operations.
Why is this a new system, not an upgrade?
With AX a clean upgrade is not really on the table, since Dynamics 365 Finance & Operations is a re-architected platform. And even if it were possible, a purely technical move of the same functions misses the substance: your company has shifted over the years, and the old system no longer reflects how you work today. So the move is the moment to review the processes, consolidate them, and shape the finance system around how you run now. More work goes in at the start, and what comes out is a system true to how the business actually operates.
What happens to our X++ customizations?
X++ customizations do not migrate on their own. For each one we first judge whether standard Dynamics 365 Finance & Operations covers it, whether you genuinely still need it, or whether the process can be set up differently. Whatever should stay is rebuilt on the new platform, and the mapping between the old and new model is defined. This part of the project tends to be the most labor-intensive, and we use AI to help with it.
Does the complete data history migrate?
Master data (customers, vendors, items, chart of accounts) does. Alongside it come unpaid items, opening balances and setup. For many years of document history there is no fixed rule. We agree the scope together: how much history you need right inside the live system and how much can sit in an archive you can reach. We are after a clean start, and you keep your data.
How long does the move take and how much does it cost?
It depends on the scope of customizations, on the volume and quality of data, and on the number of integrations. It diverges enough between companies that a single flat number would be misleading. You get a realistic frame after the initial analysis, once it is clear what migrates and what needs rebuilding. No arm-twisting and no shooting from the hip.
Do you have experience migrating to Dynamics 365 Finance?
Yes. For Tesil Fibres we handled the move from Oracle E-Business Suite to Dynamics 365 Finance, including data migration and localization. Finance & Operations belongs to the same Dynamics 365 family, and it is the same kind of task: getting a company off an aging finance system onto the current platform without losing data and in line with legislation.
Microsoft Cloud Solution Provider
You handle the move to Dynamics 365 and the licensing with one partner. We go through your situation and take care of both.
Running on Dynamics AX?
We will walk through the state of your installation and tell you what the move to Dynamics 365 Finance & Operations would involve and in what order.
Book a consultation