Go-live is supposed to be the finish line. For many Dynamics 365 projects, it's where the trouble starts. The system works. The data loaded. Training happened. Six months later, sellers are back in spreadsheets, managers pull reports from Excel, and the enhancement list is longer than the original scope.

This rarely means the software was the wrong choice. It usually means a handful of predictable decisions were made, or skipped, before launch. Here's what we see most often, and what to do about it.

The pattern underneath is the one we see everywhere: software scales whatever process and data it sits on, including the broken parts.

1. The process was never agreed on

The most common cause is a process nobody fully agreed to. Sales defined an opportunity stage one way, finance another, and the implementation picked one. The system enforces a rule half the business doesn't follow, so people work around it.

Software exposes disagreement. It doesn't settle it. If the stage definitions, approval paths, and handoffs weren't signed off by the people who do the work, the system will feel wrong to someone every day.

The fix: get the process owners in a room and agree on the process as it should run, including exceptions. Then adjust the configuration to match. This is often a few focused workshops, not a rebuild.

2. Users got the system, but not a reason to use it

People update a system when it saves them time or when something they care about depends on it. If a seller's manager still asks for the pipeline in a spreadsheet, the seller will keep the spreadsheet. CRM becomes a second job.

  • Run pipeline and forecast reviews directly from Dynamics 365, not from exports.
  • Remove required fields that nobody reads.
  • Put the information people need, like open cases, recent orders, or last contact, on the screens they already use.
  • Retire the old spreadsheet on a named date and tell everyone.

3. Data quality broke on day one

Migrations under time pressure often move data as-is. Duplicate accounts, outdated contacts, and inconsistent picklist values come along for the ride. Users search for a customer, find three, and decide the system can't be trusted.

Trust is hard to win back. The fix is a focused cleanup on the records people touch most, duplicate detection rules to stop new duplicates, and a named owner for data quality. Don't try to clean everything at once. Start with active customers and open opportunities or cases.

4. Too much customization, too early

Every request during implementation feels reasonable. Together they create a system that's harder to use, harder to test, and harder to upgrade. Microsoft ships updates on a regular release schedule, and heavy customization turns each one into a risk.

Look at what was customized and ask whether each change is still used and still needed. Replace custom code with standard features where Microsoft has caught up. Simpler systems get adopted faster and cost less to support.

5. Nobody owned the system after launch

Implementation partners often move on after hypercare. The internal team is busy with their day jobs. Tickets pile up, small annoyances go unfixed, and users conclude nobody is listening.

A live system needs an owner, a support process, and a prioritized backlog reviewed on a regular schedule. That can be an internal team, a managed services partner, or both. What matters is that users see issues get fixed.

How to get a stalled project moving again

Start with an honest assessment instead of a restart. Most stalled Dynamics 365 systems have a sound core and a few specific problems.

  • Talk to users. Ask what they avoid, what they re-type, and what they keep outside the system.
  • Review configuration and customization against how the process actually runs today.
  • Check data quality on the records people use most.
  • Agree on a short list of fixes that remove the biggest daily friction.
  • Set up ongoing ownership so improvements keep coming.

The bottom line

Go-live is the start of the value, not the end of the project. Stalled systems can almost always be recovered by fixing the process, the data, and the ownership model around the software. If your Dynamics 365 system went live and people aren't using it, that's a solvable problem.

Want a second opinion on your situation?

Tell us where work gets stuck. We typically reply within one business day.

Book a scoping call