New: Odoo and Dynamics 365 cost calculators.Estimate your costs

ERP change management: the people side of the rollout

ERP change is the move to daily use of a new ERP. Prosci's 2025 study of 1,618 leaders: 8% of budget on change, about 1 in 5 projects under 70% of benefits.

Both platformsImplementation & Go-Live12 min readUpdated 20 sources

Key takeaways

  • A sponsor title with an empty calendar. Put the ABCs on dated meetings before kickoff, and give the sponsor a deputy for go-live week.
  • ERP change means the shift in how people and processes work once a new ERP is the system of record.
  • Prosci's 2025 ERP implementations research, as published on its public landing page, blog, and webinar page, covered 1,618 implementation leaders on teams in 20 countries.
  • A system that goes live can still miss the business case.

What ERP change and ERP change management mean

ERP change means the shift in how people and processes work once a new ERP is the system of record. Search results often answer with a generic ERP explainer. For an owner, a finance lead, or an operations manager, the useful meaning is the daily one: staff run the close, the order, and the shipment in the new system, and the side spreadsheet comes out of the routine.

ERP change management is the structured approach that moves individuals, teams, and the organization from the current state to that future state. Prosci's broader definition is an enabling framework for the people side of change: prepare, equip, and support individuals so they adopt the change. Without adoption, the outcomes you bought the system for do not arrive.

A course completion date is a weak stand-in for that shift. Someone can finish training and still get lost in a changed approval flow on Monday morning. Communications build awareness and training builds familiarity, while production support, reinforcement, and measurement decide whether the change sticks after go-live. That split is the practical answer to 'what is ERP change management' for a company of 20 to 100 people.

Why the people side decides the business case

Prosci's 2025 ERP implementations research, as published on its public landing page, blog, and webinar page, covered 1,618 implementation leaders on teams in 20 countries. Organizations invested 92% of the ERP budget in technical activities and 8% in change management. Human factors outweighed technical considerations 6 to 1 in what leaders said would improve outcomes. The people side accounted for 36% of what leaders said they would do differently, set against that 92% technology spend. Prosci's FAQ cites a 92% technical-activity share to Best Practices in Change Management, 12th Edition; the 92% technical and 8% change split is the 2025 ERP study's finding. If that 8% is the part you are still sizing, Flectic's discovery call pressure-tests sponsor time, super-user load, and the adoption measures worth tracking.

The same study defines ERP failure as delivering less than 70% of expected business benefits. Reported failure was between 11% and 31%, depending on training timing, duration, and organizational characteristics, and about 1 in 5 on average. Prosci's ERP change page also attributes several Panorama Consulting figures to that literature: not having enough staff is a major reason costs exceed budget, which happens for 38.4% of organizations; 49.7% of projects meet original timelines; median duration is 15.5 months; executives who invest in a change methodology are 33% more likely to report good or excellent outcomes. Those Panorama figures are Prosci's citations.

A separate Prosci data set, covering change projects in general, says excellent change management makes organizations 7 times more likely to meet objectives, with companion claims of 4.6 times more likely to stay on schedule and 1.4 times more likely to stay on budget. Those multiples sit outside the 1,618 ERP projects. They still explain why a 20 to 100 person firm, where the same people must keep orders moving during the rollout, treats the people plan as part of the business case.

Prosci's failure definition describes a plain scene in a company of 20 to 100 people: the new system posts transactions while the old workbook still decides what ships, and the project lands under 70% of the benefits in the business case. About 1 in 5 ERP projects in the study landed there, inside Prosci's 11% to 31% range. Closing that gap takes a people plan with a budget, named owners, and dates on the same calendar as the build.

