Software Assignment Agreement Template for Australia
Generate a bespoke document
What is a Software Assignment Agreement?
A software assignment agreement permanently transfers copyright in specified software from the assignor to the assignee in exchange for agreed consideration. In Australia, the assignment must be in writing and signed under the Copyright Act 1968. Because copyright and patent rights are separate, the agreement must expressly address whether any associated patent rights are also transferred. Moral rights remain with the developer and cannot be assigned, but a written moral rights consent can be obtained alongside the assignment.
Frequently Asked Questions
What must a software assignment agreement include to be valid in Australia?
Under the Copyright Act 1968, the agreement must be in writing, clearly identify the software being assigned, state that copyright is being assigned (not merely licensed), and be signed by or on behalf of the assignor. It should also state the consideration, the effective date, and include the assignor's warranties of ownership.
Does a software assignment automatically include patent rights in Australia?
No. Copyright and patent rights are separate forms of intellectual property. A software assignment transfers copyright; any associated patented methods or processes must be assigned separately in writing under the Patents Act 1990. The agreement should expressly state whether patent rights are included or excluded to avoid ambiguity.
Can a freelancer's software copyright be assigned to a client in Australia?
Yes, and this is the standard practice. Under the Copyright Act 1968, copyright in work created by a freelancer vests in the freelancer, not the commissioning party, unless assigned in writing. Clients who want to own copyright in custom software must ensure a valid written assignment is signed at or before delivery of the software.
What is the difference between a software assignment and a software licence in Australia?
Assignment permanently transfers copyright ownership to the assignee. A licence grants permission to use the software without transferring ownership, so the original owner retains copyright and can grant licences to others. After assignment, the assignor has no continuing rights, other than non-assignable moral rights.
What warranties should the assignor give in an Australian software assignment agreement?
The assignor should warrant that they are the sole owner of the copyright, that the software is original and does not infringe third-party intellectual property, that no part of the software is subject to a viral open-source licence that would restrict the assignee's use, and that there are no outstanding licences that conflict with the assignment.
How do moral rights affect a software assignment in Australia?
Moral rights under Part IX of the Copyright Act 1968 cannot be assigned. The developer retains the right of attribution and the right not to have the software falsely attributed or derogatorily treated. The assignment should include a written moral rights consent authorising the assignee to use, modify, and adapt the software without attribution.
What are the CGT implications of assigning software copyright in Australia?
The assignment of copyright for consideration is a CGT event under the Income Tax Assessment Act 1997. The assignor's capital gain is calculated as the consideration received less the cost base of the copyright asset. The assignee acquires the copyright at its cost base equal to the consideration paid. Both parties should seek tax advice before agreeing the consideration.
Should a software assignment agreement include a source code escrow in Australia?
If the assignee is acquiring software that still requires maintenance by the assignor, a source code escrow arrangement protects the assignee if the assignor later becomes insolvent or ceases to support the software. The assignment agreement should reference the escrow arrangement and confirm what triggers release of the source code to the assignee.
About the Software Assignment Agreement
A Software Assignment Agreement is a crucial legal document that facilitates the complete transfer of software intellectual property rights from one party to another. In the United States, this agreement ensures compliance with federal copyright and patent laws while providing clear documentation of ownership transfer. You'll need this contract whenever you're acquiring software assets, selling your software business, or converting contractor-developed software into company-owned property.
When do you need this document?
You'll require a Software Assignment Agreement in several business scenarios. During company acquisitions or mergers where software assets are being transferred, this document ensures proper legal transfer of all intellectual property rights. If you've hired contractors or freelancers to develop software and want to secure complete ownership, an assignment agreement converts their work into your company's property. Startups often use these agreements when transitioning from founder-developed software to corporate ownership, or when bringing on investors who require clear IP ownership documentation. Additionally, if you're purchasing software from another company or individual developer, this agreement protects your investment by ensuring you receive full ownership rights rather than just a license to use the software.
Key legal considerations
Several critical legal elements must be addressed in your Software Assignment Agreement. The assignment clause should transfer all rights, title, and interest in the software, including source code, object code, documentation, and any related intellectual property. Warranty provisions are essential, requiring the assignor to guarantee they own the software, have the right to transfer it, and that the software doesn't infringe on third-party rights. Consider including representations about the software's functionality, security, and compliance with industry standards. Payment terms and consideration must be clearly defined, whether it's a lump sum, installment payments, or other forms of compensation. The agreement should address what happens to existing licenses granted to third parties and whether the assignor retains any rights to use the software. Include provisions for source code escrow if ongoing development or maintenance is required, and ensure all related documentation, passwords, and development tools are transferred.
Legal requirements in United States
Under United States law, your Software Assignment Agreement must comply with federal copyright law under 17 U.S.C. § 101 et seq., which governs the transfer of copyrightable software code. The agreement should address the Work for Hire Doctrine if the software was developed by employees or contractors, as this affects initial ownership rights. Patent considerations under 35 U.S.C. may apply if the software includes patentable innovations or algorithms. The Defend Trade Secrets Act requires careful handling of any proprietary or confidential information included in the software transfer. State contract law governs the agreement's formation and enforcement, so ensure compliance with your state's specific requirements for contract validity, including proper consideration and signatures. The Uniform Commercial Code may apply to certain aspects of software sales, particularly regarding warranties and remedies. Include choice of law and jurisdiction clauses to specify which state's laws will govern any disputes, and ensure the agreement meets that state's execution requirements for enforceability.
GOVERNING LAW
Applicable law
This Software Assignment 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