ICM migration
with every balance and period accounted for.
We move incentive compensation management from one platform to another, along with the commission data behind it. That covers rebuilding each compensation plan on the new system, migrating historical data and open balances, parallel runs and cutover. Our team has over a decade of experience with ICM implementations on 13 platforms.
Where an ICM migration goes wrong.
Switching commission software looks like a rebuild. Most of the risk sits in the data and the history the old system carries.
Copying the old build instead of the plan
The old system holds years of workarounds. There's a helper table for one region, a manual adjustment that runs every quarter and an override for account managers on a legacy contract. Copy them across and you pay to migrate the problems. We rebuild from the plan as written and decide which workarounds still need to exist.
History that doesn't reconcile
Year-to-date quota attainment, tiered rates based on cumulative bookings, recoverable draws and clawback windows all reach back into prior periods. If historical data lands in the new system with different totals, the first payout after cutover is wrong for every rep near a tier. We reconcile balances rep by rep before cutover.
Commission accruals that jump at cutover
Finance books commission accruals and capitalized costs from the old system. If the new system calculates the same period differently, the accrual moves and someone has to explain why. We agree with finance which system is the record for each period, and we document every difference.
Effective dates lost in the move
Plans, commission rates, territories and hierarchies change during a year. The old system knows which version applied on which date. A migration that loads only current values recalculates history with today's rules. We migrate effective dates with every plan component, so a rerun of an old period gives the old answer.
No rollback plan
Many teams switch off the old platform the month the new one goes live. If the first close goes badly, there's nothing to fall back to and no clean comparison. We keep the old system readable through at least one closed period, and we agree a rollback plan before cutover.
Reps who hear about it from their statement
A new statement layout, a new dispute process and slightly different rounding look like a pay cut to the sales team if nobody explains them. Account executives judge the new system on its first statement. We plan rep communication with sales ops, so the explanation lands before the payout.
How we run an ICM migration.
Six stages, with the old and new systems running side by side until the numbers match.
Migration planning and inventory
We inventory the old build: plans, rules, hierarchies, integrations, reports, approvals and every manual adjustment in the close. We map each item to the new platform, flag what doesn't translate and agree how much history moves. The result is a migration plan with owners and a cutover date.
Rebuilding each compensation plan
We rebuild each comp plan from its written specification, using the new platform's native features instead of copies of old workarounds. Where plan complexity forces a different design, we show finance and sales ops the trade-off before it's built.
Commission data migration
We extract, map and load historical data: transactions, credits, payouts, quota attainment, draws, clawbacks and adjustments. Each load is reconciled against the old system's totals by rep and period. Data that won't reconcile gets a written explanation instead of a silent fix.
Integrations and payroll
We repoint the feeds from customer relationship management, ERP, billing and HRIS, and rebuild the export to payroll systems. Field ownership and validation rules carry over or improve. Payroll and finance test the new files before anyone is paid from them.
Parallel run
We run both systems on the same live periods and compare every payee. Each variance gets traced to the old build, the new build or the data. We don't recommend cutover until every variance is explained and finance has signed off.
Cutover and decommissioning
We make the new system the payout of record and keep the old one readable for audits and disputes. Then we archive what you need to retain. Reps get their statements with an explanation of what changed, and we stay through the first closes after cutover.
What you get from an ICM migration.
A new platform that pays the same as the old one where it should, and differently only where you chose to change it.
What you get
A migration plan with scope, owners, cutover date and rollback plan
Rebuilt compensation plans with effective dates and documentation
Historical commission data reconciled by rep and period
Repointed integrations and a tested payroll export
Parallel run results with every variance explained
A cutover checklist, rep communication and an archive of the old system
Who it is for
Companies whose plans outgrew the commission software they started on
Teams consolidating two ICM systems after an acquisition
Finance leaders who need history and accruals to survive the switch
Sales ops teams moving from a homegrown tool to a commercial platform
ICM vendors onboarding a customer from another platform
Companies moving years of commission data out of spreadsheets
Related ICM projects and platforms.
Migration is one of four kinds of ICM project. The data work around it has its own pages.
ICM implementation services
A first rollout and a change to a live system carry different risks from a migration.
Data quality and integrations
A migration is the right moment to fix the data feeding the system.
ICM migration questions.
What is an ICM migration?
An ICM migration moves incentive compensation management from one platform to another. It includes rebuilding each compensation plan, moving historical commission data and open balances, repointing integrations and running both systems in parallel until the new one pays correctly. It differs from a first rollout because the old system and its history set the standard the new one has to match.
When should we switch commission software?
When the plan design you need costs more in workarounds than the platform saves. Common signs are manual adjustments in every close, more plans than the system handles cleanly, a GTM strategy change the build can't follow, or reports finance rebuilds outside the tool. If the platform still fits and only the build is the problem, a rebuild on the same platform is often cheaper than a move.
How much historical data should we migrate?
Enough to pay correctly and answer disputes. That usually means the current plan year, open draws and clawback windows, and any prior periods that drive tiered rates or true-ups. Older closed history can stay in an archive or a reporting database. Every extra year costs reconciliation time, so we scope history by what each period is used for.
Can we change plan design during the migration?
You can, but it makes the parallel run harder, because differences then come from the plan change as well as the build. Most companies migrate the current plans first and change them at the next plan year. If a change can't wait, we build it as a separate, effective-dated version so the comparison stays clean.
How long does an ICM migration take?
It depends on scope: the number of plans, payees and integrations, and how much history moves. A small migration with one plan can run in weeks. Several plans with years of history take a few months. The parallel run needs at least one full period, and more if your plans have quarterly tiers.
What is a parallel run?
A parallel run calculates the same live period in the old and new systems and compares the results payee by payee. It's the most reliable way to prove the new build matches the old one, or to show exactly where and why it differs. It's also where most migration surprises come out, while they're still cheap to fix.
How do we keep sales commissions accurate during the switch?
Run both systems until they agree. During the parallel run, reps are paid from the old system while the new one calculates the same variable pay alongside it. Finance compares totals by payee, and nobody is paid from the new system until every difference is explained. The sales team gets confidence in the first statement, and finance gets the transparency that audits and compliance reviews ask for.
Do we need a rollback plan?
Yes. Agree before cutover what would trigger a rollback, who makes the call and how long the old system stays available. A clean parallel run makes a rollback unlikely. Finance and payroll still need to know the fallback exists before the first payout from the new system.
How do you handle data protection during a migration?
Commission data includes pay, which is personal data. We handle extracts, transfers and storage under your security policies and the relevant data protection regulations. Access stays limited to the people who need it, and we delete working copies when the migration ends. Your legal teams and IT should approve the data handling plan first.
Who from sales ops and finance needs to be involved?
A plan owner from sales ops or RevOps, a finance owner for accruals and payouts, the current system admin, a payroll contact and an owner for each data source. The compensation professionals on your team should review the rebuilt plans, because they know the edge cases the old build hides.
Which platforms can you migrate between?
We work on 13 platforms: Xactly, CaptivateIQ, Variabl, incentX, Performio, Qobra, Spiff, Varicent, QuotaPath, Everstage, Visdum, Centify and Oracle. We also migrate from spreadsheets and homegrown tools. Our guide to incentive compensation management software covers how the platforms differ.
Can you migrate commission data without changing platforms?
Yes. The same commission data migration work applies when you restructure a build, merge two instances after an acquisition or move history into a data warehouse for reporting. The steps don't change: map the data, load it, compare totals by rep and period, and explain every difference.
Tell us what you are moving from and to.
We will tell you what it takes.
Bring the plan documents, a list of integrations and how many years of history you need. We will show you where the migration risk sits.
Start a conversation