Enterprise and ERP. HubSpot
Replacing HubSpot when the free CRM turns into a marketing bill
HubSpot gives the CRM away and sells the hubs around it. Contacts, companies, deals and tasks cost nothing, which is why so many companies start there, and then Marketing Hub, Sales Hub and Service Hub show up one tier at a time. We have integrated HubSpot with the work systems our clients run. The free CRM is good. It does the job it was built for.
What changes as you grow is where the meter sits. Marketing tiers are priced by how many contacts you market to, so the bill climbs with your database while your headcount stays where it is. The features you reach for next sit one edition up, and that edition applies to every paid seat. Custom objects, real automation, the reporting your owner keeps asking for.
Where it fits
Where does HubSpot fit?
We sell no HubSpot licenses and take no referral fees, so this is not a hit piece. These are the cases where keeping it is the honest advice, and if yours is one of them, we will say so on the call.
A marketing team that lives in email, landing pages and forms, and wants the campaign and the contact record in one place. That's what HubSpot was built for.
A company on the free CRM with a straightforward pipeline, where deals, contacts and companies cover the model and nobody has asked for a custom object yet.
A sales team that needs sequences, meeting links and email tracking working on day one, with nobody around to configure them.
Any business whose growth plan is inbound content, and whose list is still small enough that the contact tier isn't the biggest number on the invoice.
Where it breaks
Where does HubSpot break down?
The failure modes below are the ones that show up again and again as a company grows.
The CRM is free and the marketing tier is where the cost lands. Marketing Hub is priced by marketing contacts, so a list that's working is an invoice that's climbing. Teams end up policing which contacts count, just to hold the number down. That's a database shaped by a pricing model.
The higher tiers carry a required one-time onboarding fee on top of the subscription, charged per hub. What it costs to start isn't what the plan page says.
Custom objects are an Enterprise feature. Until you're there, anything you track that isn't a contact, company, deal or ticket gets forced into one of those, or kept in a spreadsheet beside HubSpot.
Automation is gated the same way. Workflows arrive at Professional, and the caps on workflows, custom reports and dashboards move with the tier. So the answer to a new requirement is the next edition, for everyone.
Quoting stops at line items drawn from a product library. Pricing with rules doesn't fit, whether that's options, tiers, margins or dependencies between lines. So quotes get built in a spreadsheet and somebody types the total back into the deal.
Contracts are annual and priced per hub. A tier you outgrow, or a hub nobody opens anymore, is still paid for until the term ends.
The replacement
What does replacing HubSpot look like?
A custom system keeps the parts of HubSpot your team touches every day and drops the meter. The objects are the ones your business names. Quoting carries your pricing rules instead of a product list. Mail goes out under your own domain with no contact tier attached to it, and reporting reads all of the data at once, so the questions leadership asks stop needing an export.
Migration is straightforward. HubSpot exports contacts, companies, deals, tickets, notes and activity, and the API covers whatever the export misses. Every field is mapped in a document you approve before anything loads. Then both systems run side by side, importing on a schedule, until your team has checked the numbers and stopped opening the old one.
Most companies want the same split, and it's the honest one. HubSpot is strongest at marketing and weakest as the system of record for a business that's more than its funnel. If marketing is earning its keep, keep it and sync to it, while quoting, delivery and the operational record move into something built for you.
You own the result. Code in a repository in your name, database and hosting on accounts in your name, unlimited users, no contact tier, and no edition gate in front of the next feature. We're added as administrators to build and support it, and you can remove us at any time.
The stakes
What does it cost to get this wrong?
More than the software. A replacement that goes badly costs you the one thing the old system was still doing, a single place your team agrees on. The failures below each turn a rebuild into a year of parallel systems, so they are the ones we plan around.
Lists in HubSpot recalculate their membership. They aren't stored groups. Export one and all you have is a snapshot, so a migration that treats active lists as data ships segments that were true on the day of the export and wrong the day after.
Workflows, sequences, forms and email templates are configuration, and no export carries them out. Cancel the hub before those are written down and the rules that routed your leads and chased your deals survive only in whatever screenshots somebody thought to take.
Custom objects sit at the top edition, so the things your business tracks are often already living in a spreadsheet beside HubSpot. Replace the CRM and leave that sheet where it is, and you've moved the easy half. The half where the errors happen stays.
The order of work
What happens, in what order, when you leave HubSpot?
Each step exists because skipping it is how the previous attempt failed. The sequence is fixed. The runway is not, and it goes in your written scope once we know the shape of your data rather than on this page as a calendar promise.
- 01
Hub by hub audit
We separate what each hub does for you from what you pay for it. Which workflows fire, which sequences get used, how many contacts are flagged as marketing contacts and why, which reports leadership actually reads. This is usually where a team finds it's been policing contact counts to hold a tier down, which means the invoice has been shaping the database.
- 02
Export and association check
Contacts, companies, deals and tickets export to CSV, and the API carries the rest, including engagements and the association types that link a contact to a company to a deal. Associations are what breaks a naive import, so we pull them explicitly. Attachments and notes need their own calls. Lists get rebuilt from their definitions, because importing them as rows would just freeze them.
- 03
Rules written down
Every workflow, sequence and form gets read for the rule it enforces, then confirmed with the person who depends on it. Some rules only move a value between HubSpot properties, or work around what a lower tier won't do. Those go away with the tier. What survives gets rebuilt as ordinary code, with no edition gate in front of it.
- 04
Build with marketing untouched
For most companies the honest split is to keep Marketing Hub and rebuild everything else. The new system becomes the record for deals, quoting, delivery and service, and syncs contacts and lifecycle stages back through the API. Marketing keeps working the way it does today while the operational half moves across.
- 05
Cutover at the renewal
Both systems run while your team checks deal counts by stage, contact totals and the reports leadership reads. When the numbers agree, the operational hubs come off at the renewal date. Contracts are annual, so canceling mid-term buys you nothing. Whatever stays is then a decision you make with evidence behind it, at a point where you can see what each hub is worth.
Limits
What we will not do
Saying this out loud is cheaper for both of us than finding out in month two. If one of these is what you actually want, we are the wrong firm and we will say so on the first call.
- We won't tell you to drop Marketing Hub if it's working. HubSpot is genuinely strong at inbound marketing. If your growth comes from content, keep the part that earns its keep and replace the part that doesn't.
- We won't write your marketing strategy, your campaigns or your content. We're software people, and pretending otherwise would be the most expensive kind of overreach. We build the system. The message inside it stays yours.
- We won't shape your data around a pricing model. If contacts were being suppressed or deleted to hold a tier down, the new system carries the whole database, and the rules about who gets contacted go back to being yours.
Questions
What people ask about leaving HubSpot
The CRM is free. Why would we pay for something else?
Because the free CRM is the entry point and the hubs are the product. The moment you need marketing automation, custom objects, real reporting or quoting with rules, you're in a paid tier priced by seat and by contact. So the honest comparison is a build against what your HubSpot invoice looks like three years from now.
Can we keep Marketing Hub and replace the rest?
Yes, and it's the most common way to start. The custom system becomes the record for deals, quoting, delivery and service, and syncs contacts and lifecycle stages to HubSpot through the API, so marketing keeps working the way it does today. Whether the hub stays after that is a decision you make later, once you can see what it's doing for you.
What happens to our workflows and sequences?
We list every workflow, sequence and form, work out with you which rules still matter, and rebuild those as ordinary code with no tier limit. Plenty of them won't survive that conversation. The ones that only move data between HubSpot properties, or patch what a lower tier won't do, go away with the tier.
Will our email still work if we leave HubSpot?
Yes. Sending mail is a solved problem outside HubSpot. Transactional and operational email goes out under your own domain through a mail provider on your account, with delivery recorded against the contact. Campaign and nurture email can be built to your rules too, and if HubSpot marketing is the part you value most, that's a good reason to keep that hub.
What does replacing HubSpot cost?
It depends on how many hubs are in real use, how much has to be rebuilt, and what the new system connects to, so we don't publish figures. After a strategy call you get a written scope naming what will be built and what it costs, set against your HubSpot invoice including the contact tier and the onboarding fees.
What happens to our reports and dashboards?
They get rebuilt as screens over your live data. HubSpot reports are configuration, so nothing comes out in an export, and copying them one for one would be the wrong goal anyway. We list the questions each report is meant to answer and who reads it, then build for those questions across everything at once, including the ones that need an export today because they cross objects or look back over a period. Historical data moves first, so the new reports have the same history behind them.
What if HubSpot changes how the contact tier works?
Then the math changes, and we'd tell you so. HubSpot adjusts its packaging regularly, and some of those changes have gone in customers' favor. But the reason companies leave is structural. The meter sits on the size of your database, custom objects and real automation sit at the top edition, and quoting stops where your pricing rules start. If a repackaging fixed all three for your situation, staying would be the right call, and scoping is where we find that out.
How do you handle permissions, teams and who can see what?
Permissions get designed by role against your org chart, and they're enforced on the server. Hiding a field in the interface was never enough on its own. Sales sees pipeline, service sees tickets, finance sees margin. A regional lead sees their own region, and you don't buy a higher edition to get partitioning. External users, whether customers, partners or contractors, get a portal scoped to their own records and cost nothing to add. Every change to a record is logged with the person and the time behind it, so your audit trail doesn't depend on a tier.
From the knowledge base
Guides for people weighing up HubSpot
Reference pages, not sales pages. Each one is useful even if you decide to stay exactly where you are.
How to tell whether your business actually needs custom software
Seven tests you can run against your own operation this week. Most businesses that run them find a configuration problem, not a build.
Salesforce and NetSuite implementation cost and timeline, by company size
A sourced comparison table at 50, 100, 250, 500, and 1,000 employees. Every figure is cited and dated, and the thin-data cells say so.
Related
Coming from a different tool?
The same honest treatment for the other platforms we used to implement, and the pages that explain the custom model itself.
Tell us where HubSpot stopped fitting
Book a strategy call, or send a short note about the workarounds your team runs today. If keeping HubSpot is the right answer, you will hear that first.