top of page
Dynamics AX

Dynamics AX to Dynamics 365 migration

Moving from AX 2009 or AX 2012 to Dynamics 365 Finance and Supply Chain — with a clear account of what carries across, what gets rebuilt, and what a decade of customization is actually worth keeping.

Overview

This is a re-implementation, not an upgrade

There is no upgrade path from AX to Dynamics 365. The data model changed, the extension framework changed, and the deployment model changed from your servers to Microsoft's.

​

That sounds worse than it is. The expensive part of an ERP is not the software — it is knowing how your business runs, having a chart of accounts that works, and having people who already understand the vocabulary. All of that carries. What gets rebuilt is the configuration and customization layer.

You are not moving a system, you are rebuilding one.

Who this is for

Where AX migrations go wrong

The most expensive mistake available.

Rebuilding every customization

Overlayered code with no documentation and no author still reachable.

Nobody can explain the overlayers

Decide what you actually need and archive the rest.

Migrating all the history

They surface late, and they are usually what moves the go-live date.

Underestimating the integrations

Why teams act now

The first question everyone asks, and the one most partners answer vaguely.

Data, process knowledge and organizational structure carry across; configuration and customization are rebuilt.

group working on migration

Before

Chart of accounts and dimension structure

 

Customers, vendors, items and master data

 

Legal entity and organizational structure

 

Process knowledge and operating model

After

X++ customizations, as extensions

 

Forms, workflows and security roles

 

AIF and custom integrations

 

Batch jobs and scheduled processes

How we work

Moving from AX 2009 or AX 2012 to Dynamics 365

1

Assessment and roadmap

Customization inventory, integration map, and data audit.

2

Analysis and design

Process workshops, chart of accounts and dimension design, and the fit-gap work.

3

Build and configure

Configuration against standard, integrations rebuilt on Data Entities and APIs, and reporting built in Power BI.

4

Cutover and go-live

Final data load, training delivered to the people who will use the system daily, and go-live.

Frequently asked questions

DYNAMICS AX MIGRATION

Find out what your estate would actually take.

A call covering which AX release you are on, how much has been built on top of it, which integrations exist, and what is forcing the timing. You will leave with a realistic view of scope — including if the honest answer is not this year.

bottom of page