CRM Pipeline Setup: How to Track Expansion vs New Business

Here is a situation that plays out at B2B companies the moment they start growing past a handful of customers. Your head of sales opens the pipeline report the morning of a forecast call. The numbers look decent: 40 open deals, healthy coverage ratio, conversion rate trending up. Then someone asks: "What is the breakdown between new logos and expansion revenue this quarter?"

Silence.

The deals are all in one pipeline. Renewals, upsells, new contracts, and reactivations are mixed together in the same stages the team built when they first set up the CRM two years ago. Nobody knows the true new-business win rate because it is buried inside a blended number that includes customer renewals, which close at a much higher rate and follow a completely different process.

This is not a small problem. The moment expansion revenue becomes meaningful (usually somewhere around 20 to 30 percent of total revenue), running it through your new-business pipeline starts producing numbers that are directionally wrong. Your conversion rate looks better than it is. Your average sales cycle looks shorter than it is. Your forecast for true new-logo pipeline is obscured by deals that would have closed anyway.

The fix is structural, not behavioral. You need a separate pipeline.

Why Mixing Expansion Into New Business Breaks Your Reports

Most CRMs default to one pipeline. Teams set it up early, build custom stages, and then use it for everything that comes in, because creating a second pipeline feels like added complexity. But the moment a customer asks about adding seats, or a contract renewal comes up for discussion, those opportunities behave nothing like new-business deals:

Conversion rate. Renewal and upsell deals close at meaningfully higher rates than cold new-business deals. When those two populations are combined, your overall win rate will always read higher than your true new-logo conversion rate. That matters when you are trying to evaluate rep performance, improve your sales process, or project new-logo growth for the next quarter.

Stage definitions. The stages you built for new business (e.g., "Discovery," "Demo Scheduled," "Proposal Sent") often do not reflect the renewal or expansion motion. A renewal conversation does not start with a discovery call. An upsell that begins with a customer asking for more seats during a support call is already at a different entry point than a net-new prospect.

Sales cycle length. A customer renewing a contract they have used for two years moves through a pipeline in days or weeks. A new logo might take three to six months. When both populations share a pipeline, your reported average cycle length is a weighted average of two very different numbers that tell you nothing useful about either.

Ownership and routing. New-business deals belong to sales reps. Renewals and upsells often belong to account managers or customer success. A shared pipeline makes it hard to assign deals correctly, enforce the right fields, or report by the team that owns the revenue motion.

The Three Revenue Motions That Need Separate Tracking

Before setting up a new pipeline, it helps to be clear about which motions you are actually running. Most B2B teams have three:

New business. A prospect who has never been a customer. Your full sales process applies: prospecting, discovery, demo, proposal, negotiation, close. This is the motion your original pipeline was built for.

Expansion. An existing customer buying more: more seats, a higher plan, an add-on product, or a new use case. The motion is shorter (you already have a relationship and know their environment), but it still needs deliberate tracking and a defined process. Left untracked, expansion conversations happen over email and Slack and disappear from your forecast entirely.

Renewal. An existing contract coming up for renewal. At some companies, renewals are nearly automatic and need only a lightweight tracking process. At others, contracts come up for renegotiation or competitive review, and the renewal looks more like a sale. Either way, it is separate data that should be reported separately.

Some teams further split expansion into upsell (same product, more of it) and cross-sell (a different product to the same customer). Whether you track those separately depends on whether they have different processes. If they do, give them different pipelines or at minimum different opportunity types within one expansion pipeline.

How to Set Up an Expansion Pipeline in HubSpot

HubSpot supports multiple deal pipelines across all paid plans. Setting up a second pipeline takes about ten minutes.

In your HubSpot account, go to Settings, then CRM, then Deals. You will see a "Pipelines" tab. Click "Add pipeline" and name it something clear, like "Expansion and Renewal Pipeline" or "Customer Revenue Pipeline." You can then create stages specific to the expansion motion.

A starting set of stages that works for most small B2B teams:

