Compensation Plan Design · Glossary

Change Management (Comp Transition)

Change management is the work of getting people to actually adopt a new commission process: training admins, rebuilding trust with reps, running parallel for a cycle, and absorbing the historical data that does not migrate cleanly. It is the cost buyers most consistently leave out of the model, and enterprise reviewers of every major ICM tool warn about it explicitly.

What is change management in a comp transition?

Change management is the work of getting people to actually use a new commission process. Not configuring it, which is implementation, and not adding reps to it, which is onboarding, but the human and organizational work of moving a team from the way they did it to the way they now do it.

It is the cost buyers leave out of the model most consistently, and they leave it out because it is not on any invoice. Enterprise reviewers of ICM tools say this plainly and repeatedly: be prepared for the change management costs that come with the transition. That warning appears in reviews of the platforms, not in the pricing pages of the platforms, and the gap between those two places is where budgets get broken.

The four hidden costs

CostWhat it actually looks likeWho absorbs it
Historical data migrationPrior periods do not come across cleanly, leaving gaps in year-over-year reporting.Finance and RevOps
Parallel runningThe old process runs alongside the new one for a cycle or two, so the work is done twice.The comp admin
Rep trustReps do not believe the new number until they have checked it against their own spreadsheet.Sales managers
Process relearningEveryone who touched the old process has to learn a new one, mid-quarter, while still closing deals.Everyone

The first is the one that surprises people. Reviewers who migrated to a new ICM tool report not being able to pull historical data across, which created gaps in year-over-year reporting that took time to resolve. That is a real reporting loss, it lands on Finance, and it is almost never scoped as a workstream.

The third is the one that lasts longest. A rep who does not trust the new system will keep their own spreadsheet running alongside it, which is shadow accounting, and they will keep it running until the new system has been right, visibly, for several months. Change management is largely the work of earning that.

What this means?

For a buyer, the useful reframing is that the transition is a project with its own cost, sitting alongside the software cost and the implementation cost. It should be budgeted, staffed, and given a timeline, rather than absorbed silently by whoever has the least ability to say no.

For RevOps, the two levers that matter most are parallel running and visibility. Running the old and new processes side by side for one full cycle and reconciling them is the single most effective trust-building exercise available, because it converts an assertion into a demonstration. And if reps can see how the new number was produced, they will stop maintaining their own spreadsheets far sooner. See commission transparency.

And a design point worth holding on to: complexity multiplies transition cost. The simpler the plan, the easier it is to set up and maintain, as one reviewer put it after a migration. A transition is a good moment to retire the plan rules nobody can justify, because you are already paying the cost of touching every one of them.

Common mistakes

1. Budgeting for the software and not for the transition

The license is the smallest of the three costs. Implementation is larger. Change management is frequently larger still, and it is the only one with no invoice attached.

2. Skipping the parallel run

It doubles the work for one cycle and it is the cheapest insurance available. A system that reproduces last quarter to the cent buys more trust than any amount of training.

3. Assuming history will migrate

Ask explicitly what comes across and what does not, and what year-over-year reporting will look like on the other side. Assume the answer is worse than you hope.

4. Migrating a broken plan

Automating a plan nobody understands produces a plan nobody understands, faster. The transition is the moment to simplify, and it is the only moment when everyone is already paying attention.

How Visdum approaches the transition

The way to reduce change management cost is to reduce the number of things people have to take on faith.

Visdum validates by recalculating a period you have already closed, so the first thing the team sees is the new system reproducing a number they already trust. That is what makes a parallel run short rather than indefinite. Because every figure on a commission statement traces back to the deals and rules that produced it, reps can check the new number rather than believing it, which is the fastest available route out of shadow accounting. And because plans are configured rather than coded, the transition is a reasonable moment to simplify rules rather than a reason to preserve them, since changing a plan later does not mean rebuilding it.

Take a self-guided product tour to see this in action, or read the complete commission close playbook.

Related terms

Implementation (ICM) · Onboarding (Sales Comp) · Shadow Accounting · Commission Transparency · Excel Hell

Calculate your OTE in 30 seconds

Enter your base, quota, and commission rate. Get your projected OTE plus earnings at common attainment scenarios.
Open the OTE calculator →

Frequently asked questions

What is change management in a commission system transition?

Change management is the work of getting people to actually adopt a new commission process, as distinct from configuring it or adding reps to it. It covers training, rebuilding rep trust, running the old and new processes in parallel, and absorbing historical data that does not migrate cleanly. It is the cost buyers most often omit.

Why do buyers underestimate change management costs?

Because it is the only cost with no invoice attached. The license is on the price sheet and implementation is quoted, but the work of retraining a team, running parallel for a cycle, and repairing gaps in historical reporting lands quietly on whoever has the least ability to refuse it. Enterprise reviewers warn about this explicitly.

What historical data problems happen during a comp transition?

Prior periods frequently do not migrate cleanly, which leaves gaps in year-over-year reporting. Reviewers who have been through a migration report exactly this. It is a real reporting loss that lands on Finance, and it is almost never scoped as a workstream, so ask specifically what comes across and what does not.

Should we run the old and new commission processes in parallel?

Yes, for at least one full cycle. It doubles the work briefly and it is the cheapest insurance available. A new system that reproduces a period you already closed, to the cent, buys more trust in one afternoon than any amount of training will, because it converts a claim into a demonstration.

How do you get reps to trust a new commission system?

By letting them check it rather than asking them to believe it. A rep who can trace a figure back to the deals and rules that produced it will stop maintaining their own spreadsheet. A rep who cannot will keep shadow accounting indefinitely, whatever the system is, and their trust will never fully transfer.

Should we simplify the comp plan during a transition?

It is the best opportunity you will get. Complexity multiplies both the build cost and the ongoing maintenance cost, and a transition is the one moment when every rule is already being examined. Automating a plan nobody can justify simply produces a plan nobody can justify, faster and at greater expense.