This article is for educational purposes only and does not constitute legal advice.
In a stock purchase or merger, buyers sometimes assume IP transfer issues are easier because the entity survives or the equity changes hands rather than each asset being separately conveyed. That assumption can be expensive. Entity-level continuity does not eliminate change-of-control clauses, broken chain of title, contractor ownership gaps, open-source exposure, privacy liabilities, or software licenses that do not travel cleanly.
For many targets, IP is not just one diligence bucket among many. It is the reason the deal exists. That makes IP diligence less about creating a giant schedule and more about answering a simpler question: will the buyer own or control everything needed to operate the business after closing without walking into a surprise?
This guide focuses on the IP and IT issues in stock deals and mergers that routinely affect value, leverage, and post-closing cleanup.
In This Guide
- Why deal structure still matters for IP
- Owned IP and chain-of-title review
- Inbound licenses, outbound licenses, and consent traps
- Software stack, open source, and data issues
- Reps, covenants, and ancillary documents
- How sellers can prepare before a process starts
Why deal structure still matters for IP
Even when the target entity survives, counsel still has to analyze whether the transaction itself triggers consent rights, anti-assignment clauses, or license termination rights. Some agreements care about assignment. Others care about change of control. Others are drafted imprecisely enough that both sides will argue about what the transaction means.
The buyer should also understand whether critical IP sits in the target, in an affiliate, in a founder personally, or in a separate holding vehicle. If the deal assumes the target owns the technology but the registrations or contract history say otherwise, the diligence problem is already economic, not merely clerical.
Owned IP and chain-of-title review
Start with what the target claims to own and test whether ownership is actually clean. Registered IP should trace to the current record owner. Contractor-developed code, content, designs, patents, trademarks, data sets, and know-how should be backed by enforceable assignment language. If the target is relying on employment status alone, that may be inadequate for some categories of IP or for some jurisdictions.
The highest-value questions are often basic:
- Do employee and contractor agreements assign IP clearly and broadly enough?
- Were founder-era assets ever actually assigned into the company?
- Are there gaps in patent, trademark, domain, or copyright recordation?
- Does any former affiliate still own or administer material IP?
- Are trade secret practices strong enough to support trade secret status?
If the answers are weak, the buyer should not treat remediation as a post-closing administrative task without pricing it. Broken ownership is often a leverage point because it affects both risk and timing.
Inbound licenses, outbound licenses, and consent traps
Inbound licenses determine what the target is allowed to use. Outbound licenses determine what the target has already given away. Both matter. A buyer wants to know whether the business can continue to operate after closing and whether the target has granted rights that reduce exclusivity, pricing power, or freedom to integrate.
Material license review should focus on exclusivity, scope, territory, sublicensing, assignment, change-of-control treatment, audit rights, source-code escrow, support obligations, and any rights that spring into existence on default or insolvency. SaaS agreements, API arrangements, data licenses, OEM deals, reseller relationships, and development agreements frequently hide the most important economics.
Do not overlook customer or strategic partner agreements that look commercial on the front end but contain embedded licenses, joint development rights, feedback licenses, or residuals language that dilute ownership on the back end.
Software stack, open source, and data issues
For software-heavy targets, the diligence set should cover the actual stack, not just a list of registrations. What proprietary code matters most? What third-party code is embedded? What open-source components are used? What obligations do those licenses impose? Are any customer commitments inconsistent with the stack as built?
Data and privacy should sit in the same review lane. If the target holds personal information, the buyer needs to understand collection practices, privacy notice accuracy, vendor flows, incident history, cross-border issues, and whether customer contracts or regulations constrain post-closing use. A privacy problem can be an IP problem if the buyer is valuing the data and the target lacks the right disclosures or permissions to use it as represented.
- Inventory material repositories, code ownership, and access controls.
- Review open-source use against distribution model and customer commitments.
- Map personal data sources, storage, vendor access, and incident response history.
- Check whether cyber representations in contracts are stronger than the target’s actual controls.
Reps, covenants, and ancillary documents
A clean IP diligence memo should feed directly into transaction paper. If chain of title is imperfect, the purchase agreement may need a special covenant, closing deliverable, or indemnity treatment. If a consent is required, the closing condition or pre-closing covenant should reflect it. If shared systems or retained IP will remain with the seller, the parties may need transition services, a license back, or a targeted assignment.
This is also where diligence discipline pays off. The better the issue list, the tighter the rep set and disclosure schedules can be. The worse the issue list, the more the buyer overreaches in reps and the more the seller has to carve out after the fact.
How sellers can prepare before a process starts
Sellers who wait for diligence requests to discover ownership gaps usually lose time and leverage. Before a live process, a seller can materially improve outcomes by tightening contractor files, confirming founder assignments, reconciling registrations, reviewing core inbound and outbound licenses, and identifying any privacy or open-source issues that need remediation or narrative context.
The goal is not cosmetic perfection. It is to know where the pressure points are before a buyer finds them first.
Copy/Paste IP Diligence Request List
Use this targeted request list to focus diligence on the IP issues that most often affect value and closing certainty in a stock deal or merger.
IP DILIGENCE REQUEST LIST 1. Ownership and registrations - Schedule of patents, patent applications, trademarks, service marks, domains, copyrights, and material unregistered IP - Copies of assignment documents and recordation evidence - Founder, employee, and contractor IP assignment agreements - Any IP owned by affiliates or founders and used by the target 2. Inbound rights - Material license, SaaS, API, OEM, reseller, data, and development agreements - Open-source software inventory and policy - Source-code escrow agreements - Agreements with assignment or change-of-control restrictions 3. Outbound rights - Material customer, partner, distribution, white-label, and joint-development agreements - Any exclusivity, MFN, field restriction, or perpetual license grants - Any feedback, derivative-work, residuals, or co-ownership language 4. Disputes and compliance - Threatened or pending IP disputes, claims, or settlement agreements - Office actions, cancellation proceedings, or invalidity challenges - Privacy and security incidents, notices, investigations, or audits 5. Operational diligence - Repository list, code-access controls, and key maintainers - Data map for personal information and key vendor processors - Standard form contracts with IP or data provisions - Post-closing integration concerns identified by management
Official and Helpful Sources
- U.S. Copyright Office: Recordation of Transfers and Other Documents
- U.S. Copyright Office: Work Made for Hire
- USPTO Assignment Center
Related Montague Law Guides
- Startup Due Diligence: A Legal Guide for Entrepreneurs Preparing to Buy or Sell
- Open Source Software Law
- Technology Assignment Agreement Template for Startups
- Locking Down Confidentiality: A Founder’s Guide to NDAs in M&A Deals
Bottom line: in stock deals and mergers, IP diligence is really continuity diligence. The buyer is asking whether ownership, control, and legal permission will survive the deal exactly where the valuation model assumes they will.
