Import Existing License Keys
Move license keys from Lemon Squeezy or another provider into Keymint. Each key stays exactly as it is, so your customers keep using the key they already have.
Overview
When you move to Keymint from another licensing or payment provider, import the keys your customers already hold. Each key is stored exactly as it is, so once your app checks keys with Keymint, existing customers keep using their key: no new key, no email.
This is built for stores leaving Lemon Squeezy, which stops processing payments on March 31, 2027 (see Moving off Lemon Squeezy), and works for any provider that can export keys.
Import a file
- Go to Licenses and select Import, or open a product and select Import on its License keys tab. You need permission to create licenses and customers.
- Choose the product the keys belong to. From a product page, the keys go into that product.
- Choose a CSV or JSON file. Download template gives you a CSV with the right columns and one example row to replace. Keymint checks every row before anything is imported and lists any problems with their row numbers.
- Select Import.
Files of more than 500 keys are imported in batches of 500. If a batch stops, fix the rows it lists and import the same file again: keys that are already imported are skipped.
File format
| Column | Required | Notes |
|---|---|---|
key (or license_key) | Yes | Kept exactly as written, including upper and lower case. 20 to 200 characters, with no spaces. |
email, name | No | Linked to the customer with that email in your workspace, or a new customer is created. |
activation_limit | No | Number of devices. Leave empty for unlimited. |
expires_at | No | ISO date. Leave empty for a perpetual key. |
status | No | active, inactive, expired or disabled. Disabled keys are imported disabled, and customers can't re-enable them. |
Lemon Squeezy files are recognised as they are: a CSV with Lemon Squeezy's column names (user_email, activation_limit, instances_count and so on) or the JSON response of its List all license keys API.
What to expect
- Activations start at zero. Device activations from your old provider can't be carried over, so each customer's app activates again through the Keymint SDK, within the same activation limit.
- No emails or webhooks. Customers aren't emailed their key (they already have it), and imports don't send
license.createdorcustomer.createdwebhooks. - Plan limits apply. Imported keys count toward your plan's license limit, and new customers toward its customer limit.
- A key can only exist once in Keymint. A key that's already in another product, or in another workspace, stops the batch and is listed so you can remove it.
- Same checks as generated keys. Imported keys are device-locked keys: they activate, validate and sign offline licenses exactly like keys Keymint generated.
After importing
Update your app to activate and validate keys with the Keymint SDK instead of your old provider's API, and ship that update to your customers before your old provider stops working.