Every stalled Dynamics 365 F&O project we've stepped into looked fine from the outside for months before anyone raised a flag. That's the pattern worth understanding: recovery situations rarely announce themselves. They accumulate quietly, one missed milestone at a time, until the gap between "behind schedule" and "seriously off track" becomes impossible to ignore.
Here are the five signals we look for first — not because they're dramatic, but because they're the ones leadership teams tend to explain away the longest.
1. Go-live has moved more than once
A single schedule adjustment is normal — data migration always takes longer than the first estimate. But a second or third slip usually means the plan itself was never realistic, not that the team is simply unlucky.
2. Budget has quietly outpaced the original quote
Change orders happen. What we watch for is whether anyone can clearly explain what the additional spend actually bought. If the answer is vague, that's usually scope creep that was never formally tracked.
3. Your own team doesn't trust the UAT results
This is the subtlest sign and the most reliable one. When user acceptance testing keeps "passing" but confidence in go-live keeps dropping, it usually means test scripts have drifted away from how the business actually operates.
"We knew something was wrong when our own finance team stopped attending UAT sessions. They'd already decided it wasn't going to work."
4. Data migration keeps getting pushed to "later"
Migration is one of the few workstreams that can't be compressed at the end of a project. If it's consistently treated as a future problem rather than a current one, the go-live date attached to the plan is more aspirational than real.
5. Someone above you has asked for a second opinion
If you're reading a post like this one, there's a reasonable chance this is already true. That instinct is usually right — an independent, two-week assessment costs far less than another missed quarter.
What an assessment actually looks for
- Whether the original scope and the current build still match
- Data readiness — not just "has it been migrated" but "has it been validated"
- Whether the team doing the work today is the team that scoped it
- A realistic, re-baselined timeline built from what's actually true, not what was originally promised
None of this requires starting over. In most cases, the technical work is closer to done than it feels — what's usually missing is an honest, external read on what's left.