Skip to main content
This is the step-by-step version of Migrate from Lemon Squeezy. It covers what moves through the API, what you set up in the dashboard, what can’t move yet, and how to move existing subscribers without charging them twice. Use it to run the migration yourself, or to check what your agent or the Creem CLI did. Lemon Squeezy stops processing payments, including subscription renewals, on March 31, 2027.

How the migration works

During the migration, your app works with both providers. New customers buy on Creem, and existing subscribers keep renewing on Lemon Squeezy until each one moves. At any time, each subscription has exactly one system responsible for its next renewal.
1

Set up Creem in test mode

Create your account and run the whole migration with test keys first.
2

Take stock of your Lemon Squeezy store

Read everything through the Lemon Squeezy API, read-only, and export your records.
3

Rebuild your catalog

Products, files, license key settings and discount codes.
4

Import customers

Create each customer with a stable ID of your own.
5

Move new sales to Creem

Checkout, webhooks, license checks and the customer portal, then go live.
6

Move existing subscribers

One subscriber at a time, around their Lemon Squeezy renewal date.
7

Finish and clean up

Reconcile, unpublish your Lemon Squeezy products and revoke the API key.

What moves

Not possible yet

1. Set up Creem in test mode

  1. Create your Creem account and store. Your account is reviewed before you can take live payments; see account reviews.
  2. Switch the dashboard to test mode and create a test API key (creem_test_…). Test requests go to https://test-api.creem.io.
  3. Run the whole migration in test mode first. Test and live mode don’t share data, so you repeat the import with a live key at the end. Stable external_id values make that second run safe.

2. Take stock of your Lemon Squeezy store

Create an API key in Lemon Squeezy under Settings → API. Treat it as full access: use it only to read, keep it in an environment variable rather than in code or a chat, and delete it when the migration is done. The Lemon Squeezy API follows JSON:API. Authenticate with Authorization: Bearer, request page[size]=100 and follow links.next until it’s empty:
inventory.ts
While you read, note what needs a decision:
  • Current prices. Lemon Squeezy keeps every price a variant ever had and doesn’t flag the current one. Take the newest price of the variant’s own category (subscription or one_time).
  • Subscribers on older prices. A Creem product has one current price, so plan a separate product for any older price you still honor.
  • Subscriptions with their status and renews_at date, especially the ones renewing before March 31, 2027.
  • Variants with license keys or files, and prices that are usage-based, tiered, use packages or carry a setup_fee.
  • Your store currency, if it isn’t USD or EUR.
Export your customers, orders and subscriptions as CSV for your records with Lemon Squeezy’s export guide.

3. Rebuild your catalog

Products

Create one Creem product per Lemon Squeezy variant with POST /v1/products. Put the variant ID in external_id, so a second run finds what the first one created.
The full field mapping is in the reference at the end of this page. Four things need care:
  • Re-runs. A second create with the same external_id answers 409 with the code external_id_taken. Treat it as “already created” and move on.
  • Descriptions. Lemon Squeezy stores descriptions as HTML; Creem’s checkout renders Markdown and doesn’t render HTML. Convert tag by tag: <p> to a paragraph, <br> to a line break, <h1>–<h6> to #–######, <strong>/<b> to **bold**, <em>/<i> to _italic_, <s>/<del> to ~~strike~~, <code> to backticks, <ul>/<ol>/<li> to - and 1. items (nested items indented), <a> to [text](url) and <blockquote> to >. Drop <img> and report it. Then turn three or more one-line paragraphs in a row, a list written one <p> per line, into a bullet list. Compare each description before and after.
  • Images. Creem stores the image URL and serves it through its image proxy; it doesn’t copy the file. Re-upload each image in the dashboard so it keeps working after Lemon Squeezy’s hosting goes away.
  • Tax category. Lemon Squeezy’s eservice has no exact match. It maps closest to digital-goods-service; confirm the category for each product.

Files and license keys

Set these up in the dashboard, product by product: upload each file under file downloads, and turn on license keys with the activation limit and expiry the variant had (license_activation_limit, license_length_value, license_length_unit). The API can’t attach files or license key settings to a product yet.

Discount codes

Create each code with POST /v1/discounts. The field mapping is in the reference. Mind these differences:
  • applies_to_products is required. A Lemon Squeezy code that applies to everything must list every Creem product, and products you create later aren’t covered.
  • Discounts can’t be edited through the API. To change one, delete it and create it again.
  • A code can exist only once. A second create with the same code fails with “The code has already been taken”, so check with search discounts before a re-run.
  • Lemon Squeezy’s start date and draft status have no equivalent. A repeating discount applies to subscriptions only.
  • Creem counts redemptions from zero. If the Lemon Squeezy code had a limit, set max_redemptions to what’s left.

