The moment it usually starts
The CEO returns from a peer dinner or an industry event convinced the CRM has to go. Someone they respect has just moved platforms, or quoted a licence bill that made the room wince. The note lands on the CIO's desk the same week the renewal paperwork is due, and it does not read as a question. Within days, a vendor the CEO met at the same event has requested a meeting, and the sales team has heard a rumour that the system they log into every morning is being switched off.
Why this is harder than a normal platform decision
The CIO now holds an impossible brief. Push back and it reads as defending an incumbent, or worse, defending their own past decisions. Comply and they own a multi-year migration whose failure modes are well documented across the industry, triggered by a conversation they were not in. Meanwhile the incumbent account team, sensing risk, escalates to the CEO directly with a retention discount that changes the economics mid-analysis. Every party in the room has an incentive that is not quite the organisation's.
- The CEO has publicly signalled a direction and now carries reputational cost if it reverses.
- The CIO carries delivery risk for a decision they did not originate.
- The incumbent vendor holds pricing and roadmap information the buyer does not.
- Challenger vendors are quoting against a scope no one has actually defined.
- The sales and service teams who live in the system have not been asked anything yet.
The costs that surface after the contract is signed
The licence fee is the visible number, and it is rarely the decisive one. What tends to surface late is the archaeology: a decade of customisations, integrations and workflow automations that nobody fully documented, each of which must be rebuilt, retired or replicated. Data migration exposes quality problems the old system had learned to live with. Adoption dips just as pipeline reviews depend on the new system being trusted. A replacement justified on cost can end up the most expensive programme in the IT portfolio.
Questions to put on the table before anything moves
- What specific outcome is the replacement meant to produce that reconfiguration of the current platform cannot?
- What did the peer organisation the CEO spoke to actually spend, over what period, and would they do it again?
- How many integrations, custom objects and automations exist today, and who can verify that count?
- What does the renewal decision look like if it is separated from the replacement decision?
- Who, by name, owns the outcome if migration runs a year over?
What to pressure-test before committing
The single most valuable move is to separate the irritation from the decision. If the real grievance is cost, test the renewal negotiation before testing the market. If it is adoption, test whether a different implementation would fix it on any platform. Pressure-test the total cost of change, not the licence delta: migration, integration rebuild, retraining, dual-running and the revenue risk of a distracted sales force through the cutover quarters. Then test the counterfactual honestly. Staying put has risks too, and they deserve the same scrutiny as leaving.
Who should be consulted, and in what order
Internally: the sales leaders whose teams live in the system, the architects who know where the bodies are buried, and finance on the true multi-year cost of both paths. Externally, implementation partners will have views, but they earn fees from migration, so their advice needs weighing accordingly. The perspective that is hardest to source internally is from executives who have actually run a CRM replacement of this scale, including ones that went badly. Selected senior operators from the Global Board who have lived through the same instruction can tell the CIO what the business case will not: where the timeline slipped, what the second-year costs looked like, and what they would refuse to sign this time.
