Trapped by Legacy ERP?
Manage Multiple EntitiesUpgrade from Dynamics AX, GP or NAV to Dynamics 365
Moving to Microsoft Dynamics 365 opens up capabilities your current system can't offer, and keeps you on current, supported technology for the years ahead. Our consultants plan every upgrade around your business goals and keep downtime to a minimum, so you see the benefits quickly.
Which system are you on today?
Why move now and the upgrade paths for AX 2012 and AX 2009.
Where every GP module lands, and how your data is moved and checked.
What stays familiar, and whether to upgrade or reimplement.
From running on borrowed time to current, supported and connected
Every year on AX adds risk and cost. Here's what changes when you move.
AX 2009 / 2012
- –Out of Microsoft support, with no security fixes since 2022–2023
- –On-premise infrastructure to maintain
- –Customizations only your original team understands
- –No native Power BI or Power Platform connectivity
- –A shrinking pool of AX-skilled consultants
Dynamics 365 Finance & Operations
- ✓Continuous updates from Microsoft, no more version lock-in
- ✓Cloud-hosted, with predictable infrastructure costs
- ✓Customizations re-platformed as supportable extensions
- ✓Native Power BI, Power Automate and Power Apps integration
- ✓A growing, current talent pool to support you long-term
AX 2012 and AX 2009 take different routes to Dynamics 365
Microsoft provides an upgrade for AX 2012 R2 and R3, and a data migration for AX 2009. Which one applies to you shapes the whole project.
| Area | AX 2012 R2 / R3 | AX 2009 |
|---|---|---|
| Microsoft support | Ended: AX 2012 R2 on April 12, 2022; R3 on January 10, 2023 | Ended April 12, 2022 (AX 2009 SP1) |
| Microsoft's route | Upgrade: code upgrade and data upgrade tools, run through Lifecycle Services | Migration: the AX 2009 Data migration tool is the only supported path |
| Your data | The AX 2012 database is upgraded, so history comes across | Tables are mapped to Dynamics 365 data entities and moved by legal entity; you choose how much history to bring |
| Your customizations | Custom code is brought forward and reworked as extensions, or replaced by standard features | Code does not carry across; what you still need is rebuilt as extensions |
| Older releases | AX 2012 RTM is first brought to a supported release before upgrading | AX 2009 RTM and earlier versions are assessed case by case |
Source: Microsoft Learn, end of support for Dynamics AX 2009 and 2012.
Every GP module mapped to its Business Central equivalent
Nothing gets migrated blind. Each area below is mapped and validated before cutover.
What moves from GP, and how it is checked
Nothing is migrated blind. Each type of data has its own route, and every route ends with a reconciliation your finance team signs off.
Master data
Customers, vendors, items, the chart of accounts and fixed assets. GP account segments become Business Central G/L accounts plus dimensions for departments, locations or projects, so your reporting structure survives the move.
Open transactions
Open receivables and payables, open purchase and sales orders, and inventory quantities and costs at the cutover date, so day one in Business Central picks up exactly where GP left off.
History
You choose how much history to bring: summarized G/L balances by period, detailed transactions, or both. Older detail can also stay available in a read-only GP or archive for lookups and audits.
Reconciliation and sign-off
Trial balance, receivables and payables aging, and inventory valuation are matched between GP and Business Central before cutover. Our data migration controls guide explains the checks.