Novosibirsk · Russian-qualified counsel Recognised by Pravo-300 · Best Lawyers · Kommersant
Corporate & Regulatory

Foreign creditors and IP and technology asset review in Russian transactions: a briefing for general counsel

Vitaliy Vetrov · February 2026 · 11 min read

Foreign creditors acquiring Russian assets often find IP title defects too late. Practical guide for general counsel on Russian IP due diligence. Make an enquiry.

In practice, the review of IP and technology assets in Russian transactions is the stage where foreign counsel most frequently encounter surprises that should have been visible from the outset. Titles appear clean in initial disclosure; then, on a closer Rospatent check or an examination of the software licensing stack, the picture shifts. For in-house counsel overseeing a Russian asset acquisition, creditor enforcement matter, or restructuring scenario involving a target with material IP — trademarks, patents, software licences, domain names, or proprietary technology — the procedural steps under Russian law are specific enough that a generic international due diligence checklist will not cover them. This guide sets out what a rigorous Russian IP and technology asset review looks like and where the risk concentrations lie.

What to prepare before the IP review begins

Before instructing local counsel to begin, a general counsel team should assemble the following materials from the target or its Russian subsidiary:

This preparation reduces the scope of the review and focuses local counsel time on substantive analysis rather than document collection.

If you are preparing for a Russian IP and technology asset review and need to scope local counsel involvement at an early stage, make an enquiry: info@vetrovpartners.com |

Step 1 — Scoping the IP and technology asset inventory in a Russian transaction

The starting point of any Russian IP due diligence exercise is a verified asset inventory. Disclosure from the target may be incomplete not because of bad faith but because Russian companies often hold IP informally — software developed in-house and never registered, licences acquired verbally, or trademark rights accumulated through use rather than registration. Under Russian law, the latter category carries significantly weaker protection than it might in certain common-law jurisdictions.

The inventory should distinguish between assets owned by the Russian entity, assets licensed in, and assets that are effectively shared with related parties but for which formal licensing arrangements may not exist. In group structures with a foreign parent or IP holding company, it is common to find that the Russian operating entity uses trademarks, software platforms, or technical know-how under arrangements that are poorly documented or that were not updated following corporate restructurings. This distinction matters acutely for a creditor seeking to understand what economic value is actually encumbered and what is merely borrowed.

General counsel should specifically instruct local counsel to identify any assets that were created, co-developed, or contributed by individuals — founders, key employees, or contractors — without a documented assignment. Under Russian employment law, IP created by an employee in the course of their duties belongs to the employer by default, but this default is conditional on the contractual arrangements being properly structured. Where those arrangements are absent or defective, the employer's title is contestable.

Step 2 — Verifying title and registration — what Rospatent and other registries reveal

Registered IP rights in Russia are recorded by Rospatent, the Federal Service for Intellectual Property. A register search at Rospatent will confirm whether trademarks, patents, utility models, and industrial designs are in force, in the name of the correct entity, and free of registered pledges or licences. This search is publicly accessible and should be conducted independently of disclosure — relying solely on a target-provided schedule of registered rights creates a verification gap that has proven costly in a number of transactions.

The Rospatent register reveals several categories of information that are directly relevant to a creditor or acquirer: the registration status and renewal dates of each right; whether a security interest or pledge has been filed over the right; whether any recorded licences — exclusive or non-exclusive — have been registered; and whether any applications for invalidation or opposition are pending. A registered exclusive licence granted to a third party may materially affect the commercial value of the underlying right, even if the licensor retains legal title.

Domain names are recorded through registrars operating under the RU and.РФ ccTLDs. Software, by contrast, is not registered in the sense that trademarks are, but copyright arises automatically under Russian civil legislation. The practical implication is that software ownership is demonstrated primarily through evidence — employment records, contractor agreements, version history documentation — rather than a single registry entry. For transactions where the target's value is substantially embedded in proprietary software, this evidentiary question deserves dedicated attention.

One risk that frequently escapes notice until late in the process: a registered trademark that has not been used in Russia for three consecutive years is vulnerable to a non-use cancellation challenge. A creditor enforcing against IP assets — or an acquirer relying on them for post-transaction value — may find that a key trademark is exposed to challenge. Russian courts have applied this doctrine consistently, and the three-year window runs from the date of registration or last documented use, whichever is most recent.

For general counsel conducting IP and technology asset review in a Russian transaction, direct partner involvement from the outset materially reduces the risk of post-completion title defects. Make an enquiry: info@vetrovpartners.com |

Step 3 — Licence chains and contractual restrictions — how far does the encumbrance run?

Once title has been verified, the licence architecture requires review. The core question is whether the Russian entity holds rights on terms that survive a change of ownership, enforcement, or restructuring, and whether those rights can be transferred or sub-licensed to a new owner or creditor without consent from the licensor.

Under Russian civil legislation, the assignment of a licence agreement — or the change of the licensee through a corporate restructuring — may require the licensor's prior written consent depending on how the agreement is drafted. This is a point of frequent friction in transactions involving group IP structures: an intra-group licence granted on standard terms by a foreign IP holdco to the Russian operating entity may not contemplate the scenario where the Russian entity changes hands in an enforcement or insolvency context. Where the licensor is a related party that remains with the original group post-transaction, continuity of the licence cannot be assumed.

