There's a famous quote that says "It's not the tools, it's the carpenter." We're all familiar with it (or some variant), especially if you play sports and buy new gear assuming you'll get better (I wish!).
Well, time and again I hear "It's never the tool. It's your process." in business.
I've said it myself. It's half right. And the half that's wrong is quietly costing some businesses a fortune.
Here's the thing. Companies bring me in when their CRM has stopped earning its keep. The last portal I assessed came back at 34 out of 100 for usage. Nothing was built wrong. The team had just stopped showing up. Deals moved back to spreadsheets, updates got chased over email, and the CRM had become a very expensive place where data went to be ignored.
When I dig into why this happens, it's usually one of two reasons. And telling them apart is the whole game.
Sometimes the CRM gets blamed for problems it didn't cause.
A new sales leader arrives and wants the system they used at their last company. The team never agreed what a qualified lead actually is, so no system on earth could report on it. Nobody was ever trained past day one. Or the process itself is broken, and the CRM is just the place where everyone can see it.
Move CRMs for these reasons and you'll spend six figures rebuilding the same mess in nicer software. I've watched it happen. The industry data backs this up: Analyst estimates put CRM project failure anywhere between 18% and 69%. And when Forrester dug into why, the top causes were all human: Cultural resistance to new ways of working (45%), poor user adoption (44%) and weak change management (42%). Technology barely features.
So no, I'm not going to tell you the grass is automatically greener with HubSpot. Anyone who does without understanding the underlying issue is selling something.
But sometimes the software itself is the problem. And I find the reasoning as to why to be the same each time:
Only one person understands how it works, and they're a contractor. Every small change needs a ticket, a specialist, and a line in next quarter's budget. Your sales team keeps a shadow spreadsheet because the real system is too slow to live in. Sales sits in one platform, marketing in another, with either no integration or one held together by duct tape that no-one trusts - so the two politely (haha) disagree about which version of the customer is true. Reporting exists, but nobody in the leadership meeting actually trusts the numbers enough to make a decision on them.
That last one is my favourite. If your board meeting starts with "these figures are roughly right", you don't have a reporting problem. You have a system problem wearing a reporting costume.
At that point you're no longer paying for a CRM. You're paying for the infrastructure required to keep the CRM alive. Those are very different bills.
Here's what I've learned from doing these migrations rather than writing about them: The move itself is often what fixes the team. Not just the destination. The journey.
A migration is a forced spring clean. Every workflow, field and automation has to justify its existence or die. The zombie processes that nobody dared touch for five years? Gone. The seventeen lead statuses that meant something to someone in 2019? Gone.
A migration also does something no SOP ever will: It resets behaviour. You cannot ask a team to suddenly use the old system properly. They have too much history with it. But a new system arrives with clean data, fresh training, leadership attention and a bit of goodwill (dare I say excitement). That window is real, and teams that use it well come out the other side with habits the old platform could never have given them.
Sometimes a change of tech is what allows the team to change. That's not a software argument. It's a human one.
We recently moved a data intelligence company off a heavily customised Salesforce and Pardot setup onto HubSpot. The old stack wasn't terrible. It was just built for a company they no longer were, and every change had become an engineering project.
Three months later they were live. Sales and marketing on one platform, one version of the truth, workflows their own team could actually maintain. Their sales ops lead told us there were no post-implementation blues. Everything just felt smooth.
That's the bar, by the way. Not "the new system has better features". The team actually using it without being chased or monitored.
Ask yourself five questions:
If you answered badly on one of them, fix your process first. If you answered badly on most of them, the tool has stopped serving you. And loyalty to a system that your team abandoned years ago isn't prudence. It's just an expensive habit.
Moving CRMs isn't admitting failure. Staying on one nobody uses is.