Skip to content

Why Field Service isn’t like your other Dynamics 365 projects

Why Field Service isn’t like your other Dynamics 365 projects

A project team sketching a data model on a whiteboard

Picture the project. A partner with a strong Dynamics 365 Sales and Customer Service practice wins a Dynamics 365 Field Service deal, and the plan looks familiar: install the app, adjust some forms, configure a few processes and train the users. The demo goes well and the build feels quick.

Then real work starts. Dispatchers can’t find anyone qualified on the board, parts won’t consume against the job, and invoices don’t match what happened on site. That’s how a rushed “just install it” project turns into a year of fixing what should have been right first time, and it happens more than you’d think.

Why it behaves like ERP, not CRM

In a Sales or Customer Service project, success often comes from tailoring the experience: a new field here, a reworked form there, a flow to fill the gaps, all shaped around how people like to work. Field Service doesn’t reward that approach. It runs on a tightly connected data model of work orders, incident types, resources, skills, bookings, agreements, inventory and locations, and its behaviour follows from how that data is set up and linked.

So when something doesn’t fit, the cause is usually the data model rather than the form. Good scheduling depends on the right resources, skills, territories and working hours, and stock only behaves when products, warehouses and inventory journals mirror the way parts really move. You’re modelling an operation, from request through scheduling, execution and completion to invoice, which is why the project has more in common with an ERP rollout than with a CRM build.

Take a breakdown call. With a CRM mindset it’s a case with a few extra fields. In Field Service it becomes a work order built from an incident type, a requirement for a particular skill in a particular territory, a booking, parts drawn from a warehouse and prices from a price list, and all of it has to line up before anything reaches finance.

Where CRM habits catch teams out

The first surprise is sequence. Field Service data has to go in a particular order, and a system loaded out of order can look healthy right up until it’s used in anger. The second is the estimate, because discovery and data deserve a far bigger share of the plan than they get in a typical CRM project. The third is the people: dispatchers, stores, finance and engineers who may be working without a signal, rather than sales teams at desks. Training, testing and adoption all have to be planned around them.

Most of these habits are visible in the first project plan, long before anything is built. Watch for these signs that a Field Service project is being run like a CRM one:

  • The plan starts with forms and views, not the data model
  • Data loading is a single task near the end
  • Nobody has mapped how stock, agreements and invoicing work today
  • Testing goes screen by screen rather than from request to invoice
  • Engineers are trained last, at a desk rather than on the mobile app

None of these are failures of effort or talent. They’re habits that serve partners well elsewhere in Dynamics 365, and they’re far cheaper to change at the estimate than after go-live.

How we work behind you

We deliver Field Service behind Microsoft partners. Your client relationship stays yours: we work white-label where you need it, we never approach your client, and we don’t name them publicly without written permission. You keep the account and the commercial lead, and we bring the Field Service design, data model, load sequence, scheduling setup, mobile configuration and training the project needs.

The best time to bring us in is at presales or discovery, before the estimate is fixed, so the plan reflects how Field Service really behaves. Our Field Service Starter Kit is the base for every implementation, so your client never begins from an empty environment. Our co-founder Mark Christie is a Microsoft MVP for Business Applications (Field Service), and the team includes MVPs and Microsoft Certified Trainers and has contributed to Microsoft’s certification exams.

Talk to our partner team

Proximo 3 originally posted this article on 18 November 2026 at 7:30 AM.

Leave a Reply