Cross-tool identity resolution: one customer, four legacy IDs, and the evidence that links them

Short answer

Cross-tool identity resolution is the work of deciding that records in different systems describe the same customer, supplier or product, and recording why. In an ordinary business workflow, one customer might be account 40417 in the ERP, a separate record in the CRM, another number in a retired billing tool and only an email domain in the help desk. Resolving it means linking those records on evidence, and holding back any link that rests on a guess.

Visual briefFull-size diagram
A resolved customer at the center linked to four system records: the ERP and CRM records joined by an exact tax ID match, the legacy billing record joined by address and phone, and the help desk organization joined only by email domain, shown as a dashed orange link held for review.
Illustrative: one customer across four systems. Three links rest on evidence; the fourth is a guess until someone confirms it.

What does cross-tool identity resolution mean in an ordinary business workflow?

It means someone, or some rule, decided that four records are one customer, and that decision is stored with its basis. Without it, a customer's order history, invoices and complaints sit in separate piles that cannot be read as one story.

AI agents that work across a company's tools run into this constantly: an agent asked to summarize a customer's open issues has to know which help desk organization, which CRM account and which ERP customer belong together. Companies that license workflow data to AI developers, a market Mercor also describes on its data page (checked October 18, 2026), are offering records where those joins either exist or do not.

Illustrative: a 310-person commercial HVAC distributor has served a regional hospital group for twelve years. Over that time the customer has been recorded four ways. Every identifier below is fictional.

SystemIdentifierCreatedStrongest field that could link it
ERP (orders, invoices)Customer 404172014Tax ID on the account
CRM (contracts, renewals)Account record with "ERP no. 40417" field2019Tax ID, plus the ERP number typed in by sales ops
Legacy billing (retired 2021)Account BL-99212016Billing address and main phone
Help desk (service requests)Organization keyed on the email domain2020Email domain only

The ERP and CRM records share a tax ID and an explicit cross-reference, so the link is close to certain. The legacy billing account agrees on address and phone, which is strong but not conclusive: the hospital group moved its accounts payable office in 2018, so older invoices carry a different address. The help desk record links only by email domain, and the hospital group's domain is shared by three affiliated clinics that buy separately.

That last row is where identity resolution earns its name. A reviewer who merges it blindly attributes the clinics' service complaints to the hospital group's contract.

Two methods appear in most companies' records, often side by side. Exact matching joins records only when a key is identical. Salesforce's documentation, for example, describes its exact method as case-insensitive and treats non-identical strings as non-matches. Scored matching weighs several partial agreements. The Fellegi-Sunter model, explained in the documentation for the open-source Splink library maintained by the UK Ministry of Justice's analytical services, scores a pair of records by how likely each observed agreement is among true matches compared with non-matches, and adds those per-field weights into one score.

Applied to the illustrative customer:

LinkEvidenceMethodDecision
ERP to CRMSame tax ID; CRM holds the ERP numberExact keyLinked
ERP to legacy billingAddress and phone agree; name differs by abbreviationScoredLinked, with the 2018 address change noted
ERP to help deskEmail domain onlyScored, weakHeld for review
Help desk to clinicsSame domain, different purchase ordersScored, weakHeld for review

The decision column matters as much as the links. A company that recorded "held for review" and later resolved it has better records than one that silently merged everything. Salesforce also notes that its fuzzy methods support only Latin characters and recommends exact matching for international data, a reminder that the method a company used shapes which links exist at all.

A link is only reusable if the reason for it travels with it. In the example, these fields carry that reason.

FieldWhere it sits in the exampleWhy the example depends on it
Native ID in each systemERP 40417, BL-9921, CRM account, help desk organizationThe four things being joined
Cross-reference field"ERP no. 40417" on the CRM accountAn explicit, human-entered link
Shared strong keyTax ID on ERP and CRMMakes the exact match possible
Matching fields and their valuesAddress, phone and name on billing and ERPThe evidence behind the scored link
Address history with dates2018 accounts payable moveExplains why older records disagree
Link decision and statusLinked or held for reviewSeparates proven links from candidates
Who decided, and whenMerge log or crosswalk change historyLets a reviewer trust or revisit each link
Retirement record for the old systemLegacy billing closed in 2021Shows BL-9921 will never gain new activity

A spreadsheet crosswalk with only two columns, old ID and new ID, carries the first field and loses the rest. It records that a link was made but not why, which leaves no way to tell the tax ID match from the email domain guess.

What the example shows, and what it cannot

  • Four systems is a small case. Companies that have been through acquisitions can hold the same customer under many more identifiers, and our guide to acquisition identity mapping covers that wider problem.
  • A held link is not a wrong link. The help desk organization may well belong to the hospital group. The record shows only that nobody confirmed it.
  • Merges can be undone, or not. Some tools overwrite the losing record when two accounts merge, and the evidence for the merge goes with it. Whether a given company's history survived is checked in review.
  • The messy cases are the valuable ones. Clean exact matches are easy to invent; the address change and the shared clinic domain are the parts that are hard to fake, one reason synthetic data rarely replaces real data.

Who owns these records, and what stays unknown

Revenue operations or sales operations usually owns the CRM and any crosswalk, finance owns the ERP and billing records, and support owns the help desk. A data or IT team may maintain merge logs. Authority to discuss licensing usually rests with the CEO, CFO or owner.

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. 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. The company qualification checklist covers the basics.

What stays unknown until SourceX reviews it: SourceX's current data needs for these records, how many links hold up under review, the outcome of the rights review, and the offer terms and any reward. Industry interest in identity resolution does not mean every customer database qualifies. Discovery stays at metadata level; never ask for or handle raw customer records. For related record families, see CRM consolidation after an acquisition, sales and CRM workflows, tool-use data and the full list of data types.

Go deeper on cross-tool identity resolution

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 a client keeps cross-references or merge logs that tie its customer records together across systems, register as a partner, confirm who qualifies, and read the program terms before introducing the decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does the company need a master data management system?

No. Many companies resolve identities with a spreadsheet crosswalk, a CRM field holding the ERP number, or a migration mapping file. What matters is that the link and its basis are written down somewhere that survives staff turnover.

Is an email domain match good enough?

Usually not on its own. Several business units, a parent group or a reseller can share a domain. Treat a domain-only link as a candidate until a stronger key, such as a tax ID or contract number, confirms it.

Should I ask the client for their crosswalk file?

No. Ask whether one exists, which systems it covers and who maintains it. Partners stay at metadata level; SourceX reviews any records under its own agreement with the company.

Sources

  1. refer.sourcex.si/terms
  2. moj-analytical-services.github.io/splink/topic_guides/theory/fellegi_sunter.html
  3. help.salesforce.com/s/articleView
  4. help.salesforce.com/s/articleView
  5. mercor.com/data

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment