On 3 September 2026 Salesforce deleted the Enterprise and Unlimited editions. Not repriced — deleted. The Sales Cloud pricing page today offers Free Suite, Starter Suite at $25, Pro Suite at $100, Core at $195, Advanced at $395 and Max at $550, per user per month, billed annually. Salesforce's own newsroom says Core replaces legacy Enterprise with "70% more value," which is the standard way of announcing that the nearest equivalent to a $165–175 seat now costs $195.

That tells you what every CRM comparison article is worth: most describe a price list that no longer exists, and will go on describing it for another year. So here is the short version up front, because I hate articles that make you scroll to the bottom for the payoff.

A feature matrix compares the one cost that is easy to compare. You are buying three things, and only the first is on the chart: a schema, an opinion about what a customer and a deal are that you will live inside for years; a workflow, the sequence the software believes selling follows; and a migration cost you pay on the way out, at a moment you don't choose. The workflow is where adoption dies, for a reason put better on Hacker News than any vendor will put it — "CRMs are tools for sales managers… ease of use for [reps] is just not a concern of the buyer." The person who signs the contract is not the person who types into the box. The migration cost nobody prices at all, and it is the part I'd weight hardest.

My verdict, flatly. If you are a small company — say under fifteen people who touch customers — buy Zoho CRM Standard at $14 per seat per month on annual billing, or Zoho's own Bigin at $7, and spend what you saved on getting your data model right. If you need a deal pipeline that genuinely drives your week, Pipedrive Growth at $39 is the honest mid-point. If your company already lives in Microsoft 365, Dynamics 365 Sales Enterprise at $105 is defensible purely because of the attach licence. If you have an engineer and a strong opinion about your own schema, self-host EspoCRM. And under thirty people I'd refuse Salesforce and HubSpot Professional, for reasons that have nothing to do with the software being bad and everything to do with what you sign.

The failure statistics are a citation loop, and I'd stop quoting them

You cannot read about CRM for ten minutes without meeting a number: 30%, 50%, 70% of CRM projects fail. I went looking for the studies. Most of them aren't there.

The 70% figure is attributed to Butler Group and Butler Group never published it. An analyst said it out loud around 2002, a journalist wrote it down, and it has been cited as research for twenty-four years. Michael Krigsman, who compiled the canonical table of these stats, checked: "the Butler Group never reported that statistic. You won't find it in any report."

The Gartner numbers are a single survey from late 2001 of roughly five hundred large Gartner clients, which found about 55% had "failed to meet expectations" — not failed. Analyst Ed Thompson later said they never repeated it; the scarier "65% rising to 85%" pair was a *forecast*; and the 80% applied only to sales-force automation. Gartner's own research director at the time, Scott Nelson, described the body of work in words that should end the conversation: "This was not one monolithic quantitative study. It was pieces of studies put together." He also said, "there isn't a unified definition of failure."

The HBR version — "around one-third of all CRM projects fail," from a 2018 article — cites a 2017 CIO magazine piece, itself an average of about a dozen analyst reports whose figures ranged from 18% to 69%. Averaging numbers that disagree by fifty-one percentage points produces a figure with no meaning. AMR Research, in three consecutive years, reported 18%, then 31%, then 29%; only the frightening ones survived. And the work that does describe its method is never cited: Bob Thompson's CRMGuru research, 448 projects in 2002 and about 2,500 more through May 2005, found roughly two-thirds self-reported *success*.

The one well-sourced figure in the whole literature isn't a failure rate at all. CSO Insights' 2006 study, n=1,275 companies, found that fewer than 40% of firms implementing these systems had end-user adoption above 90%. That's a measurement of adoption, from before the cloud, and it's still the most useful thing in the pile: the risk isn't that the project explodes, it's that half your people quietly don't use it. Nobody has measured the rest credibly, and the historical sampling that does exist came from large-enterprise client bases — a population you are probably not in. So stop quoting failure rates.

What has actually changed since 2022

Four years ago the interesting question was which vendor had which feature. That's settled and boring — at the small end they all have pipelines, custom fields, email sync and automation. What changed is the *shape of the bill*.

Pricing moved from per-seat to per-seat plus a meter. Salesforce sells Agentforce capacity as Flex Credits at $500 per 100,000 — half a cent each, 20 credits an action. Core includes 500,000 credits per org per year, and Salesforce's own worked example of service case management consumes 360,000 *per month*: the annual allowance is gone in six weeks, and unused credits do not roll over. The escape hatch is a $125 per user per month add-on that makes employee usage unmetered — 64% on top of Core's $195.

