Field Notes / Lifecycle stages

Your pipeline report and your sales team disagree. Here's how to find out why.

How to trace HubSpot pipeline mismatches to lifecycle stage errors, duplicate records, and stale deals, then fix them so the numbers agree.

TL;DR When the HubSpot pipeline report, the sales forecast, and finance all show different numbers, the gap almost always traces to three causes: lifecycle stage errors, duplicate records, and stale deal data. Reconcile in order. First lock the report definition, then match HubSpot record by record against the list your team trusts, then classify every difference by cause. Fix each one at the record, never with a report filter, and the numbers start agreeing on their own.

The pipeline review starts. The dashboard says one number. The VP of Sales has a spreadsheet that says another. Finance has a third, and nobody in the room can say which is right.

The usual response is to rebuild the dashboard. That rarely works, because the dashboard was never the problem.

I wrote earlier about why HubSpot reports stop matching reality. This post is the practical follow-up: how to trace a specific pipeline mismatch back to the records causing it. It is detective work more than reporting work, and it is more satisfying than it sounds. Every gap has a cause, and once you can name the causes, you can fix them so they stay fixed.

What is pipeline reconciliation?

Pipeline reconciliation is matching what HubSpot reports against an agreed reference, such as the sales forecast or finance's bookings, record by record, until every difference has a named cause. It is not rebuilding the dashboard. The goal is a short list of causes, each fixed at the source, so the report and the reference agree next month without anyone adjusting them by hand.

Reconciliation has a clear finish line, which is part of why it works. You are done when every deal in HubSpot either matches the reference or has a documented reason it does not. That is a much better outcome than "the dashboard looks more reasonable now," because it tells you what to fix and how to stop it coming back.

Where do you start when pipeline numbers don't match?

Start with the definition, not the data. Confirm which pipelines, deal stages, date property, and amount field each number uses. A large share of mismatches are two correct numbers answering different questions. Once definitions agree, export both lists and match them on deal or company, then sort every difference into one of three groups: only in HubSpot, only in the reference, or in both with different values.

Step one: lock the definition. Before touching a single record, write down exactly what each number measures. The usual differences:

  • Which pipelines. New business only, or renewals and expansion too?
  • Which stages. Does "pipeline" start at discovery, or at proposal?
  • Which date. Deals created this quarter, or deals expected to close this quarter? Create date and close date give very different totals.
  • Which amount. Amount, weighted amount, or annual contract value? One-time fees included or excluded?
  • Which owners. Does the report quietly exclude a team, a region, or deals owned by people who left?

Often this step alone closes most of the gap. When it does not, you now know the remainder is a data problem.

Step two: match the lists. Export open deals from HubSpot using the agreed definition, and get the reference list in the same shape. Match on deal name and company, or on the HubSpot record ID if the reference includes it.

Step three: sort the differences. Every mismatch falls into one of three groups, and each group points to a different cause:

Group Usually means
In HubSpot only Stale deals nobody closed out, or duplicate deals counting the same opportunity twice
In the reference only Opportunities that never became deals, deals in the wrong pipeline, or deals attached to a duplicate company outside the report's filters
In both, different values Stale amounts, stage, or close dates; the rep updated the spreadsheet and not the record

Now you can trace each group to its cause.

How do lifecycle stage errors distort pipeline reports?

Funnel and conversion reports count lifecycle stages, not deals. When contacts sit at Opportunity with no open deal, reach Customer with no won deal, or skip SQL on the way to a deal, the funnel shows pipeline that does not exist or hides the stage where deals actually stall. Find them with filters that compare lifecycle stage against the record's associated deals.