Figures Prosci publishes about ERP change, as of October 2026. Prosci cites the 92% technical-activity share to Best Practices in Change Management, 12th Edition; the 92% and 8% split is the 2025 ERP study. The 7 times, 4.6 times, and 1.4 times rows are Prosci's general change research, kept separate from the 1,618 ERP projects.
FigureWhat it saysScope
1,618 leaders, 20 countriesSample behind the 2025 ERP study summariesERP implementations
92% / 8%Share of ERP budget on technical activities versus the change workstream2025 ERP study
6 to 1Human factors versus technical factors in what leaders said would improve outcomesERP study
36%Share of 'what we would do differently' that leaders assigned to the people sideERP study
Under 70% of benefitsProsci's definition of ERP failure in this studyERP study
11% to 31%, about 1 in 5Reported failure, varying with training timing, duration, and organizationERP study
7 times / 4.6 times / 1.4 timesMore likely to meet objectives, stay on schedule, and stay on budget with excellent change managementChange projects generally

Why ERP projects miss the benefits after go-live

A system that goes live can still miss the business case. Prosci's failure article lists causes that show up together: unclear objectives, poor data quality, timelines that were never realistic, over-customization, thin testing, and weak support once the partner's cutover week ends. Each of those has a people-side twin.

Unclear objectives leave supervisors inventing local rules. Dirty data makes the first month look like the software is wrong. Heavy customization rebuilds the old workaround inside the new database.

Microsoft warns Dynamics 365 teams about three traps. The first is investing in theoretical problems that never arise. The second is treating a training and communication PowerPoint as the whole plan. The third is writing change management off. The second trap is the common one in companies of 20 to 100 people, because the project already has a busy controller and a plant manager, and a deck feels like progress.

Prosci describes the fear underneath resistance in plain terms. The finished system is hard to see until near go-live, so people are asked to trust a design they have not used. Mid-career employees feel pressure to reskill while they still have to hit this week's numbers. Fear of looking incompetent produces quiet workarounds. Reinforcement exists because people go back to the old path after go-live, especially when volume spikes.

Third Stage frames the same resistance as perceived imperfection, ambiguity, loss of mastery, and purpose drift, and treats change as the design of the work. Track touchless transaction rate, exception volume, and shadow-system usage. Those three tell you if the business case is arriving.

ADKAR, the 3-Phase Process, and where Kotter and Lewin fit

Pick a model so managers know what 'ready' means for a person, and a process so the program has deliverables. Prosci's ADKAR model is five observable elements of individual change: Awareness, Desire, Knowledge, Ability, and Reinforcement. Prosci states that ADKAR is a model. The methodology is the 3-Phase Process.

Awareness is why the company is changing. Desire is the personal reason to take part, and the message that answers what the change means for someone's own job usually comes from their supervisor. Knowledge is how the new task works. Ability is doing the new task at the speed of the job. Reinforcement is what stops the slide back to the spreadsheet.

The Prosci 3-Phase Process is the organizational method. Phase 1, Prepare Approach, produces a change management strategy. Phase 2, Manage Change, produces a master change management plan. Phase 3, Sustain Outcomes, produces a change management closeout. Each phase has three stages.

Use Phase 1 to name the sponsor, the impacted roles, and the risk. Use Phase 2 to schedule messages, practice, and coaching on the same weeks as test and cutover. Use Phase 3 to hand the adoption measures to a business owner.

Kotter's 8 steps are a leadership sequence: urgency, a guiding coalition, vision, a volunteer group, removal of barriers, short-term wins, sustained acceleration, and instituting the change. It is useful when the owner needs a narrative for why this ERP, this year. Lewin's Unfreeze, Change, Refreeze (later writers often say Reinforce) is the short explanation for why hypercare exists. You disturb the current routine, install the new one, and then hold it in place long enough that it becomes the default.

Microsoft says Prosci is its preferred change-management approach, and the leading change-management certification organization in North America, for Dynamics 365 business-application projects. Prosci's certification page says the ADKAR model is used by 80% of Fortune 100 companies and that Prosci has trained and certified 267,000+ practitioners. Prosci's change-management overview says more than 100,000 certified practitioners. Both headcount lines were on live Prosci pages in October 2026. A 40-person firm can run with one trained lead plus managers who will coach.

Who sponsors ERP change, and what the sponsor does each month

Prosci's ABCs are the sponsor job description: active and visible participation throughout the project, building a coalition of peer leaders, and communicating support to the groups who have to change how they work. In a company of 20 to 100 people the sponsor is usually the owner, the COO, or the CFO. Naming that person on a steering slide is the start. The calendar has to show the town halls, the floor walks, and the decision to retire a shadow workbook.