HubSpot now runs two pricing models at once. The March 2024 seats model — Core, Sales, Service and Revenue seats plus free View-Only seats, Sales Hub Professional at $90 per seat annually, Enterprise from $150 — runs in parallel with a "flexible seats-and-credits" model for new EMEA customers that has only GTM and Ops seats and abolishes marketing-contact tiers. On top of either, HubSpot charges a required one-time onboarding fee: $1,500 for Sales Hub Professional, $3,500 for Enterprise, $3,000 and $7,000 for the Marketing equivalents, all excluded from the headline price. For five seats on Sales Hub Professional that's $5,400 of licence plus $1,500 of onboarding — 22% of year one. Credits are $0.010 each with 3,000 a month on Professional, don't roll over, and the default spend cap sits 50% *above* your allowance, so overage is on unless you turn it off.

The asymmetry is what I'd actually warn about. HubSpot's terms say plainly: "You are not permitted to downgrade your Subscription Service during your Current Term." Seat reductions cannot go below your order form's minimum commitment, there are no refunds of prepaid fees, and on renewal HubSpot "may increase your Subscription Fees up to our then-current list price" with thirty days' notice. Adding is instant and billable; removing is a scheduled event you must request five business days ahead.

Microsoft did almost nothing, which is itself informative. Dynamics 365 Sales Professional is still $65, Enterprise $105, Premium $150, billed yearly, unchanged in the October 2026 licensing guide, with no published monthly price at all. The attach licence is the detail that matters: a user who needs a second Dynamics app pays $20 rather than full price, so Sales Enterprise plus Customer Service Enterprise is $125 a seat instead of $210. And the trap: Sales Professional has no Power Apps or Power Pages use rights at all, and no Copilot.

Pipedrive quietly renamed and re-cut its ladder: Lite $14, Growth $39, Premium $59, Ultimate $79 per seat per month annually, with Essential, Advanced, Professional, Power and Enterprise now legacy — so any 2026 article listing five Pipedrive tiers is describing a price list you cannot buy. Lite has no automations and no email account sync, so the real entry point is Growth at $39. Zoho still publishes everything: Standard $14, Professional $23, Enterprise $40, Ultimate $52 annually, Bigin at $7, $12 and $18. Its trap is Zoho One, a bargain at $37 per employee per month until you read the condition — "Your business will have to commit to purchase Zoho One licenses for ALL employees on payroll." Five CRM users in a twelve-person company means twelve licences, or $90 per user on flexible pricing.

That is the shortlist, and it's short on purpose. Freshsales puts sequences behind a jump from $9 to $39. Monday CRM sells seats in blocks of 3, 5, 10, 15, so a six-person team buys ten — a 67% premium on headcount. Folk keeps custom objects, deals and API access behind its $48 Premium tier and has no documented whole-workspace export I could find. SuiteCRM 8 shipped in 2021 and SalesAgility is still extending version 7 to December 2027 "to allow a successful transition to SuiteCRM 8" — when the maintainer won't call the successor ready after five years, that's your answer. Twenty is genuinely alive, around 59,600 GitHub stars with commits landing today, but it's open core with enterprise-only files marked inline in the same tree and cloud Pro caps you at 50 API calls a minute: worth watching, not yet worth betting your records on.

The questions that actually decide it

Here is the spine I'd use. Each question eliminates options; feature checklists don't.

  1. How many people will type into it, as opposed to read it? This reprices everything. Someone described a fifteen-person team where "90% of people might only log in once a month to have a look at the pipeline — don't want to either have a shared account or to pay $150/month so we stick to a spreadsheet." If your answer is "three type, twelve read," you want free read-only seats, and HubSpot's View-Only seats being unlimited and free is the best argument in its favour.
  1. Do you have, or will you hire, someone whose job includes this tool? The most honest line I've read about Salesforce: it "is intended mostly for companies that can hire a dedicated Salesforce admin (or two) […] which means that smaller companies that don't have the resources to do that would be better off with one of the less-flexible CRMs." The same goes for open source — of CiviCRM, a commenter on lobste.rs said it suffers "the somewhat typical OSS affliction of basically being designed to be operated by a developer… and not necessarily accessible to the staff such users are likely to have." Admin burden isn't a property of the licence; it's a property of the flexibility.
  1. Does your sales motion run on email, or somewhere else? The whole Western CRM market assumes email is where the relationship lives: threads sync, addresses are the identity key, sequences are the core automation. If your conversations happen in a messaging app instead, most of that machinery is decoration you're paying for.
  1. What is the second system, and will the vendor still be here? CRMs are chosen alone and then live in a crowd. The market dynamic, bluntly: "If you look at 1000 data integration or marketing automation tools on the market, 1000 of them will have OOTB integration with Salesforce as a selling feature." One developer, burned twice — when 37signals mothballed Highrise and when Batchbook was discontinued — concluded that "going for the biggest most well-known market-leading CRMs ends up being a good choice just from the point-of-view of data longevity and peace of mind." That is the honest case *for* the expensive incumbent, weighed against a consultant on the same thread: "About 1/3 of our projects are coming in and fixing something other consultants screwed up."

