Infor M3 Fit-Gap Analysis Worksheet
A fit-gap worksheet is where an M3 implementation either stays honest or quietly grows. This one lets you log every requirement, classify how M3 will meet it, and put a day count and cost next to it before the contract is signed.
| Req ID | Requirement | M3 area | Resolution | Priority | Effort (days) | Day rate | Estimated cost | Owner | |
|---|---|---|---|---|---|---|---|---|---|
$3,600 | |||||||||
$900 | |||||||||
$7,200 | |||||||||
$14,250 | |||||||||
$2,700 | |||||||||
$5,100 |
Add one row per requirement. Filter the exported Excel by Resolution to produce the gap list for sign-off. Day rates and efforts shown are illustrative placeholders.
Optional fit-gap review
Send your exported worksheet and an M3 practitioner will comment on the riskiest rows.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Run the fit-gap in workshops by process area, not by department. For each requirement, record the business statement in plain language, the M3 area it touches, and one resolution. Resolve in this order: standard fit, configure, process change, extend, integrate, custom development. Enter effort in days for the build and test, then the blended day rate. The cost column calculates itself and the totals update as you add rows. Export to Excel to share with the steering group or attach to the statement of work.
- One requirement per row, written as a verb plus an outcome
- Always assign a priority so Could items can be dropped under pressure
- Name an owner who can say yes or no on the business side
- Re-baseline after each workshop and keep version history
Choosing the right resolution
Standard fit means M3 does it with the base setup of programs such as customer order, purchase order and item master maintenance. Configure means settings, order types, status levels, number series, approval or document layouts change but no code is written. Extend covers H5 Client scripts, Infor OS or Mashup style front-end changes, and extensions that stay upgrade safe. Integrate means data moves through MEC, ION or MI APIs. Custom development should be the last resort, because it carries upgrade and support cost for the life of the system.
- Prefer process change when the legacy behavior has no business value
- Label anything that touches M3 base tables as high risk
- Count integration separately from extension so effort is not hidden
Reading the totals
The total days and cost give you the delta between the base license scope and the real project. Look at the share of rows marked custom development or integrate: a large share is a signal that the process design needs another pass. Compare the average effort per requirement against your past projects. If one area such as warehouse or manufacturing holds most of the days, plan a dedicated design owner for that area and schedule it first in the project plan.
Common mistakes
Teams often log solutions instead of requirements, which forces a gap by default. Others forget test effort, data conversion for new fields, training and documentation. Another frequent mistake is marking items Standard fit without anyone demonstrating them in the configured sandbox. Treat a fit as unproven until a consultant has shown it in the system with the customer data.
Frequently Asked Questions
What is a fit-gap analysis in an Infor M3 project?
It is a structured comparison of business requirements to what M3 does with standard functionality and configuration. Each requirement is classified as a fit, a configuration, an extension, an integration or a true gap, and costed so the project scope and price reflect reality.
Should I include process changes in the worksheet?
Yes. A requirement resolved by changing the business process still needs an owner, training and communication effort. Logging it keeps the work visible and shows leadership how many legacy habits are being retired rather than coded into M3.
How granular should requirements be?
Granular enough that one row can be tested with one scenario. Avoid rows like 'handle sales orders'. Prefer 'apply customer specific price with quantity break on order line'. Smaller rows give better estimates and clearer test cases later.
Can I import this into my project tool?
Export to Excel or CSV and import it into your tracker of choice. The Req ID column is meant to carry through to functional specs and test scripts so you keep traceability from requirement to test result.
If your requirement list is long and you want help checking it against how M3 really behaves, Netray partners can review the worksheet and flag items that are likely cheaper than they look.
Related Tools
Infor M3 Functional Specification Template
Fill-in functional specification for an M3 enhancement, interface or report, ready to export as a Word or PDF document for sign-off.
Infor M3 & CloudSuiteInfor M3 Implementation Effort Estimator
Rule of thumb calculator for M3 implementation effort from scope drivers, with cost, team size and duration, plus a chart by site count.
ERP Migration & SelectionInfor M3 Data Conversion Mapping Worksheet
Track every legacy field to M3 target mapping with transformation rule, owner, record counts and cleansing status in a single table.
Infor M3 & CloudSuiteInfor M3 User Acceptance Test Script Template
Fill-in UAT script with scenario, preconditions, step table, results and sign-off for M3 end to end process testing.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 H5 Script Review Checklist
- Infor M3 Upgrade Test Checklist
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Interface and Integration Inventory Worksheet