ICM Implementation Checklist: What to Prepare Before You Start
ICM implementations fail more often from poor preparation than from technology problems. The platform rarely breaks. What breaks is the data model, the plan rules, and the internal alignment around both.
This checklist is for teams who have already selected a platform and are preparing for implementation. If you are still evaluating platforms, see the ICM Software Comparison tool. If you need a selection framework, see How to Select an ICM Platform.
Data readiness
Your ICM platform ingests deal data from your CRM, which means CRM hygiene is upstream of everything the system produces. Before implementation starts, audit these fields for completeness and consistency:
Close date — are historical deals dated correctly?
Deal owner and co-owner attribution
Split percentages, if you use them
Product and SKU tagging
Contract value vs. recognized revenue (which one actually drives comp?)
Data quality problems found mid-implementation add four to eight weeks to a typical timeline. Finding them before go-live costs two to three weeks of audit work. Finding them early is almost always the cheaper path.
Rep records in your HRIS need the same treatment. Hire dates, role classifications, plan assignment dates, and territory assignments should be clean before they're imported into the ICM system. Mismatches between CRM and HRIS records are one of the most common sources of calculation errors in the first post-launch cycle, and they're annoying to untangle after the fact.
You'll also want at least twelve months of historical attainment and payout data in a consistent format. Two reasons: you need to validate that the new configuration produces the same outputs as your prior system for historical periods, and you need a baseline to work from for quota methodology.
Plan documentation
If your plan rules live in someone's head or in a patchwork of emails, write them down before implementation begins. ICM platforms need explicit logic. Ambiguous plan language that humans have been interpreting informally will produce wrong answers once it's in system rules.
Every plan has exceptions — deals that don't fit the standard rules. Your implementation team needs to know how exceptions currently get decided, who approves them, and what documentation is required. If there's no real exception process today, the implementation is a reasonable time to build one. Probably overdue.
Decide what reps should see on their commission statements. Line-item deal breakdowns, attainment percentages, accelerator tier indicators, YTD earnings? Statement design is harder to change after launch, so pin down the requirements before configuration starts.
Stakeholder alignment
Finance needs to approve how the system will calculate earnings before go-live. ICM platforms produce the actuals that feed your accrual process, and a surprise at month-end close is not the introduction you want for a new system. Walk them through it early.
Sales leadership — usually VP Sales or the CRO — should sign off on quota methodology, accelerator structure, and tiering logic before configuration, not after. Changes to core plan mechanics mid-implementation reset significant configuration work.
If your jurisdiction requires plan agreements to be signed by reps before they're enforceable, those agreements should be ready at or before go-live. Most ICM platforms include electronic acknowledgment workflows, but the legal content has to be approved first.
Systems and integrations
Identify the internal owner of the CRM-to-ICM integration. This is typically a RevOps or Sales Ops resource, not the implementation vendor. When a data pipeline fails during go-live, someone on your team has to be able to diagnose it. The vendor won't always be the fastest path to an answer.
Map the handoff to payroll the same way. What file format does payroll need, what's the processing deadline, and who owns the exchange? This coordination gets treated as an afterthought more often than you'd think, which is why the first post-launch cycle frequently gets run manually.
If you're on SSO, loop IT in before kickoff. Provisioning issues are a boring but common cause of delayed user access at launch.
A realistic timeline
A mid-complexity implementation — single plan type, one CRM integration, 50 to 150 quota-carrying sellers — usually runs twelve to sixteen weeks from signed contract to live cycle processing. Implementations that try to compress that to eight weeks still carry the same twelve to sixteen weeks of work. The work doesn't disappear; it just shows up as errors per week.
Build in two to three weeks of parallel testing before go-live. Running the first cycle manually alongside the ICM output before cutting over fully is the most reliable way to catch configuration errors before they hit paychecks. That's the only real backstop you have, and it's worth the extra time.
→ How to Select an ICM Platform — the selection framework to run before implementation.
→ Contact us— we run ICM implementations and can assess your readiness in a single conversation.