Data synergies in M&A: operational value versus licensing value

What are data synergies in M&A, and which are licensable?

Data synergies are the gains an acquirer expects from combining two companies' records. Most are operational: better cross-sell, cleaner reporting, shared analytics, consolidated systems. A second kind is licensing value: after integration, the combined pre-acquisition records of the acquired companies may be licensable to AI developers, if rights and consents allow.

The two kinds need different tests, different owners and different timing. A deal model should not mix them.

Operational value versus licensing value

Operational synergies appear in the model as cost or revenue lines. A license payment, if one is ever received, should be shown separately and not annualized.

Why corporate development teams should separate them

A corporate development team that puts both in one line cannot defend either in front of an investment committee. Operational synergies are tested by integration planning. Licensing value is tested by rights and records. Mixing them also invites the wrong risk allocation: an operational miss is an execution problem, while a licensing problem is usually a contract or consent problem found in diligence.

Treat licensing value as upside, not as part of the base case or the purchase price rationale, unless the legal and records work is done. See the corporate development referral page for how deal teams approach it.

What must be true before acquired records can be licensed?

Run five tests, one per target and one for the combined entity.

• Records: the target holds years of its own operational records across several systems, and someone can export them.
• Rights: the target created the records, and customer contracts, employee notices, privacy policies and vendor terms allow licensing; the purchase agreement transfers or preserves those rights.
• Consents: any consent the agreements require was obtained, or the affected data is excluded.
• Separation: the target's pre-acquisition records can be identified apart from the combined company's later records.
• Authority: an authorized sponsor at the post-closing company can approve a license.

Customer data held for clients, consumer personal information and protected health information are common stoppers. If a record set fails any test, it stays out. Privacy and consent questions are for counsel, and the data quality due diligence checklist helps sort the records.

Where in the deal timeline does this belong?

Preserve archives before systems are shut down. Records deleted during integration cannot be licensed later.

Illustrative example

Illustrative: a fictional acquirer buys three regional IT services firms over two years. The operational case rests on shared tooling and cross-selling managed services. Separately, deal counsel notes that each target's pre-acquisition ticketing and project records sit in different systems, with different client contract terms. Before integration retires the legacy ticketing tools, the integration lead takes a full export of each, tags the source entity and years covered, and flags records governed by client confidentiality clauses. Two years later, the CFO can ask a clean question: which of these record sets do we hold the rights to license? The answer may be some, none or all, and no price or timing is assumed.

Questions to put to each target in diligence

• Which systems hold the longest histories, and when were any retired?
• Which client contracts restrict use of records about their work?
• What privacy notices were given to employees and customers?
• Who can run a full export, and has one ever been done?
• Has any of this data already been licensed or shared with a third party, including for AI training?

These questions cost little in diligence and are hard to answer after closing. They also tie to claims a target makes about its own data assets, which the guide on AI washing in due diligence helps test.

What does this mean for a referral partner?

Partners such as corporate development staff, integration consultants and advisors can introduce a post-closing company that qualifies. The company needs 50+ full-time employees at peak (contractors excluded), several years of documented operations and an authorized sponsor. The introduction is made through the referral form or the partner's referral link, and the partner never handles records. See also the page for post-merger integration consultants and the guide on testing proprietary data claims.

A company keeps ownership; data is licensed, not sold, typically with exclusivity for AI training for an agreed term. Nothing is binding until the company agrees price and terms and signs. 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 only after the buyer pays and SourceX receives its fee. No reward is guaranteed. Check your employer's and professional rules on referral fees first.

How should deal teams document the decision?

Write a one-page memo at closing that states which pre-acquisition record sets exist, where they are stored, who is the custodian, and which rights questions are open. Update it at each integration milestone. The memo lets a later CEO or CFO decide on licensing quickly, and it shows an investment committee that licensing value was considered but not assumed.

Limits and open questions

• Many records cannot be licensed because of client contracts or privacy law.
• Pre-acquisition records are only useful if they remain separable and exportable.
• Buyer demand varies, and no deal is promised.
• Engineering archives, such as those in AutoCAD, raise ownership questions that depend on customer contracts.

The company fit checker gives a preliminary, non-binding screen, and the guide to building an M&A buyer list shows where data buyers fit in a sell-side process.

Next step

Keep licensing value out of the base case, and test it when the deal closes. To introduce a company, register as a partner or let the company apply at sourcex.si/apply.