Change tasks belong on the same plan as configuration, data, and test, reviewed in one meeting that the sponsor chairs, where process owners bring the exceptions that need a decision and super users report the tasks people still cannot finish. Agree the ABCs before kickoff, write the first three messages in the sponsor's voice, and book the dates. If the sponsor will be in customer meetings during go-live week, name a deputy who can make the same call on workarounds.

What to say, who should say it, and how often

ERP communication fails when the same all-staff email tries to carry the business case and the personal impact. Prosci's communication research points teams at repeating key messages across channels and levels. People in that research say they would have communicated more, more often, to more people, and at more levels. Repetition feels excessive to the project team and barely enough to a buyer who heard the plan once in a kickoff.

Sender choice is specific. Employees prefer executives and senior leaders for organizational messages: why this system, why now, what risk the company is retiring. They prefer the immediate supervisor for personal impact. A plant supervisor telling a shift what happens to the paper traveler is a different message from the owner's note about inventory accuracy.

For a mid-market rollout, sequence a sponsor kickoff, a short vision from the owner, function briefings from managers, a cutover countdown that names downtime, and a go-live note that says who is affected, what to do differently, where to get help, and what is temporarily unavailable, with one owner, one approval path, and one list per audience.

Stakeholder map, process owners, and super users

Sort people by whether they can block the rollout and by how much their week changes. Finance and operations leaders sit in the group you manage closely. Anyone whose screen changes at least needs a clear briefing and a practice path. High-power people with low day-to-day interest, often the owner of a sister entity, still need a direct update so they do not reopen scope in the last month.

Super users are internal staff, sometimes called power users or floor walkers. They join design and testing, coach during go-live, and teach peers. In a 20 to 100 person company, one or two per function is the usual pattern: accounts payable, shipping, planning, a sales coordinator, a warehouse lead. They need backfill. If the super user is still expected to clear a full queue, the network exists only on the RACI chart.

Change champions overlap that group. They are the people others already ask. Keep them through the first months after go-live, because Prosci's resistance guidance says people revert once the project team leaves. Third Stage treats go-live as the start of reinforcement, which matches that pattern. Pulling floor support in week one is how shadow systems return.

Map the routines that have to move: an invoice keyed in the ERP, a stock move posted the same day it happens, and a supervisor approving in the system during the shift before a spreadsheet export the next morning. Build the cue into the job with a required field, a manager checklist, or a super user on the floor at peak. Training explains the screen, and the cue is what changes on the second live shift.

ERP change for a transformation lead in automotive and industrial plants

A chief transformation officer in their mid-40s to mid-60s, running an automotive supplier or a similar industrial operation in the US, usually inherits plants that already make the number. Supervisors protect output with tribal spreadsheets, offline travelers, and a shipping log that has survived two previous systems. The ERP threatens that mastery. Prosci calls out this mid-career reskill directly: people must learn the new job while the current job still has a due date, and they cannot see the finished system until late in the project.

The change plan that fits that floor is operational. The sponsor, often the COO or the transformation lead, walks the line and sits in the steering meeting. Supervisors are the senders for what the change does to a shift. Super users include a planner and a shift lead, named before configuration freezes, and scheduled for the weeks after go-live. Microsoft's second trap applies here with force: a training PowerPoint is one artifact, and the plan still has to name which shadow files retire, who retires them, and what the supervisor checks on the second live shift.

Assume a 70-person US automotive supplier with two sites, moving finance, inventory, and production onto Dynamics 365 Business Central. The owner sponsors, the controller and the plant manager own the processes, and four super users cover accounts payable, shipping, planning, and one shift supervisor. One internal lead takes Prosci's online certification, listed at USD 4,500 as of October 2026, and the larger cost is those people's hours in workshops and on the floor. Measure success on shadow-system count, late shipments keyed outside the ERP, and exception volume in receiving; classroom attendance stays on the training log.

