Business Central Implementation Statement of Work Template
A clear statement of work prevents the two classic Business Central project disputes: unclear scope and unclear acceptance. Fill in the fields, review the generated document and export it to PDF or Word as the base of your proposal.
Fill in
Business Central Implementation Statement of Work Template
Statement of Work: Business Central Implementation
Customer: Northfield Precision Ltd Partner: Example BC Partner Inc. Date: 2026-11-02 Product: Microsoft Dynamics 365 Business Central Premium, Cloud SaaS Named users: 35
1. Purpose and objectives
This SOW describes the services Example BC Partner Inc. will deliver to implement Business Central for Northfield Precision Ltd. Objectives: replace legacy systems for the areas below, standardise processes, and go live by 2027-04-01.
2. Scope
In scope: Finance, sales, purchasing, inventory, warehouse, and manufacturing with production orders.
Out of scope: Custom EDI, shop floor data collection, and historical transaction migration beyond open items.
3. Phases and deliverables
| Phase | Key activities | Deliverable | Customer role |
|---|---|---|---|
| Initiate | Kickoff, governance, project plan | Project charter | Sponsor, project lead |
| Analyse | Process workshops, fit-gap | Fit-gap and design documents | Process owners |
| Configure | Setup, extensions, data design | Configured sandbox | Key users |
| Migrate | Trial loads, reconciliation | Signed-off migration | Data owners, finance |
| Test and train | UAT, training, cutover plan | UAT sign-off, trained users | Key users |
| Go-live and support | Cutover, hypercare | Live system, handover | All users |
4. Assumptions and dependencies
Customer provides subject matter experts for 4 hours per week; data is supplied in agreed templates; three trial migrations are included.
The schedule depends on timely customer decisions, availability of subject matter experts and access to the BC tenant and legacy data.
5. Fees and payment
Fee basis: Fixed price per phase. Licence costs are billed separately by the licensing reseller unless stated. Travel and expenses are invoiced at cost with prior approval.
6. Change control
Any change to scope, schedule or fees must be raised in writing, estimated by Example BC Partner Inc. and approved by both parties before work starts.
7. Acceptance
Each deliverable is reviewed by Northfield Precision Ltd within 5 business days. Acceptance is deemed when written approval is given or the deliverable is used in production. Defects against agreed requirements are corrected without additional fee.
Approvals
This is a starting point, not legal advice. Have your own counsel review fees, liability, data protection and intellectual property terms, and attach your master services agreement.
Scope review
Have your SOW scope and assumptions reviewed for gaps before signature. Optional.
Optional. The tool and every export work without this. No spam.
How to use the template
Enter customer and partner names, edition, deployment model and user count, then write scope and exclusions in plain language. Choose the fee basis that matches your commercial agreement. The document structure follows common ERP delivery phases: initiate, analyse, configure, migrate, test and train, and go-live with hypercare. Export, then edit the tables to your methodology and add module-specific deliverables.
What makes a BC SOW strong
Be specific about modules, such as Finance, Sales, Purchasing, Warehouse, Manufacturing and Service, and about integrations, reports and extensions. Say how many trial migrations are included and what data volume is expected, because migration is where fixed price projects overrun. State the number of training sessions and who delivers them. Name the environments: sandbox for configuration and testing and production for live use.
- List integrations one by one with direction and frequency
- Specify reports as new, standard or modified
- Define hypercare duration and response expectations
Fixed price versus time and materials
Fixed price per phase works when requirements are well understood after analysis. Time and materials fits exploratory work or heavy customisation. Many partners fix the analysis phase and then fix later phases against the signed fit-gap, which aligns risk with knowledge. Whatever you choose, change control must be in the same document.
Common mistakes
Vague acceptance language is the biggest risk: define who reviews, how long they have and what counts as a defect versus a change request. Do not leave data migration as an assumption without volumes. Do not forget customer obligations; a project lacking subject matter expert time slips regardless of the partner's skill.
Frequently Asked Questions
Is this SOW legally binding as exported?
It is a template and a starting point. It becomes binding only when signed under an agreement your legal advisers have reviewed. Add your master services agreement terms, liability caps, data protection clauses and governing law before use.
Should the SOW include licence costs?
Business Central licences are normally sold through a Microsoft partner under a separate agreement. State clearly whether licensing is part of this contract. Most SOWs cover services only and reference licence quantities as an assumption.
How detailed should the scope be?
Detailed enough that a stranger could tell whether a requirement is in or out. Name modules, integrations, reports, extensions and migration objects. Use an exclusions list; it protects both sides more than a long list of inclusions.
Can I use this for an upgrade or a NAV migration?
Yes, but adjust phases. Upgrade projects need a technical assessment, code and extension conversion, and data upgrade trials. Replace the Analyse and Configure rows with those activities and keep the change control and acceptance sections.
Netray works with BC and ERP partners on data migration, reporting and AI assistants. If you want a second pair of eyes on a scope document, ask for a review.
Related Tools
Business Central Functional Design Document Template
Document a Business Central customisation, report or integration with requirement, standard behaviour, gap, design, test and sign-off sections.
Microsoft DynamicsBusiness Central User Acceptance Test Script Template
A UAT script for Business Central processes such as order to cash and purchase to pay, with steps, expected results and sign-off.
Microsoft DynamicsBusiness Central Go-Live Cutover Plan Template
A cutover runbook for moving to Business Central: freeze, extract, load, reconcile, go/no-go decision, hypercare and rollback.
Microsoft DynamicsBusiness Central Data Migration Field Mapping Worksheet
Map every legacy source field to a Business Central table and field, record the transformation rule and volume, and see how much data is ready to load.
More Microsoft Dynamics tools
See all- Business Central API v2.0 URL Builder
- Business Central Configuration Package Worksheet
- Business Central Permission Set Design Worksheet
- Business Central Year-End Close Checklist
- Business Central Posting Groups Setup Worksheet
- Business Central Chart of Accounts Mapping Worksheet
- Business Central License Cost Calculator
- Business Central Core Table Numbers Reference
- Business Central Item Setup Options Reference