How a Licensing Law Firm Reviews Software Transfers after Acquisitions

In a stock purchase, the target generally remains the licensee, although a change-of-control clause may require approval. An asset buyer may need vendor consent or a replacement license. California Corporations Code § 1107(a) provides for succession of rights in mergers governed by that provision. It does not override applicable contractual or federal IP restrictions.

The governing merger law depends on the entities involved. Buyers planning asset acquisitions should assess software permissions separately from ownership of equipment.

Some agreements treat mergers or asset sales as assignments, while others allow transfers to specified successors. A change-of-control clause may apply even when the licensee remains unchanged. Check definitions of assignment, control, affiliate, and permitted successor, along with notice and approval requirements.

Under 17 U.S.C. § 101, an exclusive copyright license can constitute a transfer of copyright ownership, while a nonexclusive license does not. Neither status automatically gives the licensee unrestricted assignment rights. In Gardner v. Nike, Inc., 279 F.3d 774 (9th Cir. 2002), the Ninth Circuit required the licensor's consent to assign an exclusive copyright license unless the agreement permitted assignment. The case did not involve a software acquisition. Nonexclusive licenses may face separate federal transfer limits. State law generally governs contract interpretation, subject to applicable federal law. A software licensing review should examine the rights actually granted.

The contract may require advance notice, prior consent, or approval only for specified transactions. Check exceptions and any limits on the vendor's ability to refuse. Written consent should identify the agreement, transaction, approved entity, and effective date. Approval of an assignment does not automatically permit more users or installations.

The license may cover target employees but exclude the buyer's parent, other subsidiaries, or contractors. A centralized IT team accessing software across entities can exceed those permissions. Compare the post-closing organization chart with the named licensee and authorized-user definitions. Seek expanded rights before adding entities.

Agreements may limit named users, devices, processors, servers, or subscription tiers. SaaS terms can also restrict account sharing. Compare existing entitlements with planned workloads before migration. Additional use may trigger fees, a royalty dispute, or contractual remedies. Licensing and contracts review can distinguish agreed charges from new vendor proposals.

Gather signed licenses, order forms, amendments, renewals, and applicable online terms. For each essential product, record:

• The licensee and authorized users or affiliates.
• Assignment, merger, control, and notice restrictions.
• Usage metrics, renewal and support terms, and fees.
• Required vendor consent, responsible party, and deadline.

Classify licenses as transferable, continuing without transfer, or requiring further approval. Critical unresolved consents may warrant closing conditions.

The purchase agreement can allocate responsibilities and costs but cannot compel a vendor to grant additional rights. Alternatives include negotiating a new license, delaying integration, or migrating platforms. A transition services agreement allows access only where the vendor's license or separate authorization permits it. Related technology transactions may need distinct data-access and migration terms. Unauthorized transfers may trigger remedies or termination, but termination is not always automatic. Examine notice, cure, and termination provisions.