Cross-border M&A advisors: introducing a US company after the deal closes

For cross-border M&A advisors, one of the best post-acquisition opportunities is the window between closing and system migration. While the acquirer moves the US company onto group email, CRM and ERP, the advisor can ask the US CEO to assess years of records first and, with the new owner's approval, introduce the company to SourceX.

Why the months after closing matter

Closing ends your mandate, not your relationship. You spent months with the US CEO and CFO on the data room, management presentations and disclosure schedules, and you probably understand how the company keeps its records better than anyone at the acquirer's head office.

That knowledge is most useful in the first year of ownership. An acquirer based in Europe or Asia will often want its new US business on group email, group finance and a single CRM instance. Each migration forces a decision about which history moves, what gets archived and what is quietly deleted.

If you raise a records assessment before those decisions are final, the US company keeps an option it would otherwise lose: licensing its operating history to AI developers through SourceX for a one-time payment, while keeping ownership of the data.

Why is integration the trigger?

Integration is when legacy systems are retired, and retired systems are where years of records disappear.

AI developers are building agents that carry out multi-step work, and training them takes examples of how real companies handle tickets, deals, approvals and projects. Most of that material sits inside private systems rather than on the public web. Researchers at Epoch AI estimate that, if current trends continue, language models could fully use the stock of public human-written text between 2026 and 2032. It is a forecast with wide uncertainty, but it explains why permissioned company records attract interest.

For the company you advised, the question is narrower: will the full history of its helpdesk, CRM and shared drives survive the move to group systems? If nobody has decided yet, you have a reason to call.

Timeline: from signing to the first anniversary

WhenWhat is happening at the US companyWhat you can do
Signing to closingInterim covenants limit unusual contracts; both deal teams are stretchedNothing on licensing yet. Note privately which systems held the deepest history
Closing to week 4Day-one announcements, bank mandates, payroll and reporting-line changesSend a thank-you note; mention records only in passing, if at all
Weeks 4 to 12The integration office maps systems and group IT drafts the migration planAsk the CEO whether complete exports are planned before anything is retired
Months 3 to 9Email tenant, CRM and helpdesk move to group platforms; transition services wind downMake the introduction if the CEO and the new owner agree to explore it
Months 9 to 12First budget under new ownership; earn-out periods may be measuredConfirm any license is handled consistently with the purchase agreement

Deal size and any transition services agreement shift the dates, but the sequence rarely changes: map the systems, migrate, then retire. Aim to be part of the conversation before the migration plan is signed off.

Who has to say yes after closing?

The US company now makes decisions inside its new owner's governance. The CEO is still your natural first contact, but a data license will usually need sign-off above them.

PersonWhy they matterWhat to ask
US CEONatural sponsor and the person you know bestWould you want to explore licensing before history is migrated or archived?
US CFO or controllerKnows customer contracts and how proceeds would be bookedDo any customer or vendor contracts restrict how records can be used?
Group integration leadOwns the migration plan and its datesWhich legacy systems are due for retirement, and when?
Group general counselDelegations of authority, IP and data protection policyWho in the group can approve an IP license granted by a US subsidiary?
Group CIO or IT directorRuns exports and archive decisionsWill complete exports of the legacy systems be kept?

Never go around the acquirer. If the group's delegation-of-authority matrix reserves IP licensing to the parent board, the US CEO needs that approval before signing anything, and an introduction that surprises group management damages your standing with both sides of the deal you just closed.

Permissions, approvals and the purchase agreement

Three sets of documents decide what is possible, and you probably helped negotiate at least one of them.

  1. The purchase agreement. Ask counsel whether the earn-out definition of revenue or EBITDA would capture a license payment, and whether any post-closing covenant restricts new IP arrangements. A license that moves an earn-out number can start a dispute between the sellers and the buyer.
  2. The transition services agreement. In a carve-out, some of the target's records may still sit on the former parent's systems. Records held on another company's infrastructure need clear rights before anyone can license them.
  3. Customer and employee terms. Records that mainly belong to the company's clients, and consumer or health data without a licensing basis, usually fall outside scope.

