What's the best CMMS for a Salesforce shop?
If you're running facilities at a company that already runs on Salesforce, the answer is more interesting than the usual list of CMMS vendors — but only if you're willing to have an honest conversation about how IT and facilities actually work together.
Spoiler: usually not very well.
The default reflex when evaluating CMMS options is to look at the big standalone names — IBM TRIRIGA, Planon, Nuvolo, FM:Systems, Eptura. They're capable platforms. They've been around for a long time. They show up in every Gartner report. And every one of them sits outside the Salesforce environment, with its own login, its own data model, its own integration tax, and its own quarterly invoice.
For a Salesforce shop, that's a strange answer to a fairly simple question. Let me explain why — including the awkward part nobody mentions in the sales pitch.
The IT/FM relationship problem
Before we talk about software, let's talk about the people.
In nearly every company I've ever walked through, the IT team and the facilities team work in the same buildings, often on the same floor, sometimes on adjacent issues — and they do not consider each other partners. Mention IT to a working facilities manager and watch the eyes roll skyward. Mention facilities to an IT director and watch a similar reaction.
It's not personal. It's structural.
IT operates on a roadmap, a backlog, and a budget cycle. Facilities operates on whatever broke in the last fifteen minutes. IT prioritizes systems used by the most employees — which means facilities, normally with just a handful of users and physical-world problems, ends up at the bottom of the queue. So the FM team learns to fend for itself. They buy their own software. They run their own spreadsheets. They figure it out.
Until IT shows up and tells them they have to use ServiceNow because the company already has it. Or worse, until IT buys something for them — based on a sales pitch IT attended without inviting anyone from facilities — and the FM team is told to make it work.
And then there's the other direction. IT deploys a lot of beautiful technology into the buildings. Video conferencing systems. Smart sensors. Digital signage. Most of it is fragile, and when an exec walks into a conference room and the screen won't share, who gets the call? Not IT. The workplace team. Because they "own" the office.
This is the dynamic any new CMMS purchase walks into. If you're a facilities leader and you're not thinking about it, the procurement is going to stall. If you're an IT leader and you're not thinking about it, the deployment is going to fail. Both of you should be thinking about it.
The hidden cost of a non-native CMMS
When you bolt a separate CMMS onto a Salesforce environment, you're not buying one system. You're buying a system, an integration project, and a second platform for IT to support, secure, and audit.
I spent nearly a decade at Salesforce running the RETECH organization — real estate technology for the company itself. I've watched smart teams burn six months and a quarter-million dollars wiring up CMMS integrations that work fine on day one and start drifting on day ninety. The vendor record in one system doesn't match the vendor record in another. The location list in one has 47 sites; the other has 52. Nobody knows which one is right.
This is the "four versions of the truth" problem, and it's the enemy of every AI initiative your CIO is going to launch in the next eighteen months. You can't shove AI at chaos and expect a clean answer.
It's also part of why so many "FM bought a CMMS" projects quietly die. Every standalone vendor becomes another thing for IT to own — security review, SSO, renewals, admin skillset. IT couldn't get to it. Facilities couldn't deploy it without IT. Six months later, everybody's back to spreadsheets.
What "Salesforce-native" actually means
There's a real difference between integrated with Salesforce and native to Salesforce. A lot of vendors blur the line in their marketing.
Integrated means the CMMS lives somewhere else, and there's a connector that moves data back and forth. Sometimes the connector is good. Sometimes it falls over when Salesforce ships a release. Always, the data lives in two places.
Native means the CMMS is built on the Salesforce platform itself — a managed package your existing Salesforce admins already know how to install, configure, and maintain. Same security model. Same release cadence. Same audit posture. Same AI surface as everything else Salesforce ships.
The native benefits include:
Same platform vendor — IT already has a relationship and a security review file
Same admin skillset — your existing Salesforce administrators can manage it
Same security and compliance posture — what's approved for Salesforce already covers this
Same AI roadmap — Agentforce is deeply integrated with your data, apps, and the humans using them
That’s why we chose to build sonpito on Salesforce - because it is a trusted, enterprise-level platform that can be deployed quickly and meet IT standards.
The FM team isn't in Salesforce. That's fine.
Here's the awkward truth most CMMS posts dance around.
If you're a facilities manager reading this, you're almost certainly not using Salesforce today. Maybe somebody in procurement submits PO requests through it. Maybe finance pulls reports from it. But the boots-on-the-ground facilities work — the morning walks, the inspection rounds, the vendor coordination, the broken espresso machine before the exec meeting — none of that is happening in Salesforce. It's happening in a clipboard, a spreadsheet, an email thread, and somebody's head.
That's not a problem. That's the starting point.
The question isn't whether the FM team uses Salesforce today. The question is whether the next tool you choose runs on a platform your company already operates, or whether it's a standalone you'll be integrating, securing, and renewing in isolation for the next ten years.
A native CMMS gives the FM team a clean, mobile-first application designed for their work — inspections, permits, assets, vendors, work orders. They don't need to know it's Salesforce underneath. They just open the app and do their walk.
sonpito is the CMMS your IT team will actually approve
I'll say the quiet part out loud, because Fawn Perazzo and I have had this exact conversation with enough facilities leaders that it's worth naming directly.
The reason most CMMS purchases die in IT review isn't that IT hates facilities. It's that IT looks at a new standalone vendor and sees a list of things they'll have to own — security review, SSO, admin function, integrations, renewals. They're already underwater. They push back, the timeline slips, the project loses momentum, and eventually facilities goes back to using spreadsheets.
A Salesforce-native CMMS changes that math. IT looks at it and sees a managed package on a platform they already operate. The security review file already exists. The SSO is already configured. The admin skillset is already on the team. The renewal goes through the same process as every other Salesforce SKU.
That's a yes from IT they can give without adding to their headcount.
But — and this is the part nobody mentions in the sales pitch — IT will probably ask facilities to fund a Salesforce administrator, fully or partially, to maintain the system. That's a fair ask. Salesforce admins aren't free, and the FM team is the one getting the value. In most companies, the conversation ends up at "facilities funds half an admin, IT manages the resource, everybody's happy." That's a healthier outcome than facilities buying a standalone tool that IT refuses to support — which is where these projects usually land.
If you're an FM leader, factor an admin into your CMMS budget conversation from day one. It changes IT from a blocker into a partner.
How to evaluate any option
Whether you end up looking at sonpito or somewhere else, here's the framework I'd use as a Salesforce customer.
Ask whether it's a managed package or an external integration. Managed packages install into a Salesforce org. Integrations don't. This is the single biggest determinant of long-term operational complexity and total cost of ownership.
Ask about the possible deployment models. Will this go into our customer-facing org, a dedicated FM org, or somewhere else? A vendor without an opinion on this hasn't worked with enterprise customers.
Ask about security review. Salesforce AppExchange security review is rigorous — three rounds is normal, and many vendors give up. If a product is on AppExchange, it's been audited against a long list of standards. If it's "Salesforce-compatible" but not on AppExchange, ask why not.
Ask who owns the platform internally. Get the conversation about admin funding on the table early. It's almost always part of the deal, and surfacing it day one builds trust with both sides.
Ask about AI roadmap honestly. Everybody and their mother is shipping AI features right now. The question isn't whether the vendor has AI — it's whether the AI has clean, governed, unified data to work with. AI on top of fragmented data produces AI slop.
The real question underneath
If you've read this far, you're probably not actually trying to buy a CMMS. You're trying to figure out how the facilities team can work the way the sales and service teams already do — with one trusted platform, clean data, mobile access, IT as a partner instead of a blocker, and a procurement story that doesn't take eighteen months.
That's the right question. The CMMS market spent twenty years answering a different one — how to digitize work orders for a maintenance shop. That's a real problem, but it's not the only problem facilities teams have. For a Salesforce customer, it's not even the most expensive one.
The most expensive problem is operating in a parallel universe to the rest of your business — running a critical function on tools your IT team won't support, your finance team can't audit, and your AI strategy can't reach.
Don't be afraid to push back on the default options. Don't be afraid to bring IT into the conversation early — even if the eye-roll is automatic. The native answer exists now. It didn't five years ago.
-
A Salesforce-native CMMS is a computerized maintenance management system built directly on the Salesforce platform as a managed package — not a separate product with a Salesforce connector. Native means the same security model, same admin skillset, same release cadence, and same AI surface as the rest of the Salesforce environment. It may be deployed into its own dedicated Salesforce org or an existing Salesforce org, managed by the same team that runs Salesforce elsewhere in the company.
-
No. Salesforce Field Service is a field service management platform — built for crew scheduling, dispatch optimization, and complex work order routing for mobile workforces. A CMMS focuses on the administrative and compliance backbone of facilities operations: inspections, permits, asset management, vendor relationships, and case-based incident tracking. The two can coexist in the same company. Field Service is the heavyweight option for work-order-heavy use cases. A CMMS is the right tool for the day-to-day operational work of facilities teams.
-
Yes. A native CMMS is administered by the same team and skillset that runs Salesforce — which means your existing admins can manage it, but somebody has to own it. In most enterprise deployments, IT asks facilities to fund a Salesforce administrator, fully or partially, as part of the deal. Build that into the budget conversation from day one. It turns IT from a blocker into a partner. We recommend that someone from your FM team also “owns” Salesforce and works with the Salesforce Admin on implementation and upkeep. This ensures that the system aligns with operational needs, driving better adoption and faster ROI.
-
A CMMS (computerized maintenance management system) focuses on maintenance, inspections, assets, and vendor relationships. A CAFM (computer-aided facility management) system focuses on space management, floor plans, and move management. An IWMS (integrated workplace management system) tries to do all of the above plus real estate portfolio management and capital project planning. IWMS platforms tend to be expensive, complex, and slow to deploy — what some FM professionals call an "imaginary workplace management system" because the breadth rarely matches the marketing. Most facilities teams need a focused tool, not an everything-platform.
-
Salesforce AppExchange security review is one of the most rigorous in enterprise software — a multi-month process covering code analysis, penetration testing, OWASP compliance, and platform integration patterns. Three rounds is normal; many vendors give up. A product on AppExchange has been audited against standards your IT team would otherwise have to verify themselves. If a product is "Salesforce-compatible" but not on AppExchange, ask why not.
