Intellectual Property and Software Due Diligence in Vietnam

Vietnam IP due diligence is critical whenever intellectual property and software represent most of the value in a technology, digital services or consumer-brand acquisition. Yet ownership is often less certain than the target’s presentations suggest. Code may have been written by contractors, trademarks may sit with founders, licences may prohibit a change of control, and open-source components may create disclosure or distribution obligations.

This guide explains how buyers should investigate intellectual property and software assets in a Vietnam acquisition and convert findings into practical deal protection. The review should sit within the wider Vietnam M&A due diligence process.

Why IP diligence matters in Vietnam M&A

A buyer needs more than evidence that a target uses valuable technology or branding. It must establish who legally owns each asset, whether registrations and agreements are valid, what third-party restrictions apply, and whether the business can continue using the assets after closing.

Weak ownership can affect valuation, financing and integration. It may also prevent the buyer from enforcing rights against competitors or transferring technology across a group.

1. Build a complete IP asset register

Request a schedule of trademarks, patents, industrial designs, copyrights, domain names, software, databases, trade secrets and proprietary know-how. The schedule should identify the owner, registration or application number, jurisdiction, status, expiry date and relevant product or business unit.

Reconcile the register against accounting records, product materials, websites, app stores, customer contracts and management interviews. Important unregistered assets are often absent from formal lists.

2. Verify ownership and chain of title

Examine certificates, applications, assignment agreements and employment or contractor documents. Confirm that the target—not a founder, affiliate, developer or marketing agency—owns the assets it claims to own.

For acquired or commissioned technology, trace each transfer from the original creator to the target. An invoice or payment record does not necessarily prove assignment of intellectual property rights.

3. Review employee-created intellectual property

Sample employment contracts for developers, designers, researchers, product managers and senior executives. Check confidentiality, invention assignment, moral-rights treatment where relevant, and obligations to execute further documents.

Compare contract language with the work actually performed. Code or content developed before employment, outside assigned duties or using personal resources may require a separate assignment or confirmation.

4. Test contractor and vendor arrangements

Review agreements with software developers, freelancers, consultants, universities, laboratories and creative agencies. Identify whether deliverables were assigned, merely licensed or left silent. Confirm that subcontractors were permitted and bound by equivalent terms.

Where a critical module was outsourced, obtain delivery records, source code, technical documentation and acceptance evidence. Remediation may be required before closing if ownership language is incomplete.

5. Examine registered rights

Check ownership, scope, renewal status, oppositions, cancellations, security interests and territorial coverage for registered trademarks, patents and designs. Compare registered goods and services with the target’s current and planned activities.

Determine whether pending applications face objections or deadlines. A brand used in Vietnam but registered only overseas may lack the protection assumed in the valuation.

6. Review software architecture and source-code control

Understand the principal applications, repositories, programming languages, hosting environment, deployment process and dependencies. Confirm repository access, branch controls, backup practices and documentation.

Identify key-person dependency and code that exists only on personal devices or accounts. Confirm that the target controls administrator credentials, signing certificates, cloud accounts and production environments.

7. Conduct open-source software diligence

Request software composition reports and policies governing open-source use. Scan critical products where proportionate. Identify component versions, licences, known vulnerabilities and modifications.

Copyleft obligations, attribution requirements and source-code disclosure conditions should be analysed against how the product is distributed or offered as a service. A legal conclusion requires both the licence text and the actual technical use.

8. Analyse inbound and outbound licences

Review licences for databases, development tools, APIs, content, fonts, cloud services and embedded technology. Check territory, users, sublicensing, assignment, change-of-control, audit and termination provisions.

For outbound licences, determine whether customers received exclusivity, perpetual rights, source-code access or unusually broad modification rights. Revenue contracts should be cross-checked against the IP schedule.

9. Assess trade-secret protection

Identify algorithms, formulas, processes, customer data, pricing models and other confidential know-how. Review access controls, confidentiality undertakings, offboarding procedures and incident records.

A trade secret is difficult to protect if the company cannot show reasonable confidentiality measures. Shared passwords, unrestricted repositories and uncontrolled downloads weaken both security and enforcement.