None of these is your call. Your contribution is raising the question early enough that the people who decide can answer it before records are lost.

What to say to the US CEO

Treat it as a conversation starter, not a pitch, and do not describe the company's records to anyone outside it.

If the CEO wants it in writing, adapt the post-closing note to the US CEO, which includes a copy note for the group integration lead. For a wider view of integration work, see the advisor plan for acquisition integrations.

What the company should preserve before migration

You never export, upload or review records yourself. What you can do is prompt the company to keep complete exports while it still can.

  • The legacy email tenant archived in full before mailboxes are merged into the group tenant
  • A CRM export with activity history, notes and closed-lost opportunities, not only the open pipeline
  • Helpdesk tickets with full threads, internal notes and resolution codes
  • Code repositories with commit and pull-request history, plus the issue tracker
  • Shared drives and wikis, including SOPs and project folders from teams that have since left
  • General ledger and payables detail for prior years in a readable export
  • One named person at the US company who owns the export list

Companies with deep histories often run 10 to 15 or more systems, and archives of tools the company stopped using years ago are frequently the most distinctive part of the inventory.

Which acquired companies are worth the call?

Apply the baseline SourceX uses: a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, the right to license its records and an authorized sponsor such as the CEO, CFO or owner. Industry matters less than how much connected history exists. The M&A advisor partner page covers fit by deal type.

Skip the call when the target was mainly an agency or outsourcer whose records belong to its clients, when the acquirer has already deleted legacy archives, when the business mostly holds protected health information or consumer personal data, or when the earn-out is already in dispute.

Rewards, tax paperwork and your own rules

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and rewards become payable only after the buyer pays and SourceX receives its fee. An introduction, a meeting or a signed license on its own does not trigger payment, and no reward is guaranteed. Credit goes to the first valid referrer whose introduction leads to a verified company application within the attribution window. The referral earnings calculator shows how the formula works.

Advisors can join from any supported country. If a US payer asks your firm for a W-8BEN-E, the guide to completing a W-8BEN-E for an advisory firm explains the form. Check your firm's conflicts policy and any regulator rules on third-party payments, and tell the client about the reward. This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting. The program terms set out the current details.

Next step

Pick one US company you advised in the last 18 months and find out where its integration stands. If legacy systems are still running, register as a partner and raise it with the CEO using your referral link, or let the CEO apply directly at sourcex.si/apply.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Can I raise data licensing with the target before the deal closes?

It is better to wait. Between signing and closing, interim covenants usually restrict contracts outside the ordinary course, and both deal teams are focused on conditions and funds flow. A private note of which systems hold the deepest history is enough for now. Raise the idea once the acquirer owns the company and the integration plan is being drafted, and only with the new owner's knowledge.

Does the acquirer have to approve a license by its new US subsidiary?

In practice it usually does. The subsidiary signs the license, but group delegations of authority often reserve intellectual property and data decisions to the parent, and group legal will want to review rights and privacy. Expect the US CEO to sponsor the work and the acquirer's general counsel or board to approve it. SourceX works with whoever holds that authority.

Could a license payment affect the sellers' earn-out?

It might, depending on how the purchase agreement defines the earn-out metric. A one-time license payment could count toward revenue or EBITDA under some definitions and be excluded under others. Because that can shift value between the sellers and the acquirer, ask both sides' counsel to confirm the treatment before the company signs, and keep yourself out of that negotiation.

What if the integration team has already migrated the US company's systems?

The company can still qualify if complete exports or archives survived. Ask whether the old email tenant, CRM and helpdesk were archived in full or only partly migrated. Data moved into group systems may still be separable by date and entity. If the legacy history was deleted, the opportunity is usually gone, and it is better to say so early.

I advised the US seller, not the buyer. Can I still make the introduction?

Yes, as long as you can reach someone with authority at the company as it is now owned. After a share sale the records stay with the company, which the acquirer controls, so a former owner cannot license them alone. If the founder stayed on as CEO, they are a natural first contact, but the new parent will still need to approve.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment