This gap analysis belongs to the guide to cross-tool identity resolution, which links one customer across an ERP, a CRM, a retired billing tool and a help desk. Here the focus is on what a review expects to see behind links like those, what customer archives usually hold, and how to describe the difference.
What a link review looks for
A reviewer asks two things of every link: what evidence joined these records, and did anything later prove the join right? Methods vary. Salesforce describes exact matching alongside fuzzy methods such as edit distance and Jaro-Winkler; the Fellegi-Sunter model explained in Splink's documentation weighs agreement on each field. Each method leaves different evidence, and the review needs to see it.
| # | Expected evidence | What it lets a reviewer say |
|---|---|---|
| 1 | Native ID in each system | Which records are being joined |
| 2 | Cross-reference field (one system storing another's ID) | Someone deliberately linked them |
| 3 | Migration map for each retired system | Older history can be attributed |
| 4 | Merge log with retired and surviving IDs and dates | Which activity belonged to which record before a merge |
| 5 | Shared strong key such as a tax ID or contract number | The link rests on an exact match |
| 6 | Matching rule or data dictionary, with the years it applied | How scored links were made, and whether the rule changed |
| 7 | Rights basis for each source system | Joined records may be used together |
| 8 | Downstream confirmation such as an applied payment or a contract number on both sides | The link held in practice |
Typically held, usually missing
| Evidence | What companies usually keep | What usually goes missing | How it goes missing |
|---|---|---|---|
| Native IDs | Always | Rarely | Only when a system is deleted |
| Cross-reference field | For key accounts | Smaller accounts and older years | Typed in by sales ops when someone remembered |
| Migration map | The latest migration | Earlier maps | Deleted after go-live |
| Merge log | Surviving record only | The retired ID and merge date | Tools that keep only the winner |
| Shared strong key | Tax ID on ERP accounts | The same key in the CRM or help desk | Never collected outside finance |
| Matching rule | A steward's habit | Any written rule | Lives in one person's head |
| Rights basis | Contracts on file | Which terms applied to which system's records | Nobody mapped contracts to systems |
| Downstream confirmation | Applied payments | Disputes that broke a link | Disputes handled outside the system |
Rules nobody wrote down are worth a word. A data steward who merged on "same domain plus similar name" for years leaves a consistent archive, but no one can audit the rule, and the method shapes which links exist at all. Salesforce, for example, notes that its fuzzy methods support only Latin characters and recommends exact matching for international data, so a company with customers in several scripts may have quietly linked fewer of them. Ask whether a matching rule or data dictionary exists, and for which years.
An equipment rental company, link by link (Illustrative)
A fictional 400-person equipment rental company runs one ERP and one CRM and absorbed three regional branches with their own billing tools. Its finance systems lead was asked, for every 10 customer links across systems, roughly how many carry each item. These are estimates from a call, not system counts.
| Evidence | Expected per 10 links | Available per 10 | Missing per 10 | Cause given |
|---|---|---|---|---|
| Native IDs | 10 | 10 | 0 | None |
| Cross-reference field | 10 | 7 | 3 | Branch customers never got the field filled |
| Migration map | 10 | 6 | 4 | One branch's map was deleted after integration |
| Merge log | 10 | 3 | 7 | The CRM kept only surviving records until 2022 |
| Shared strong key | 10 | 8 | 2 | Cash customers have no tax ID on file |
| Matching rule | 10 | 2 | 8 | Merges followed a coordinator's judgment |
| Rights basis | 10 | 4 | 6 | Branch customer terms never compared |
| Downstream confirmation | 10 | 9 | 1 | Payments applied to the linked account |
The archive is better than the merge log row suggests. Most links rest on a shared key and are confirmed by payments, so they can probably be trusted. The weak spots are concentrated: one branch's history before integration, merges before 2022, and the question of whether branch customer terms allow joining their records to the main CRM. That last point needs the rights review, not the introducer. The guide to identity mapping after an acquisition covers the same break when a whole company is absorbed.
Writing the gap into an introduction
One sentence per gap, with scope and cause, is enough. Some templates:
- Merge log: "The CRM logged retired IDs on merges only from 2022; earlier merges kept the surviving record alone."
- Migration map: "Mapping files survive for two of the three acquired branches; the third was deleted after integration in 2020."
- Matching rule: "Merges were made by one coordinator using domain and name; the rule was never written down."
- Rights basis: "Branch customers signed different terms that have not been compared with the main contract."
Those sentences give SourceX a starting scope. They also protect the introducer, because nothing in them overstates what the company holds.
Gaps that stop an introduction
Record gaps narrow the usable share of links. These conditions stop the introduction until they change.
| Condition | Effect | Introducer's move |
|---|---|---|
| Under 50 full-time employees at peak (contractors excluded) | Fails eligibility | Do not introduce |
| A parent group or franchisor controls the customer systems | The company cannot license them | Find who can authorize |
| No documented operating history | Fails eligibility | Do not introduce |
| No authorized contact | Nobody can open a discussion | Identify the CEO or owner-CEO |
Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
What stays unknown until SourceX reviews it: how many links survive checking, whether joined records can be used together under their original terms, buyer interest and any offer. Help desk history that may not survive a tool change is covered in whether to migrate closed tickets to a new help desk; separation between customers' data in shared systems in MCP multi-tenant security; and de-identification of support records in anonymizing support tickets. To screen first, use the identity resolution qualification scorecard; for what the company prepares later, see the review packet contents list. Other record families are under data types.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the company passes the gates and you can describe its link gaps in a few honest sentences, register as a partner, check who qualifies and read the terms before you introduce the owner.