Sub-licence arrangements add a further layer. A third-party sub-licensee holding an exclusive sub-licence over the target's technology may have rights that survive a change of ownership of the head licence, depending on the specific terms and whether the sub-licence was registered. The practical implication for a creditor taking security over IP or acquiring the entity is that certain revenue streams embedded in sub-licences may be more stable than the underlying title, while others may be terminable on assignment.

Open-source software components in proprietary technology stacks require specific attention. Certain open-source licences impose conditions — including copyleft obligations — that can affect the commercialisability of the combined software product. Russian courts have not yet developed a settled body of case law on open-source licence enforcement, but the contractual obligations bind under general civil law principles. A technology stack review should identify the open-source components present and the licences applicable to each.

Step 4 — Technology transfer agreements and cross-border compliance in Russia

Where the transaction involves the acquisition or enforcement of IP rights that have been developed, licensed, or transferred across borders, the cross-border dimension of Russian IP law introduces additional compliance questions. Technology transfer agreements involving Russian parties — particularly those that include know-how, technical data, or software source code — may be subject to Russian currency control rules, export and import notification requirements, or sector-specific regulatory approvals depending on the nature of the technology.

Agreements for the transfer of rights over technology developed with public funding carry specific obligations under Russian innovation and public procurement rules. A target company that commercialised technology originally developed under a state contract or with grant funding may not hold unencumbered title; the state may retain co-ownership rights or rights of use. This is a category of defect that does not appear on the Rospatent register and requires review of the target's historical funding arrangements and research agreements.

For transactions in the technology sector — software products, platforms, or data-intensive businesses — the intersection of IP review with Russian data protection law (Federal Law No. 152-FZ on Personal Data) should not be overlooked. A software platform that processes personal data of Russian residents is subject to localisation requirements and audit exposure. A general counsel team reviewing IP assets in such a target should ensure that the data compliance review and the IP review are conducted in parallel, as deficiencies in data localisation can affect the operating licence position of the business.

Step 5 — Remediation and residual risk — what should general counsel require before signing?

The output of a Russian IP due diligence review is not a clean bill of health or a simple list of defects. It is a risk-stratified map that distinguishes between defects that are remediable before completion, defects that must be addressed by post-completion covenants or price adjustment mechanics, and defects that are structural and may affect the commercial rationale for the transaction.

Remediable pre-completion items typically include: formalising an assignment of IP rights from a founder or contractor whose contribution was not properly documented; registering an existing intra-group licence at Rospatent where the failure to register affects its enforceability against third parties; and renewing trademarks approaching expiry. These items are addressable with time and co-operation from the target.

Post-completion risk items — those that cannot be fully resolved before signing — should be reflected in the transaction documents. Representations and warranties on IP ownership and the absence of undisclosed encumbrances, together with indemnities for specific identified risks, provide a contractual backstop. For creditors rather than acquirers, the appropriate response may instead be a specific carve-out in the security documentation that reflects the IP title position accurately, rather than creating a potential enforcement defect.

Residual risks that are structural — a trademark exposed to a non-use challenge, a technology stack that includes open-source components subject to copyleft obligations, or an operating licence that depends on a licence agreement with a counterparty that may not consent to assignment — require frank discussion with the client before completion. General counsel's role in these cases is to ensure that the risk is understood, quantified to the extent possible, and reflected in the commercial terms of the transaction.

If you are advising on or managing a Russian transaction with IP and technology assets in scope, an early-stage conversation with Russian counsel is the most cost-effective intervention. Speak to our team: info@vetrovpartners.com |

Frequently asked questions

Q: How long does an IP and technology asset review typically take in a Russian transaction?

A: The timeline depends substantially on the volume and complexity of the IP portfolio and how promptly the target produces documentation. For a mid-sized Russian company with a focused trademark portfolio and standard software stack, a review covering registration verification, licence chain analysis, and preliminary risk assessment typically takes two to three weeks from receipt of complete documentation. Transactions with substantial proprietary technology, multiple sub-licences, or cross-border technology transfer arrangements will require additional time. General counsel should factor this into the overall transaction timeline and, where possible, initiate the IP review in parallel with — rather than sequentially after — the financial and commercial diligence streams.

Q: Which IP defects are most commonly found in Russian transactions involving foreign creditors?

A: In practice, the most frequently encountered defects are: unregistered exclusive licences that are unenforceable against third parties under Russian law; trademark rights that have been maintained in the name of a former group entity following a corporate restructuring without a formal assignment; IP developed by founders or contractors without documented assignment agreements; and technology stacks that include open-source components whose licence terms were not reviewed at the time of development. For creditors in particular, undisclosed pledges over registered IP rights — which are visible on the Rospatent register but often missed in disclosure — represent a material risk that affects the value of the security.

Q: Can a foreign company enforce its own IP rights in Russia directly, or does it need Russian counsel?

A: Foreign IP rights holders may initiate infringement proceedings before Russian courts directly, including the Russian IP Court for certain categories of IP dispute. In practice, however, pursuing these proceedings without qualified Russian counsel is rarely effective. Procedural requirements for documentary evidence — including legalisation or apostilling of foreign corporate documents and translations — are strictly applied, and the IP Court's procedural rules require engagement with local procedural norms that differ materially from common-law equivalents. A foreign IP rights holder should instruct Russian counsel at the earliest stage, particularly where evidence preservation or interim relief is required.

Practitioner note

This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.

Facing a matter like this?

Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.

Make an enquiry