AX 2012 to D365 Upgrade Effort Estimator
AX 2012 does not upgrade in place to Dynamics 365 Finance and Operations. It is a re-implementation of code and a migration of data. This estimator builds a labour estimate from the counts you can pull from your own AOT.
Your numbers
Classes, forms, tables, reports, and extensions in CUS, VAR or USR layers.
Analysis, rework as extension, unit test.
Customizations dropped because D365 covers them.
Extract, transform, load, reconcile.
Your results
A planning estimate from your own inputs. It excludes licences, hosting, third-party products and business-side effort. Validate with a partner assessment before committing a budget.
Labour cost vs share of customizations retired
Sweeps Share retired or replaced by standard from 0 to 100, holding your other inputs fixed.
AX upgrade scoping help
Share your counts and get an outside check on hours and scope. Optional.
Optional. The tool and every export work without this. No spam.
How to use the estimator
Start with counts, not guesses. Your AX developers can list objects in the CUS, VAR and USR layers, count integrations from AIF ports, batch jobs and services, and count SSRS or Management Reporter reports in use. Enter them with your own hours per item. The slider for retired customizations is the single biggest lever, and the chart shows how cost changes as more custom code is dropped in favour of standard behaviour.
- Pull object counts from the AOT or a code compare
- Count only reports users actually run
- Count each interface once, not each message type
- Use your own rate, not a list price
The method behind the numbers
Code remediation is objects times hours per object, reduced by the share you retire. Build adds integrations, reports and data migration cycles. Testing is a percentage of build, and project management is a percentage of build plus testing. Duration divides total hours by team size times 130 productive hours per person-month. D365 uses an extension model rather than overlayering, so each retained customization is re-written, not copied, which is why hours per object stay high.
Reading the result
The total hours and labour cost are for the technical project. A result that looks too low usually reflects an underestimate of integrations or data quality. Compare the duration with your business calendar: a long elapsed time means more parallel work or a phased approach. Use the retire slider to test a scenario where you fit processes to standard D365, then compare the savings to the change management cost you will incur.
Common mistakes
Teams underestimate data migration because AX 2012 history is large and uneven, forget Management Reporter and SSRS, and count customizations by form instead of by behaviour. Do not forget licensing, Azure or Lifecycle Services setup, and a cloud-hosted test environment. Finally, business users need time away from daily work for testing, which does not appear in these developer-side hours.
Frequently Asked Questions
Can AX 2012 be upgraded in place to D365?
No. Moving to D365 Finance and Operations is a new implementation with data migration and re-developed customizations. Tools exist to analyze code and help move data, but the application layer is rebuilt using extensions.
What drives upgrade cost the most?
The volume of retained customizations, integration complexity and data migration scope usually dominate. Standardizing processes and retiring custom code is the most reliable way to reduce cost and risk.
Does the estimate include licences?
No. It estimates labour only. Add D365 licences, environments, ISV products, training and business-side time separately to get a total program budget.
How accurate is a bottom-up estimate like this?
It is as good as your counts and hours per item, typically good for a planning range rather than a fixed price. Refine it after a code analysis and a first mock data migration.
If you want a second opinion on a customization inventory or help identifying which AX objects can be retired, we can review your list.
Related Tools
Dynamics AX Customization Inventory Worksheet
Editable inventory of AX customizations with layer, disposition and rework estimate per object, totaled for upgrade planning.
Costing & FinanceGP vs Business Central Migration Cost Comparison Calculator
Multi-year cost comparison of staying on GP versus moving to Business Central, with payback period and a horizon chart.
ERP Migration & SelectionLegacy ERP Data Archive Checklist
Twenty-eight checks to decide what history to keep, where to keep it and how to decommission a legacy ERP safely.
Microsoft DynamicsDynamics GP End of Support Migration Assessment
Ten-question readiness score for Dynamics GP customers who need a decision on what comes after GP.
More Microsoft Dynamics tools
See all- Dynamics AX 2012 Retirement Project Charter Template
- AX 2012 to D365 Data Entity Mapping Worksheet
- AX 2012 Customization Remediation Effort Calculator
- Dynamics AX 2012 X++ Table Methods Reference
- Dynamics AX 2012 AIF Inbound Sales Order Message Generator (File System Adapter)
- Dynamics AX 2012 SQL Reporting Query Generator (DATAAREAID, PARTITION, Enums)
- Dynamics AX 2012 R3 Safety Stock Journal Minimum Calculator
- D365 F&O Manufacturing Data Entities Reference
- D365 F&O OData URL Builder
New to Microsoft Dynamics AX 2012? Start with the Microsoft Dynamics AX 2012 guide and toolkit.
Keep exploring
Free tools
- AX 2012 Table to D365 Data Entity ReferenceLook up the D365 F&O data entity and OData collection that corresponds to a Dynamics AX 2012 table when planning data migration.
- AX 2012 Customization Remediation Effort CalculatorConverts counts of overlayered objects, custom reports, integrations and ISV modules into hours, cost and calendar weeks for D365 Finance and Operations remediation.
- AX 2012 to D365 Data Entity Mapping WorksheetPlan each AX 2012 data object, its D365 data entity, load sequence, record count and owner in one editable migration sheet.
ERP fixes and how-tos
- Planning an AX 2012 to Dynamics 365 Finance and Operations upgradeHow an AX 2012 to Dynamics 365 Finance and Operations upgrade actually runs: LCS upgrade project, code upgrade of customizations, and data migration, with the main risks.
- Adding a Private AI Layer to Dynamics AX 2012 On-PremAdd AI to Dynamics AX 2012 on-prem without moving data: SQL replica, AIF services, retrieval index, local LLM, mirrored AX roles, approved write-back.
- Dynamics 365 Supply Chain Management API: OData, Custom Services and Data PackagesD365 Supply Chain / F&O APIs explained: OData data entities, custom services, the data management package API, Entra ID authentication and when to use each.
AI on your ERP
- AI for Dynamics AX 2012, Without the Forced MigrationDynamics AX 2012 R3 left mainstream support in 2021. Add a private LLM over AX data now, use it to de-risk a future migration, without a forced move to D365.
- AI for Dynamics 365 Finance and Supply Chain beyond CopilotAI for D365 Finance and Supply Chain beyond Microsoft Copilot: private LLM grounded on data entities and OData, on-prem-capable via Local Business Data.
Integrations
- How to add AI agents to Microsoft Dynamics AX 2012How to add AI agents to Dynamics AX 2012 using AIF services, SQL read paths and approval gates, without a forced move to Dynamics 365 first.
- How to use ChatGPT with Microsoft Dynamics AX 2012How to use ChatGPT with Dynamics AX 2012: exports versus live access, custom GPT actions over AIF, enterprise data controls and when to go private.