ERP Migration & SelectionFree worksheetPDF, Excel, Word exportQAD

QAD Customization Inventory Worksheet (for Upgrade or Migration)

Customizations are the biggest source of surprise cost when upgrading or moving away from QAD. This worksheet gives you one place to list them, record how often they are used and decide what happens to each.

Download:

Customization	Type	Module	Usage	Decision	Effort (hours)	Rate per hour	Estimated cost
							$2,280
							$3,800
							$760
							$0
							$3,040
							$1,140

Total effort (hours)

116

Total estimated cost

$11,020

Average cost per item

$1,837

Find customizations by comparing your program libraries, reports, database schema and interface logs against a standard install, then ask users which ones they still use. Unknown usage is a prompt to ask, not a reason to keep the item.

Want help sizing your customization effort?

Optional: an expert reviews your inventory and flags likely rework.

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

How to use the worksheet

Add one row per customization, report, interface, screen change or extra database field. Record the module, how often it is used and what you plan to do with it. Estimate effort in hours and enter a blended rate, and the sheet computes cost per row and in total. Start with a first pass from your development team, then walk the list with business users to confirm usage and to find items nobody listed. Export to Excel to share with the steering group.

Making the decision for each item

Retain means the logic stays as is and is ported. Rebuild means the need is real but the technique must change. Replace by standard means current standard functionality now covers it, which is common after years of vendor releases. Retire means the item is no longer needed. Use frequency as a guide: items used daily deserve care, while rarely used items are often better handled by a standard report or an export.

Reading the totals

The total hours and cost give an early view of the customization effort in your plan. Look at the split by decision: a high share of retire and replace by standard means a cheaper project. A large block of items marked review means scope is uncertain, so keep contingency until they are resolved. Compare average cost per item with similar items you have changed before.

Common mistakes

Lists often miss reports that live in spreadsheets, scheduled batch jobs, and interfaces on a partner side. Teams also copy everything forward because it is easier than asking users, which carries old workarounds into the new system. Finally, effort estimates for rebuilds usually leave out testing and user acceptance, so add those hours explicitly.

Frequently Asked Questions

How do I find all customizations?

Compare your program source, menu entries, report definitions and database schema with a clean install, check interface and scheduled job logs, and interview users. No single source is complete, so use several.

What rate should I use?

Use a blended internal or partner rate you actually expect to pay. If rates differ by skill, add rows or use an average, and note the assumption in the notes so reviewers can challenge it.

Should I keep unused items?

Usually not. If nobody uses an item, retire it and keep the source archived. Carrying unused code costs testing time and adds risk during every future upgrade.

Can I use this for other ERPs?

Yes. The columns are generic apart from the QAD wording, and the same approach works for any ERP with custom code, reports and interfaces.

If you want help finding hidden customizations or estimating the rebuild effort, we can review your list with you.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Back to All Tools