Dynamics 365 Fit-Gap Analysis Document Template
A fit-gap document turns a list of business requirements into a decision for each: use standard, configure it, extend it, buy an ISV or change the process. This template gives you the structure and a worked example row.
Fill in
D365 Fit-Gap Analysis Document Template
Fit-Gap Analysis: D365 Finance and Supply Chain Rollout
Customer: Northfield Precision Components Ltd Prepared by: Functional consultant Date: 2026-10-20 Functional area: Production control
Scope and assumptions
Two legal entities, discrete manufacturing with make-to-stock and make-to-order items, standard D365 production control, no customisation unless approved.
Classification key
Fit (standard): met by out-of-the-box features. Fit (configuration): met by parameters, setup or personalisation. Gap (extension): needs custom development in an extension. Gap (ISV): needs a third-party solution. Gap (process change): business changes the process to match the system. Out of scope: removed by agreement.
Requirement register
| ID | Requirement | Classification | Proposed solution | Effort (days) | Priority |
|---|---|---|---|---|---|
| PC-014 | Report operation quantities at the shop floor terminal and update the production order automatically. | Fit (configuration) | Use the production floor execution interface with job cards, configure the reporting parameters and worker registration. | 3 | Must |
Risks and dependencies
| Risk or dependency | Impact | Owner | Mitigation |
|---|---|---|---|
Approvals
A starting point for project documentation, not a contractual document. Align classification labels and effort estimation rules with your implementation partner's methodology.
Legacy customisation mapping
Optional: an expert maps your legacy customisations to D365 standard features and likely extensions.
Optional. The tool and every export work without this. No spam.
How to use it
Fill in the project header, the functional area and the scope assumptions. Then record each requirement with an identifier, its classification, the proposed solution and an effort estimate in days. Duplicate the table row pattern for each requirement, or export to Word and extend it. Keep one document per functional area so owners can review their section and sign it off separately.
Choosing the classification
Be strict about what counts as a fit. A requirement that needs a parameter change is a configuration fit, but one that needs a new field and a business rule is an extension. Prefer changing a process to building a customisation when the business benefit is small, because every extension adds testing and upgrade work, especially with continuous service updates in D365.
- Fit means no code
- Extension gaps need design, build and regression testing
- ISV gaps need licensing and support terms
- Process change gaps need business sign-off
What a good register looks like
Each line is testable: it states what must happen and by whom. Link requirement IDs to process maps and to test cases so coverage can be shown at the end of the project. Capture the reason for every gap decision. Review the effort total by area to spot where the project risk concentrates, and revisit estimates after design workshops, since they usually move.
Common mistakes
Writing requirements as solutions, such as 'add a field', hides the real need. Classifying without a demonstration leads to hidden gaps found in testing. Leaving priority blank makes scope negotiation harder later. Skipping approvals means the register has no authority when a change request arrives. Version the document and keep a change log as decisions evolve.
Frequently Asked Questions
What is a fit-gap analysis?
It compares business requirements with what the ERP does out of the box and records whether each requirement is met by standard features, configuration, custom development, a third-party product or a changed process.
When do I do it?
Usually during the analysis or solution modelling phase, after process workshops and before design and build. It drives scope, estimate and the decision on extensions and ISV products.
How do I estimate effort for gaps?
Estimate design, build, unit test, documentation and support separately, and add contingency. Many teams size extensions by complexity bands agreed with the partner rather than by guesswork on every line.
Can I export to Excel?
The requirement register table exports with the document. For large projects, many teams keep the register in a spreadsheet or tracking tool and use this document as the summary and approval record.
If you hold large requirement lists or legacy customisations and want them mapped to D365 standard features faster, Netray can help with private AI analysis alongside your implementation partner.
Related Tools
D365 Data Migration Cutover Duration Calculator
Estimate how many hours your D365 go-live data load will take, including rework and reconciliation, and whether it fits the cutover window.
Microsoft DynamicsD365 Finance and Supply Chain License Cost Calculator
Estimate monthly, annual and term cost for D365 Finance and Supply Chain users, including attach licenses, team members and discount.
Microsoft DynamicsD365 Batch Job Window and Runtime Calculator
Estimate how long a D365 F&O batch job will take for a given record volume and thread count, and whether it fits the nightly window.
Microsoft DynamicsD365 Trade Agreement Price and Margin Worksheet
Plan sales price lines and trade discounts per item, see the net price, extended revenue and margin, and export the worksheet to Excel.
More Microsoft Dynamics tools
See all- D365 Item Coverage Min Max and Safety Stock 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
- D365 Master Planning Setup Checklist
- D365 One Version Update Test Checklist