10. Review domains, apps and digital accounts

Confirm registrant details and administrative control for domain names, social-media profiles, app-store accounts and advertising platforms. Founder-controlled accounts should be transferred before or at closing.

Check renewal dates, disputes, suspended listings and platform-policy violations. These assets can be operationally critical even when they are not recorded as intellectual property in the accounts.

11. Investigate disputes and infringement risk

Request cease-and-desist letters, takedown notices, opposition proceedings, licence audits and settlement agreements. Search for material disputes involving the target’s brands and products.

Management should explain how freedom-to-operate was assessed for core technology and markets. The absence of litigation does not prove the absence of infringement exposure.

12. Coordinate IP, data and cybersecurity reviews

Software diligence overlaps with personal data, cybersecurity and commercial-contract reviews. Repository access may expose personal information; customer data use may exceed contractual permissions; and security incidents may affect code integrity.

Findings should therefore be shared across workstreams instead of analysed in isolation.

Negotiation pitfalls buyers encounter after Vietnam IP due diligence

A recurring gap in Vietnam IP due diligence is assuming employee-created works and inventions automatically belong to the employer, as is common under a “work-for-hire” doctrine in some other jurisdictions. Vietnamese law does not apply an automatic work-for-hire presumption in the same way; ownership of copyright and invention rights created by employees generally depends on the terms of the employment contract or a separate written assignment. Buyers frequently discover during Vietnam IP due diligence that key software or product IP was never formally assigned to the company by its original developers, leaving a chain-of-title gap that must be cured before closing.

A second pitfall involves open-source software. Where Vietnam IP due diligence identifies copyleft-licensed components (such as GPL-family licenses) embedded in proprietary code without adequate compliance controls, the buyer may inherit an obligation to disclose or license out proprietary source code. Sellers often characterise this as a low-probability risk, but buyers should insist on a source-code composition scan and specific representations addressing open-source usage, since remediation after closing can require substantial engineering rework.

Sellers also commonly resist a broad indemnity for third-party infringement claims, preferring to rely on general warranty caps. Where Vietnam IP due diligence has not confirmed a clean chain of title or freedom to operate against known competitor patents, buyers should negotiate a specific, uncapped or high-cap indemnity for IP infringement claims tied to pre-closing conduct.

Vietnam IP due diligence market practice: assignments, escrow, and licence transferability

Market practice on Vietnam technology and manufacturing deals increasingly requires, as a closing condition, that all outstanding employee and contractor IP assignments be executed and IP asset registers reconciled against actual registered rights before completion, rather than relying on a post-closing indemnity alone. This reflects a broader freedom-to-operate discipline used across M&A due diligence generally: confirming not just that the target owns its IP, but that using it does not infringe a third party’s registered rights in the relevant markets.

For software targets, buyers increasingly request source-code escrow arrangements, particularly where the target’s core product depends on a small engineering team, to protect continuity of the technology if key personnel depart after closing. Vietnam IP due diligence should also confirm whether material inbound licences (cloud infrastructure, third-party APIs, enterprise software) contain change-of-control clauses that could be triggered by the transaction, since an unanticipated licence termination can disrupt operations immediately after closing.

Worked example: converting an IP finding into deal protection

Consider a hypothetical software target where Vietnam IP due diligence reveals that the company’s core product incorporates a component licensed under a strong copyleft open-source licence, integrated directly into the proprietary codebase by a contractor who is no longer engaged. The company has no record of a compliance review at the time the component was adopted, and the resulting license-compliance risk was never assessed.

In this hypothetical, buyer’s counsel would typically commission a targeted source-code composition analysis to confirm the scope of affected code, then negotiate a specific indemnity for licence-compliance remediation costs, potentially combined with a pre-closing condition that the seller either replace the affected component or obtain a compatible commercial licence. This structure is illustrative only; the appropriate remedy depends on the specific licence terms and how deeply the component is integrated into the product.

Key red flags

