Software Asset Purchase Agreement Template for Australia
Generate a bespoke document
What is a Software Asset Purchase Agreement?
A software asset purchase agreement transfers ownership of specified software, including source code, object code, related intellectual property, and associated assets from the vendor to the purchaser. In Australia, copyright assignment requires a signed written agreement under the Copyright Act 1968. The agreement should also address open-source licence risks, purchase price allocation for tax purposes, the treatment of embedded third-party licences, and any transitional support obligations of the vendor after completion.
Frequently Asked Questions
What does a software asset purchase agreement transfer in Australia?
It transfers ownership of specified software assets, which may include the source code, object code, documentation, development tools, related intellectual property rights, domain names, and any associated contracts with customers or suppliers. The agreement should clearly list what is and is not included in the assets being sold.
How must copyright in software be transferred in Australia?
Under section 196 of the Copyright Act 1968, copyright assignment must be in writing and signed by the assignor. The software asset purchase agreement itself satisfies this requirement if it clearly identifies the software and states that copyright is being assigned. Oral or informal transfers have no legal effect.
What due diligence should a purchaser conduct before signing a software asset purchase agreement in Australia?
The purchaser should verify the vendor's ownership of the software copyright, check for open-source components that may impose licence restrictions on the acquirer, review any third-party licences embedded in the software, check for pending infringement claims, and confirm that employee or contractor IP assignment agreements are in place.
What warranties does a vendor typically give in an Australian software asset purchase agreement?
Standard warranties include that the vendor owns the copyright free of encumbrances, that the software does not infringe third-party intellectual property rights, that there are no undisclosed open-source components with viral licences, that the software conforms materially to its specifications, and that there is no known malware or undisclosed functionality.
How is purchase price allocated between software assets in Australia?
The agreement should allocate the price between depreciable software (which may be depreciated over its effective life under the Income Tax Assessment Act 1997), copyright (a capital asset), and any other assets such as domain names or customer contracts. The allocation affects both parties' tax positions and should be consistent with the parties' tax returns.
What open-source licence risks arise in an Australian software asset purchase?
Some open-source licences (notably the GPL family) require that any software incorporating the open-source code also be released under the same licence. Undisclosed copyleft components can significantly reduce the value of the software asset. The agreement should include a warranty and indemnity covering GPL or other viral-licence contamination.
Does a software asset sale include customer contracts in Australia?
Only if they are expressly listed in the schedule of assets being transferred. Transferring customer contracts requires either a novation (replacing the vendor with the purchaser as a party, requiring customer consent) or an assignment (possible without consent unless the contract prohibits it). The agreement should specify the mechanism and address which party bears the risk if a customer refuses to consent.
How should escrow arrangements be addressed in an Australian software asset purchase agreement?
If the purchaser acquires the software but the vendor continues to maintain it for a period, the source code should be held in escrow and released to the purchaser on defined trigger events such as vendor insolvency, material breach of the maintenance agreement, or cessation of the vendor's business. An escrow agent and release conditions should be specified.
About the Software Asset Purchase Agreement
When you're acquiring software assets for your business, a Software Asset Purchase Agreement serves as the foundational legal document that transfers complete ownership rights rather than temporary licensing arrangements. This comprehensive agreement governs the sale and purchase of software intellectual property, source code, documentation, and related technological assets under United States law.
When do you need this document?
You'll need this agreement when your company is acquiring another business's software products, purchasing proprietary technology to integrate into your operations, or buying software assets during corporate restructuring. Technology companies frequently use these agreements when acquiring competitors' products, purchasing custom software solutions developed by third parties, or obtaining software assets through bankruptcy proceedings. Venture capital firms and private equity investors also rely on these agreements when acquiring software companies or their technological assets. The document becomes essential whenever you need to secure complete ownership rights rather than licensing permissions, ensuring you can modify, distribute, and commercialize the software without ongoing restrictions.
Key legal considerations
The intellectual property transfer clause requires careful attention, as it must clearly convey all copyrights, patents, trademarks, and trade secrets associated with the software. You'll need comprehensive warranties from the seller regarding their ownership rights, the absence of third-party claims, and compliance with open-source licensing requirements. Indemnification provisions protect you against future intellectual property disputes or undisclosed liabilities. The agreement should address escrow arrangements for source code, ongoing maintenance obligations, and transition services to ensure business continuity. Consider including representations about the software's functionality, security vulnerabilities, and compliance with industry standards. Due diligence provisions allow you to verify the software's condition, review existing licenses, and assess potential legal risks before completing the purchase.
Legal requirements in United States
Federal copyright law under 17 U.S.C. governs the transfer of software ownership rights, requiring written agreements to effectuate copyright transfers. The Digital Millennium Copyright Act imposes specific obligations regarding technological protection measures and digital rights management systems. You must comply with the Computer Fraud and Abuse Act when accessing and evaluating software systems during due diligence. State contract laws vary by jurisdiction but generally require consideration, mutual assent, and proper execution formalities. The Uniform Commercial Code may apply to certain software transactions, particularly those involving tangible goods or hybrid products. Federal Trade Commission regulations govern disclosures about software capabilities and limitations, especially in consumer-facing applications. Patent law considerations become crucial when the software incorporates patented technologies or algorithms.
GOVERNING LAW
Applicable law
This Software Asset Purchase Agreement is drafted to comply with Australia law. Key legislation includes:
Explore 208,390+ legal templates
Explore 208,390+ legal templates
Genie's Security Promise
Genie is the safest place to draft. Here's how we prioritise your privacy and security.
Your data is private:
We do not train on your data; Genie's AI improves independently
All data stored on Genie is private to your organisation
Your documents are protected:
Your documents are protected by ultra-secure 256-bit encryption
We are ISO27001 certified, so your data is secure
Organizational security:
You retain IP ownership of your documents and their information
You have full control over your data and who gets to see it