This guide is written for the seller. If you hold a licence you no longer need, transferring it legally is straightforward — but only if you establish transferability first, and most sellers discover the answer after they have already taken payment.
Step One: Establish Whether You Can Transfer At All
Read the EULA. Search it for "transfer", "assign", and "resell". The language is usually explicit. Common phrasings: "this licence is personal to you and non-transferable" (you cannot), or "you may permanently transfer this licence provided you retain no copies" (you can, with conditions).
Check the vendor's published transfer policy. Larger vendors have documented procedures, sometimes with a fee and a form. This is the safe path, because the licence ends up registered to the buyer.
Where the terms are silent, ask support. Get the answer in writing. It costs an email and it is the only authoritative source.
Transferability by Licence Type
Perpetual licences — most likely transferable. Older desktop software often permits a one-time permanent transfer.
Subscriptions — usually tied to an account and a payment method. What is sometimes possible is an account handover, which is a different thing and frequently prohibited.
OEM licences — bound to the hardware they shipped with. Not separately transferable.
Volume and multi-seat — the agreement is with an organisation. Individual seats are not yours to sell, and splitting them typically breaches it.
Academic, non-profit, and startup-programme licences — issued on eligibility. Not transferable.
Lifetime deals — depends entirely on the vendor. Many explicitly prohibit transfer.
Preparing a Clean Transfer
Deactivate first. Release the licence from your machines before listing. A key still bound to your hardware will fail activation for the buyer, and that is the most common failed handover in this category.
Gather proof of purchase. The invoice or order confirmation, with your personal details redacted. A buyer with no proof of provenance has no way to distinguish your legitimate licence from a grey-market key.
Complete the vendor's process where one exists. If a transfer form is required, initiate it — do not sell a key and leave the paperwork to the buyer.
Document the state. Version, edition, seat count, activation limit, remaining activations, and expiry if any.
Listing It Honestly
State the software, exact version and edition, licence type, original purchase date, and whether the vendor's transfer process has been completed or is pending. Say plainly whether the licence will end up registered in the buyer's name or remain in yours — that difference is material and buyers who discover it late will dispute.
Realistic pricing for a transferable perpetual licence sits around 40–70% of current retail, less for older versions.
Completing the Transfer Under Escrow
On Escrozon the buyer's funds are held before anything is handed over, which protects both sides — you know the money exists, and they know it is not released until the licence is verified.
- Buyer opens escrow.
- You provide the key and redacted proof of purchase in the deal chat.
- Where the vendor requires it, you both complete the transfer paperwork.
- Buyer activates on their own machine and checks the licence panel — type, seats, expiry, and registered name.
- Buyer confirms receipt; funds release.
Keep everything in the deal chat. If a licence is later revoked, that record is what determines the outcome of a dispute.
What Happens If It Goes Wrong
If the vendor revokes after transfer, the buyer's recourse is against you, not the vendor — they were never the vendor's customer. This is precisely why establishing transferability before listing matters more than any step afterwards.
Escrozon facilitates the transaction; it does not adjudicate whether a vendor permits transfer. That responsibility sits with both parties, and the vendor's own terms are the authority.
Vendor Approval in Practice
Where a licence can only move with the vendor's agreement, that agreement is the deal. Everything else is preparation.
Ask before you list, not after you sell. Vendors vary enormously, and some answer within hours while others take weeks or route the request through an account manager. Discovering the timeline after a buyer is waiting turns a straightforward sale into a stalled one.
Get the answer in writing. A support agent saying it should be fine is not the same as a documented approval, and the person who eventually processes the transfer will want the latter.
Ask what they actually need. Most vendors that permit transfers want the same handful of things: proof of the original purchase, the licence or order identifier, and confirmation from both parties. Assembling that in advance removes most of the delay.
Establish whether the transfer is free. Some vendors charge an administrative fee or require the new owner to be on a current version. Both change the economics of the sale, and both are better known before a price is agreed.
Documenting the Transfer
The record you keep is what protects you if the vendor later queries the licence.
- Save the approval correspondence. Full message threads, not screenshots of one reply.
- Record the moment of reassignment. A short screen recording showing the licence leaving your account and appearing in the buyer's is the clearest possible evidence that the transfer completed.
- Note the licence identifiers before and after. Some vendors reissue a key on transfer, and a buyer who later has trouble will need both.
- Keep proof of your original purchase. Handing over a copy to the buyer is often required by the vendor, and keeping your own copy protects you if the chain is ever questioned.
Once the buyer has confirmed the licence works under their own account, keep this material for a while rather than discarding it. Licence disputes tend to surface at renewal, which can be months after the sale completes.
Frequently Asked Questions
Can I sell my Adobe or Microsoft 365 subscription? Generally no. Subscriptions bind to an account. Some older perpetual products have a documented transfer path.
What about JetBrains or similar developer tools? Policies vary and change. Check the current terms and ask support — many vendors permit transfer of perpetual fallback licences under conditions.
Do I need to deactivate before selling? Yes. It is the single most common cause of a failed handover, and it is entirely within your control.
Can I sell one seat from a five-seat licence? Almost never. Volume agreements are with an organisation and splitting them typically breaches the contract, which risks all five seats rather than one.
What if the vendor refuses the transfer after the sale? Refund the buyer. You sold something you could not deliver, and the deal chat will show what was promised. Establishing transferability first avoids this entirely.
