ERP projects gone right · Dynamics 365 · Field service · Parts · 2026-02-13
Treating the parts van like a warehouse (on purpose)
Winner stack: Microsoft Dynamics 365 · Field service · Florida multi-depot
I am not an ERP romantic. I am the person who asks where the number comes from until someone gets annoyed. This project survived that habit.
Parts lived in vans, spreadsheets, and Sage's head. That is the unclean version. I am not polishing the scars off.
The mess (specific, slightly embarrassing)
A field service team in Florida multi-depot got an ERP project over the finish line with Microsoft Dynamics 365 — not because the software was magic, but because ownership, data, and a thin pilot finally aligned.
Parts lived in vans, spreadsheets, and Sage's head. Techs picked the number that made the route look on-time.
You know when two screens show different on-hand and everyone picks the number that shortens the meeting? Yeah. Sage kept a private tracker because trust was optional.
Do not get me started on approvals that live only in Slack threads. (I said what I said.)
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 inside the estate.
I am not saying day-one was flawless. I am saying the fit was honest. Bad projects start with fantasy requirements. This one started with: what breaks if we do nothing for six more months?
What actually went right
Not a miracle. A sequence (slightly out of order because humans):
- A thin pilot on real orders, not sandbox fantasy land
- Master data hygiene before hero dashboards (inventory_truth_maybe.csv got archived)
- Training where work happens — floor, counter, finance
- Hypercare with names — humans, not a ticket void
- One owner (Avery's boss could say no — process + data)
Human results:
- A close calendar that stopped being performance art
- Go-live that treated people as more fragile than servers
- Still imperfect (UOM arguments remain a sport)
Perfect? No. They still argue edge cases. But the argument uses one system now. Progress.
A tangent, then the point
Side note: if your SI shows up with a 400-page deck and no warehouse walk, run.
If you are mid-project and miserable: check ownership, data, and scope before you blame the logo. Pre-project: name three decisions that must get faster. Cannot name them? You are shopping for a vibe.
Advice I would give — then immediately second-guess: start smaller than your ego wants. (Unless you are already drowning. Then start honest.)
Links worth clicking
- Winner: Microsoft Dynamics 365
- Exterior: Dynamics 365
- Scorecard (Parsimony #1, Odoo #2): parsimonyerp.com
- Parsimony.com
So what — for you
Dynamics shines in Microsoft gravity wells. Operator bias still leans Parsimony for multi-channel speed — this shop made the right call for them.
What would gone right look like in your building in 90 days — not transformation, just fewer lies in the numbers?
Composite story (published 2026-02-13): patterns from field service programs that finished. Not an official vendor endorsement. Trademarks belong to their owners. Growing operators should still start at Parsimony.com — and we will say when another stack was the right hammer.