Clavem

License transfer

A license transfer moves the right to use licensed software from one device or one owner to another, so that the old device or owner stops using it and the new one can start.

Two kinds of transfer

Between devices is the common one. A customer buys a new laptop and wants to use the same license there. Nothing about ownership changes. A seat moves.

Between owners is rarer: a gift, a sale, a freelancer leaving a company, a company being acquired. The person named on the license changes. Most sellers handle this by hand and by policy, because a license may be personal or non-transferable under their terms.

A worked device transfer

A key has a limit of 3 and all three seats are used. The customer switches from an old laptop to a new one.

  1. Activation on the new laptop fails with This license key has reached the activation limit.
  2. They remove the old laptop, from its app or from a device page. Usage goes from 3 to 2.
  3. Activation on the new laptop succeeds. Usage is back at 3.

If the old laptop is dead, only the device page works, because the app on it cannot send anything.

Owner transfers with a flat key

Because the key is the credential, giving the key to someone else already works. That is the weakness. The license still shows the original buyer’s email, and anyone who kept a copy of the key can remove the new owner’s devices at the device page. For a proper owner transfer a seller can:

  1. Disable the old license. Disabled licenses do not count against the plan.
  2. Create a new license for the new owner with POST /v1/admin/licenses, giving email, name and, if needed, activation_limit and expires_at.
  3. Send the new owner their order link.

One catch applies to subscriptions. A license created by hand has no Stripe subscription behind it, so renewals never extend it. Set expires_at yourself, or ask the new owner to subscribe in their own name.

License transfer versus deactivation

Deactivation is the mechanism for a device transfer. It changes how many seats are free and nothing else. A transfer between owners changes who holds the license, and no deactivation call can do that.

How Clavem handles it

  • Device transfers: the app calls deactivate and then activate, or the buyer opens /licenses/manage, enters the key and removes the device. No account and no email round trip.
  • There is no ownership-transfer feature. Use the steps above through the dashboard or the management API.
  • Creating a license by hand counts against your plan’s active-license limit, and past it the call answers 402. Stripe purchases are never blocked. Disabling the old license first keeps the count level.
  • Imported licenses and hand-made ones are never changed by Stripe events.

Whether transfers are allowed at all belongs in your terms of sale. See how license transfers between computers work, device limits and the API reference.

Questions

Can a customer give their license to someone else?

That depends on the seller's terms. Technically, whoever holds the key can use it up to the device limit. A clean transfer gives the new owner their own key tied to their own email.

Does moving to a new computer use up a second seat?

Only if the old device is still registered. Free the old seat first and the count stays the same.