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 type | Before the deal | After the deal | Changed | Join status |
|---|---|---|---|---|
| Field technician account | t.017 at old domain | t017 at acquirer domain | 2023-09 | Repaired: mapping file kept by IT |
| Crew lead account | crew lead at old domain | Two profiles in the scheduling app | 2023-09 | Broken: duplicate profile created on first sign-in |
| Project key | SRV | GEOS | 2023-11 | Repaired: old key still resolves in Jira |
| Issues moved by an add-on | SRV-4410 to SRV-4980 | GEOS keys, no old key recorded | 2024-02 | Broken: redirect missing for this range |
| Billing entity | Surveying firm LLC | Engineering group, survey division | 2024-01 | Partial: 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:
- Was a user, project or entity mapping file kept during integration, and who holds it?
- Which systems changed identifiers, and in which month?
- Were any record ranges moved by add-ons or scripts rather than native tools?
- Do pre-deal and post-deal records share any stable key, such as an employee number or a job number printed on documents?
- 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.