The best formulation of when all this actually resolves came from u/ops_and_chaos in r/CRM in August 2026: "I'd switch when I realized we were spending more time accommodating the CRM than the CRM was spending accommodating us." If you can keep that sentence false, you chose well.

The exit cost, which no chart prices

Start with how migration vendors bill, because their price list is an honest description of the problem. MigrateMyCRM defines its unit this way: "a record is a single entity, such as a contact, an email, an attachment, a deal, etc." So a company with 5,000 contacts, logged email and attachments is not a 5,000-record migration — it's a hundred-thousand-record one. Three details in that price list tell you the rest: the basic plan includes ten migration runs; "catch the records that changed while we were migrating" is a priced Delta Migration at +15%; and changing your field mappings after the fact is a $149 SKU.

Moving the rows is not the cost. The RevOps lead at Hightouch, after a HubSpot-to-Salesforce move: "from start to finish, we migrated all of our data from Hubspot to Salesforce in less than four hours" — and "we spent more time configuring Salesforce than we did migrating our data." The clearest practitioner version comes from u/DifficultyDirect8881 in r/CRM in May 2026, writing up a HubSpot-to-GoHighLevel move under the title "the stuff nobody puts in their tutorial videos": "The contact import was the easy part. Took a few hours. Clean data, field mapping done right, no drama. The automation rebuild actually took weeks." His diagnosis is the schema point exactly — HubSpot is relational, companies and contacts and deals linked, while GHL is contact-centric, "everything radiates from one flat contact record," and "that structural difference means nothing transfers automatically."

So what doesn't come with you:

  • History. Salesforce's AccountHistory, CaseHistory and ContactHistory objects do not support create() — "they are audit tables. If you could edit your audit trail, it would not be entirely useful as an audit trail." Entirely reasonable, and it means "when did this deal change stage" does not survive the move. Your funnel trend reporting restarts at zero on cutover day.
  • Automation and reports. Flows, assignment rules and approval processes have no import path; reports and dashboards, none transfer; formula fields don't execute in the destination, so historical values land as frozen static numbers.
  • Email history, which is priced separately and quietly. u/everrest88 in r/CRM in October 2026, answering a thread asking for people's worst migration experience: "How about discovering that you can migrate almost everything from Pipedrive to HubSpot for free by exporting csv files, but migrating Emails is possible only by a 3rd party app and costs $2K?" The records are free; the conversation is two thousand dollars.
  • Restorability, if you assumed an export was a backup. One practitioner on Salesforce: "You can't restore backups! You can export your data, but there's no way to import it, because you can't set the object Id." Relationships are stored by ID and the IDs change on insert, so you track old and new IDs for every record and "insert the objects in topological order."

And the exports are getting narrower, not wider. In July 2026 a Salesforce customer posted in r/salesforce about a notice regarding heavy use of the Data Export Service — which they said they hadn't used as described — reminding them that Salesforce "follows a shared responsibility model" and that "customers are responsible for implementing comprehensive backup and recovery measures." In the same thread u/alstc described the practice: "They've been rate limiting exports since the last few months… Before I could just mass-click the export link for each ZIP file, now you get a 429 error if you try to download more than one." A September 2026 thread in the same subreddit is someone trying to reconstruct a business from nothing but an export's ZIPs and CSVs, the original org gone, asking how people handle "the consolidation and relationship mapping" — archaeology, because nobody kept their own copy. Attio shows the same pattern in documentation rather than anecdote: a full-workspace CSV backup on every plan, and also, plainly, that emails cannot be exported and enriched attributes cannot be exported at all, coming out as blank cells.

