Skip to main content
Kelviq imports your Lemon Squeezy store for you. Your products, plans, customers, order history, discount codes, files, and license keys arrive in your Kelviq organization. Your plans are published and your discount codes work at checkout, so they are ready to sell as soon as the import finishes. A report is emailed to you at the end.
Import by January 31, 2027 and you pay 2.9% + 40¢ on your first $50,000 in sales. See the special offer.

Four ways to move

Each one runs the same import on Kelviq’s servers and ends with the same report in your inbox. Run it yourself, or have our team do it.

CLI

One command in your terminal.

AI agent

One sentence to your coding agent.

API

One POST request from your backend.

Done for you, by a dedicated person on our team

One person at Kelviq runs the import, checks it against your Lemon Squeezy store with you, and stays your contact until the move is done.
Whichever you pick, start with a dry run: the whole import is rehearsed, nothing is saved, and the report shows what a real run would do. The rest of this guide covers what the import brings over, how to run it, and how to move your app.

Special offer

Lemon Squeezy charged 5% + 50¢ per transaction. Move your store to Kelviq and you pay 2.9% + 40¢ on your first $50,000 in sales. On that volume you keep over $1,000 more. Other organizations get this rate on their first $5,000.
  • Nothing to claim. The import is the proof. We apply the rate to your organization once your production import finishes, and confirm it by email.
  • A dry run is free. It rehearses the whole import, saves nothing, and does not start the six months. Neither does a sandbox import.
  • Lemon Squeezy keeps running. The import does not change your store there and does not email your customers. You switch your checkout when you are ready.
  • Kelviq can run it for you. A dedicated person on our team does the import with you, at no charge.
Start with a dry run.

Where your existing customers stand

The move happens on two tracks, and you can start the first one today. Your customers are not emailed during the import, and no webhooks fire for imported records. Nothing changes for a buyer until you change your app. To keep those subscribers paying after March 31, 2027, do one of two things: have Kelviq move them (write to hi@kelviq.com), or have them subscribe again on Kelviq before their last Lemon Squeezy renewal.
To move active subscriptions and saved cards so that renewals continue on Kelviq, write to hi@kelviq.com before you choose a destination in Lemon Squeezy’s migration form. Lemon Squeezy only lets subscriptions paid by card move to another provider.

Key dates

These dates are Lemon Squeezy’s published schedule, plus the last day to qualify for Kelviq’s special offer.

What the import brings over

The import runs as eight steps, in this order. You can run all of them or pick a subset. Later steps build on earlier ones: orders needs products, and renewals and licenses need orders. A license key is imported only if its order was. Not part of the import: affiliate programs, email subscriber lists, and storefront pages.

Before you start

You need four things. If our team runs the import for you, you only need the first and the third.
  1. A Kelviq organization. Create one at app.kelviq.com. The person who creates it is its owner.
  2. A Kelviq Server API Key created by the organization owner. Create it under Settings → API keys while signed in as the owner. A server key created by another team member, a Client API Key, or a dashboard session is refused with 403. Sandbox and production each have their own keys.
  3. A Lemon Squeezy API key. Create one in your Lemon Squeezy dashboard under Settings → API.
  4. Your Lemon Squeezy store id. It is the number shown next to your store under Settings → Stores. One store is imported per run. A single Lemon Squeezy API key can reach several stores, so repeat the run with each store’s id.
Both keys are secrets. Keep them in an env file or your shell, never in source control or a chat window.

The path, start to finish

Kelviq keeps sandbox and production separate. Each has its own data and its own keys, and nothing imported into one appears in the other. A dry run previews only the environment it ran in. The import goes into sandbox unless you choose production, so rehearse the whole move in sandbox, then repeat it in production.

In sandbox

  1. Do a dry run. Nothing is saved.
  2. Read the report that is emailed to you.
  3. Run the real import. It publishes your plans and switches on your discount codes.
  4. Review your plans and discount codes.
  5. Add Kelviq to your app with sandbox keys.
  6. Test payments end to end.

In production

  1. Complete the business review.
  2. Store a production key with kelviq login --prod.
  3. Do a dry run with --prod and read its report.
  4. Run the real import with --prod. Your plans are live as soon as it finishes.
  5. Review your plans and discount codes.
  6. Register your webhook endpoint with --prod.
  7. Switch your app to production keys. See Prepare for production.
Sales keep arriving on Lemon Squeezy while you switch. Run the import again to bring them in.

Run the import

Start with a dry run. It goes through the whole import, saves nothing, and emails you a report of what a real run would do. The examples below import into sandbox.
Install the Kelviq CLI and store your Kelviq key with kelviq login. To import into production, store a production key as well with kelviq login --prod.The command needs your Lemon Squeezy API key. Give it either way:
  • From an env file. The command reads LEMONSQUEEZY_API_KEY from .env.local or .env in the folder you run it from. Many apps already have it there.
  • At the prompt. Run the command without the variable set and paste the key when asked. The input is masked.
