HubSpot wins solar, heat pump and EV installers on the way up - and loses them as soon as the install team starts using it. Five patterns we keep seeing in migration calls.
Matt Franklin
Over the last year, more than thirty clean-energy installers have walked into a Payaca demo telling roughly the same HubSpot story. The names and tech stacks change. The shape of the exit is almost identical.
They started on HubSpot at 5-10 people because the free tier and the marketing tools were genuinely useful. They paid the upgrade to Sales Hub Professional somewhere around 15 employees. By the time they crossed 25-30 people and started doing 20+ installs a month, the system was already breaking, and the migration conversation had begun.
This isn't a HubSpot critique post. HubSpot is excellent software for what it was built for. It's a post about why "what it was built for" stops being what a clean-energy installer needs the moment quotes stop being deals and start being projects.
Already mid-migration off HubSpot?
We've helped installers move off HubSpot in 2-4 weeks, with customer records, deals, and pipeline history brought across. Book a 20-minute walkthrough and we'll show you what your workflow looks like in a system built for the job.
HubSpot's data model assumes a Deal moves through a pipeline and ends at Closed Won. For a software vendor or an agency, that's true: signing the contract is the finish line.
For an installer, the signed proposal is the starting line. After Closed Won, the project still has to be designed, surveyed, submitted to the DNO, permitted, scheduled, installed, commissioned, signed off, invoiced, and registered. The CRM has no concept of any of that. So the office team builds a parallel system: a Trello board, a Google Sheet, a folder structure in Drive, a separate scheduling tool. Each one of those becomes a place where information lives that isn't in HubSpot.
By the time you have 30+ jobs running, your "CRM" is the thinnest layer of three or four systems, and your team is reconciling between them every morning.
HubSpot is sold as one CRM, but the workflow an installer ends up running spans four. Sales Hub for the pipeline. Service Hub so the post-install support tickets sit somewhere. Operations Hub for the sync wiring that keeps the contact record consistent across the others. Often Marketing Hub too, because that's where the lead-gen story started.
Each hub has its own price ladder. Each hub has its own Pro and Enterprise step. And the workflow that actually matters, a customer becomes a quote becomes a job becomes a paid invoice, is spread across all of them. The system is doing one thing. The bill is itemised for four. Plus the implementation partner who wires it together.
Most installers don't see this until renewal. They see it when someone runs the line items and notices that the CRM has more SKUs attached to it than the rest of the software stack combined.
This is the one HubSpot users talk about least and feel most. There is nothing in HubSpot that knows about MCS, DNO connections, BUS voucher applications, MIS 3005 commissioning paperwork, F-Gas records, or US AHJ permit tracking. There is no reason there should be. HubSpot is a CRM.
So compliance lives somewhere else. A spreadsheet, a folder, a separate platform, the engineer's head. Every job is a copy-paste exercise: customer details out of HubSpot, into the DNO portal, into the MCS Installation Database, into the warranty registration. The data is identical. The work is manual. And every single one of those handoffs is a place where wrong information makes it into a regulator's system.
A purpose-built platform treats compliance as a stage in the project, not a parallel universe. Submission status, voucher state, and certification are fields on the job, not tabs in a different browser.
HubSpot's mobile app is a competent sales-rep app. You can log a call, update a deal stage, fire off a quick email from a stage gate. That's the use case it was designed for, and it does it well.
It is not a field engineer's app. An installer on a flat roof in February doesn't want to log a call. They want to:
When that workflow doesn't exist in your CRM's mobile app, your engineers stop opening the CRM. They take photos in WhatsApp, send the commissioning sheet by email, and let the office reconcile it. Your data quality starts decaying the moment the field team disengages, and it doesn't come back.
The reports you can build in HubSpot are good ones. Deal velocity. Pipeline coverage. Conversion rate by source. Average deal size.
The reports a 30-50-install-per-month operator actually needs to make decisions look like this:
None of those exist in HubSpot. They can't, because the underlying records don't have the fields. Building them means writing custom objects, and at that point you're paying a HubSpot consultant to build a project management tool inside a CRM. That's the moment most operators we talk to start a migration project.
Three patterns dominate the off-HubSpot conversations.
The first is "back to spreadsheets, plus a job-management bolt-on." This is the cheapest exit and the most common short-term answer for businesses under 15 people. It works for a while. It does not survive the next hiring round.
The second is enterprise field-service software like ServiceTitan or Salesforce Field Service. The fit is closer because these tools understand jobs and schedules, but the price tag and the implementation horizon (often 6-12 months) put them out of reach for most growing installers. ServiceTitan in particular is excellent for HVAC and plumbing but doesn't natively understand solar, heat pump or EV charger workflows.
The third is a purpose-built clean-energy platform. Payaca sits here. The pitch is simple: one system that runs from lead to commissioned job to paid invoice, with compliance built in, design tools that connect, and a mobile app actually built for engineers on site. Pricing is sized for scaling installers, not for sales-led SaaS organisations.
HubSpot is a great call for clean-energy businesses that are still primarily sales-stage and pre-installation. If you're running a 5-person business that hasn't built out the install side yet, or you're a lead-generation company that hands jobs off to subcontractors, HubSpot's marketing tooling and lead-management is hard to beat. We're not trying to talk you off it.
The question isn't whether HubSpot is good software. It is. The question is whether you're using it for what it was designed for, or whether your team is quietly building a project-management system inside it because there isn't one anywhere else.
If you recognise the pattern, you're not the first to spot it. The exit conversation is a worn path now, and there's no need to re-walk every step yourself.
See how Payaca helps clean tech installers save time and grow their business.
Book a demo
Decision-stage migration guide for UK clean-energy installers leaving HubSpot. What imports cleanly, what doesn't, what HubSpot stays good at, and how to sequence a 4-week cutover without losing project history.
Mid-sized UK installers spend two engineers a year maintaining a bespoke CRM that handles maybe 60% of the workflow. The other 40% is on spreadsheets. Here's what's actually being paid for, and why the build never catches up to MCS, DNO and BUS V5.
Decision-stage migration guide for US clean-energy installers leaving HubSpot. What imports cleanly, what doesn't, what HubSpot stays good at, and how to sequence a 4-week cutover without losing project history or AHJ permit state.