After an acquisition, the identity map decides whether an archive still joins up

Short answer

Identity changes after an acquisition can split one person, project or customer into two records that no longer join. Renamed user accounts, re-keyed projects, merged domains and new legal entities each break links between pre- and post-deal data unless someone kept a crosswalk mapping old identifiers to new ones. An archive whose joins survive tells a continuous story; one whose joins break reads as two unrelated datasets. Ask whether the crosswalk exists before a licensing conversation, not after.

Visual briefFull-size diagram
Before and after panels: on the left, old user, project and entity identifiers fail to join to post-acquisition records, shown as broken orange links; on the right, a crosswalk table sits between them and every link turns green.
Illustrative crosswalk for a fictional surveying firm acquired in 2023. No real identifiers are shown.

How do identity changes after an acquisition affect joined archive records?

They break the keys that connect records across systems and across time. A work order still exists, but the technician who closed it, the project it belonged to and the entity that billed it may now carry different identifiers, so a join returns nothing or returns duplicates.

The live page on whether an acquired company can license its historical data covers rights and who signs. This page covers a narrower, technical question that decides how useful those records are once rights are settled: do they still connect?

Where the joins break: four identity changes

Each change below is common in integrations. Vendors document the behavior for two of them.

  • User accounts renamed. When employees move to the acquirer's email domain, their sign-in names change. Microsoft documents that a User Principal Name change can break the link between a Microsoft Entra user and that user's profile in a SaaS or line-of-business app, and that apps using just-in-time provisioning may create a duplicate profile an app admin must repair. Two profiles for one person split that person's history.
  • Projects re-keyed. Integration teams often rename project codes to the acquirer's scheme. Atlassian documents that after a Jira project key changes, the old key still works in JQL and old issue keys still resolve through the REST API, but text links are not rewritten. Atlassian also notes that issues moved by third-party apps may not record their old keys, which breaks the redirect.
  • Legal entities renamed or merged. Invoices, contracts and approvals before the deal name one entity; after, another. Without a mapping, revenue and approval chains look like they stop on the closing date.
  • Customer and vendor accounts merged. Duplicate accounts are often merged during cleanup, and the losing record's history may be reattached or dropped depending on the tool.

All vendor behavior above checked 2026-10-18; versions differ, so the company's administrator confirms what happened in its own systems.

The crosswalk (Illustrative)

A fictional 140-person land surveying firm was acquired in 2023 by a 600-person engineering group. Its field records from 2012 to 2023 sit in the old systems; work since then sits in the acquirer's. This is the crosswalk an integration lead would show the owner. Every identifier is invented.

Identifier typeBefore the dealAfter the dealChangedJoin status
Field technician accountt.017 at old domaint017 at acquirer domain2023-09Repaired: mapping file kept by IT
Crew lead accountcrew lead at old domainTwo profiles in the scheduling app2023-09Broken: duplicate profile created on first sign-in
Project keySRVGEOS2023-11Repaired: old key still resolves in Jira
Issues moved by an add-onSRV-4410 to SRV-4980GEOS keys, no old key recorded2024-02Broken: redirect missing for this range
Billing entitySurveying firm LLCEngineering group, survey division2024-01Partial: mapping only in the finance team's spreadsheet

Read across the last column. Two of five joins are intact, two are broken, one depends on a spreadsheet one person maintains. That is a normal result, and it is exactly what an owner should know before deciding whether the pre-deal archive is worth reviewing. The fix for the broken rows is usually a one-time mapping exercise by the company's own IT team; the partner never touches the data.

Questions to put to the owner

Keep it at metadata level:

  1. Was a user, project or entity mapping file kept during integration, and who holds it?
  2. Which systems changed identifiers, and in which month?
  3. Were any record ranges moved by add-ons or scripts rather than native tools?
  4. Do pre-deal and post-deal records share any stable key, such as an employee number or a job number printed on documents?
  5. Which entity holds the rights to the pre-deal records today, and who can sign for it?

For the wider integration program these questions sit inside, see an acquisition integration; serial acquirers face the same issue repeatedly, as covered in programmatic M&A strategy. The decision tier of a CRM is especially sensitive to renamed owners: see CRM outcome data vs contact lists.

Does the company qualify?

Being acquired does not disqualify a company. The baseline still applies: at least 50 full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Details are on who qualifies.

Unknown until SourceX reviews: whether the records match a SourceX's current data needs, how much of the archive survives de-identification, and whether any purchase-agreement terms limit reuse.

Limits and unanswered questions

  • Counsel decides rights. A clean crosswalk says nothing about whether the purchase agreement or customer contracts permit licensing.
  • Some joins cannot be rebuilt. If no mapping was kept and no stable key exists, part of the archive may only be usable on its own.
  • The crosswalk is identifying. It links people across systems, so it stays with the company. SourceX handles de-identification under any agreement.
  • Money stays separate. Compensation for licensed data is agreed between SourceX and the company. A partner's reward is paid separately by SourceX and never reduces the company's payout.

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 an acquired company's owner can say who holds the crosswalk and which entity holds the rights, introduce that officer: register, check who qualifies, and read the terms. More playbooks are in guides.

  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 a broken identity map disqualify an acquired company?

No. It means some joins need repair or will be missing for a period. SourceX reviews what survives. The owner simply knows more if the crosswalk question is asked before the conversation.

Who usually holds the identity crosswalk?

Often the integration team or IT: a migration mapping file, a directory sync log, or an admin's spreadsheet. Sometimes nobody kept one, which is worth knowing early.

Should I ask to see the mapping file?

No. Ask whether it exists, who holds it and which systems it covers. The file links people across systems, so it stays with the company; the partner never needs it.

Sources

  1. learn.microsoft.com/en-us/entra/identity/hybrid/connect/howto-tr…
  2. confluence.atlassian.com/adminjiraserver/editing-a-project-key-938847…
  3. support.atlassian.com/jira/kb/moved-issues-no-longer-redirect-from…
  4. refer.sourcex.si/terms

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