The same pattern fits Odoo for a plant of this size. A phased Odoo rollout still needs the sponsor, the supervisors, and a reinforcement window on the project plan. Canadian plants in the same size band use the same role design. Prosci's public study covers teams in 20 countries and publishes one failure range for that sample, and the certification page lists the course fee in USD.

How the people plan sits on a Dynamics 365 or Odoo timeline

The people-side work is the same discipline on Microsoft Dynamics 365 and on Odoo. The calendar differs because the implementation lifecycle differs. Microsoft's Success by Design maps a Dynamics 365 implementation to five methodology-agnostic phases: Discover, Initiate, Implement, Prepare, and Operate. Go-live readiness sits in Prepare, and Operate is stabilization and the next wave of enhancements. FastTrack is optional, and Microsoft recommends the framework for all Dynamics 365 projects, telling teams to scale change management to risk and complexity.

On Dynamics 365, start the sponsor and the impact list in Discover, lock the change strategy in Initiate, and run role practice during Implement. Prepare is where you prove people can complete the cutover tasks, while the environment is technically ready. Operate is where reinforcement, ticket review, and the next wave live. Microsoft contrasts a single go-live, which compresses cutover into a shorter window and raises the blast radius, with a phased release by module, site, or business unit. Phased releases are frequently favored for cloud projects because each go-live asks users to absorb less at once.

Odoo rollouts for companies of this size often follow a phased modular path: GAP analysis and kickoff, then iterative build cycles, go-live, and often a second deployment to widen scope. A phased rollout of that shape still needs the sponsor, the supervisors, and a reinforcement window on the project plan, because every cycle asks one group to absorb a change and hold it. Shorter cycles compress the calendar, so name the sponsor and the super users earlier, when the project has fewer weeks in which to build ability.

Prosci's case sketches show the same sequence at enterprise scale. EisnerAmper ran an 18-month cutover of four systems, including SAP, touching 3,300+ employees, with roadshows in 16 offices. A food company consolidated six legacy systems for 500 SAP users with 40 change agents. An entertainment company trained 60+ people, ran eight PCT and ADKAR assessments, and reported an 86% improvement in project success while growing from 500 to 1,200 employees. A 40-person firm copies the sequence of named agents, assessments, and reinforcement.

People-side activities on Success by Design for Dynamics 365 and on a phased Odoo rollout. Odoo leaves the people-side method to the project. The activities are how a 20 to 100 person company keeps adoption on the project plan.
People-side activityDynamics 365 (Success by Design)Odoo (phased modular)
Sponsor activationABCs agreed in Initiate and visible in blueprint reviewsSponsor in the room at kickoff and at each cycle review
Impact and role listStarted in Discover and refreshed each phaseBuilt during GAP analysis, when process gaps are named
MessagesKey messages repeated across channels and levels from Discover through OperateFront-loaded across the long implementation cycles
Super usersNamed before Implement; on the floor in Prepare and OperateNamed before the first cycle; kept through the second deployment
Training versus abilityPractice in Implement; proficiency checked in PreparePractice inside the cycles; a live task check before go-live
After go-liveOperate: stabilization, ticket themes, next waveSame measures, on a shorter baseline if the scope was small

Three budgets buyers mix up, and the one published price

Software subscriptions, implementation services, and the change workstream are three different checks. Subscriptions pay for the application. Implementation services pay for configuration, data, integrations, and testing. In Prosci's 2025 study, organizations put 92% of the ERP budget into technical activities, which covers subscriptions and implementation services together, and 8% into the change workstream: sponsor time, process owners, super-user backfill, practice, and someone who can run the plan. Match the split to your headcount before you copy it into a purchase order.

As of October 2026, Prosci lists Change Management Certification at USD 4,500 online and USD 4,850 in person, per person; the fee covers tuition, materials, and renewable digital content, and the in-person fee adds breakfast and lunch. Online class time is about 8 hours a day, plus about 1 hour of self-study on days 1 and 2. Duration is listed as 3 to 5 days, with a 3-day intensive agenda, and the fee includes a 90-day Prosci membership trial. The certification page lists the fee in USD. A standard public price for an ERP change retainer, a rescue, or a hypercare block is absent from that page.

