ERP Migration & SelectionFree worksheetPDF, Excel, Word exportQADAll QAD tools

QAD EE Custom Code Inventory Worksheet

Before any QAD upgrade or move to Adaptive ERP, the real question is how much custom code you have and how much of it still matters. This worksheet inventories each customization, scores complexity and records a retire, replace or rebuild decision.

Free, optional. Reopen it on any device.

Download:

Program or report name	Type	Business use	Last used	Complexity (1 to 5)	Base hours per complexity point	Rebuild hours	Decision
						16
						32
						24
						16
						40

Total rebuild hours if all rebuilt

128

Customizations listed

Average hours per customization

25.6

The effort column is a rough planning figure. Retire and Replace decisions should reduce the real rebuild total, so filter the exported sheet by decision to size only the work you will actually do. Last-used dates should come from usage logs, not memory.

Get your customization list summarised

Optional: we can discuss using private AI to document and classify your custom code in place.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use the inventory

Pull a list of custom programs, reports, interfaces, triggers and screen changes from your source code library and your menu configuration. Add the business use and, from logs or user interviews, the date it was last used. Score complexity from 1 for a simple report to 5 for deep logic touching many tables. Set the base hours per point from your team's experience and the sheet computes rebuild hours. Then record a decision for each item.

Retire first, rebuild last

In most customization audits a meaningful share of items has not been used for years or duplicates a function in the standard product. Retiring those is free. Replacing with standard saves rebuild effort and ongoing maintenance. Only what is both used and genuinely differentiating should be rebuilt, ideally as extension code outside the core so it survives future upgrades.

No use in 12 to 24 months is a strong retire candidate.
Ask whether the standard product now covers the need.
Prefer extension patterns over modifying core objects.

Reading the totals

Compare the all-rebuilt total with the total after filtering to Rebuild and Rewrite decisions. The gap is the effort you avoid by rationalising. If most hours sit in a few complexity 4 and 5 items, those deserve their own design and test plan, because they carry the upgrade risk. Review the list with business owners, not only developers.

Common mistakes

Teams inventory only programs and miss reports built in external tools, spreadsheets that read the database directly, and scheduled jobs. Another mistake is estimating from lines of code instead of complexity and test effort. Finally, skipping the usage check leads to carrying dead code into the new platform.

Frequently Asked Questions

Does this cover QAD Adaptive ERP specifics?

It is platform neutral: it lists whatever custom objects you have and records your decision. Which patterns suit Adaptive ERP, and how existing customizations map, should be confirmed with QAD or your implementation partner.

How do I find last-used dates?

Use menu usage logs, database audit data, scheduler history or report server logs where available. If none exist, ask the owning department and treat the answer as unverified until a trial retirement period passes.

What base hours should I use?

Use your own history of similar work, including design, build, test and documentation. The sample value of 8 hours per point is only a placeholder for illustration.

Should reports be included?

Yes. Custom reports are often the largest group by count, and many can be replaced by standard reporting or a BI tool, which makes them the best retire and replace candidates.

Netray can help analyse custom ERP code with on-prem AI to summarise what each program does and flag likely duplicates of standard functions, without sending source code outside your network.

Talk to an Expert Explore More Free Tools