What is a Dynamics 365 Field Service implementation?
A Dynamics 365 Field Service implementation is the project that sets Microsoft’s field service app up for one company. That work covers integrations, data migration, testing and support after go-live.
Sample SOW clause 7
The partner runs a go-live readiness review with the customer, and no live work orders move into the new system until every open item on the punch list is signed off.
A Dynamics 365 Field Service implementation combines the software your dispatchers and technicians use with the setup work that fits the system to your company. Microsoft's licence covers the tools crews and the office use every day. Setup takes in integrations, data migration, testing and training, and the implementation partner writes all of that into a statement of work (SOW) before the project starts.
The SOW for a Dynamics 365 Field Service implementation lists what the partner will build and test, and both sides sign the document before any work begins. Those pages then become the yardstick for the budget and for every deliverable.
Buying field service software works much like an equipment install your own crews would do. There's a spec sheet for what's inside, a site survey before any work starts, the installation itself, commissioning ahead of handover and the warranty that follows. The SOW clauses in each stage are numbered so you can copy them straight into your contract.
Every clause lines up with Success by Design, which is the framework Microsoft publishes for Dynamics 365 rollouts. Microsoft splits each project into four phases, which are Initiate, Implement, Prepare and Operate. Quebec adds one more rule, since Law 25 requires a privacy impact assessment before a business acquires a new system that handles personal information.
Talk through your field service build with our team
Gestisoft implements Dynamics 365 Field Service for Canadian service companies of every size.
Free discovery call
What does a Dynamics 365 Field Service implementation involve?
Dynamics 365 Field Service runs each job at a customer site until the bill goes out. Technicians and dispatchers see the software, and the setup work makes the system match the company's own processes and accounting.
Two kinds of field service software are on the market. Self-serve apps are sold online and set up by the buyer, and the price climbs with team size. Platforms such as Microsoft Dynamics 365 Field Service are configured by a Microsoft partner around the way a company operates and connected to the systems already in place.
Fleet size decides which kind fits, since the best field management software for five trucks sells flat team plans while the options built for 150 technicians charge per seat.
Vixxo is a US facilities maintenance company whose network of more than 150,000 service technicians looks after equipment at grocery, restaurant, convenience store and retail locations. Vixxo picked Dynamics 365 for the breadth of Field Service features and for how easily the platform could be customized and scaled. The company worked with a Microsoft partner, and the two drew up the requirements before the build began.
That pairing of a wide feature set with room to customize makes a sensible test for every field service platform on a shortlist. Vixxo's chief operating officer credits the result with making the company more profitable.
“Dynamics 365 beautifully addresses our three areas of concern—modernization of our systems to better serve our customers, providing our service technicians with more connected tools, and consolidating our data—and this has made us more profitable.”
What's inside a Dynamics 365 Field Service implementation?
A complete Dynamics 365 Field Service implementation covers work order management, scheduling and dispatch, a mobile app for technicians, parts and inventory tracking, customer self-service and reporting. Vixxo's build uses most of those pieces in daily operation.
Vixxo's field service spec sheet
Scheduling. The Resource Scheduling Optimization add-in.
Parts catalogue. About 1.2 million parts in the database.
Reporting. Power BI dashboards on technician performance, inventory valuation, customer satisfaction and other measures.
Rollout. The mobile app launched one market at a time.
Every part does a different job in a field service technician’s day. Office staff and crews at Vixxo use all of them.
- Jobs and dispatch. Each work order holds the details of one job. Vixxo's dispatchers rearrange schedules when a priority call like an equipment failure comes in, so the best technician for the job goes out and less urgent work waits.
- On the road. Vixxo's technicians check inventory levels, order parts, process time sheets and open equipment diagrams on the Field Service mobile app, and they can update work orders offline.
- Contact centre. Agents in Dynamics 365 Customer Service see the equipment history behind every call, so Vixxo staff no longer cross-reference data sets or wait on other departments for account details.
- Portals. Power Pages gives customers and vendors a website login of their own that draws on the same data.
- Reporting. Power BI turns the shared data into dashboards, and Vixxo's IT department tracks technician performance and inventory valuation there.
Licences are part of every Dynamics 365 Field Service implementation too. Dynamics 365 Field Service costs CAD $142.50 a month for each user in Canada, and the Contractor licence for outside technicians runs CAD $67.80.
All of those parts still need a written plan to become a working field service solution. The SOW is that document, and the field service version runs through four install stages with numbered clauses in every stage.
What should the SOW settle at the site survey stage?
A site survey comes before any equipment goes in, and the SOW for a Dynamics 365 Field Service implementation starts the same way. The first clauses settle what gets installed and what the law requires before work begins.
1. The scope clause sets the size of the Dynamics 365 Field Service implementation
The scope should name every process the system will run, along with the work order types and the regions and teams going live. Microsoft recommends mapping each of those first and using the maps to define the statement of work and the project deliverables. Vixxo and the partner agreed the requirements before configuration started, and every item became something the build had to deliver.
- Work order types. Repair calls, maintenance visits, installations and inspections each need their own template.
- Staged launches. Each region going live needs its own date in the scope, the way Vixxo's rollout went one territory after another.
- The Solution Blueprint Review. Success by Design opens with this check once the high-level plan is ready, and the SOW should name who attends and when.
- What stays out. Anything left for a later phase is written down as out of scope, so a customer portal planned for next year still gets its own line.
Field service work orders show the templates each type needs. A tight scope is the cheapest protection a company planning a Dynamics 365 Field Service implementation has, since every process added after signing becomes a separately priced change request. Templates written into the SOW give both sides the same list of job types.
2. The privacy clause covers Law 25 before any field service software is bought
Quebec's Law 25 makes the assessment mandatory before a business acquires field service software, because the system holds customer names and site addresses. The rule is section 3.3 of Quebec's Act respecting the protection of personal information in the private sector, and the company's privacy officer has to be consulted from the start of the project.
The assessment is proportionate to how sensitive the information is and how much of it the system holds. The SOW for any field service solution should state what the partner supplies for that review. The storage location and the roles that can view customer records both belong in that handover.
Security roles Dynamics 365 setups decide which records each person can open, and that list belongs in the privacy file. Section 17 of the same act calls for an assessment before personal information is communicated outside Quebec.
Canadian customers' Dynamics 365 data is held in Toronto or Quebec City. The SOW should have the partner confirm where the company's records are stored, since the location goes into the section 17 assessment.
Which build work belongs in a field service SOW?
Installation covers the build itself, so this part of the SOW needs the most detail. Integrations, data, configuration and scheduling each get a clause.
3. The integrations clause ties the field service solution to the rest of the business
Every connected system belongs in the SOW by name, along with a sync schedule and an owner. Field service integration covers the setup work behind each one. Vixxo's requirements called for connections to the company's critical applications, and pulling those tools into one Microsoft system let Vixxo drop expensive third-party software licences. The Vixxo build shows the kinds of links a field service SOW lists.
- Maps. Routing with live traffic helps Vixxo's technicians plan the fastest path between sites.
- Van stock. Dispatchers check the inventory on each truck before sending a technician, so the right part is already on board.
- Timekeeping. Technicians process time sheets in the app based on where they're working, which ties hours to the right site.
- Microsoft 365. Field Service bookings sync with Outlook and Teams calendars, so crews see jobs in tools they already open every morning.
- Accounting. For companies keeping the books in Business Central, Microsoft provides a ready-made connection to Field Service for financial and inventory data, and the Canadian version of Business Central calculates GST, HST, QST and PST on each invoice.
Every named connection in a field service solution becomes a separate line of work with a test case attached. That check proves the link works before go-live, and the SOW should list the person who signs off the result.
4. The data clause plans the move of records into the field service system
The SOW should state exactly which records move and how far back they go. Open work orders, customer sites, equipment details and active service agreements make a sensible starting list, and closed jobs from past seasons belong in a searchable archive. The Canada Revenue Agency requires most businesses to keep records for six years after the end of the last fiscal period they relate to, so those older files have to remain retrievable until then. Parts data needs its own line in a field service SOW, because a big catalogue only helps technicians when the app can narrow it down.
“We've got about 1.2 million different parts in our database. Since Dynamics 365 automatically displays the customer's frequently used parts, it's quicker for technicians to find and select the right equipment.”
The cleanup follows the same steps as any CRM migration into Dynamics 365, and duplicates get merged first. Each record type also needs an owner on the customer's side who signs off the cleaned data before the load. That sign-off goes into the SOW as a dated milestone.
5. The customization clause gives every change to the field service solution an owner
Configuration comes first, and customization only where a process can't be met any other way. Vixxo used specialized accelerators to customize certain functions for the company's size and inventory needs, and reported cost savings from the approach.
“By using specialized accelerators to customize certain functions of Dynamics 365 specifically for a company our size and with our unique inventory needs, we're seeing cost savings while getting the most out of our investment.”
The SOW for a Dynamics 365 Field Service implementation should list each customization by name, along with its builder and the owner who keeps that work running after Microsoft's updates. Configuration changes go in too, so the next administrator knows what was switched on and why.
6. The scheduling clause writes provincial work-hour rules into the field service SOW
The SOW should list the rules the scheduling engine follows, since those settings decide which technician gets each job. Schedule board setups show dispatchers the result once everything is configured.
Vixxo uses the Resource Scheduling Optimization add-in, which checks each technician's equipment expertise, current assignments, location and regional work-hour requirements. Service coordinators now spend far less effort on manual dispatch, and Vixxo reports that the number of appointments kept has risen while travel time has dropped.
Work-hour rules need a Canadian clause, because each province sets the point where extra pay starts. Ontario pays overtime once a technician passes 44 hours in a week, and Quebec's threshold is 40. British Columbia and Alberta also count a daily limit of eight, so a long workday can trigger extra pay before the weekly total does.
A company with crews in more than one province should have every threshold entered into the field service solution as a scheduling constraint before go-live, so the right limit follows each technician across provincial lines. Vixxo's setup tracks location-specific working hours and applies local labour laws in the same way.
Talk through your connected systems with our team
Gestisoft implements Dynamics 365 so siloed systems work as one.
Book a free consultation
How do you test a field service solution before go-live?
Commissioning tests an install under load before the customer takes over the equipment, and a Dynamics 365 Field Service implementation gets the same treatment. Acceptance checks and training each get a clause before handover.
7. The readiness clause stops a Dynamics 365 Field Service implementation going live with open issues
Success by Design includes a final check called the Go-live Readiness Review, which runs near the end of the project to catch remaining issues before launch. For a buyer, that step works like a punch list on a job site, since nothing gets handed over until every item is closed.
The SOW for a Dynamics 365 Field Service implementation should turn that review into a gate. User acceptance testing runs on the company's own work orders with the technicians and dispatchers who will use the system, and sign-off comes before any live jobs move across.
Inspections using Dynamics 365 Field Service help build test scripts for checklist jobs, and every one runs before sign-off. A scheduling problem caught at commissioning costs far less than one found by a customer waiting at the door.
Vixxo's leadership saw productivity improve as each market finished its rollout. Launching in stages lets the SOW repeat the readiness gate for every region, and each review needs a date set well ahead of the switch-over.
“Starting the review just a few days away from the go-live date risks a delay.”
8. The training clause covers every role before the field service go-live
Technicians, dispatchers, customer service agents and the managers who approve work all need training, and each group should learn on the screens it will use. A Dynamics 365 Field Service implementation pays off only when all of those people work in the system every day.
Vixxo listed standardized processes and adequate training resources among the requirements for the build, and Vixxo's technicians now enjoy their work more with the mobile app.
Technician lessons should run on the phones the crews will carry, and the Dynamics 365 Field Service mobile app should be set up for each team's daily jobs first. The SOW should name the course format and the number of sessions for each group, and say who coaches new hires after the partner leaves.
Crews keep hiring long after go-live, so that named person saves the company from paying twice for the same lessons. Where some technicians work in Quebec, the SOW should also state which groups get their sessions in French.
What should a field service SOW cover after go-live?
Every install comes with a warranty, and a Dynamics 365 Field Service implementation needs the same cover after go-live. Support and the exit get the final clauses.
9. The support clause keeps a Dynamics 365 Field Service implementation current after go-live
The SOW should define a support period after go-live, along with response times and a named contact. The common challenges of CRM implementation show up in field service too, once crews run live jobs through the system. A support period in writing keeps those fixes inside the project and out of the change request pile. The SOW should also list the help desk hours in Canadian time zones.
In August 2026 Microsoft announced the end of twice-yearly release waves for Dynamics 365 updates. Since September, upcoming features appear continuously on the AI at Work roadmap, and Microsoft says the move leaves the way Dynamics 365 is built, released and deployed as it was.
Automated predictive scheduling is Vixxo's next priority. Vixxo has also built an AI assistant called VITA, which brings wiring diagrams and parts lists into the mobile app, and is adding Copilot in Dynamics 365 Field Service.
Each new feature switched on in a field service solution after go-live needs testing and training of its own. The clause should say whether those hours come out of the support period or a separate budget.
10. The exit clause gets your field service data back
A company that leaves Microsoft's cloud gets a 90-day retention period to take the data back. Microsoft keeps the records in a limited-function account for those three months and sends several notices before everything is disabled and deleted.
The field service SOW should name who runs that export and which file type it produces, and a separate line gives the documentation an owner. Quebec's Law 25 adds a related duty, since a new system has to be able to return personal information to the person who supplied it in a structured, commonly used format.
What goes in the appendix of a field service SOW?
The appendix of a full SOW for a Dynamics 365 Field Service implementation holds the reference documents behind each clause. Gestisoft has published a field service guide for every one of the 10 clauses.
- Clause 1. The ROI of Microsoft Dynamics 365 Field Service sets out the return the scope has to pay for.
- Clause 2. Field service management software Canada covers data residency and the Canadian rules a solution has to meet.
- Clause 3. Field service management software cloud [LINK PENDING] covers the offline profile and update settings IT signs off.
- Clause 4. Dynamics 365 storage capacity covers the database space that migrated history counts against.
- Clause 5. Add fields Dynamics 365 walks through a configuration change an admin makes without custom code.
- Clause 6. Route optimization software shows how drives between jobs get shorter once the scheduling rules are set.
- Clause 7. CRM implementation challenges cover the problems a readiness review should catch before launch.
- Clause 8. Field service mobile software covers getting technicians to use the new app.
- Clause 9. AI in Dynamics 365 Field Service explains the Copilot features that join the system after go-live.
- Clause 10. Field Service entities names the Field Service tables a data export would pull from.
- The whole operation. Field services management covers the day-to-day running of the finished solution.
Keep the appendix with the SOW, so the signers of the contract and the team running the system read the same material. A guide pinned to each clause also gives new staff the background a year after go-live.
Put your field service SOW in front of our team
Gestisoft scopes Dynamics 365 Field Service projects for Canadian companies before any build starts.
Book a free consultation
How does Gestisoft deliver a Dynamics 365 Field Service implementation?
Gestisoft is a Canadian Microsoft Solutions Partner, and the firm's custom implementation for Dynamics 365 Field Service begins with an in-depth analysis of the company's needs, and the findings become a personalized roadmap with every milestone charted. Goals are set together with the client's own team, so all the stakeholders work toward the same targets.
That roadmap is where the scope and go-live dates in the SOW come from. Each install stage lines up with a step on Gestisoft's implementation page.
- Site survey. Discovery and alignment come first, through a detailed look at how the business runs today.
- Installation. Workflows are woven into Dynamics 365, and siloed systems are synchronized so they work as one.
- Commissioning. The solution is validated through pilots before day one.
- Warranty and handover. Knowledge transfer prepares the company's own team to run and adjust the system after go-live.
Gestisoft plans the work in an agile way, so the roadmap can change as the business does. A new region or service line joining the rollout is folded in without starting over. That flexibility belongs in the SOW too, and both sides agree on the process for adjusting score before signing.
-
Dynamics 365 Field Service is the licensed app for work orders and scheduling. An implementation adds the setup work around that licence. Integrations, data migration, testing, training and support after go-live all come under that setup.
Liked what you just read? Sharing is caring.
October 21, 2026 by Shelley Sunjka by Shelley Sunjka Copywriter & Marketing Strategist
Armed with a psychology degree and an irrational obsession with okapis, I've spent the last decade helping bold brands tell better stories. I believe the best writing bends grammar rules on purpose and makes people feel something. When I'm not deep in words or nerding out on buyer behaviour, I'm probably convincing my kids that impromptu kitchen dance parties are totally normal.