• Core trademarks, domains or repositories are held by founders or affiliates.
• Contractor agreements do not contain clear assignments.
• Source code depends on unsupported or vulnerable components.
• Open-source obligations have not been identified.
• Critical licences can terminate or require consent on a change of control.
• Customers received broad exclusivity or source-code rights.
• Trade secrets are accessible without meaningful controls.
• Key digital accounts use personal email addresses or devices.

Turning findings into transaction protection

Missing assignments, registrations and consents can be made conditions precedent. Identified disputes or licence breaches may justify a price adjustment, escrow or specific indemnity. Representations should address ownership, non-infringement, open-source use, registered rights, confidentiality and the accuracy of the asset schedule.

Material technology exposure should also be considered alongside hidden liabilities and the buyer’s plan for turning diligence findings into contractual protection.

Vietnam IP due diligence checklist summary

Deal teams can use the following checklist to confirm IP coverage before signing:

• Vietnam IP due diligence: reconcile the IP asset register against actual registered rights and filing status.
• Vietnam IP due diligence: confirm employee and contractor IP assignments are complete and properly executed.
• Vietnam IP due diligence: run a source-code composition scan for open-source licence compliance.
• Vietnam IP due diligence: assess freedom to operate against known competitor patents in relevant markets.
• Vietnam IP due diligence: review inbound licences for change-of-control and termination triggers.

For the underlying registration framework, see the National Office of Intellectual Property of Vietnam’s public guidance on registered rights, which supports the ownership verification described throughout this Vietnam IP due diligence guide.

Key takeaways on Vietnam IP due diligence

• Vietnam IP due diligence should never assume automatic employer ownership of employee-created IP without a written assignment.
• Vietnam IP due diligence findings on open-source compliance are most effective when converted into a specific indemnity plus a remediation closing condition.
• Vietnam IP due diligence should assess freedom to operate separately from ownership, since owning valid IP does not preclude infringing someone else’s rights.
• Vietnam IP due diligence covering software targets should evaluate whether source-code escrow is warranted given team concentration risk.

Conclusion

Effective IP and software due diligence combines legal documents with technical evidence and operational control. The buyer should finish with a verified chain of title, a clear map of third-party dependencies, quantified remediation priorities and transaction protections matched to the most valuable assets.

IVLF Advisors’ M&A advisory Vietnam team routinely leads Vietnam IP due diligence for cross-border technology and manufacturing acquisitions, converting ownership and licensing findings into enforceable assignments, indemnities, and closing conditions. Buyers evaluating a Vietnamese target should also review our related guides on cybersecurity due diligence and personal data protection due diligence, both of which frequently intersect with software and technology IP. For a transaction-specific risk assessment, contact IVLF Advisors as your Vietnam M&A lawyer to structure protection before signing.

Frequently Asked Questions

Does a Vietnamese company automatically own IP created by its employees?

Not automatically in every case. Vietnam IP due diligence should confirm that employment contracts or separate assignment agreements clearly vest ownership of employee-created copyright and inventions in the company, since Vietnamese law does not apply a blanket work-for-hire presumption equivalent to some other jurisdictions.

Why does open-source software matter in Vietnam IP due diligence?

Certain open-source licences impose “copyleft” obligations that can require disclosure or licensing-out of proprietary code incorporating the licensed component. Vietnam IP due diligence should include a source-code composition review to identify such components before they become a post-closing compliance obligation.

What is freedom to operate and why does it matter?

Freedom to operate confirms that using the target’s products or technology does not infringe a third party’s registered patents, trademarks, or other IP rights in the relevant markets. Vietnam IP due diligence should assess this separately from ownership diligence, since a company can own valid IP while still infringing someone else’s rights.

Should software targets use source-code escrow?

Source-code escrow is commonly requested where the target’s product depends heavily on a small engineering team, to protect the buyer’s ability to maintain the product if key developers depart after closing. Vietnam IP due diligence should assess whether this protection is warranted based on the target’s technical dependency profile.

How does Vietnam IP due diligence treat trademarks differently from trade secrets?

Registered trademarks can be verified against the National Office of Intellectual Property’s public register, while trade secrets depend entirely on the strength of the target’s confidentiality practices and non-disclosure agreements, which diligence must assess qualitatively rather than through a public registry search.