← Insights

ServiceNow Buys Sweep: What Salesforce Orgs Must Do Now

ServiceNow's acquisition of Sweep creates immediate operational risk for any Salesforce org running the tool. Here's the remediation checklist.

What Just Happened

ServiceNow acquired Sweep — an agentic metadata monitoring tool that holds live OAuth tokens inside customers' Salesforce, HubSpot, and ServiceNow instances — for an estimated hundreds of millions of dollars. The deal closed fast and quietly. If you're running Sweep inside a Salesforce org, the clock is already ticking.

The legal mechanism is specific: Salesforce's Partner Program Agreement (§9.2) permits immediate termination of a partner's access upon a competitor acquisition announcement. ServiceNow is, unambiguously, a competitor. That means the Salesforce connector Sweep relies on could be revoked at any point — not eventually, now.

The Operational Risk No One Is Talking About

Sweep isn't a passive reporting tool. It holds live OAuth tokens and has been actively writing configurations, flagging metadata drift, and implementing fixes inside customer orgs. When access goes, it doesn't just go quietly — it leaves behind automation maps with no documentation trail, connected apps that may behave unpredictably without their governing layer, and no automated handoff.

Most ops teams running Sweep built workflows around its outputs. If the connector gets pulled before you've exported those configs and maps, you're reconstructing your own system from memory. That's not a hypothetical — it's a support ticket waiting to happen at the worst possible moment.

There's also the question of ServiceNow's support commitment. They acquired the technology, not necessarily the obligation to maintain cross-platform connectors that compete with their own CRM ambitions. Assuming continuity without a written commitment is a business risk, not just a technical one.

What to Do This Week

Three actions, in order of urgency:

  1. Pull your Connected Apps OAuth Usage report in Salesforce. Confirm what Sweep currently has access to and what it's been touching. This is your baseline.

  2. Export all Sweep-generated config docs and automation maps while the connector is still live. Don't wait for a formal deprecation notice — by then you may be locked out.

  3. Ask ServiceNow in writing about the committed support window for the Salesforce connector. Get a specific date, not a reassurance. If they won't commit in writing, treat that as your answer.

This isn't about abandoning a tool that was working. It's about not being caught flat-footed because an M&A team in Tel Aviv and San Jose made a decision that has direct consequences for your production CRM environment. Assign this to someone with Salesforce admin access today — not next sprint.