Here is why I'd weight all of this heavily. Exit cost is not just your risk — it is the vendor's pricing power, and the people who negotiate these contracts say so out loud. When a customer posted in r/salesforce in July 2026 that they'd cut headcount from the thirties to the twenties and their account executive was "already threatening discount reductions due to the headcount/license reduction," u/Stephen9o3 answered: "Salesforce will work very hard to prevent ACV contraction in any way they can… They know most customers won't actually switch CRMs on a whim, cost of change being so high, so they need to think you're serious." Read that twice: the difficulty of leaving is why the renewal quote looks the way it does, and shrinking your company can cost you money. A customer in another thread the following month reported their base quote "went up 9% this year," and signed a 36-month term purely to escape the annual uplift.

One counterweight, because I don't want to overstate lock-in: an IT director wrote in June 2026, "I moved a company off of Salesforce in 45 days without a big issue." The harder problem is rarely technical. At another of his clients "the sales VP shot down a conversion because he liked being able to say 'we run on Salesforce!'", and u/Vladeeno, in r/CRM in November 2025, saw the same thing structurally: the decision "was based almost always on a Senior Sales Manager that has used Salesforce before and 'liked it'."

Build versus buy, honestly

I've built a quoting and pricing system for our gemstone business and I've been writing and rewriting our own CMS since 2017, so I have no principled objection to building software rather than renting it. I would still not build a CRM, and I want to be precise about why, because the reason isn't "it's hard."

It isn't hard. The record-keeping part of a CRM is tables with a UI, and anyone reading this could build a serviceable one in a fortnight. The reason to buy is that the cost is almost entirely in the parts that don't look like the product — Gmail data on your own server means a CASA security assessment reverified at least every twelve months, and then deduplication, where one builder's summary is exactly right: "merging is judgement, not code, and if nobody owns it the database quietly rots." Jason Lemkin, who has built substantially in-house at SaaStr, says it best: "Building it is the fun 10%. The other 90% is keeping it running."

The key-person cost is what kills these projects. Someone recounted a conversation with an owner thrilled to have dropped a $40,000 Salesforce bill after an employee built a CRM with AI assistance, until asked what happens when Joe leaves or has a health emergency: "This will save him $40K a year until he decides to hire another person, at which point this 'free' software will cost him $150K per year."

The insight that reconciles it: "A CRM that can satisfy two orgs seems about 10x more complex than a CRM that can satisfy one." Vendor CRMs are expensive because they're general; your build is cheap because it's specific — and stays cheap exactly as long as your company stays the shape it is today.

People build anyway, and the honest thing is to report it. In September 2026 u/yfraw described in r/CRM a company that had moved to Zoho One three years earlier as a cost-saving exercise, found "it never really felt like one smoothly integrated platform," ended up gluing Zoho to Xero with Make.com, and was now at 25 users heading for "an in-house CRM that we've built around the way our company operates" — a rational decision at exactly the scale this article is about. Against it: the same subreddit that month carried a thread titled "My manager says RevOps doesn't need to be technical. Now we're migrating HubSpot to Twenty," to which u/ride_whenever replied, "trying to one shot a crm migration is going to be a disaster." Building deliberately, around a process you understand, is defensible; building because the migration looked easy is not.

The middle path is the advice of someone who built their own after leaving Salesforce: "always always always keep the canonical source of your data in house." Buy the CRM, own a copy of the data, build the thin specific thing on top. That's a strategy; replacing the record of every customer relationship you have with a side project is not.

What I'd do, in order

  1. Write your schema down on one page — objects, the fields you genuinely need, how they relate — before you see a demo. If a product can't express it in an afternoon's configuration, it's the wrong product, whatever the chart says.
  2. Open the vendor's export documentation before the pricing page. Can I get email history out? Attachments with their filenames? Enriched fields? What are the API rate limits? If any answer is bad, you now know the real price.
  3. Assume you will migrate once. Budget ten times the tool cost, accept that reports, automations and field history don't come with you, and keep a copy of your own data somewhere you control from day one — so the day you leave is a configuration problem rather than an archaeology problem.
  4. Buy the cheapest tier that includes working automation, not the cheapest tier. A CRM without automation is a shared spreadsheet with a worse editor — and if that's all you need, use the spreadsheet and keep the money.
  5. Don't buy AI capacity in year one. Rates change on thirty days' notice or less, overage is on by default, and unused credits expire at Salesforce, HubSpot and Microsoft alike.

After thirty years of this, the pattern I trust is that the systems you can leave are the ones you end up keeping, and the ones built to be impossible to leave are the ones you eventually leave at enormous cost. That's why I'd refuse Salesforce under thirty people — not the $195, but that the decision becomes very hard to reverse at precisely the moment you've learned enough to want to. The useful question was never "which has the most features." It's "what does this cost me in year four, and what do I lose on the way out." Nobody puts that in a chart, which is exactly why it's worth writing down.