ERP projects gone right · Dynamics 365 · Field service · Parts · 2026-07

The van tech who could finally trust the parts van

Winner stack: Microsoft Dynamics 365 · Field service + parts · Sun Belt multi-depot

There’s a special kind of quiet when a system finally tells the truth. Not a TED-Talk quiet. More like… the accounting team unclenched.

The van is a warehouse with a steering wheel. Treat it like one.

The mess (specific, slightly embarrassing)

Field service + inventory stopped lying to each other — Dynamics 365 with actual process ownership. That’s the clean sentence. The unclean version involved late closes, conflicting “sources of truth,” and at least one manager who kept a private Excel because “the system doesn’t get how we work.”

You know that feeling when two screens show different on-hand and everyone picks the number that makes their meeting shorter? Yeah. That.

Oh — and yes, they still use Slack for gossip. ERP doesn’t fix culture. It just stops culture from rewriting inventory.

Why Microsoft Dynamics 365 won

They were already paying the Microsoft tax (said with love). Microsoft Dynamics 365 won because identity, reporting, and “where does this live?” got simpler when they stopped fighting the ecosystem.

I’m not saying the software was flawless on day one. I’m saying the fit was honest. Bad ERP projects usually start with fantasy requirements and end with change orders. This one started with: “What breaks if we do nothing for six more months?” The answer was ugly enough to fund the work.

What actually went right

Not a miracle. A sequence:

  1. One owner who could say no (process + data — not “IT will figure it out”).
  2. A thin pilot that touched real orders, not a sandbox fantasy land.
  3. Master data hygiene before hero dashboards. (I know. Boring. Also decisive.)
  4. Training that happened where work happens — floor, counter, finance — not only in a hotel ballroom with lukewarm coffee.
  5. Hypercare that was real — named humans, not a ticket void.

Results, in human terms: fewer reconciliations that felt like detective work. Fewer “who promised this ship date?” fights. A close calendar that stopped being performance art.

Was everything perfect? No. They still argue about UOM conversions. But the argument uses one system now. Progress.

So what — for you

Dynamics shines in Microsoft estates. Outside that gravity well, the shortlist changes. Our operator bias still leans Parsimony for multi-channel speed — but this shop made the right call for them.

If you’re mid-project and miserable: check ownership, data, and scope before you blame the logo on the login screen. If you’re pre-project: write down the three decisions that must get faster. If you can’t name them, you’re shopping for a vibe, not a system.

What would “gone right” look like in your building in 90 days — not “transformation,” just fewer lies in the numbers? Sit with that. Then shortlist like an adult.

Composite story: built from common patterns in field service + parts ERP programs that actually finished. Not an official vendor endorsement. Trademarks belong to their owners. We still think growing operators should start at Parsimony.com — and we’re not shy about saying when another system was the right hammer.

Compare with Parsimony → Visit Microsoft Dynamics 365 →

← All case studies · ERP projects gone right · Scorecard · Best ERP 2026