1. Expansion Identified - a customer signal has been logged (request, renewal date flagged, usage data reviewed)
2. Stakeholder Engaged - initial conversation has happened, the right contact is involved
3. Scope Defined - the specific expansion has been agreed in principle (seats, tier, product)
4. Commercial Review - pricing confirmed, contract being processed
5. Closed Won or Closed Lost

Once the pipeline exists, set your required fields for each stage the same way you would for new business. At minimum, require an estimated close date, a deal value, and an owner before a deal can advance past the first stage.

To separate reporting, use HubSpot's deal reports with a pipeline filter. You can save separate report views for new-business pipeline and expansion pipeline, and compare conversion rates, cycle lengths, and revenue forecasts for each motion independently.

One useful addition is a custom "Deal Type" property (a dropdown with values like New Business, Upsell, Cross-sell, Renewal). This gives you a second cut of the data if you ever want to report across pipelines by deal type, rather than by pipeline alone.

How to Set Up Expansion Tracking in Salesforce

Salesforce includes a standard "Opportunity Type" field out of the box with predefined values including "New Business," "Existing Business," and "Renewal." The field is already in your org. The problem is that most teams never populate it consistently, so it becomes useless over time.

To make Opportunity Type reliable, do two things:

First, add it to your page layouts and make it required. A required field at the Opportunity create screen ensures the classification happens at entry rather than as an afterthought.

Second, build separate list views and reports filtered by Opportunity Type. In Salesforce, go to Reports, create a new Opportunities report, and add Opportunity Type as a filter. Save it as "New Business Pipeline" and "Expansion Pipeline" separately. This gives your managers a one-click view of each motion without needing to build a second pipeline.

For teams running Salesforce Enterprise or above, creating separate record types for New Business and Expansion Opportunities allows you to have different required fields and page layouts for each motion. A new-business opportunity might require a Discovery Call Date and a Competitor Identified field. An expansion opportunity might require a Current Contract Value and an Expansion Trigger field. Record types let you enforce those differences cleanly.

How to Set Up Expansion Tracking in Pipedrive

Pipedrive supports multiple pipelines as a core feature. In your Pipedrive account, click on the pipeline name at the top of the deals view and select "Add new pipeline." Name it and build stages appropriate for the expansion motion.

Pipedrive also has a "Label" feature at the deal level that functions similarly to HubSpot's Deal Type property. You can create labels for Upsell, Cross-sell, and Renewal and apply them to deals in any pipeline, which lets you filter and report across pipelines by deal label when you need a combined view.

Like HubSpot, the key is separating pipeline-level reports. Pipedrive's built-in reports let you select which pipeline you are viewing. Save separate dashboard views for each revenue motion so your team sees the right numbers by default.

The Data Capture Problem That Kills Expansion Tracking

The structural setup is the easy part. The hard part is the same problem that exists for new-business pipeline data: the conversations that generate expansion revenue are not being logged.

Account managers and customer success managers have the same logging discipline problem as sales reps. When a customer sends an email asking about adding seats, or mentions during a quarterly business review that they want to explore a new use case, that signal lives in an inbox. It does not automatically become a deal in your expansion pipeline.

Most B2B teams discover this in retrospect. A customer expands their contract, and when someone goes to look at the CRM record, there is no pipeline entry for the expansion deal, no logged conversations that led to it, and no way to understand what drove the revenue. The expansion shows up in the win column with no process data behind it. That means you cannot replicate it.

The teams that track expansion revenue accurately have usually solved the same problem they solved for new-business: reducing the friction between a customer signal and a logged deal record. For pipeline visibility across all revenue types, the same approach that auto-captures rep email threads for new-business deals applies equally to account manager communications with existing customers.

If your expansion revenue is becoming meaningful, it is worth applying the same activity capture infrastructure you use for new-business to the customer communication layer as well. The same setup that reduces manual CRM data entry for sales reps applies equally to account manager inboxes. That means connecting account manager inboxes and calendars to your CRM in the same way you connected sales rep inboxes, and flagging expansion signals (seat requests, escalations, usage conversations) as pipeline entries in the expansion pipeline rather than leaving them to float in email.