Kelviq uses the key for this import only. It is never returned in a response or included in the report email.Preview the import:
When the report looks right, run it for real. The command shows what it is about to do and asks before it starts:
Add --prod to either command to import into production. The Lemon Squeezy key is never taken as a flag and never printed. See the command reference for every option.
The import runs in the background and can take from a few seconds to more than an hour for a large store. There is no progress to check; the report email tells you when it is done.

Choose what to import


Have Kelviq run it for you

If you would rather not run anything yourself, a dedicated person on the Kelviq team does the migration with you. You deal with the same person from your first email to the final check.
  1. Create your Kelviq organization at app.kelviq.com.
  2. Create a Lemon Squeezy API key just for the move. In your Lemon Squeezy dashboard, go to Settings → API and create a new key. Do not reuse the key your app runs on.
  3. Share the key and your store id with us at hi@kelviq.com, from the email address on your Kelviq account.
  4. Your migration contact does the rest. They do a dry run and send you the report. Once you approve it, they run the import, then check your plans, discount codes and license keys against your Lemon Squeezy store with you.
  5. Delete the key in Lemon Squeezy as soon as we confirm the import is finished, so it only lives as long as the move does.
Adding Kelviq checkout and webhooks to your app is still a change in your code. The same person helps you through those steps too.

Read the report

One email arrives when the import ends, whether it succeeded or stopped. A dry run adds “(dry run, nothing saved)” to the subject. The report contains:
  • the store and the organization it went into
  • a count for each record type, for example “Orders: 1,204 created, 3 skipped”
  • the totals charged, tax and refunds from Lemon Squeezy, to compare with Kelviq’s gross volume
  • up to 50 warnings for anything that was skipped or imported differently
  • the start time, the duration and the steps that ran

After the import

1. Review your plans and discount codes

The import publishes each plan, so it can be bought as soon as your app points at it, and your discount codes work at checkout. Open Product Catalog → Products in the dashboard and check each plan’s price and settings against its variant in Lemon Squeezy. kelviq status lists every plan with its price and entitlement counts. Then read the report’s warnings. Two cases need you:
  • A plan that could not be published stays a draft and is named in the report. Publish it in the dashboard.
  • A discount code limited to plans that are not published stays switched off. Publish those plans, then run the import again to switch the code on.
To review everything before it can be bought, import with --no-publish-plans and --no-publish-discounts (publishPlan: false and publishDiscount: false in the API). When you are ready, run the import again without them: it publishes the plans it left as drafts and switches on the codes.

2. Add the Kelviq equivalent of each Lemon Squeezy call

Existing subscribers still use the Lemon Squeezy calls in your app, so add the Kelviq ones beside them. Copies of your app that are already installed keep calling Lemon Squeezy’s license API until your users update. Ship the license change well before March 31, 2027. Creating a checkout and verifying a webhook look like this in Node. body is the raw request body, and client is your Kelviq client.
Webhook events map as follows. Register your endpoint and write its signing secret into your env file in one command. List every event your handler uses:

3. Keep the Lemon Squeezy path running

Existing subscribers still renew on Lemon Squeezy. Keep your Lemon Squeezy webhook handler, its signing secret, and the Lemon Squeezy portal link those subscribers use. Record which platform each subscription bills on, so that portal and cancel actions go to the right one. Remove the Lemon Squeezy path only when no subscription is billing there any more.

4. Test before you go live

Run a purchase end to end in sandbox with the cards in Test payments, and confirm your app grants access from the Kelviq webhook.

5. Run the import again to catch up

Sales and refunds keep happening on Lemon Squeezy while you switch. Run the full import again; it only adds what is new, including license keys issued since. Records that were already imported are skipped, and refunds made since the last run are picked up. If you imported with --no-publish-plans or --no-publish-discounts and want to keep reviewing, pass them again. Without them, the catch-up run publishes the plans and switches on the codes.
If you sell no license keys, --only orders,renewals is quicker:

Common questions

A 400 with Lemon Squeezy rejected the API key or the store id. or Lemon Squeezy store 12345 was not found for this API key. means the Lemon Squeezy key or the store id is wrong. Check both. To list the store ids your key can reach, run this in a shell where LEMONSQUEEZY_API_KEY is set:
Only one import runs per organization at a time, and a second request is refused with 409. Wait for the report from the first.
Large stores can take over an hour, so allow time first. No report is sent in two cases:
  • You started a second import while one was running. Only the first one reports.
  • The import could not start within 24 hours.
After 24 hours, run the import again. If that returns 409 and still no report arrives, contact hi@kelviq.com with the taskId from the response. Support can clear a run that stopped.
Codes work at checkout as soon as the import finishes, with two exceptions: a code limited to plans that are not published, and every code if you imported with --no-publish-discounts. The report names each code that is waiting on a plan. Publish the plans it is limited to, then run the import again; it switches on the codes that are still off.
Read the detail in the response.
Yes, imported sales are added to revenue analytics. Pass --skip-analytics (skipAnalytics in the API) to leave them out.