# What happens to Original Source when HubSpot contacts merge?

> When HubSpot contacts merge, HubSpot keeps the oldest Original Traffic Source unless it was edited by hand. What that means for attribution reports.

- URL: https://dedupe.ly/blog/hubspot/hubspot-original-source-after-merge
- Section: blog
- Published: 2026-11-19
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

Skip to content
[New Dedupely Intelligence Now on every paid plan, monthly or yearly.](https://dedupe.ly/ai-deduplication)
[Blog](https://dedupe.ly/blog)
[HubSpot](https://dedupe.ly/blog/hubspot)

## What happens to Original Source when HubSpot contacts merge?

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated November 19, 2026
#
min read
TL;DR
- HubSpot keeps the oldest Original Traffic Source when contacts merge.
- If someone changed the value by hand, that rule doesn't apply.
- Page views and other analytics totals are added together.
- Duplicates split attribution before the merge, so reports change after a cleanup.
- Dedupely follows HubSpot's own merge for these values and logs every original in Merge History.
Original Traffic Source tells you how a contact first found you: organic search, paid social, a referral. When the same person exists twice, each record has its own source, and your attribution reports count the person twice. Merging fixes that, but only one source can survive.
Here's what HubSpot keeps, why, and what to check in your reports after a cleanup.

### What HubSpot keeps

| Property | After a merge |
| --- | --- |
| Original Traffic Source | The value from the oldest record, unless it was updated by hand |
| Create date | The oldest record's create date |
| Page views and visits | Added together from both records |
| Lifecycle stage | The stage furthest down the funnel |
| Number of form submissions | Added together |
| Most other properties | The primary record's value, or the other record's when the primary is blank |
The logic is simple: the oldest record shows how the person first arrived. A contact created from an ad in March and again from a webinar in July first came from the ad.

### When the rule doesn't apply

If someone edited Original Traffic Source by hand on one of the records, HubSpot doesn't apply the oldest-value rule to it. Teams sometimes do this to fix a misattributed lead, or after an import set every source to "Offline Sources". After a merge, check a sample of contacts where the source was edited.

### How duplicates distort attribution

Before the merge, duplicates make attribution look better than it is:
- **One person counts as two new contacts,** often from two channels.
- **The later channel gets credit** for someone the earlier channel already brought in.
- **Conversion rates drop,** because one of the two records never converts.
Example
Say a contact first came from organic search in January, then filled in a paid-social form in May with a work email, creating a second contact. Paid social reports a new contact for May. After the merge, the contact's Original Traffic Source is organic search, and May's paid-social count goes down by one.

### What to check after a cleanup

- **Compare source reports before and after** the cleanup for the same date range.
- **Expect new-contact counts to drop** for the channels that created the second records.
- **Explain the change to the team** that owns attribution, so it isn't read as a drop in performance.
- **Check hand-edited sources** on a sample of merged contacts.
Pro tip
Export the contact list with Original Traffic Source and create date before a large merge. If someone asks why a channel's numbers moved, you can show which records were combined.

### How Dedupely handles source data in HubSpot merges

Dedupely merges HubSpot contacts through HubSpot's own merge, so HubSpot's rules apply to Original Traffic Source and the analytics totals. Merge Rules decide the other fields, like owner, phone or lead status. Merge History keeps every original record's values, so you can see each record's source before the merge and export it as a CSV.
[Clean up HubSpot contacts without losing attribution](https://v2.app.dedupe.ly/signup)

### The first source survives

When HubSpot contacts merge, the oldest Original Traffic Source is kept unless it was edited by hand, and analytics totals are added together. Reports change after a cleanup because duplicates were double-counting people, so compare before and after and let the attribution owner know what to expect.

### Frequently asked questions

#### What happens to Original Source when you merge HubSpot contacts?

HubSpot keeps the value from the oldest record, unless the property was updated by hand.

#### Are page views lost when contacts merge?

No. HubSpot adds the page views and visits of both records together.

#### Why did my source report change after a cleanup?

Duplicates counted one person twice, often under two channels. After the merge, each person counts once, under their first source.

#### Can I choose which Original Source to keep?

HubSpot's merge keeps the oldest value. If it's wrong, edit Original Traffic Source on the merged contact.

#### Which create date does the merged contact keep?

The oldest record's create date.
Behind the article

### Gaby Salinas

Marketing Assistant at Dedupely
Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start.
As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes.
[Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns)

### Contact us

We’d be happy to help you get this set up.

#### Write us a message

We probably know the answer to your question already
help@dedupe.ly
Email copied to your clipboard!
[Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler)

### Discover Related Blog Posts

Stay updated with our latest articles and insights.
- [CRM Organization How to tell if duplicates are skewing your reports Duplicates inflate customer counts and pipeline and drag down conversion and win rates. Signs to look for, and a quick check before a report goes out. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-organization/duplicates-skewing-reports)
- [CRM Organization How duplicate records distort lead scoring Duplicates split one buyer's engagement across records, create false MQLs and delay routing. Merge the obvious ones before you tune lead scoring. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-organization/lead-scoring-duplicates)
- [CRM Organization What happens to workflows and record IDs when you merge A merge can change a record's ID, end its workflows and fire automations. See what HubSpot and Salesforce do, and what to check before a bulk merge. Gaby Salinas October 30, 2026](https://dedupe.ly/blog/crm-organization/merge-workflows-automations-record-ids)

### Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.
[Try for free](https://v2.app.dedupe.ly/signup) [Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)
[Or sign up with Google](https://v2.app.dedupe.ly/signup/google)
Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)