Worked split for the 70-person automotive supplier above: certification for one internal lead is USD 4,500 if they attend online. Assume the controller, plant manager, and four super users each give a scheduled half day a week for eight weeks of design and practice, which is 6 people times 4 hours times 8 weeks, or 192 hours, before go-live coaching. Edit that hour count to your own loaded cost. If those hours are unpaid overtime, the 8% in the study describes a different project from the one you are running.

Canadian buyers can use the same split. Prosci's sample spans 20 countries, and the people-side ratios above are the ones it publishes for that sample. Budget the internal hours in CAD at your own loaded cost, and treat the USD 4,500 or USD 4,850 course fee as a USD invoice. The certification page lists those USD amounts as of October 2026.

What each budget pays for on a Dynamics 365 or Odoo project, as of October 2026. Certification is the only published price in this table.
BudgetWhat it pays forWhat is published
Software subscriptionLicenses for Dynamics 365 or Odoo users and appsVendor quote on your user count. Prosci's 2025 study puts 92% of ERP budget on technical activities, subscriptions and services combined.
Implementation servicesConfiguration, data, integrations, testing, cutoverCovered by that 92% technical share
Change workstreamSponsor time, process owners, super-user backfill, practice, reinforcementProsci: 8% of ERP budget in the 2025 study
Practitioner courseOne person equipped to run ADKAR and the 3-Phase ProcessUSD 4,500 online or USD 4,850 in person. The page lists USD only.

A 30-60-90 plan from readiness through reinforcement

Models need dates, so run two clocks. The build clock runs to cutover, inside the first-phase timeline Flectic sets in the written scope. Days 0 to 30 name the sponsor message, the audiences, the role map, the super users, and the behaviors you will count. Days 31 to 60 run scenario practice, manager scripts, access checks, and a staffed help path. Stretch those two windows if the build runs longer. The live clock starts at cutover. Its first 30 days carry refreshers, a daily issue review, and a weekly adoption check the sponsor reads, and reinforcement usually holds for 60 to 90 days after go-live.

Align the two clocks to Success by Design if you are on Dynamics 365: the build windows sit in Initiate, Implement, and Prepare, and Operate is the weeks after go-live, where stabilization, ticket review, and the next wave live. On Odoo, drop the same tasks onto the iterative cycles and then onto the weeks after go-live. Leave hypercare when severe issues have an owner and the adoption measures are moving. The contract go-live week is a weak exit test on its own.

Judge the live window on transaction evidence: the shadow systems still open, the touchless rate on invoices, receipts, and shipments, the exceptions on those flows, time to proficiency by role, and tickets per active user. Login counts hide empty sessions. A finance close metric is a different series from a warehouse pick metric, so split the dashboard by role.

People-side windows for a company of 20 to 100 people. The first two run inside the build. The third starts at cutover.
WindowMessagesPracticeSupportMeasures
Build, day 0 to 30Sponsor kickoff and audience listRole map, training needs, named super usersIntake path, severity, and who covers the deskBaseline behaviors by role
Build, day 31 to 60Manager scripts and downtime windowsScenario practice and access confirmedIssue log and a daily standupPractice completion and open tasks
Cutover plus 0 to 30 daysLive updates and recognition of the new pathRefreshers for roles that are slippingReinforcement, then a named business ownerUsage, exceptions, tickets, shadow systems

How to tell training from adoption after go-live

Adoption is consistent, correct use of the new system for the work the business case named. Change management is the set of actions that produce it. A passed quiz shows knowledge; ability shows up in the transaction. Whatfix's distinction is the right test: communications build awareness, training builds familiarity, and support plus reinforcement plus measurement decide whether execution improves. A user who finishes a course and then stalls in a changed approval is a knowledge pass and an ability miss.

Build a small scorecard a controller can review weekly for the first month, then monthly. Count each shadow system that is still in use, by file name. Count the touchless rate on invoices, receipts, or shipments that should post without rekeying, and count exception volume on the same flows.

Record time to proficiency by role, meaning the week a new user completes the standard task without a super user sitting beside them. Record tickets per active user and read the themes.

