ERP Fit Gap Analysis Worksheet (Excel Template with Effort Totals)
A fit gap analysis compares what the business needs against what the ERP does out of the box. This worksheet gives each requirement a fit category, an effort estimate and a cost, and totals the customization burden.
| Requirement | Process area | Fit | Priority | Effort (days) | Day rate | Estimated cost | Decision owner | |
|---|---|---|---|---|---|---|---|---|
$0 | ||||||||
$2,700 | ||||||||
$1,800 | ||||||||
$5,400 | ||||||||
$7,200 |
Set effort to 0 for Standard fits. Review every Custom development row with the sponsor before design freeze.
Gap review with an ERP practitioner
Send your custom development rows and get a short review of what could be configuration or reporting.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List requirements one per row, taken from workshops, not from a wish list. Classify each as Standard, Configuration, Workaround, Custom development or Not supported. Add a priority using MoSCoW style Must, Should and Could. Estimate effort in days for anything beyond Standard and enter your blended day rate. The cost column and totals update. Export to Excel for the design authority and re-sort by cost to see where to challenge the requirement.
- One requirement per row
- Agree fit categories first
- Challenge every custom row
- Name a decision owner
Fit categories explained
Standard means the requirement works with delivered features. Configuration means parameters, workflows or user defined fields satisfy it without code. Workaround means a process change or manual step is accepted. Custom development means new code, extensions or reports are built. Not supported means the business must drop it or buy a third party add on. Count the Custom and Workaround share: a high share of custom rows is a warning that the product or the process design is a poor match.
- Standard: delivered
- Configuration: no code
- Workaround: process change
- Custom: new code
- Not supported: drop or buy
Reading the totals
Total days and cost give you the customization budget to compare against your contingency. A useful rule of thumb many teams apply is to keep Custom development below a small minority of Must requirements, because every custom item adds testing, upgrade and support cost over the life of the system. Also compare the Must rows against the Should rows. If the cost is concentrated in Should and Could items, defer them to a later phase.
Common mistakes
Teams record requirements as solutions, such as build a screen, instead of the underlying need. Others skip the effort for testing and training, understating cost. Another trap is classifying a requirement as Standard without a demonstration in the sandbox. Validate Standard claims with a scripted demo using your own data. Finally, a fit gap is not a one time exercise; update it when scope changes through change control.
Frequently Asked Questions
What is a fit gap analysis?
A structured comparison of business requirements against ERP capabilities. Each requirement is classified as fit or gap, and gaps get a resolution such as configuration, workaround, custom development or dropping the requirement.
When do we do the fit gap analysis?
During selection to compare vendors, and again during the design phase against the chosen system with your own processes and data. The second pass drives the build scope.
How do we estimate custom effort?
Ask the build team for development, unit test, documentation and support estimates, then add functional design and user testing. A single developer number usually understates the real effort.
How many custom items is too many?
There is no universal number, but a growing custom list raises upgrade, support and test costs. Treat each custom item as a standing cost and ask whether a process change would do.
If many gaps are reports and lookups, ask whether natural language access to ERP data could close them without custom code.
Related Tools
ERP Implementation Risk Register Template
An editable risk register for ERP projects. Score each risk by probability and impact, assign an owner and mitigation, then export to Excel.
ERP Migration & SelectionERP Project Change Request Form Template
A change request form for ERP projects that captures the reason, impact on scope, schedule, cost and risk, and the approval decision.
Costing & FinanceERP Implementation Contingency Reserve Calculator
Estimate how much contingency to hold on an ERP project based on complexity drivers such as sites, integrations, data quality and customization.
ERP Migration & SelectionERP UAT Defect Log Worksheet
A defect log for ERP user acceptance testing with severity, owner, status and ageing, ready to export to Excel.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment