HubSpot ships with pipelines for deals and tickets, but plenty of real business processes don't fit either one. A custom object pipeline lets you track any stage-based process — onboarding, renewals, applications, projects — on its own object, with its own stages, automation, and reporting, separate from your sales pipeline. Used well, it gives a messy process a clear home. Used carelessly, it adds clutter nobody maintains. Here's the practitioner's read on when to build one and how to do it right.
What is a custom object pipeline?
It's a set of stages you define on a custom object, so records of that object move through a process the same way deals move through a sales pipeline. In HubSpot, a pipeline is just an ordered set of stages a record progresses through. Deals have them by default; tickets have them too. A custom object pipeline brings that same stage-and-progress structure to an object you've created yourself — say, "Onboarding" or "Renewal" — so each record has a clear status, can trigger automation as it moves, and shows up in board and reporting views. It's the difference between a status field someone updates by hand and a real process you can manage and measure.
When should you use one instead of a deal pipeline?
Use a custom object pipeline when the process isn't a sales opportunity but still has distinct stages, owners, and outcomes you want to track separately. The trap is forcing everything into the deal pipeline. Onboarding a signed customer isn't a deal — the sale already closed — but it has stages (kickoff, setup, training, live) that deserve their own tracking. Cramming it into deal stages pollutes your sales reporting and confuses your forecast. Worked example: a team running customer onboarding inside deal stages couldn't tell real pipeline from post-sale work — splitting onboarding onto its own custom object cleaned up the forecast and gave the success team a board that was actually theirs.
How do you create a custom object pipeline?
Create the custom object first, then define its pipeline and stages, then layer on automation — in that order. The setup follows a clear sequence. First, in your CRM settings, create the custom object and its properties (custom objects require an Enterprise-tier subscription, so confirm your plan supports them). Second, define the pipeline: name the stages in the order a record should travel through them, and keep the list short — five to seven stages is usually plenty. Third, decide what each stage means and write it down, so everyone moves records on the same criteria. Fourth, add automation: set stage-entry triggers to assign owners, create tasks, or send internal notifications. Finally, build a board or report view so the team works the pipeline visually. Worked example: a renewals object with stages of Upcoming, In Discussion, Negotiating, Renewed, and Churned — each one triggering the right task — turns a renewal spreadsheet into a managed process.
What mistakes should you avoid?
Too many stages, vague stage definitions, and building the pipeline before anyone agrees on the process. A pipeline with twelve stages nobody can keep straight is worse than a status field. So is one where "In Progress" means three different things to three different people. The discipline is the same as any good process design: map how the work actually flows before you model it in HubSpot, keep the stages few and clearly defined, and make sure each stage has a clear entry rule and, ideally, an owner. This is exactly the order we follow with clients — agree on the process first, then build it, never the reverse.
The IV-Lead take
Custom object pipelines are one of HubSpot's most useful and most under-used features. They let you manage the parts of your business that aren't sales but still need structure — and they keep that work out of your deal pipeline, where it distorts your numbers. But a pipeline is only as good as the process behind it. Build it on a clear, agreed flow with few stages and real owners, and it becomes a tool the team actually runs the work from. Build it on guesswork and it becomes another tab nobody updates.
Not sure whether a process belongs in a custom object pipeline or a deal pipeline? Book a 30-minute portal audit — we'll map your processes to the right HubSpot structure so your reporting stays clean. For the bigger picture, see how we approach HubSpot implementation and optimization.
Frequently asked questions
Do I need a specific HubSpot plan to use custom objects?
Yes. Custom objects require an Enterprise-tier subscription. Without it, you can still build extra pipelines on deals and tickets, but you can't create a brand-new object with its own pipeline.
How is a custom object pipeline different from a deal pipeline?
Mechanically they work the same way — ordered stages a record moves through. The difference is what they track: deal pipelines are for sales opportunities, while custom object pipelines are for any other staged process you want to manage separately from sales.
How many stages should a pipeline have?
Usually five to seven. Enough to reflect the real process, few enough that everyone can keep them straight. Each stage should have a clear entry rule so records move consistently.
Can a custom object pipeline trigger automation?
Yes. You can set stage-entry triggers to assign owners, create tasks, send internal notifications, or update properties — the same automation you'd build on a deal pipeline, applied to your custom process.