Moving from Dynamics AX to Business Central: a migration mapped and rehearsed

When a Dynamics AX to Business Central migration makes sense

Dynamics AX was built for large, complex firms. Microsoft's direct successor to it is Dynamics 365 Finance and Supply Chain Management. Many mid-sized firms on AX use only part of that depth. For them, Business Central is often the better landing place. It is a smaller system. Microsoft updates it in the cloud.

It is not right for everyone. Heavy process manufacturing can point to Finance and Supply Chain Management instead. So can advanced warehousing across many sites, or very large volumes. We start by listing the AX modules you really use. Then we check each one against standard Business Central.

How AX data maps in a Dynamics AX to Business Central migration

The two products store data in different ways. AX legal entities become Business Central companies. Financial dimensions in AX become dimensions and dimension values. You pick the two you use most as global dimensions. Main accounts become the chart of accounts. Released products become items with posting groups and units of measure.

We write the mapping down table by table before anything moves. It covers customers, vendors, items, bills of materials, open orders and open receivables and payables. It also covers inventory on hand and general ledger balances. Fields with no direct home are dropped with your agreement or carried in a small extension. So nothing disappears by accident.

What happens to X++ code in a Dynamics AX to Business Central migration

AX custom code uses X++. None of that code can be converted to Business Central. What carries over is the need behind it. We go through each change and ask who still depends on it. Then we sort it into three groups. Standard features cover it, an AppSource app covers it, or we rebuild it as an AL extension.

This step usually shrinks the list a great deal. Reports written long ago, fields added for a customer who left and workarounds for old limits can retire. We rebuild what remains as clean extensions that sit beside the base application. So you can apply Microsoft's updates without redoing the work each time.

How we run the data move for AX to Business Central migration

Microsoft has no cloud tool for AX. So data moves through setup packages and Excel templates. For large volumes, we use the Business Central APIs. We extract from the AX database and clean the data in staging files. Then we load it into a sandbox environment.

We repeat each load until the numbers tie out. We compare the trial balance, open receivables, open payables and stock value with the same reports from AX. Then we find the cause of any gap. Your users then try daily tasks on the moved data. Only then do you agree a cutover date.

Pitfalls in a Dynamics AX to Business Central migration

The most common mistake is trying to rebuild AX inside Business Central. The products treat stock costing, warehouse setup and planning in different ways. Copying old settings field by field builds a system that fights itself. We design around how Business Central works. Then we explain each difference to the people affected.

The second trap is history. Bringing every old transaction across is slow and rarely useful. Most companies load open items and opening balances. They add summarized ledger history for comparison reports. They also keep the AX database available read-only for lookups. We agree that scope with you early.

Dynamics AX to Business Central migration questions

Is there an upgrade path from Dynamics AX to Business Central?

No. They are separate products with different data models and code, so there is no in-place upgrade. A Dynamics AX to Business Central migration is a new Business Central setup with data moved from AX. Microsoft's own upgrade route for AX leads to Dynamics 365 Finance and Supply Chain Management.

Should we move to Business Central or to Finance and Supply Chain Management?

It depends on size and complexity. Business Central suits small and mid-sized firms. They have standard finance, distribution and light manufacturing. Very large, multi-site or heavily regulated operations often fit Finance and Supply Chain Management better.

Can our X++ code be converted to AL?

Not automatically. X++ and AL are different languages on different platforms. We treat each custom change as a need. We check whether standard Business Central or an existing add-on covers it. Then we rebuild only what you still need as an AL extension.

How much AX history should we bring across?

Usually open transactions and opening balances, plus enough summarized general ledger history for comparison reports. Detailed history stays in the AX database. You can keep it read-only or copy it into a reporting database for lookups and audits.

Which AX versions can you migrate from?

In a Dynamics AX to Business Central migration, we extract and load the data rather than upgrade in place. So the AX version matters less than the quality of the data. We work from older AX releases up to the last on-premises one. We check the data before we plan the move.

Related migration and planning pages

Leaving AX touches data, design and product choice at once. The pages below cover the general method and the data work. They also compare Business Central with AX and its direct successor. Read them before you plan a Dynamics AX to Business Central migration. Then tell us which AX modules you use, and we will outline the steps. For the product detail, see Microsoft Learn: migrating customer data to Business Central.