What Fields to Capture Differently for Expansion Deals

Beyond the pipeline structure, expansion deals often need a different set of fields than new-business deals. Here are the most useful additions:

Current contract value. Knowing what the customer pays today is essential context for sizing an upsell conversation and calculating expansion percentage.

Expansion trigger. What prompted the expansion discussion? Usage hitting a limit, a customer request, a QBR, a renewal flag? This data tells you over time what the most reliable triggers are and where to direct account manager attention.

Current product or plan. If you sell multiple tiers or products, log what the customer currently has so the deal record reflects the before state, not just the after.

Renewal date. For renewals specifically, the contract end date is the deal's natural close date anchor. Require it in the pipeline so your forecast includes realistic timing.

Expansion ARR. Track the incremental annual recurring revenue from the expansion separately from the contract total value, so you can report net new ARR alongside new-logo ARR.

Reporting Expansion Revenue to Leadership

Once your expansion pipeline is set up and populated, you can report in the format that actually matters to a board or leadership team: new-logo ARR versus expansion ARR versus churn, giving a net revenue retention picture alongside the new-business pipeline.

The key metrics to surface for expansion pipeline are the same as for new-business, but the baselines are different. A healthy expansion conversion rate will be higher than new-business conversion, often significantly so. A healthy expansion sales cycle will be shorter. Calibrate your benchmarks to each motion, not to the blended pipeline that mixes both.

For the teams running a weekly pipeline inspection process, the expansion pipeline should be reviewed on the same cadence as new-business, with the same discipline around last-activity date, close date validity, and documented next steps. Expansion deals go stale for the same reasons new-business deals do: a conversation happened, nobody logged it, and the deal sits untouched while the customer's interest fades.

The Practical First Step

If your expansion revenue is still small, the fastest path to visibility is not a second pipeline, but a required "Deal Type" field added to your existing pipeline. Flag every deal as New Business, Upsell, Cross-sell, or Renewal at creation. This gives you a working segmentation without restructuring your pipeline, and it gives you the data to see when expansion volume has grown enough to justify a dedicated pipeline.

When expansion deals are consistently 20 to 30 percent of your open pipeline by count, it is time to split. That threshold is roughly when the stage definitions and required fields start diverging enough that a shared pipeline creates more friction than it saves.

The data quality work that supports a reliable expansion pipeline is not different from what it takes to maintain a reliable new-business pipeline: clear ownership, required fields, consistent logging, and activity capture that reduces how much the rep or account manager has to do manually. The teams that track expansion revenue accurately are the same teams that have already solved the logging problem for new-business deals. Both motions reward the same investment in activity capture and structured field hygiene.

Frequently Asked Questions

Should upsell and renewal deals go in the same CRM pipeline as new business?

No. Renewals typically close at much higher rates than new deals, so mixing them inflates your new-business conversion metrics and muddles the forecast. A separate pipeline with stages that match the actual expansion motion gives you clean reporting for each revenue type.

What stages should a renewal or expansion pipeline have?

A typical expansion pipeline runs four to six stages: Expansion Identified, Stakeholder Engaged, Proposal or Scope Defined, Commercial Review, and Closed Won or Lost. Stage labels should reflect your actual motion. If renewals are largely automatic, three stages may be enough; if each requires a formal review call, add a stage for that.

How do I report on expansion revenue separately in HubSpot?

Create a separate deal pipeline for expansions in HubSpot, then use the pipeline filter in your deals reports to isolate each revenue motion. You can also add a custom Deal Type property (New Business, Upsell, Renewal) and segment reports by that field for cross-pipeline analysis.

Why does upsell data go missing in the CRM?

Customer success and account managers often log expansion activity less consistently than sales reps log new-business conversations. Without a defined expansion pipeline and clear field requirements, upsell conversations stay in email and Slack and never surface in CRM records.

What is the difference between upsell and expansion revenue?

Upsell means selling a higher tier or more seats to an existing customer. Expansion is the broader category covering upsells, cross-sells of different products, and contract expansions. Both are tracked separately from new business because they use different sales motions and close at very different rates.