A wave of AI-native challengers is going after Salesforce and HubSpot on the promise that the system configures itself. Nobody selling that promise will say how long the migration underneath it actually takes.
The pitch from every AI-native CRM entrant this year is a version of the same sentence: the software builds itself, so you skip the part everyone hates. It's a good pitch, and it's answering the wrong question. The part everyone hates was never configuration. It was migration — and migration doesn't get faster because the destination system is smarter.
The market making this pitch, in numbers
The category is real money, not a niche. The global CRM market is valued at roughly $72 billion in 2025 and projected to exceed $130 billion by 2030, and Salesforce alone accounts for around $35 billion of annual revenue — a scale that tells you how much switching friction the incumbents have built up over two decades of deep configuration and integration.
Against that, a new generation of challengers has raised real capital on the self-configuring pitch: Attio has raised $33.5 million in a Series B positioning itself as AI-assisted with a human in the loop rather than fully autonomous; Clay raised $46 million and functions as connective tissue across go-to-market workflows, with some teams reportedly running it as their primary CRM outright; Folk, a European entrant, markets itself as closer to "Notion meets CRM," leaning on AI auto-categorisation; and newer entrants like Lightfield pitch a system that ingests data and infers pipeline structure without administrative setup at all.
Early adopters — reportedly mostly 10-to-200-person startups — are already ditching legacy CRMs entirely. What none of the coverage of this shift says is how long that ditching actually took, for a team that size, with their specific data. The absence of that number is the story.
Why "self-configuring" isn't the same clock as "migrated"
Setup and migration are different problems wearing the same name. A self-configuring system removes the admin work of building pipelines and fields from scratch. It does nothing about the four things that actually determine how long a CRM replacement takes for an existing sales organisation.
Visual 1 — What actually sets the migration clock
Factor | Why it drives timeline | What the "self-configuring" pitch doesn't touch |
|---|---|---|
Historical data volume & quality | Years of notes, custom fields and duplicate records need cleaning before they mean anything to a new system | An AI can ingest messy data faster; it can't decide what's worth keeping |
Integration count | Every connected tool — marketing automation, billing, support, the data warehouse — needs re-wiring | Integrations depend on the other systems' APIs, not the new CRM's intelligence |
Customisation depth | Bespoke approval flows, territory rules and comp-plan logic built up over years | The new system still has to replicate or deliberately drop each rule, one by one |
Rep habit change | Adoption, not setup, is what determines whether the new system actually gets used | A smarter interface shortens training slightly; it doesn't remove the change-management curve |
How to read it: The self-configuring pitch addresses the top-left cell of a much bigger grid. The rest of the grid is exactly the same size it was five years ago, regardless of how intelligent the destination system is.
What the "10-to-200-person startup" detail is actually telling you
The reported early-adopter profile is the most honest data point available, precisely because it isn't being marketed as one. Small teams migrate fast for a structural reason that has nothing to do with AI: less historical data to clean, fewer integrations to rebuild, fewer bespoke rules accumulated over time, and a rep headcount small enough that habit change happens through a few conversations rather than a formal enablement programme.
None of that scales linearly. A 500-person sales organisation considering the same move isn't facing a bigger version of the same migration — it's facing a different category of problem, in every one of the four rows above, at once.
How to size your own migration timeline, since no vendor will do it for you
Count your integrations, not your users. Integration count correlates with migration time far more reliably than headcount does.
Audit custom fields and approval logic before you shortlist a replacement. This inventory takes a week and saves months of surprise later.
Ask any vendor for a reference customer at your team size and data volume, specifically — not their fastest case study, their most comparable one.
Separate "live in the new system" from "reps have stopped using workarounds in the old one." Vendors report the first date. RevOps lives with the second.
What follows from this
Budget the migration as a distinct project from the licence decision. The two get bundled into one evaluation timeline far too often, and the migration is usually the larger cost and the larger risk of the two.
Treat integration count as your primary sizing variable when comparing vendor timelines against your own situation. It's the factor most consistently underweighted in both vendor pitches and internal planning.
Expect the AI-native pitch to keep improving setup speed and staying roughly silent on migration speed, because setup speed is the demo-able part and migration speed depends on your data, not theirs.
The category will keep growing — the market numbers support that regardless of which vendors win. What won't arrive on schedule is an honest, published answer to the actual planning question RevOps leaders are asking. Until it does, the only reliable estimate is the one you build from your own integration list, not the one in someone else's pitch deck.
Sources and method. A SalesHubMedia original. CRM market sizing ($72 billion in 2025, projected above $130 billion by 2030) and Salesforce's approximately $35 billion in annual revenue, alongside funding and positioning detail on Attio ($33.5 million Series B), Clay ($46 million raised), Folk and Lightfield, and the reported 10-to-200-person early-adopter profile, per Starts Club. The migration-timeline framework and its four driving factors reflect SalesHubMedia's independent analysis; no vendor in this piece has published a formal migration-time benchmark, which is itself the article's central finding. Journalism, not procurement advice. Corrections will be made openly on this article.