Third Stage uses the same family of signals: touchless rates, exception volume, and shadow-system usage. Set the baseline in the month before go-live and agree the direction with the sponsor. Prosci and the digital-adoption vendors publish the signal names, and a 50-person manufacturer still needs its own starting numbers. Falling tickets with rising shadow workbooks means people gave up on the help desk and went around the system. That pattern should bring the supervisor and the super user back to that team.

Review the scorecard in Operate on Dynamics 365, and in the weeks after go-live on Odoo. Tie one business result to the same page. Examples that match common business cases: days to close, inventory adjustments, or on-time shipment keyed in the ERP. If the result is flat while logins are high, keep the reinforcement window open.

Patterns that quietly drop the business case

The same misses show up on Dynamics 365 and Odoo programs in this size range. Most of them are choices about time and attention in the months around go-live.

  • A sponsor title with an empty calendar. Put the ABCs on dated meetings before kickoff, and give the sponsor a deputy for go-live week.
  • One sender for every message. Leaders carry the business reason. Supervisors carry personal impact. Plan repetition of the key messages across channels and levels.
  • A training calendar standing in for the whole plan. Knowledge is one ADKAR element. Awareness, desire, ability, and reinforcement still need owners.
  • Super users released the week after go-live. Prosci says people revert to old ways once the pressure of the current job returns. Keep local coaching through the first 60 to 90 days.
  • A single weekend cutover for every site and module when a phased release was available. Microsoft notes the higher blast radius of a big-bang go-live.
  • Customizing the new system so nobody has to change the old habit. Rebuilding the old workaround as a customization adds technical scope that the people plan then has to absorb.
  • An 8% people budget that is only a slide. If super-user hours are unpaid leftovers, the study's spend split is not what your project is doing.
  • Counting logins as adoption. Pair active use with touchless rate, exceptions, shadow systems, time to proficiency, and tickets per active user.

How Flectic can help

Flectic implements Odoo and Dynamics 365 for companies of 20 to 100 people in the US and Canada, and training and adoption sit inside each phase of the plan. Each phase has a defined scope and price before it starts, and the first one delivers a working part of the system. Read how Flectic runs an ERP implementation, then book a free discovery call to start.

