The vendor question used to settle on its own — ServiceNow for ITSM, Salesforce for CRM, no overlap. That stopped being true once Agentforce IT Service shipped with credible incident, change, and request handling on a Salesforce-native foundation. The 180+ switching announcements through February 2026 are not all greenfield deals; some are real displacements with real lessons for both sides.
The Numbers
By February 2026, more than 180 organizations had selected Agentforce IT Service to replace an existing ITSM platform — disproportionately Salesforce-native organizations whose IT teams already lived in Slack and whose data team was already on Data Cloud. The switching is real, not pilot demos. Average deal size skews mid-market (1,000 to 10,000 fulfillers), with a handful of larger enterprises in regulated industries quietly evaluating.
What Transitions Well
Organizations with heavy Slack adoption, ITSM processes that map cleanly to conversational handling, and ticket volumes dominated by deflectable intents (password reset, access request, status check). Teams comfortable with the Salesforce stack accept Agentforce’s metadata model without friction. Cases that look like Salesforce Cases — opened by a person, resolved through a conversation, with attachments and approvals — port directly. The migration tends to take 6-9 months for mid-market and includes a parallel-run period.
Strong fit signals:
- 60%+ of tickets are conversational (chat, email-driven)
- Existing Salesforce CRM/Service Cloud footprint
- Slack as the primary internal collaboration tool
- Limited custom ITOM, CMDB, or asset management depthWhere Resistance Persists
Enterprises with deep ServiceNow investment in ITOM (Discovery, Service Mapping, Event Management), custom apps in scoped applications, or governance built on years of update sets and CMDB hygiene. The switching cost is massive and Agentforce IT Service does not yet match ServiceNow’s ITOM depth. Heavy Discovery customers, mature SAM Pro implementations, and large CMDB consumers are the slowest to consider any move.
The Broader Pattern
ITSM vendor wars are heating up after a decade of stability. ServiceNow responds with AI-native positioning across the platform. Salesforce leans into Slack-native conversational handling. Microsoft brings Copilot Studio plus Teams as a credible third option. Mid-market and SMB face genuine vendor consolidation decisions for the first time in years; large enterprise stays mostly with incumbent ServiceNow but evaluates more aggressively at renewal.
Cost Considerations
Per-fulfiller licensing is broadly comparable across the three; the differentiation is in adjacent modules. ITOM, SAM Pro, GRC, and FSM remain ServiceNow strongholds where price-per-feature still favors the incumbent. Agentforce IT Service can win on net-new conversational AI capability without paying for ITSM modernization separately. Microsoft tends to win when the IT team already has E5 and the AI usage budget is bundled into existing commitments.
Implementation Sequence for Evaluators
If you are evaluating a switch, prove out three workflows end-to-end on the candidate platform before committing — incident with cross-team collaboration, change with CAB approval, and a regulated request with audit. The demo always works; the workflows expose the platform’s true depth. Compare total cost of ownership over three years including migration cost, parallel-run cost, and the cost of replacing adjacent tooling that the incumbent provided.
What to do this week: list the top five workflows your IT team runs and ask honestly which platform handles each natively versus through customization — that map decides where the switching cost actually lives.
