Home
Blog
B2B Entity Resolution: One Record for Every Person and Company
RevOps & CRM
November 17, 2026
|
8 min read

B2B Entity Resolution: One Record for Every Person and Company

CRM records go stale from the day they're saved. B2B entity resolution keeps one record per person and company, with its history intact.

B2B Entity Resolution: One Record for Every Person and Company
Table of Contents
Try it free

TL;DR

When a person or company changes and the CRM creates a second record, the relationship history splits or disappears. That split keeps happening because CRM records go out of date without warning. B2B entity resolution keeps one record per person and company through every change, so the history stays intact.

When bread goes stale, you have options. You can trash it, toast it, or make some ducks very happy. Stale CRM contacts are less palatable. They don't go hard and dry to warn you. They sit in your database looking fresh, right up until someone emails a prospect who left six months ago. Every record was right on the day someone typed it in. After that, people change jobs, companies rebrand and numbers get reassigned, while the record stays put.

B2B entity resolution is the process of recognizing that a new record describes a person or company you already have, then keeping them as one. Surfe does it by giving every person and every company a unique identifier that stays the same through each change. Identity resolution is the part that handles people, and entity resolution covers people and companies together. When it works, your team starts each conversation with the full history in view. This article covers how CRM data decay happens, what it costs and how Surfe keeps records whole.

Your CRM record ages from the day it's saved

The industry calls this CRM data decay. B2B data decays roughly 2.1% a month, or about 22.5% a year, with no active hygiene.¹ Treat those figures as a guide rather than a forecast for your own database.

Most records only get updated when someone trips over an error, which is a bit like waiting for a flat tire before checking the pressure. Your team isn't the problem. People and companies change for ordinary reasons, and nobody can track every move by hand.

Change comes in more forms than the obvious one

A promotion is the easiest change to miss, because the person never leaves the building. Their email signature changes, your record keeps the old title, and a static database has no way to know the difference.

Other changes are bigger. A company can merge with another, get acquired, rebrand or move to a new domain. A person can change their name after marriage or for any other reason. Someone can relocate to another country, which brings a new phone number format, a new region and sometimes a new legal entity to work for. Each of these is ordinary. Together, they mean a record can be right in one field and wrong in several others, with nothing in the record to flag it.

When a record splits, the history goes with it

A contact who moves to a new company can come back as a brand-new record. Instead of updating the old one, the CRM creates a second record with no link between them. Now two records exist for one person, and each holds part of the story.

Past deals sit on one record, recent emails on the other, and the notes explaining why the last champion said yes sit on neither. Anyone who opens either record gets a partial view.

The costs add up fast. Reps spend time working out which record is current. Outreach goes to someone who left months ago. Context has to be rebuilt from memory or old email threads, and plenty of it is lost for good.

B2B entity resolution gives each person and company one ID

Surfe resolves records by giving every person and every company a unique identifier, then matching each new record to it. When a record arrives, Surfe checks it against its own database using a set order of signals: for a company, that starts with the website domain, then the company name; for a person, it starts with their LinkedIn profile, then their name and employer. Behind both sits a much longer list of identifiers working together for the harder cases, where a domain, a name, or a profile alone isn't enough to settle it. A match means the record joins the person or company you already have, rather than starting a new one.

To a CRM, a company entered once with 'Ltd' and once without is two different companies. To anyone who's sold to them, it's one. Because both records carry the same website domain, Surfe resolves them to the same company. The same logic handles acquisitions and rebrands: records that still use an old company name or domain resolve forward to the current company.

People work the same way. A contact who moves to a new company keeps the same identifier, so their record follows them instead of a second one turning up with their name on it. The matching is rule-based: thousands of set rules decide whether two records describe the same person or company.

Your team keeps one record and the full history

Good CRM record history depends on one record per person and per company. With B2B entity resolution, the same person is recognized as the same person through every change, with one record updated in place, the full history kept and no second copy created. A company that merges, is acquired or renames itself resolves to the same company record, with its history intact.

Job Change Alerts adds the sales signal on top. It flags when a contact moves, so your team knows when to reach out. For the sales side of that story, read our piece on job change tracking.

Consider a simple example: a contact moves from one company to another. The old company's record shows the move and the departure. The new company's record gains the contact, with everything from the earlier relationship still attached.

Without it, the problem reaches forecasting and outreach. RevOps teams build forecasts, routing rules and territory decisions on data that was only briefly true. Sales and marketing then spend real time and budget chasing leads built on the same fragmented records: contacts who have left, duplicates and people who were never the right target. Some of those leads were never going to convert, because the record pointed at the wrong person from the start. Those losses trace back to records that went unchecked for too long.

Perhaps not exactly the best thing since sliced bread, but one record per person means your next conversation starts from the history your team already has.

Key takeaways

  • A CRM record is accurate on the day it's saved, and CRM data decay starts from there.
  • Decay comes from ordinary changes, including promotions, mergers, renames and relocations.
  • Duplicate CRM records split the relationship history across partial versions.
  • B2B entity resolution keeps one record per person and company through every change, using a unique identifier for each.
  • Job Change Alerts flags when a contact moves, so your team knows when to reach out.

¹ HubSpot, Database Decay Simulation, citing MarketingSherpa.

Pipeline starts here.

Join 50,000+ revenue professionals running on verified data.
Free to start. No credit card. Live in 60 seconds.

GDPR Compliant
ISO 27001 Certified

Frequently Asked Questions

Your most pressing questions, answered with clarity.

What is B2B entity resolution?
What is CRM data decay?
Why do duplicate CRM records appear?
What happens to CRM record history when a contact changes jobs?
Does a company merger or rename create duplicate records?
How does entity resolution help RevOps?

Pipeline starts here.

Join 50,000+ revenue professionals running on verified data. Free to start. No credit card. Live in 60 seconds.

GDPR Compliant
ISO 27001 Certified
SOC 2 Compliant
Abstract glossy blue 3D wave-shaped graphic on a transparent background.