Transferring founder-owned software to a Cyprus company

First establish what the founder actually owns

A repository under the founder’s personal account is evidence of access, not a complete ownership analysis. The code may contain contributions from earlier employers, co-founders, freelancers and open-source projects. Review that history before promising the company unrestricted rights.

Identify the software and relevant versions, preparatory material and third-party components. Check whether the founder created it independently or under an employment or client agreement. An individual cannot reliably transfer rights they do not hold, and a later company cannot cure that gap simply by describing the product as proprietary.

Separate the original software from trademarks, domain names, datasets and customer contracts. These may require different transfer steps and can have different tax treatment. A single broad label such as “all IP” may leave important commercial details unresolved.

Document the transaction and the rights

The transaction may involve an assignment, a licence or a contribution in exchange for shares, depending on the intended structure. These are not interchangeable labels. Specify the parties, rights, effective date, territory, consideration and any rights retained by the founder.

Record how the company will receive practical control: repository administration, build materials, relevant credentials and documentation. Operational handover supports the business but does not replace the legal transfer. Both the rights and the ability to use them should be clear.

Where several founders or contributors are involved, complete the chain for each relevant contribution. Resolve exceptions explicitly rather than assuming one founder’s signature covers everyone else’s work. Have the documentation prepared for the actual governing law and circumstances.

Review valuation and tax before signing

The transfer can have consequences for the founder and the company. Establish the founder’s tax residence, the asset’s history and the form of consideration. A cross-border move can involve the originating country’s disposal or exit-tax rules as well as Cyprus treatment.

The current Cyprus Income Tax Law addresses capital expenditure on intangibles introduced into a company for share capital and the need for supported market value. This does not make a founder’s chosen number automatically acceptable or establish a tax-free transfer in every country.

Keep a valuation file proportionate to the transaction. It should explain the rights, commercial assumptions and relevant evidence. A valuation is not simply a desired nexus input. Where the parties are related, consider the applicable pricing and documentation rules separately.

Historic founder work is not automatically company QE

Suppose a founder developed a product personally and the company later acquires it. The company needs to analyse its acquisition and subsequent development expenditure. It should not insert an invented salary for the founder’s earlier unpaid work into its own QE schedule.

If the company incurs genuine qualifying R&D after the transfer, those costs may affect nexus on the relevant basis. Preserve the distinction between the transferred asset’s acquisition cost and later development. The uplift may partly offset acquisition costs, but its cap does not remove the need for classification.

This can produce a different tax result from a product developed by the company from the outset. Model the actual transaction before relying on a full-nexus 3% illustration. The model should also reflect relevant annual profit deductions without confusing them with the expenditure ratio.

A founder-to-company handover checklist

Use the following checklist to organise the evidence. It is a practical preparation aid, not an official filing form or a substitute for a transaction-specific agreement.

• Identify the code, versions and other assets being transferred.
• List creators, previous employers, clients and contributor agreements.
• Inventory third-party licences and retained rights.
• Document the transfer or licence and consideration.
• Support valuation and assess tax in each relevant jurisdiction.
• Complete operational handover and record company control.
• Establish the opening asset register and nexus expenditure history.
• Track subsequent company-funded development separately.

Keep later contracts consistent with the transfer

Once the company holds the relevant rights, customer and development contracts should reflect that position. Future contractors should grant the rights the company needs, and founder employment or service arrangements should address later work.

Review changes when a new investor, co-founder or purchaser enters the business. A clear original transfer file reduces the need to reconstruct ownership at the point when the software is most commercially valuable.