Assignment Restrictions in Software Contracts Before an Exit

A software company can look ready for exit until diligence reaches the contract repository. Revenue may be recurring and code valuable, but key agreements may say that rights cannot be assigned, transferred, sublicensed or moved without counterparty consent.

For PE buyers, strategic acquirers and founders preparing an India-linked software exit, assignment review is a closing-risk exercise. The question is whether revenue, product delivery and software rights can survive the transaction structure.

Why This Matters

The Indian Contract Act, 1872 is the starting point because assignment risk usually depends on the contract signed and the obligations being moved. In software deals, that can include customer subscriptions, implementation work orders, reseller appointments, support commitments, escrow terms, OEM licences and cloud dependencies.

The issue is often missed because teams treat assignment as a back-office legal clause. If a buyer is acquiring assets, migrating customers into a new entity or combining the target with a group platform, assignment restrictions can affect which contracts transfer and which counterparties must sign consents. Even in a share sale, clauses may still restrict indirect transfers, affiliate transfers, subcontracting or control changes.

The Companies Act, 2013 matters because board authority, approvals and execution records may need to support the transfer plan. The Information Technology Act, 2000 is relevant where contracts, clickwrap terms, renewals and amendments were completed electronically. If the contract carries software, documentation, APIs or implementation deliverables, the Copyright Act, 1957 helps frame licence continuity and ownership questions.

What Counsel Should Review

Start with a ranked contract inventory. The first pass should cover top customers, enterprise accounts, platform partners, reseller agreements, inbound software licences, development agreements, support arrangements, hosting providers, escrow agreements and loan documents.

Each agreement should be coded separately for assignment, novation, delegation, subcontracting, sublicensing, affiliate transfer, change of control, merger, business transfer and notice requirements. These are not interchangeable labels. A clause that blocks assignment may not block a share sale. A clause that permits affiliate transfer may not permit transfer to an acquirer.

Customer value should drive priority. If a minor customer needs consent, that may be a post-closing cleanup item. If the target's largest enterprise customer can refuse assignment, demand new terms or terminate on transfer, the issue belongs in the deal model and closing timetable.

Inbound licences deserve special attention. Many software companies depend on third-party code, APIs, SDKs, data feeds, marketplace terms and cloud credits. A buyer can acquire the target and still lack the right to move, sublicense or embed a licensed component in the combined roadmap.

Counsel should then connect the matrix to structure. A share purchase, slump sale, business transfer, merger, asset sale or post-closing reorganisation can produce different outcomes. The buyer should know before signing which contracts require consent, which require notice and which should stay with the target entity until renewal.

Relevant Judicial Guidance

In Nabha Power Limited v. Punjab State Power Corporation Limited, Civil Appeal No. 8478 of 2014, reported as 2024 INSC 833, the Supreme Court considered express contractual wording and business efficacy. Paragraph 41 of the official judgment supports the limited point that commercial interpretation cannot contradict clear contract language.

For assignment diligence, the practical point is simple. If a software contract says prior written consent is needed before assignment, merger or transfer to an affiliate, the buyer should plan around that wording. It should not assume that commercial convenience will cure a missing consent after signing.

Typical Timeline and Cost Range

A focused assignment review for a software company with a clean repository can often be completed within 1 to 2 weeks after the full document set is available. A deeper review across legacy enterprise terms, reseller documents, software licences and escrow arrangements usually takes 2 to 4 weeks.

Fees should be scoped by contract volume, customer concentration, licence complexity, execution evidence, consent planning and whether counsel must prepare a risk matrix, consent letters, novation agreements or closing conditions.

Common Mistakes

1. Assuming a share sale avoids every assignment issue. Some contracts restrict indirect transfers, affiliate transfers, control changes or post-closing migrations even when the target entity remains the contracting party.
2. Ignoring inbound software and platform licences. Customer contracts may transfer cleanly while APIs, SDKs, hosting terms, data feeds or reseller licences block the combined product plan.
3. Treating all consent items as equal. A consent right in a low-value contract is different from a consent right held by a top customer, core vendor or mission-critical licensor.

How KAS & Co. Can Help

KAS & Co. helps investors, acquirers and Indian software companies review assignment restrictions before investments, acquisitions and exits. The review can cover customer contracts, inbound licences, reseller arrangements, escrow terms, consent matrices, transaction structure and purchase-agreement risk allocation. For support, contact KAS & Co..

FAQs

1. Is assignment the same as novation?

No. Assignment usually transfers rights, while novation replaces one contracting party with another and commonly requires counterparty agreement. Software exits often need both concepts reviewed.

2. Which software contracts should be reviewed first?

Start with top customer agreements, long-term enterprise subscriptions, implementation statements of work, reseller and channel contracts, core platform licences, escrow agreements, hosting terms and payment-provider arrangements.

3. Can a buyer leave contracts in the target entity after closing?

Sometimes. That may reduce assignment friction in a share acquisition, but it may not solve restrictions on affiliate use, sublicensing, integration, support migration or post-closing group restructuring.

4. What should an assignment consent matrix include?

It should list the counterparty, contract value, restricted action, clause wording, consent or notice requirement, timing, owner, communication plan and whether the item is a signing or closing condition.

Sources

• The Indian Contract Act, 1872 - India Code
• The Companies Act, 2013 - India Code
• The Information Technology Act, 2000 - India Code
• The Copyright Act, 1957 - Copyright Office
• Nabha Power Limited v. Punjab State Power Corporation Limited - Supreme Court of India