Dynamics AX Customization Inventory Worksheet
Before anyone can price an AX 2012 to D365 move, someone has to know what is actually customized. This worksheet gives developers and architects a structured way to list objects, decide what happens to each and total the effort.
| AOT object | Type | Module | Layer | Business purpose | Lines of code | Rework factor (1 low, 3 high) | Estimated hours | Disposition | |
|---|---|---|---|---|---|---|---|---|---|
33.6 | |||||||||
3.6 | |||||||||
12 | |||||||||
150 | |||||||||
78 | |||||||||
8 |
The estimate uses four hours per 100 lines of code multiplied by your rework factor, a rough planning rule you should replace with your own history. Objects dispositioned as Retire to standard should be set to a factor of zero so they drop out of the estimate. Pull counts and line counts from a code compare or your source control, not from memory.
Customization review
Share your inventory and get comments on retire and rebuild candidates. Optional.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Export object names and layers from the AOT or a code comparison, then list one row per object. Choose the type, module and layer, describe the business purpose in plain words, and enter lines of code. Set a rework factor from 1 for simple to 3 for deeply overlayered code. Pick a disposition for each row. Review the list with business owners so that objects with no clear purpose are challenged, since those are the cheapest to retire.
- One row per object, not per project
- State the purpose in business terms
- Challenge anything without an owner
- Set factor to zero when retiring to standard
Disposition options
Retire to standard means D365 handles the need with standard features or configuration. Extension means the behavior is kept and re-written using the D365 extension model, since overlayering is not available. Rebuild means the design is changed, often as a new extension, service or a Power Platform component. ISV replacement means a third-party product covers it. Undecided rows are a risk, so aim to clear them before you finalize a budget.
Reading the totals
The hours total gives a developer-side estimate that you can feed into the upgrade effort estimator. The average hours per object helps you sanity check against your own experience. Look at the distribution: a few large rows, often in production or pricing, usually account for most of the effort. Those are where fit-gap workshops pay back. Compare the count of retire candidates with the total to see how much simplification is realistic.
Common mistakes
Counting only forms and forgetting tables, batch jobs, SSRS reports, AIF ports and workflows is the most frequent error. Another is listing objects by how they were named rather than what they do, which hides duplicates. Do not copy a rework factor of one across the board, as that makes the estimate look low. Update the worksheet as decisions are made so it stays the single source of truth for the project.
Frequently Asked Questions
How do I get a list of AX customizations?
Use the AOT, a code compare tool or your source control to list objects in the CUS, VAR and USR layers. Microsoft also offers code upgrade tooling for analysis. Combine it with interviews so each object has a business purpose.
Why does D365 need customizations rewritten?
D365 Finance and Operations does not allow overlayering of standard code. Changes are made through extensions, events and new models, so most retained customizations must be rewritten rather than moved.
What rework factor should I use?
Use 1 for simple, isolated objects, around 2 for moderate dependencies, and 3 for deeply overlayered code with many touch points. Replace the rule of thumb with your own historical hours as soon as you have a pilot result.
Can I send the inventory to a partner?
Yes. Export to Excel and share it. A well-formed inventory with purposes and dispositions typically shortens a partner's assessment and gives you a more reliable quote.
If you want help identifying which AX customizations map to standard D365 features, we can review your inventory with you. Optional.
Related Tools
AX 2012 to D365 Finance and Operations Upgrade Effort Estimator
Bottom-up hours, cost and duration estimate for an AX 2012 to Dynamics 365 Finance and Operations upgrade.
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.
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.
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
- 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
- D365 Security Role Design Worksheet