Sources

  1. Prosci defines change management as an enabling framework for the people side of change: prepare, equip, and support individuals so they adopt the change. Without adoption, the desired outcomes are not delivered. The overview page also says more than 100,000 certified practitioners. Across change projects generally, excellent change management makes organizations 7 times more likely to meet objectives, 4.6 times more likely to stay on schedule, and 1.4 times more likely to stay on budget.

    prosci.comChecked 2026-10
  2. Prosci defines ERP change management as a structured approach that moves individuals, teams, and the organization from the current state to the desired future state so people use the updated ERP in daily work. The people side accounts for 36% of what leaders said they would do differently, against 92% of ERP budget spent on technology. Case sketches: EisnerAmper, 18-month cutover of four systems including SAP, 3,300+ employees, roadshows in 16 offices; a food company consolidating six legacy systems for 500 SAP users with 40 change agents; an entertainment company training 60+ people, eight PCT and ADKAR assessments, 86% improvement in project success, growth from 500 to 1,200 employees. Prosci attributes to Panorama: staff shortages as a major reason costs exceed budget for 38.4% of organizations, 49.7% of projects meeting original timelines, a 15.5 month median duration, and executives who invest in a change methodology 33% more likely to report good or excellent outcomes.

    prosci.comChecked 2026-10
  3. Prosci's 2025 ERP research summary covered 1,618 implementation leaders. Organizations invested 92% of the ERP budget in technical activities and 8% in change management, while human factors outweighed technical considerations 6 to 1 in what leaders said would improve outcomes. The PDF is behind a form; these figures are the ones on the public landing page.

    empower.prosci.comChecked 2026-10
  4. A Prosci webinar page says the 1,618 implementations span teams in 20 countries. The page does not list five benefit levers.

    prosci.comChecked 2026-10
  5. Prosci defines ERP failure in the 2025 study as delivering less than 70% of expected business benefits. Reported failure was between 11% and 31% depending on training timing, duration, and organizational characteristics, and about 1 in 5 on average. Causes include unclear objectives, data quality, timelines, over-customization, thin testing, and weak post-go-live support. The FAQ also attributes a 92% technical-activity budget share to Best Practices in Change Management, 12th Edition.

    prosci.comChecked 2026-10
  6. ADKAR is Awareness, Desire, Knowledge, Ability, and Reinforcement. Prosci states ADKAR is a model, not a complete methodology.

    prosci.comChecked 2026-10
  7. The Prosci 3-Phase Process is Phase 1 Prepare Approach (Change Management Strategy), Phase 2 Manage Change (Master Change Management Plan), and Phase 3 Sustain Outcomes (Change Management Closeout). Each phase has three stages.

    prosci.comChecked 2026-10
  8. As of October 2026, Prosci Change Management Certification is USD 4,500 online and USD 4,850 in person, per person, covering tuition, materials, and renewable digital content. Online class time is about 8 hours a day plus about 1 hour of self-study on days 1 and 2. Duration is 3 to 5 days with a 3-day intensive agenda, plus a 90-day membership trial. In person includes breakfast and lunch. No CAD price is listed. The page says ADKAR is used by 80% of Fortune 100 companies and that Prosci has trained and certified 267,000+ practitioners.

    prosci.comChecked 2026-10
  9. Microsoft says Prosci is its preferred change-management approach and the leading change-management certification organization in North America for Dynamics 365 business-application projects. Teams should scale change management to risk and complexity. Three failure modes: theoretical problems that never arise, treating a training and communication PowerPoint as the whole plan, and writing change management off.

    learn.microsoft.comChecked 2026-10
  10. Success by Design maps Dynamics 365 to Discover, Initiate, Implement, Prepare, and Operate. Go-live readiness sits in Prepare. Operate is stabilization and the next wave. FastTrack is optional. The framework is recommended for all Dynamics 365 projects.

    learn.microsoft.comChecked 2026-10
  11. ERP fear shows up as fear of the unknown because the finished system is not visible until near go-live, pressure to reskill while still doing the current job (called out for mid-career employees), and fear of failure that produces workarounds. Reinforcement is required because people revert to old ways after go-live.

    prosci.comChecked 2026-10
  12. Third Stage says many transformations treat change as communications or training. Resistance causes include perceived imperfection, ambiguity, loss of mastery, and purpose drift. Adoption signals include touchless rates, exception volume, and shadow-system usage. The same page discusses resistance and post-go-live support.

    thirdstageconsulting.comChecked 2026-10
  13. Enterprise software change management prepares users, guides changed workflows, and measures whether execution improves after go-live. Communications build awareness and training builds familiarity, while production support, reinforcement, and measurement decide whether the change sticks. A user can finish a course and still get lost inside a changed approval flow. The page separates familiarity from execution after go-live.

    whatfix.comChecked 2026-10
  14. Prosci's ABCs of sponsorship are active and visible participation throughout the project, building a coalition, and communicating support. Employees prefer senior leaders for messages about the organization and their direct supervisor for messages about personal impact.

    prosci.comChecked 2026-10
  15. Prosci's communication research says key messages need repetition, and participants say they would communicate more, more often, to more people, and at more levels.

    prosci.comChecked 2026-10
  16. Kotter's 8 steps: urgency, guiding coalition, strategic vision, volunteer army, remove barriers, short-term wins, sustain acceleration, institute change.

    kotterinc.comChecked 2026-10
  17. Lewin's three stages are Unfreeze, Change, and Refreeze, with later adaptations naming the last stage Reinforce.

    prosci.comChecked 2026-10
  18. Microsoft contrasts a single go-live (a shorter cutover window, higher blast radius, harder rollback) with a phased rollout by module, business unit, or geography. Phased releases are frequently favored for cloud projects.

    learn.microsoft.comChecked 2026-10
  19. Odoo's implementation post describes the phases as GAP analysis, kickoff, iterative implementation cycles, then go-live, often followed by a second deployment to widen scope.

    odoo.comChecked 2026-10
  20. Super users, also called power users or floor walkers, are internal experts who join design and testing, coach at go-live, and teach peers.

    netsuite.comChecked 2026-10

