CRM replacements are relatively uncommon in these interviews: several hundred companies discuss running a CRM, and only a few dozen describe a completed migration or a committed replacement already underway — an observation from interviews, not a measured switching rate, and the pattern behind the CRM nobody leaves. The changes documented fall into two distinct groups. Some companies are adopting their first packaged CRM or retiring a homegrown or legacy system — more than a third of the changes with a known starting point — and most of those go to Salesforce. Others replace one established CRM with another, most often Salesforce for HubSpot or for Microsoft Dynamics. Across both, about two of every three changes with a stated reason come with a broader event, such as a suite consolidation, several CRMs folded into one or an acquisition. About a quarter name no origin, so these are directional findings, not churn rates or market share. The companion reads are what CRM buyers wish they'd known, where the ratings live, and top complaints about CRM platforms.
The pressure that builds
These are the product-related reasons buyers give for replacing a CRM. Some moves are explained by them without a broader event; in others, the same frustrations accompany a consolidation, an acquisition or a change in how the company sells.
An old system that has aged out
The pressure buyers name most, and the main reason behind retiring homegrown and legacy CRMs. “They had a homegrown system beforehand, which is broken all the time,” one buyer says; another describes a simple before and after: “we made a migration from an old Siebel CRM system to Salesforce.” Every homegrown CRM and every Siebel system replaced in these interviews went to Salesforce.
Named in this context: Salesforce · Siebel · homegrown systems
Too complex to run
The main reason companies give for moving from Salesforce to HubSpot. “It's just too difficult to use and almost always requires pretty expert customization to implement,” one buyer says of Salesforce. Complexity also pushes companies off agency-built systems — “it is an extremely cumbersome system. That's why we're transitioning into Salesforce.”
Named in this context: Salesforce · HubSpot
Cost, capability and integration
Named about equally, and often together. One company's move to Microsoft was about “better integration, more widely used and personalization, and long-term cost investment.” Another retired a small CRM it had inherited because “it doesn't scale.” In pharma, one buyer replacing an industry CRM says its “AI roadmap and future capabilities are not on par with Salesforce.”
Named in this context: Microsoft Dynamics · Salesforce · Keap · Veeva
Sales teams that won't use it
Less common, but blunt when it comes up: “We were on Salesforce for a while, which didn't work out because our salespeople just were anti, I don't want to sit there and input stuff in.” It comes up among companies still evaluating, too — a tool used “more as a record keeper” than as help in selling.
Named in this context: Salesforce · SugarCRM
The event that fires the decision
These are the broader events buyers associate with about two of every three explained moves. They help explain when a company acts, though they often overlap with the pressures above, and the share rests mostly on the first two: without suite and multi-CRM consolidation, fewer than half of explained moves name an event.
Consolidating onto one vendor's suite
The event buyers name most, and often Microsoft. When a company runs its ERP and productivity tools on Microsoft, the CRM tends to follow: “So we're largely a Microsoft house from an ERP perspective.” Half of the moves into Microsoft Dynamics in these interviews come with a suite or ERP decision, and most moves into Dynamics leave Salesforce. Suite decisions also run toward HubSpot, Salesforce and industry vendors, such as an auto dealer group consolidating on the supplier that already runs its dealer systems.
Named in this context: Microsoft Dynamics · HubSpot · Salesforce
Several CRMs, folded into one
Teams, brands and regions that each ran their own CRM, brought onto one: “We want to try and consolidate a lot of it, and that's also why we've started moving to better CRM this year.” Half of these moves name no complaint about any one system; the problem is that there are several.
Named in this context: Salesforce · HubSpot
An acquisition, growth or a new sales motion
Acquirers move the companies they buy onto their own CRM — “We've acquired a few companies since then and we migrate them off whatever they're using onto Salesforce” — though sometimes the acquired company's lighter tool wins instead. Growth opens the question too, for example when a company first builds a sales team: “We just brought on a sales team for the first time, so new go-to-market motion that way.”
Named in this context: Salesforce · HubSpot · Keap
Renewals, and the new idea of building your own
No completed or underway CRM move in these interviews was triggered by a contract renewal; renewals come up only among companies still evaluating. A very small number of companies have replaced a CRM with a tool they built themselves using AI app builders — an early signal, not yet a pattern.
Where they go
Across first packaged CRM adoptions, legacy-system retirements and replacements of established CRMs — counting completed migrations and committed replacements being implemented — Salesforce is the most frequently observed destination, followed by HubSpot and then Microsoft Dynamics. Its arrivals come disproportionately from the first two groups: companies replacing homegrown systems, retiring Siebel and other legacy systems, or getting a CRM for the first time. Among companies replacing an established CRM, the movements look different, and Salesforce to HubSpot and Salesforce to Microsoft Dynamics are the recurring paths. Companies leaving Salesforce go down-market to HubSpot, usually over complexity, or into the Microsoft estate. Buyers often describe outgrowing HubSpot, but in the completed and underway moves found here more companies moved from Salesforce to HubSpot than the other way, and HubSpot's own departures scatter in different directions. Within the counted moves, Salesforce, HubSpot and Dynamics all show more observed arrivals than departures. These are directional findings from the interview set; because about a quarter of moves identify a destination without the CRM being replaced, departures are undercounted, and none of this is a measure of vendor growth or churn. The vendor-by-vendor departures are on Salesforce CRM alternatives and HubSpot alternatives.
The industries that run their own CRMs
Some of the most deliberate moves in these interviews happen outside the general-purpose CRMs. In pharma, a company is moving off Veeva to Salesforce, while another buyer warns that “changing over a CRM system in the pharmaceutical industry takes years.” Auto dealer groups move between dealer-specific CRMs, and one rejected Salesforce as too complicated. A health system moved its CRM onto its electronic medical record vendor to keep patient data in one place. And franchise businesses adopt CRMs built for franchises, one on the strength of what other franchisees used.
Due for a stack physical?
Book mine →The stories behind the switches
The counter-current: why most stay
The CRM holds the company's history, and buyers do not expect to get it out cleanly: “it has so much of our data and so much of our current automation that I think the cost of migrating will be too high.” Few have seen it done — “I think it is a huge project to upend and migrate a CRM. I don't know many people who have done that.” One buyer puts it plainly: “A number of the tools are relatively easy to switch. Certainly the CRM is not.” Familiarity holds too: “Salesforce is kind of like the Toyota of the CRMs. Everybody drives one, and you know what you get.” It is not only Salesforce — of HubSpot, one buyer says “it's tricky for us to do a migration because those are all very interconnected,” and another simply that “HubSpot's doing the job. There's no need for us to switch to anything else.”
What this means if you're weighing a switch
In about two of every three explained CRM moves, buyers name a broader event alongside the decision, and many of those moves involve no stated complaint about the CRM being replaced. Other moves are explained primarily by an ageing system, complexity, cost or adoption, and these pressures can also contribute when a larger initiative creates the opportunity. Our recommendations, not practices buyers describe: if a suite, ERP or acquisition decision is coming, decide the CRM as part of it rather than inheriting whatever comes with the larger platform; be clear whether you need more CRM or less, since the moves here run toward Salesforce from homegrown systems and away from it toward simpler tools; scope the data and integration migration before choosing, since that is what keeps most companies in place; and test the new CRM with the people who will enter the data, since a CRM the sales team won't use is one of the reasons companies leave.
Common questions
Why do companies switch CRM platforms?
Relatively rarely in these interviews: few changes are documented compared with how many companies run a CRM, though that is an interview observation, not a measured switching rate. When they do, the pressures buyers name are a homegrown or legacy system that has aged out, complexity that needs admins, cost, capability gaps, integrations, and sales teams that will not use the tool. In about two of every three explained moves buyers also name a broader event — most often consolidating onto one vendor's suite, often Microsoft, or folding several CRMs into one, followed by acquisitions, growth and an ERP decision. Events and complaints often overlap, and no single event explains most moves.
Which CRM do companies switch to?
Across first packaged CRM adoptions, legacy retirements and replacements of established CRMs in these interviews, Salesforce is the most frequently observed destination, followed by HubSpot and then Microsoft Dynamics. Most of Salesforce's arrivals are first adoptions or legacy retirements; among companies replacing an established CRM, the recurring paths are Salesforce to HubSpot and Salesforce to Microsoft Dynamics. These are observed decisions, not churn rates.
Why do companies move from Salesforce to HubSpot?
In these interviews companies moving from Salesforce to HubSpot most often describe complexity — a system that needs expert customization and admins to run — and sometimes sales teams that would not use it, a change in business model or an acquisition that brought HubSpot in. Buyers often describe outgrowing HubSpot, but in the completed and underway moves found here more companies moved from Salesforce to HubSpot than the other way.
Why do companies move their CRM to Microsoft Dynamics?
In these interviews about half of the moves to Microsoft Dynamics come from companies standardizing on Microsoft, often with a Microsoft ERP, so the CRM follows the rest of the estate; some cite cost and integration instead. Most of these moves come from Salesforce.
Why do companies stay with a CRM they complain about?
Because the CRM holds years of data and history that are hard to migrate, it is wired into many other systems, sales teams already know it, and a migration is a multi-year project with an uncertain payoff. In these interviews a contract renewal did not trigger any of the completed or underway moves.
A physical for your tech stack
Peer-powered: built from hundreds of verified buyer interviews, and fitted to the tools you already run. You get a shortlist for your stack and your next steps.
Book my stack physicalFree · no password · your answers are anonymized before they inform research like this.