TL;DR: moving from HubSpot or Pipedrive to a custom CRM makes sense when three signals line up: a team of 15 to 20 paid seats on a Professional plan, a sales process the tool can no longer model without workarounds, and data constraints (sensitivity, hosting) the vendor does not cover. Below those thresholds, a well-configured off-the-shelf CRM stays cheaper. The migration itself takes 8 to 12 weeks: complete export first, then a 2 to 4 week cutover with the old tool in read-only mode.
Key takeaways
- HubSpot Sales Hub Professional is listed at $90 per seat per month on an annual commitment, plus a $1,500 onboarding fee (HubSpot pricing page, September 2026): 20 seats cost $21,600 a year in licenses.
- Pipedrive Professional is listed at $59 per user per month billed annually (Vendr, February 2026): 20 users cost $14,160 a year.
- A custom CRM costs €8,000 to €25,000 for a complete tool and €30,000 to €100,000 to replace an off-the-shelf product; the financial break-even sits around 15 to 20 HubSpot Professional seats over three years, higher on Pipedrive.
- 55% of CRM implementations fail to deliver the expected value (Nutshell, May 20, 2026): a botched migration costs more than the licenses it saves.
The short answer: three signals, never just one
A small or mid-sized company leaves HubSpot or Pipedrive for a custom CRM when the license bill, the process workarounds and the data constraints all point the same way. One signal alone is not enough: a high bill with a standard process is solved by dropping a tier, an unusual process with five users is solved with custom fields and two automations, a requirement to host data in France is sometimes solved by a European vendor. It is the combination that makes custom rational. This article gives the thresholds, what the two vendors actually let you export, then the four-phase migration plan.
When staying on HubSpot or Pipedrive is the right call
Staying on an off-the-shelf CRM is the right call for most companies with 10 to 100 employees. Three situations come up all the time.
Fewer than ten users and a classic pipeline. Pipedrive Essential is listed at $14 per user per month billed annually according to Vendr (February 2026), and HubSpot Sales Hub Starter starts at $20 per seat on monthly billing according to HubSpot's pricing page. A team of eight pays between $1,344 and $1,920 a year; no custom build gets anywhere near that, maintenance included.
The problem is the setup, not the tool. A twelve-stage pipeline where seven stages are never used, mandatory fields left empty, duplicates, a team re-keying everything into Excel on the side: these symptoms describe a badly configured tool, not a bad one. A clean-up is measured in days. That was the choice made for Horus Condition Report, a niche software vendor selling in two languages: Pipedrive configured around the real process was enough.
The ecosystem matters more than the CRM. If your sales reps live in Gmail and invoicing is wired in through a native connector, a custom CRM would have to rebuild those integrations one by one, a hidden cost that often tips the calculation back toward the off-the-shelf product.
The table below sums up the decision by starting situation.
| Situation | Decision | Why |
|---|---|---|
| Fewer than 10 users, classic pipeline | Stay, Essential or Starter plan | Licenses under $2,000 a year: no build is cheaper |
| 10 to 20 users, symptoms of poor setup | Stay, clean up the configuration | Pipeline, fields and permissions are fixed in days |
| 15 to 20 Professional seats, daily workarounds | Evaluate migration | Three-year licenses comparable to a custom CRM |
| Sensitive data, mandated hosting, no multichannel | Migrate, after scoping | Constraints no vendor setting removes |
When migration becomes rational
Migration becomes rational when three years of license costs meet the price of a custom CRM and the process no longer fits the tool. HubSpot Sales Hub Professional costs $90 per seat per month on an annual commitment, $100 monthly, plus a mandatory $1,500 onboarding fee (HubSpot pricing page, checked September 21, 2026). Fifteen seats come to $16,200 a year, twenty seats to $21,600. Over three years, twenty seats represent $64,800 in licenses, before add-ons. Pipedrive Professional, listed at $59 per user per month billed annually, puts twenty users at $14,160 a year, or $42,480 over three years.
On the other side, a custom CRM replacing an off-the-shelf tool runs from €30,000 to €100,000 depending on scope, figures detailed in my 2026 pricing guide, plus annual maintenance. The two curves cross around 15 to 20 HubSpot Professional seats, and more like 25 to 30 Pipedrive users. That threshold is only a necessary condition: a team of twenty whose process fits HubSpot has no reason to move.
The second signal is the process, and you recognise it by the workarounds: deals tracked in a spreadsheet because the CRM cannot handle two linked pipelines, free-text notes because the business object does not exist, follow-ups managed from memory because the native automation does not know the rule. When a team spends more time squeezing its business into the tool than selling, the tool no longer models the business.
The third signal is about data. Health data or data on minors, mandatory hosting in France or the European Union with your own admin access, real-time multichannel handling: these constraints are not solved in a settings menu. That was the situation at e-Enfance, the French association operating 3018, the national helpline against online abuse: the Emma CRM, co-built for twelve counsellors and managers, brings together five channels, integrated telephony and a sovereign AI hosted in France, because no generic tool combined those three requirements.
What HubSpot and Pipedrive actually let you export
Both vendors export most of your data, but not in the same way, and this is the first thing to check. HubSpot exports contacts, companies, deals, tickets and custom objects in CSV, XLSX or XLS, with a limit of 1,000,000 rows per file, 300 exports per rolling 24-hour window and files that stay downloadable for 30 days, according to HubSpot's export documentation. Activities (calls, notes, emails) do not come out with the records: you have to go through activity reports or the engagements API.
Pipedrive exports leads, deals, organisations, people, activities, notes and files in XLSX or CSV, with notes in HTML or plain text, according to Pipedrive's documentation. Activities, notes and files attached to deals are exported separately, files stored on Google Drive are not exported, and exports remain available for 28 days.
The table below compares what each vendor lets out.
| Data | HubSpot | Pipedrive |
|---|---|---|
| Records (contacts, companies, deals) | CSV, XLSX, XLS; 1,000,000 rows per file | CSV, XLSX; export per object |
| Activities and notes | Activity reports or engagements API | Separate export; notes in HTML or text |
| Attached files | Not included in record export | Separate export; Google Drive files excluded |
| Email history | Via the API, not one click | Not included in the standard export |
| File availability | 30 days, 300 exports per 24 h | 28 days, administrators only |
Practical consequence: conversation history is the hardest data to recover from either vendor. A company selling on six-month cycles must budget an API extraction before signing anything.
How to migrate without losing your history: the four-phase plan
The migration runs in four phases over 8 to 12 weeks, not counting the build itself. The Nutshell guide (updated May 20, 2026) gives orders of magnitude consistent with what I see: 6 to 8 weeks for a simple migration, 8 to 12 for a standard one.
Phase 1, audit and complete export (weeks 1 and 2). Export everything that can be exported, API included, before any decision. Count the records, measure the duplicates, list the fields that are actually filled in: a field filled in on 12% of records will not be migrated, it will be dropped. This phase produces the mapping between source fields and target objects, and cleaning takes longer than the transfer itself.
Phase 2, building the critical path. The custom CRM starts with the path that hurts most, usually the main pipeline and follow-ups, put in the hands of two or three users with real data. Their feedback corrects the mapping before the full migration.
Phase 3, parallel cutover (2 to 4 weeks). The old CRM goes read-only, the new one becomes the system of record. Beyond four weeks, the two systems drift apart and nobody knows which one is right. The rule: no more data entry in the old tool after the cutover date.
Phase 4, decommissioning. Keep a complete, dated, offline export before closing the account, and cancel at the end of the annual commitment: a cutover scheduled two months before renewal avoids paying for two tools for ten months.
What I see in the field
On my CRM engagements, the first answer is almost always a fix to the tool already in place. At e-Enfance, I first worked on their off-the-shelf CRM, Salesforce, as an administrator (Apex, LWC components, 3CX telephony), a separate engagement from the Emma CRM build: working inside the existing tool made it possible to know what a configuration could or could not achieve. For Horus Condition Report, the answer went the other way: bilingual Pipedrive, properly configured, and no custom build.
The migration study fits in a Sprint from €400: export audit, data count, field mapping, and costing of the three scenarios (stay and fix, switch vendor, build). The rest is a fixed quote after a scoping call; the three engagement modes are detailed on the custom CRM page.
One exercise to run this week: run a full export of your CRM and look at what is missing. If conversation history is not in there, you already know the first line of your migration budget. If everything is there and your licenses stay under $10,000 a year, the right answer is probably to fix the tool, not to replace it.
Frequently asked questions
At how many users does a custom CRM become cheaper than HubSpot?
Around 15 to 20 HubSpot Sales Hub Professional seats ($90 per seat per month billed annually), three years of licenses ($48,600 to $64,800) meet the price of a custom CRM replacing an off-the-shelf tool (€30,000 to €100,000). Without an unusual process or a data constraint, staying on HubSpot remains the right choice.
Can you recover email and call history when migrating from HubSpot?
Yes, but not through the standard record export. HubSpot activities (emails, calls, notes) are extracted through activity reports or the engagements API, which requires development work or a third-party tool. This point must be costed before the decision, because it is often the most expensive part of the transfer.
How long does a migration from Pipedrive to a custom CRM take?
The migration runs 8 to 12 weeks for a small or mid-sized company: two weeks of audit and export, the build of the critical path, then a 2 to 4 week cutover with the old CRM in read-only mode. The full build of the tool adds to that timeline and is set during scoping.