About the service
Dynamics AX 2009 and 2012 are already out of Microsoft support, with no security fixes or regulatory updates. Staying on AX is a growing risk, not a stable status quo.
ANEGIS moves organisations from AX to Dynamics 365 Finance and Supply Chain Management, the successors to AX, in the cloud or on-premises, keeping the full transaction history. The key decision, upgrade or a fresh implementation, you make on the basis of an environment assessment that can be carried out even before buying licences.
Dynamics AX is out of support today. Staying on it is not stability, it is deferred risk.
Support for all AX versions has already ended: for AX 2009 and 2012 in April 2022, for AX 2012 R3 in January 2023.
- No security fixes or regulatory changes. Every new regulation that AX will not handle becomes a problem on your side.
- Rising maintenance cost. Servers, the database, and the enhancement plan (about 16% of the license value per year) are outlays with no new value.
- X++ customisations and over-layering. Dynamics 365 no longer supports over-layering, so years of modifications need redesigning anyway.
- No access to modern capabilities. Automation, analytics, AI, and continuous updates remain out of AX's reach.
- Fading AX skills. Specialists are becoming scarcer on the market, which makes migration more expensive and riskier every year.
- Fear of the migration itself. The risk of data loss and downtime holds up the decision. This is exactly the risk we manage
From an AX environment assessment to a stable start on Dynamics 365
Environment assessment (Analyze)
An inventory of the AX version, customisations, integrations, and data; it can be run even before buying licenses.
Deciding on the path and option
Upgrade or re-implementation, cloud or on-premises: a recommendation based on analysis, not assumptions.
Code upgrade or rebuild
Converting code from AX 2012 and refactoring from over-layering to the extension model, under version control.
Data migration
The full transaction history via a data upgrade from AX 2012, or an agreed scope from AX 2009, with validation and cleaning.
Integrations and add-ons
Rebuilding integrations and selecting Dynamics 365-compatible versions of ISV solutions or their equivalents.
Testing and trial cutover
Functional testing and trial runs (mock cutover) before the production start.
Go-live and stabilisation
Go-live with a contingency plan, user training, and support in the first weeks.
The value that leaving AX genuinely delivers
- An end to the risk of an unsupported system. Security and regulatory updates are back on Microsoft's side.
- Transaction history preserved. On the upgrade path we move the full database, and reporting continuity stays intact.
- Lower cost of ownership. Continuous updates instead of costly, step-change migrations every few years.
- Processes simplified along the way. Migration is the moment to tidy up customisations, instead of moving them across unchanged.
- Access to modern capabilities. Automation, Power BI, Copilot, and AI, most fully in the cloud option.
- Polish compliance maintained automatically. KSeF, JPK, and local requirements handled by ready-made ANEGIS solutions.
Products that help us drive change
We migrate to the finance and operations applications, Dynamics 365 Finance and Supply Chain Management, the successors to AX, in the cloud or on-premises. We work with Microsoft tools: Lifecycle Services, the code and data upgrade tools, and Azure DevOps. Polish compliance is added by ANEGIS accelerators: KSeF, JPK, and the Polish Localisation Pack.
Proven performance, reliable results
We work according to our proven delivery method, based on Microsoft Success by Design and aligned with the FastTrack approach. We run the project in stages, with decision gates and architecture reviews, so that risks surface early and decisions are deliberate.
- Analysis before purchase. An environment assessment, fit-gap, and estimate with no commitment. The decision on the path is made at the very start.
- Data migration iteratively. From the development environment through the sandbox (UAT) to production, with validation at every step.
- A trial cutover before the start. We eliminate risk before it touches production.
- Go-live and stabilisation. A launch with a contingency plan and a move to the continuous-update model (One Version).
Why entrust the migration from AX to us
- Knowledge of both worlds. AX with X++ and over-layering, and Dynamics 365 with the extension model.
- Documented migrations from AX. Carried out in large, complex organisations.
- Project recovery in our practice. We know at which points migrations fail, and how to prevent it.
- A presence in Poland and the UK. Local support and international rollouts.
- Our own accelerators. The Polish Localisation Pack and KSeF shorten the path to compliance and go-live.
From the initial consultation to a fully operational system
Switching systems doesn't have to mean chaos. We guide you through five steps so that at every stage, it’s clear what is happening, why, and what the next step will be.
Discovery call
Free consultation: we learn about your situation, goals, and constraints. No strings attached and no sales pitch.
Analysis and recommendation
We map processes and requirements, assess platform fit, and recommend the scope, path, and approach.
Plan and decision
Schedule, budget, roles, and decision gates. You make project decisions based on facts, not assumptions.
Phased implementation
We implement step-by-step, with testing, risk control, and reviews at every milestone.
Stabilization and support
Launch with a contingency plan, post-launch support, and transition to ongoing maintenance.
See how we transform tech companies
BUUK Infrastructure: migration to Microsoft Dynamics 365
Microsoft Dynamics 365 Sales implementation for Georg UTZ
Microsoft Dynamics 365 modernisation for a global advertising holding
Microsoft Dynamics 365 Finance development for Eton Shirts
Leaving AX under control
We move organisations from AX 2009 and 2012 to Dynamics 365 keeping the transaction history, in the cloud or on-premises. We start with a free environment assessment, before the licensing decision.
Which way from AX: paths and options
The path depends on the AX version, and the target option on your requirements. Both decisions are made in the analysis phase.
AX 2012 R2/R3 → upgrade
Microsoft tools move the code and the full transaction history (data upgrade).
AX 2012 (RTM) → via R3
the older 2012 takes a path through R3, for which the upgrade is supported.
AX 2009 → a fresh implementation
there is no upgrade path; the tool migrates the data and we build the solution from scratch.
Re-implementation despite an available upgrade
with a heavily modified environment, a rebuild to standard is often cheaper and safer.
Option: cloud
fully managed, with continuous updates and the broadest range of capabilities; the default choice.
Option: on-premises (Local Business Data)
when regulations require data locally; you maintain the infrastructure and updates yourself.
Collaboration models
See other services
Dynamics 365 updates
Keep your Dynamics 365 environment on the current version, using new features and security without disrupting daily work.
Rollout
Extend a proven Dynamics 365 solution to further branches and countries, keeping processes and standards consistent across the whole organisation.
Managed support
We will provide ongoing care for your Dynamics 365 environment, responding to tickets and keeping the system stable and trouble-free.
Frequently asked questions about migration from Dynamics AX
Upgrade or a fresh implementation?
AX 2012 R2/R3 have a supported upgrade path that carries over code and data. AX 2009 has no upgrade path; that means data migration and building from scratch. With a heavily customised environment, even one on 2012, a re-implementation is sometimes the better choice.
Will we keep the full transaction history?
On the upgrade path from AX 2012, yes; the data upgrade brings over the entire database. With AX 2009 or a re-implementation, we migrate the agreed scope of data needed for operations and reporting.
What happens to X++ customisations?
Dynamics 365 does not support over-layering, so customisations are moved to the extension model. A Microsoft tool converts the code and flags conflicts; along the way we remove modifications that are no longer needed.
Do we have to move to the cloud, or can we stay on-premises?
Both options are available. The cloud is the default choice, managed and continuously updated. We use on-premises where regulations require it, with the caveat that you maintain the infrastructure yourself.
What determines the time and cost?
The AX version, the number and complexity of customisations, the integrations, and the chosen path and option. We start with an analysis that gives you a realistic schedule and cost range before you decide.
Let's start with an assessment of your AX environment
