A HubSpot deal moves through stages in a pipeline you define, each stage carrying a probability used for forecasting. Merging duplicate deals, importing a batch from a spreadsheet, and running more than one pipeline for different sales motions are all native. What HubSpot's pipeline can't do on its own is confirm that the real-world condition behind a stage move, a credit check, a stock count, an approved PO, is actually true.
Every deal lives in exactly one pipeline at a time, moving left to right through stages your team defines, like Qualified, Demo Scheduled, Proposal Sent, Closed Won. Each stage has a default probability percentage, used to weight your forecast, and paid tiers let you require specific fields be filled before a deal can advance to a given stage, a basic gate against someone fat-fingering a deal to Closed Won with half the fields empty.
Running more than one pipeline, say a separate one for renewals versus new business, is a Sales Hub feature, not something the free CRM offers; check your current tier if you're trying to split pipelines and the option isn't there.
Merging and importing deals work the same way they do for contacts. A deal's Actions > Merge combines two records, favoring the one you pick as primary. The Import tool takes a CSV of deals and can associate each row with an existing contact or company automatically if the matching data lines up.
The required-field gate HubSpot offers natively can stop a deal from advancing without a number filled in, but it has no way to check a fact that lives outside HubSpot entirely: whether the customer's credit is actually clear in your accounting system, whether the product quoted is in stock in your warehouse, or whether a signed PO has actually landed in your inbox. A rep can move a deal to Closed Won on schedule even when one of those is false, because HubSpot genuinely has no way to know.
What happens the moment a deal does close, invoicing, provisioning, onboarding, is its own topic with its own real automation patterns; that's covered on the main HubSpot page → and, for anything trigger-based inside HubSpot itself, on the HubSpot workflows page →.
A deal can't actually advance to Closed Won until an external check comes back clean, a credit hold clears in accounting or stock confirms in the warehouse, instead of relying on a rep remembering to check first.
Pricing, terms, or product details pulled from outside HubSpot at quote time, so what's on the deal record is what the customer actually agreed to, not what a rep typed from memory.
A deal stage is a promise. We can tell you how often it gets broken before you have to find out from a customer.
Tell us what a rep is trusting by eye when they move a deal, stock, credit, an approval that lives somewhere else entirely. We'll look at whether that check can run itself. Deals and pipelines are one example; n-frames automates whatever's manual, in HubSpot or in any other system you run.
Let's talk →The steps a deal moves through on its way to closing, like Appointment Scheduled, Decision Maker Bought In, or Contract Sent, each one specific to the pipeline it belongs to. You define the stages and their order when you set up or edit a pipeline; HubSpot's default pipeline comes with a standard set you can rename or replace.
Open one of the two deal records, choose Merge from the Actions menu, and pick which record should survive. HubSpot combines the associations and activity history onto the surviving record. There's no bulk merge for more than two deals at once; duplicates beyond a pair take repeated manual merges.
Go to Import under Data Management, upload a CSV or Excel file, and map each column to a deal property. You can associate rows with existing contacts or companies in the same import if the matching data (like an email address or company name) lines up correctly.
Yes, the CRM Deals API covers creating, updating, and associating deals programmatically, which is the foundation for most of the deal-side automation built on HubSpot, including the stage-gating patterns described above.
No. A deal lives in a single pipeline at a time. If a deal's sales motion genuinely changes, say from a new-business process to a renewal process, moving it means changing which pipeline it's assigned to, not duplicating it across both.