4. Import customers

Create each customer with POST /v1/customers. Importing customers creates no orders and sends them no email.
  • external_id is your application’s own customer ID when you have one, or ls_customer_<id> otherwise. It’s how you find the customer again.
  • name is required. Lemon Squeezy allows customers without one; fall back to the part of the email before the @.
  • Country and marketing status have no field yet. Keep them in metadata.
  • Customers who later buy on Creem with the same email are matched to the customer you imported.
Creating a customer with an email that already exists in your store returns that customer and replaces its name and external_id. Look the email up first with GET /v1/customers?email= and decide whether to skip or update it.

5. Move new sales to Creem

Checkout

checkout.ts

Webhooks

Create an endpoint with POST /v1/webhooks or in the dashboard, and map your handlers to Creem’s events. The full mapping is in the reference. The common ones: Both providers sign the raw request body with HMAC-SHA256. Lemon Squeezy sends the hex digest in X-Signature; Creem sends it in creem-signature. Creem makes up to five delivery attempts for each event, so make your handlers idempotent on the event id.

License keys

Creem’s license endpoints need your API key, so call them from your backend, never from the app you ship. Lemon Squeezy’s License API needs no key, so apps often call it directly; route those calls through your server. During the migration, your app accepts both: Creem keys for purchases on Creem, Lemon Squeezy keys for customers who haven’t moved. Lemon Squeezy hasn’t said whether its License API keeps answering after March 31, 2027, so plan for it to stop.

Customer portal

Replace links to Lemon Squeezy’s customer portal with Creem’s customer portal. POST /v1/customers/billing returns a signed-in customer_portal_link for a customer; customers can also sign in with their email. If you sell usage-based plans, send each subscriber’s usage to Lemon Squeezy until they move, and to Creem usage-based billing from then on.

Go live

Once your account is approved, create a live API key, run the catalog and customer import again with it, and swap the links and API calls on your site. New customers now buy on Creem. Leave your Lemon Squeezy store running for the subscribers who haven’t moved yet.

6. Move existing subscribers

Creem can’t import an active subscription or a saved card yet: each subscriber starts their Creem subscription with one checkout. A direct import that keeps the paid period is in development.
Move subscribers one at a time, close to each one’s Lemon Squeezy renewal date (renews_at), so nobody pays twice for the same period.
1

Create a checkout for the subscriber

Use the product that matches their plan, the customer you imported, and the Lemon Squeezy IDs in metadata. Add a discount_code if you offer one, for example to cover days they already paid for.
2

Send them the link

Creem doesn’t send migration emails, so send your own: that Lemon Squeezy is shutting down, that Creem is now the seller on their statement and invoices, the link, and the date their Lemon Squeezy subscription would renew.
3

Cancel on Lemon Squeezy only after Creem is active

Creem copies the checkout’s metadata to the subscription. When subscription.active arrives with your ls_subscription_id in it, cancel that subscription with the Lemon Squeezy API (DELETE /v1/subscriptions/{id}). It stays active until its paid period ends and doesn’t renew. Never cancel on Lemon Squeezy first.
4

Track who has moved

Store the Lemon Squeezy and Creem subscription IDs side by side in your database and remind the subscribers who haven’t moved. Anyone still on Lemon Squeezy on March 31, 2027 stops renewing there.
Before you cancel real subscriptions, test a cancellation in Lemon Squeezy’s test mode: check whether Lemon Squeezy emails the customer, and make sure your own subscription_cancelled handler doesn’t revoke access for a subscriber who just moved.

7. Finish and clean up

  • Reconcile. Compare products, discount codes, customers and subscriptions in both systems, and confirm that each subscription renews in exactly one place.
  • Unpublish your Lemon Squeezy products in the Lemon Squeezy dashboard so nobody buys there; the Lemon Squeezy API can’t change products.
  • Re-upload product images in the Creem dashboard if you haven’t yet.
  • Keep your Lemon Squeezy webhook handlers until the last Lemon Squeezy subscription has ended, then remove the Lemon Squeezy code paths.
  • Delete your Lemon Squeezy API key.

Migrate with a coding agent

A coding agent can do most of this work. The prompt below asks it to plan first and to follow the rules on this page. Review its plan before it changes anything, and never paste API keys into the conversation.

Use the Creem CLI

For the catalog alone, the Creem CLI copies products and discount codes in one command. See With the Creem CLI for the commands and the fields to fix after a run. Prefer help? Email support@creem.io and our team can run the migration with you.

Reference

API basics

Objects

Products and variants

Discount codes

Customers

Subscription statuses

Creem’s expired status isn’t Lemon Squeezy’s: it means the period ended without a successful payment while retries can still succeed. canceled is final.

Webhook events

Checkout fields