Change management for Dynamics 365
How to run change management on a Dynamics 365 implementation — stakeholders, comms, training timing, and the cultural patterns that decide adoption.
Of all the things that can wreck a Dynamics 365 go-live, change management ranks at or near the top. The technology works; the configuration works; users have ten different ways to ignore both. Treating change management as serious work is the difference between adoption and quiet failure.
Who owns it. The customer, full stop. A partner can advise, build materials, deliver training, but the cultural shift around new ways of working can only come from inside the organisation, with visible sponsorship from leadership. Buy-in from the CFO, COO, sales VP, and ops director is non-negotiable — not just nominally, but visibly: they're on the steering committee, they review the project, they communicate with their teams.
Stakeholder mapping. Early in the project, identify the stakeholder groups: power users, daily transactional users, occasional users, executives, IT, finance, external auditors. Each has different concerns and different change tolerances. The materials, training, and comms approach for each group differs.
Communication cadence. A drumbeat from kick-off to post-go-live:
- Awareness phase — what's changing and why. Sponsored by leadership; emphasise business outcomes, not features.
- Engagement phase — workshops, configuration choices presented to power users, feedback collected. People care more about systems they helped shape.
- Training phase — formal training delivered close to go-live. Earlier than four weeks before, and users forget. Later than two weeks, and there's no time to absorb.
- Go-live phase — daily check-ins, prominent help channels, leadership visibility.
- Stabilisation phase — drumbeat continues with usage metrics, success stories, additional training.
Training. Don't ship a recorded course library and call it training. Live, role-based sessions with realistic scenarios from the customer's own data. Workbook handouts users can write on. Floor walkers in the first week of go-live who physically sit with users.
Champions network. Identify and resource a champions network — one or two users per team who go deeper than their peers, attend extra sessions, and become the local go-to. Champions surface concerns before they become formal complaints and broadcast small wins.
Resistance is signal. Loud resistance is feedback. Sometimes it's "I'm scared and tired" and the answer is empathy and a check-in. Sometimes it's "you've broken my workflow and I have to do twelve clicks where I used to do three" — and the answer is fixing the workflow. Listen.
Measure adoption. Use Dataverse and BC telemetry. Active users, time-to-first-transaction, abandoned sessions, support ticket volume by team. Adoption metrics keep the project leadership honest about what's working.
Don't declare victory at go-live. Stabilisation runs for three to six months. The change-management programme runs alongside.
Related guides
- Budget management for Dynamics 365 implementationsHow to budget and manage costs for a Dynamics 365 project — cost categories, tracking discipline, change control, and the patterns that prevent budget overruns.
- Change readiness assessment for Dynamics 365 implementationsHow to assess organisational readiness for a Dynamics 365 implementation — readiness dimensions, surveys and interviews, gap analysis, and the interventions that close gaps before go-live.
- Risk management on Dynamics 365 projectsHow to identify, track, and mitigate risks on Dynamics 365 implementations — the risk register, scoring framework, escalation, and the discipline that prevents most project failures.
- Stakeholder management for Dynamics 365 implementationsHow to identify, engage, and manage stakeholders through a Dynamics 365 project — RACI, communication plans, influence mapping, and the patterns that prevent stakeholder surprises.
- Test data management for Dynamics 365How to build and maintain test data for Dynamics 365 environments — anonymisation, synthetic data, data subsetting, and the workflows for keeping non-prod environments useful.