What the importer reads
Open Import in the Clavem dashboard and choose Dodo Payments. Pick live or test mode and paste an API key with read access to license keys, customers and products. A key that starts with dodo_test_ is sent to Dodo’s test host and dodo_live_ to its live host, and the key is used for that run only and never stored. You map each Dodo product to a Clavem product, or let Clavem create one with the same name. Pages of 100 are read in turn, and a stopped run resumes where it ended.
| Dodo | Clavem | Note |
|---|---|---|
key |
key |
Kept as written. Longer than 256 characters is refused. |
customer email, name |
email, name |
Looked up per key. |
status active |
active or inactive |
Active once a device is on it, otherwise inactive. Both are valid. |
status expired or disabled |
same | |
activations_limit missing |
-1, unlimited |
|
activations_limit 0 |
the Clavem product’s limit | Dodo does not document a meaning for zero, so it is not turned into a lock. |
expires_at |
expires_at |
|
created_at |
created_at |
|
instance id (lki_…), name, created_at |
device instance_id, name, date |
A missing name becomes “Imported device”. |
Dodo’s ids are strings, while the License API’s meta ids are numbers, so no Dodo ids are carried into meta. Clavem answers with its own numbers there. If your app compares a product id, change it to Clavem’s meta.product_id.
Read this before you start
The importer calls GET /license_keys. As of November 2026 Dodo’s reference marks that endpoint deprecated, saying “This endpoint will be removed in a future release”, and tells you to use List Customer Grants with integration_type=license_key, where each grant carries a license_key object with the key, status, expiry, activations used and activations limit. Dodo manages keys through its Entitlements system now.
So do three things. Import soon, while the endpoint answers. Keep a copy of what you import. If the endpoint is gone when you try, build a CSV or JSON from the grants list with the columns in Import existing licenses and use the file import.
Import one product, look at the first page of the result, and compare a handful of keys with the Dodo dashboard before you run the rest.
Step by step
- Create an API key in Dodo with read access to license keys, customers and products. Keep it out of any app.
- In Clavem, open Import, choose Dodo Payments, pick the mode and paste the key.
- Map products. Create them in Clavem first if you want your own names and device limits.
- Run it. Keys already in your account are never overwritten and only gain devices they lacked, so a repeat run is safe. Expired and disabled keys do not count against your plan, and a page that would pass your plan limit is refused whole before anything is written.
- Validate a key and an instance id by hand:
curl https://clavem.io/v1/licenses/validate \
-d license_key=PRO-AAAA-BBBB-CCCC-DDDD \
-d instance_id=lki_abc123
An imported device answers valid: true. A device that was not imported answers 404 with instance_id not found., and your app should activate again instead of failing.
Change the app
Dodo’s license endpoints need no secret and are called by the app, as Clavem’s are. The names differ:
| Dodo | Clavem |
|---|---|
POST /licenses/activate with license_key, name |
POST /v1/licenses/activate with license_key, instance_name |
activation response id (lki_…) |
instance.id |
POST /licenses/validate with license_key, license_key_instance_id |
POST /v1/licenses/validate with license_key, instance_id |
POST /licenses/deactivate with license_key, license_key_instance_id |
POST /v1/licenses/deactivate with license_key, instance_id |
// Before: Dodo
await fetch('https://live.dodopayments.com/licenses/validate', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ license_key: key, license_key_instance_id: instanceId }),
});
// After: Clavem
const res = await fetch('https://clavem.io/v1/licenses/validate', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ license_key: key, instance_id: instanceId }),
});
const data = await res.json();
if (!data.valid) lock(data.error);
Dodo’s validate answers valid: true when the key is active and not expired, and so does Clavem. Branch on valid and the HTTP status, not on the error text.
Subscriptions
In Dodo, a subscription key has no expiry, and its validity follows the subscription: Dodo’s table says keys are disabled when a subscription is cancelled, expired, paused or on hold, and that a plan change disables the old keys and issues new ones. Keys imported into Clavem carry none of that logic. An imported key has no Stripe subscription, so Stripe events never change it, and with no expires_at it never expires. Before you move subscribers, give each subscription key an expiry such as the end of the paid period, and move it with PATCH /v1/admin/licenses/:id as people renew. Or let them subscribe again through Stripe and issue a new key.
Dodo is a merchant of record, so it holds the saved payment methods. Its documentation index lists no guide for moving subscribers to another provider, so ask Dodo support what it can do for you. Leaving a merchant of record also moves tax collection onto you. This is general information, not advice; ask an accountant before you switch.
Connect Stripe as described in Connecting Stripe and map each Stripe product to a Clavem product before you send new buyers there.
Rollback
Import reads from Dodo and writes to Clavem only. Dodo’s guide documents the way back as well: keys can be imported into Dodo with its Create License Key API, which keeps the same key strings, and an existing string answers 409. Keep the License API host in your app as a setting so one release can switch it, and export your keys from Clavem’s Licenses screen as CSV if you need them elsewhere.
Questions
How do I check a Dodo import before running it in full?
Import one product first, look at the preview of the first page of results, and compare a handful of keys with the Dodo dashboard before importing everything.
What happens when Dodo removes the license keys list?
Dodo's reference marks GET /license_keys as deprecated and says it will be removed in a future release, and points to List Customer Grants with integration_type license_key. Clavem's file import takes over from an export built from that.
Do imported subscription keys follow the subscription?
No. In Dodo, subscription keys have no expiry and are disabled when the subscription is cancelled, paused or on hold. An imported key has no Stripe subscription, so it never expires unless you give it an expiry date.
Sources
- Dodo Payments, license keys feature guide (checked November 2026)
- Dodo Payments API, list license keys, marked deprecated (checked November 2026)
- Dodo Payments API, list license key instances (checked November 2026)
- Dodo Payments API, list customer grants (checked November 2026)
- Dodo Payments documentation index (checked November 2026)