Lifecycle stage and deal stage measure different things, and pipeline mismatches often start when they are treated as one. (Anthony's post on lifecycle stage versus deal stage covers the distinction properly.) Lifecycle stage describes where the person or company is in the relationship. Deal stage describes where one opportunity is in the sales process. A funnel report built on lifecycle stages will disagree with a pipeline report built on deals whenever the two drift apart.

Four filters find most of the drift:

  • Opportunity with no open deal. Contacts or companies at Opportunity whose deals are all closed, or who have no associated deal at all. These inflate the middle of the funnel.
  • Customer with no won deal. Usually from an import or a manual edit. These inflate customer counts and break any conversion rate that ends at Customer.
  • Skipped stages. Records that reached Opportunity or Customer without ever entering SQL. Your SQL-to-Opportunity rate is now computed on a partial population.
  • Company and contact disagree. A company at Opportunity whose contacts are still Leads, or the reverse. Account-level and person-level funnel reports will tell different stories.

Two things usually sit behind these. One is lifecycle sync settings that set stages when a deal is created or won, combined with workflows trying to do the same thing on different rules. The other is people editing lifecycle stage by hand to make a record "look right." Both are worth reading about in the guide to spotting conflicting workflows. The lasting fix is a single transition contract per milestone, so stage changes happen in one place with the same writes every time.

How do duplicate records inflate or split pipeline?

Duplicates distort pipeline in two directions. Duplicate deals count one opportunity twice. Duplicate companies split one account's deals across two records, so account views undercount and territory or segment filters can drop a deal entirely. Duplicate contacts split engagement and attribution. HubSpot catches many duplicate contacts and companies automatically, but duplicate deals usually need a manual check.

HubSpot deduplicates contacts by email address and companies by domain as records are created, and the manage duplicates tool (Professional and above) surfaces likely matches that slipped through. Bulk merging requires Data Hub Professional or Enterprise. That covers a lot. It does not cover everything that affects pipeline.

Duplicate deals are the most direct pipeline distortion, and the one HubSpot's automatic checks are least likely to catch. They tend to come from a rep creating a deal while a workflow or integration creates another, a deal recreated after a stage change went wrong, or an import run twice. To find them, sort open deals by associated company, then look for the same company with similar amounts and create dates within a few days of each other.

Duplicate companies cause the subtler problem. When one account exists twice, say once with its primary domain and once with a regional or legacy domain, the deals split between them. If one of those records is missing the region, segment, or owner your pipeline report filters on, its deals drop out of the report entirely. This is a common reason a deal appears in the reference list and not in HubSpot's number.

Duplicate contacts rarely move the pipeline total, but they split engagement history and source data, which is why marketing's contribution to pipeline so often looks smaller than it is.

Before you merge Decide which record survives and why, then check associations after every merge. Merging two companies is the moment a deal can end up attached to the wrong account, owner, or pipeline. Merge a handful, confirm the result in the record and in the report, then do the rest.

How do you find stale deal data in HubSpot?

Look for open deals with a close date in the past, deals sitting in one stage well beyond your normal cycle, deals with no activity in weeks, deals with blank or placeholder amounts, and deals owned by people who have left. HubSpot's date entered current stage and time in current stage properties make stage aging easy to report on Professional and Enterprise.

Stale data is the most common cause of the "in both, different values" group, and the most common reason HubSpot's pipeline runs higher than the forecast. Reps usually know which deals are dead. The record just never got told.

  • Past-due close dates. Open deals whose close date has already passed. Each one is either lost and unmarked, or alive with a date nobody can forecast against.
  • Stage aging. Use time in current stage, grouped by stage, to find deals sitting two or three times longer than your typical cycle for that stage.
  • No recent activity. Open deals with no logged call, email, or meeting in 30 days or more. A deal with no activity is a deal nobody is working.
  • Placeholder amounts. Blank amounts, zero, or suspiciously round numbers entered at creation and never updated.
  • Departed owners. Open deals owned by someone who no longer works there. These are often the oldest and largest stale deals in the pipeline.

The fix has two parts. Clean the current list with the deal owners in a single working session, closing what is dead and updating what is alive. Then prevent it: require key properties such as amount and close date before a deal can move to later stages, and set up a weekly digest or task for any deal whose close date passes while it is still open.

How do you run a full reconciliation pass?

Lock the definition, match the lists, classify every difference by cause, then fix in order of dollar impact: stale deals and duplicate deals first, then duplicate companies, then lifecycle errors. Fix each one in the record, rerun the report, and confirm the gap closed. Have sales and finance sign off on the final number and the definition behind it.

Symptom Likely cause Where to look Fix at the source
HubSpot higher than forecast Stale or duplicate deals Past-due close dates, stage aging, same company and amount Close out or merge; stage requirements; past-due digest
HubSpot lower than forecast Missing deals or split companies Reference deals not in HubSpot; duplicate companies missing report fields Create the deals; merge companies; require owner and segment
Funnel disagrees with pipeline Lifecycle stage errors Opportunity with no open deal; Customer with no won deal; skipped SQL One writer per stage; settle sync settings vs. workflows
Totals match, deals don't Offsetting errors Record-level match, not totals Fix both sides; totals that agree by accident will not stay agreed

One rule matters more than any other here: fix the record, not the report. It is tempting to add a filter that excludes the deals you know are wrong. That makes this month's number look right and guarantees next month's will not, because the bad records are still there and new ones keep arriving. Every fix should change data or process, not the lens.

The last step is the one teams skip. Write down the agreed definition, the number it produced, and the causes you fixed, and have sales and finance both sign off. That page is what keeps the next pipeline review from starting the same argument.

How do you keep HubSpot pipeline and reality in sync?

Make reconciliation a monthly habit on a sample rather than a quarterly crisis. Run a weekly stale-deal digest, require key deal properties at stage changes, keep one writer for each lifecycle transition, and review duplicates on a schedule. Give the definition and the hygiene an owner by name.

  • Weekly: a stale-deal digest to each owner (past-due close dates, no activity, stage aging) and a quick look at the duplicate queue
  • Monthly: reconcile a sample of 20 to 30 deals against the forecast, and check the lifecycle filters above
  • Quarterly: revisit the pipeline definition with sales and finance, and review stage requirements and sync settings

The win shows up quickly. Pipeline reviews get shorter because nobody is arguing about the number. Forecasts get closer because the deals behind them are current. And when leadership asks what marketing contributed, the answer comes from records everyone already trusts. Dirty data is a trust problem, and reconciliation is how you earn the trust back.

Frequently asked questions

Why doesn't my HubSpot pipeline report match the sales forecast?

Usually because of definitions first and data second. The two numbers may use different pipelines, stages, date properties, or amount fields. Once definitions match, the remaining gap almost always traces to stale deals, duplicate deals or companies, or lifecycle stage errors. Matching the two lists record by record shows which cause applies.

How do I find duplicate deals in HubSpot?

HubSpot automatically deduplicates contacts by email and companies by domain, but duplicate deals usually need a manual check. Sort open deals by associated company and look for the same company with similar amounts and create dates within a few days. Check the property history on each to see which was created by a rep, a workflow, an import, or an integration.

How do I report on stale deals in HubSpot?

On Professional and Enterprise, use the date entered current stage and time in current stage deal properties. Build a deal report filtered to open deals where time in current stage exceeds your normal cycle, grouped by stage and owner. Add filters for close date before today and no recent activity to catch the rest.

Why are contacts at Opportunity with no open deal?

Lifecycle stage moves forward easily and does not move back on its own. A contact that reached Opportunity stays there after its deal closes lost, unless something deliberately recycles it. Lifecycle sync settings, imports, and manual edits can also set Opportunity without a deal. Filter for Opportunity contacts with no open associated deals, then decide on a recycle rule.

Should I fix pipeline mismatches with report filters?

No. Filtering out records you know are wrong makes one report look right while the bad data keeps affecting every other report, workflow, and forecast. Fix the record, then fix the process that produced it, such as stage requirements, duplicate prevention, or a single writer for lifecycle stage changes.

Is your pipeline report the one everyone argues about?

Focus+Scale reconciles HubSpot pipeline and reporting: we trace every gap to a cause, fix it at the record, and keep the numbers honest month to month.

Get in Touch →