Frequently asked questions

What is ERP change management?

ERP change management is the structured people-side work that moves individuals, teams, and the company from today's workarounds to daily use of the updated ERP. Prosci describes it as preparing, equipping, and supporting people so they adopt the change; without that adoption, the outcomes in the business case do not show up. Training is one part of the work. Sponsorship, local coaching, and reinforcement after go-live are the rest.

How much change management does my project need?

Microsoft tells Dynamics 365 teams to scale change management to risk and complexity. A finance-only Business Central or Odoo phase for 20 users needs a named sponsor, two or three super users, and a short reinforcement window. A multi-site manufacturer replacing shop-floor spreadsheets needs process owners, shift-level coaching, and measures of shadow systems after go-live. A slide deck does not cover either case.

How do I fit change work into budget, time, and headcount?

Keep three budgets separate: software subscriptions, implementation services, and the change workstream. In Prosci's 2025 study of 1,618 leaders, organizations put 92% of the ERP budget into technical activities and 8% into change management. The only published practitioner price as of October 2026 is Prosci certification at USD 4,500 online or USD 4,850 in person. Internal time for the sponsor, process owners, and super users is usually the larger line, and public pages do not list a standard retainer in USD or CAD.

Where should change management focus?

Focus where the new system removes a workaround people trust. In a manufacturer that is finance close, shipping, purchasing, and the supervisor who keeps the shift moving. Prosci finds employees want senior leaders for the business reason and their own supervisor for what the change means for their job. Put super users in design and test, then keep them available after go-live, when people revert to old paths.

What percentage of ERP implementations fail?

Prosci defines failure in its 2025 ERP study as delivering less than 70% of expected business benefits. Reported failure sat between 11% and 31%, depending on training timing, duration, and organizational characteristics, and about 1 in 5 on average. The range comes from Prosci's public summary of 1,618 implementations. Use it to judge benefit delivery after go-live as well as whether the system switched on.

Why do ERP implementations fail?

Prosci's failure write-up points to unclear objectives, weak data, timelines that slip, too much customization, thin testing, and thin support after go-live. The same research says human factors outweighed technical considerations 6 to 1 in what leaders said would improve outcomes, while the people side was 36% of what they would do differently. Fear of an unfinished system, pressure to reskill while still doing the current job, and workarounds after go-live are the patterns Prosci describes on the floor.

Can implementation, training, and change management be one engagement?

Yes. The technical plan and the people plan should share one calendar, and Microsoft maps Dynamics 365 work to Discover, Initiate, Implement, Prepare, and Operate with change management scaled to risk across that life. Training builds familiarity; ability shows up when someone can complete the live task, such as a changed approval, without dropping back to a spreadsheet. Flectic runs that people-side work on Dynamics 365 and Odoo rollouts.

What does change management change about adoption?

Across change projects in general, Prosci says excellent change management makes organizations 7 times more likely to meet objectives, 4.6 times more likely to stay on schedule, and 1.4 times more likely to stay on budget. Those multiples come from Prosci's broad change research; the 1,618 ERP projects are a separate sample. In that ERP sample, Prosci defines failure as delivering less than 70% of expected business benefits, with reported failure between 11% and 31% and about 1 in 5 on average.

What does ADKAR stand for?

ADKAR is Awareness, Desire, Knowledge, Ability, and Reinforcement. Prosci treats it as a model of individual change. The organizational method is the 3-Phase Process: Prepare Approach, with a change management strategy; Manage Change, with a master plan; and Sustain Outcomes, with a closeout. Microsoft names Prosci as its preferred change approach for Dynamics 365 business applications in North America.

Who owns change management on an ERP rollout?

The sponsor owns visible support and the decision to stay with the new process when volume spikes. Process owners in finance and operations own the redesigned work, super users own local coaching, and the project manager keeps change tasks on the same schedule as build, test, and cutover. A certification can equip one internal lead. As of October 2026 that course is USD 4,500 online or USD 4,850 in person, and Prosci's page lists a USD price only.

More on the blog: Implementation and go-live