D365 Finance and Supply Chain Fit-Gap Analysis Worksheet (Excel Export)
A fit-gap register is the document that decides how much of a D365 Finance and Supply Chain project is configuration and how much is development. This worksheet keeps the register, sizes each gap, and totals cost as you edit.
| Req ID | Area | Requirement | Fit type | Priority | Build hours | Rate per hour | Gap cost | |
|---|---|---|---|---|---|---|---|---|
$0 | ||||||||
$6,000 | ||||||||
$900 | ||||||||
$3,600 | ||||||||
$2,400 |
Set Build hours to 0 for Standard fits. Filter the exported file by Fit type to produce the customization shortlist for the steering committee.
Review your fit-gap with an ERP expert
Optional: a short review of your register to spot hidden customization and upgrade risk.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List each requirement on its own row with a short ID. Classify the fit type honestly: Standard if the process works out of the box, Configuration if parameters, workflows or setup solve it, Personalization for user-level interface changes, Extension for developer-built changes, ISV where a third-party solution covers it, and Not supported where the business must change the process. Enter build hours and a blended rate, and the cost column calculates automatically.
- One row per testable requirement
- Mark priority with Must, Should, Could
- Use the same Req ID in your FDDs and test cases
- Export to Excel for the steering committee pack
Reading the totals
Watch the share of total hours that sits in Extension rows. A high share suggests the business process is not yet aligned to standard D365, which raises upgrade, regression and support burden under One Version continuous updates. Compare hours for Should and Could rows to the budget, because these are the first candidates to defer. Average hours per requirement is a sanity check, not a target.
Method and honesty in classification
Good fit-gap sessions are run against a configured baseline, not slides. Demonstrate the process in a prototype or a Microsoft-provided demo environment and ask users to confirm. Consultants tend to under-estimate extension hours by omitting design, code review, unit tests, deployment and documentation, so apply a loading factor when you convert coding hours to build hours.
Common mistakes
Teams often treat a wish as a requirement, record a fit that has not been demonstrated, or hide gaps under the Configuration label. Also avoid mixing reporting needs with transactional gaps: many reporting requirements are solved by Excel add-in, workspaces or Power BI without code. Review the register again after every major design workshop.
Frequently Asked Questions
What is the difference between a fit-gap and a gap analysis?
A fit-gap compares business requirements with what the ERP does in standard form, then sizes the difference. A broader gap analysis can compare any current and target state, including process, skills or data. On D365 projects the terms are often used interchangeably.
How many requirements are typical?
It varies widely by scope. A single-entity manufacturer may log a few hundred, while a multi-country rollout can reach several thousand. Quality matters more than count: every row should be testable and have an owner.
Should integrations be on this register?
Yes, but many teams track them in a separate interface register for detail. Keep a summary row here so effort appears in the total, and cross-reference the interface ID.
Can I import this into Azure DevOps?
Export to Excel or CSV and use the Azure DevOps Excel integration or import tools to create work items. Map Req ID to a custom field so you retain traceability between requirement, design and test.
If your fit-gap list lives in several spreadsheets, Netray can help build a private assistant that matches new requirements against your past gaps and standard D365 capability, with consultant review on every answer.
Related Tools
D365 Finance and Supply Chain Functional Design Document Template
A fill-in functional design document for a D365 F&O gap, covering requirement, process, data, security and test approach, with sign-off lines.
Microsoft DynamicsD365 Finance and Supply Chain Implementation Effort Estimator
A rough-order estimate of D365 F&O implementation hours and cost from modules, legal entities, integrations, extensions, migration objects and reports.
Microsoft DynamicsD365 Finance and Supply Chain UAT Test Case Worksheet
An editable UAT tracker with process area, scenario, expected result, tester, result and defect reference, with pass-rate totals.
Microsoft DynamicsD365 Finance and Supply Chain Integration Interface Register
An editable interface inventory for D365 F&O with pattern, direction, frequency, volume and owner, summing daily message volume.
More Microsoft Dynamics tools
See all- D365 F&O OData URL Builder
- D365 Data Management Import Worksheet Template
- D365 Batch Job Checklist
- D365 Security Role Design Worksheet
- D365 One Version Update Test Checklist
- D365 Finance and Supply Chain Data Migration Mapping Worksheet
- D365 Finance and Supply Chain Cutover Plan Template
- D365 Finance and Supply Chain Change Request Form Template
- D365 F&O Inventory Dimensions Reference