AX 2012 Customization Remediation Effort Calculator
AX 2012 customisations were built by overlayering, which D365 Finance and Operations does not allow. Every modified object must be rebuilt as an extension, a new class or a retired requirement. This calculator turns an inventory into a defensible effort range.
Your numbers
Classes, tables, forms and other elements modified in a higher layer.
Rework into extensions or event handlers.
Your results
Hours per object vary widely. Calibrate them with a pilot on ten representative objects before committing a budget.
Cost vs contingency
Sweeps Contingency from 0 to 60, holding your other inputs fixed.
Optional customization scan
We can help turn layer exports into a categorised inventory. The calculator needs none of this.
Optional. The tool and every export work without this. No spam.
How to use it
Start from a real inventory: run a best practice and layer comparison on your AX model, export object counts by layer, and count custom reports and interfaces from the business. Set hours per object from a small pilot rather than from a guess. Then adjust testing and contingency to match how well documented the code is.
- Count by layer, not by feeling
- Pilot ten objects first
- Split simple and complex objects
- Review ISV vendors for D365 versions
The method
Development hours are the sum of count times hours for each category. Testing is a percentage uplift on development. Contingency multiplies the sum. Cost is hours times the blended rate, and duration is hours divided by team size times 32 productive hours per week. Retired requirements reduce counts directly, so rationalise first.
Common mistakes
Teams usually under-count reports and integrations, and they forget that some customisations disappear because standard D365 now covers the need. Run the estimate twice: once for everything, once after a business review that retires unused features. The difference is often the best argument for a fit-gap workshop.
Frequently Asked Questions
Why are overlays a problem for D365?
D365 Finance and Operations does not support modifying Microsoft code in a higher layer. Changes must be implemented through extensions, event handlers or new objects, so each overlayered element needs rework or retirement.
What hours per object are realistic?
Simple field additions can take an hour or two, while deep logic changes in core classes can take days. That spread is why a pilot on a sample set is the best way to calibrate.
Does this include data migration?
No. Data migration is a separate work stream. See the cutover window calculator in this set for volume and timing.
How much contingency should I add?
Twenty percent suits well-documented code with a pilot behind the numbers. Use thirty to fifty percent when documentation is thin or the original developers have left.
Netray can help scan code and layer exports to produce the object counts this calculator needs. You can use the calculator on its own.
Related Tools
Legacy ERP Data Cutover Window Calculator
Estimates final load duration, window utilisation and total rehearsal time from record volume, throughput and validation overhead.
Costing & FinanceERP Migration Payback and NPV Calculator
Calculates payback period, net present value and ROI for a GP or AX replacement from investment, run-cost savings and productivity gains.
ERP Migration & SelectionLegacy ERP Parallel Run Cost Calculator
Shows what each month of parallel running costs once you add legacy fees, double entry and reconciliation effort.
ERP Migration & SelectionLegacy ERP On-Prem Run Cost Calculator
Adds servers, SQL licences, admin staff, disaster recovery and vendor maintenance into one annual run cost with a multi-year inflation view.
More Microsoft Dynamics tools
See all- AX 2012 to D365 Finance and Operations Upgrade Effort Estimator
- Dynamics AX Customization Inventory Worksheet
- Dynamics AX 2012 Retirement Project Charter Template
- AX 2012 to D365 Data Entity Mapping Worksheet
- D365 F&O Manufacturing Data Entities Reference
- D365 F&O OData URL Builder
- D365 Production Order Status Reference
- D365 Data Management Import Worksheet Template
- D365 Batch Job Checklist