· AvaGuru · migration guides · 10 min read

Recurring Software Licenses on Telegram: Moving Beyond Lemon Squeezy

Preserve existing software buyers, plan the switch from Lemon Squeezy licensing, and sell new 30-day license subscriptions through Telegram Stars.

You can sell recurring software licenses in Telegram with AvaGuru: buyers approve a new 30-day Stars subscription, the first confirmed payment assigns a license key, and subsequent confirmed payments extend that same key. If you are replacing Lemon Squeezy, you can also import existing keys, their expiry dates and supported device records. Importing an old license does not move its payment agreement or make that key renew. The buyer’s new Stars subscription is a separate purchase and issues a new key.

That distinction matters more than the checkout screen. Your business needs to keep existing customers working, give them a clear reason to renew, and collect payment with their agreement. Your application also needs to ask the right licensing service whether a key is still valid.

We build AvaGuru. This article describes the implementation and migration workflow we reviewed on November 17, 2026. Automated tests cover licensing and subscription behavior; we have not yet verified a real Stars renewal pilot or published results from customer migrations. Treat the workflow below as a plan to test with your own software, not a promise of a disruption-free migration.

When does a Telegram license subscription make business sense?

This model fits software you control: a desktop utility, a plugin, or another application whose license checks you can update. It is especially useful when customers already use Telegram for your releases, community or support. They can purchase and manage their subscription in the same place they hear from you.

A recurring price needs a recurring promise. Explain whether buyers receive continued application access, ongoing updates, a maintained library, or support. Do not quietly turn a perpetual license into a subscription. Preserve the rights you sold, and offer a separate recurring product when the terms change.

AvaGuru’s Renewing license product requires a current paid merchant plan and the subscription feature to be available for your store. Buyers pay your store bot in Telegram Stars, which Telegram requires for digital goods sold inside bots and Mini Apps. AvaGuru charges for its software subscription and takes no percentage of each sale, but Telegram costs, withdrawal conditions, taxes and your operating expenses still matter. Refer to current plans and the Stars payment guide when budgeting.

This is not a Merchant of Record replacement. Moving from Lemon Squeezy to your own Telegram store changes who handles tax and other seller responsibilities. It also changes how customers pay. If keeping existing card billing is the priority, assess that separately before choosing Stars.

What actually moves from Lemon Squeezy?

A software sale has three separate parts: the license entitlement, the devices using it, and the permission to take the next payment. A successful import of one part does not prove the others have moved.

Part of the relationship What AvaGuru can carry over What still needs your attention
Existing license Original key string, supplied expiry, activation limit and supported status Export complete entitlement data; do not turn a time-limited license into a permanent one by omitting its expiry.
Activated devices Optional device records, preserving supported source instance IDs, up to 50 devices per key Check exported devices, identifiers and activation limits against representative installed clients.
Buyer identity A restored purchase linked to the buyer’s Telegram account after verification Send the restore link and explain email-code or license-key proof.
Future billing A newly authorized 30-day Stars subscription The buyer must opt in. Its first payment assigns a new key; it does not renew the imported one.
Application license checks AvaGuru’s public activation, validation and deactivation API Release and test a client or backend update that uses AvaGuru. Old clients still call their configured service.

Use the Lemon Squeezy migration guide for the orders export and Restore Buyers steps. Its basic two-column key export preserves key strings; for a licensing migration, also supply expiry, status, activation limits and the optional device file. Review the import preview before committing the import. More than 50 devices for a key, invalid or conflicting device identifiers, and invalid explicit activation limits must be corrected before import; do not assume unsupported records will be silently dropped.

An expiry date is not a billing schedule. An imported license remains subject to the expiry you supplied; AvaGuru does not charge the buyer or extend it simply because it came from a subscription product.

How do you keep existing customers working during the change?

Preserve their entitlement before asking them to subscribe

Start with a small, representative set of purchases: an unused key, an activated key, a key used on multiple devices, and a license close to expiry. Check the imported key, status, expiry and device records against the source. Include disabled or revoked records in your review so they do not accidentally become valid access.

Keep the old licensing dependency available while you test the replacement and release the application update. Ask buyers to restore their purchase through your store bot. Restore Buyers links the eligible purchase to their Telegram identity after they prove it with their purchase email or key; it does not ask them to buy their existing entitlement again.

Test the installed application, not just an API response

AvaGuru exposes license activation, validation and deactivation operations with a response shape intended to ease migration from Lemon Squeezy. That does not make every client a zero-code switch. Applications may check product or store identifiers, expect particular metadata, cache validation results, or store a device instance ID locally.

Test those assumptions with an already activated installation. Confirm that the correct edition opens, its existing device is recognized, a valid license remains usable and an expired or revoked license is rejected according to your application’s policy. Check a fresh installation as well. Preserving supported device IDs helps continuity, but does not remove the need to roll out an endpoint or client update.

The distinction also protects your promises: AvaGuru can manage licenses for your own integrated software. Importing a Steam code or another publisher’s key does not transfer that publisher’s activation system to AvaGuru. See the license-key sales guide for that inventory-and-delivery use case.

How do new license subscriptions and renewals work?

Create a digital product with Renewing license delivery, set the recurring price and add license keys to its pool. You do not need to connect a paid Telegram channel. Use a separate product when the new subscription has different terms from the original purchase.

The buyer opens the product in your Telegram Mini App and approves a recurring Stars invoice. After a confirmed first payment, AvaGuru assigns a key from the pool. The buyer can view it in My Orders and manage renewal in My Subscriptions.

On subsequent confirmed payments, AvaGuru extends the same subscription key. It does not consume another key from inventory for each renewal. Each distinct successful charge is still a real sale; a scheduled payment is not earned revenue until it succeeds.

For a migrating customer, this means two keys may exist during the transition: the imported key for their remaining old entitlement, and the new key for the new Stars subscription. Plan when they should switch in the application. Do not tell them that subscribing automatically upgrades or renews their old key.

What happens when a buyer cancels, misses a renewal or requests a refund?

Event Subscription and license outcome What to tell the buyer
Successful renewal Extends the existing subscription key for the confirmed paid period. Keep using the same key; no new activation code is issued for each renewal.
Buyer cancels Stops future renewal and preserves entitlement until the current paid period ends. There is no additional cancellation grace period. Cancellation does not immediately erase the time already paid for.
Active subscription reaches its end without a successful renewal Retains access for a 24-hour grace period, then expires if it has not renewed. The extra day is an access rule, not a guarantee that Telegram will collect payment.
A payment from that subscription is refunded Cancels future renewal and the current entitlement of that subscription, even if the refunded payment was from an older period. Check the effect on current access before refunding a historical charge.
Old imported license reaches its supplied expiry The old entitlement expires; importing it did not schedule any Stars renewal. A new subscription is a separate purchase with a new key.

These are server-side entitlement rules. Your software must use validation results appropriately; cached or offline access does not disappear from a device simply because a database record changes. Test your application’s enforcement and explain its behavior in your terms.

Lemon Squeezy also documents that cancellation of a subscription leaves its associated license valid until the end of the billing cycle. Preserve that remaining time in the migration instead of treating cancellation as immediate loss of access.

How should you tell buyers about the new billing arrangement?

Give each customer their actual dates and price. Coordinate cancellation of old billing with the start of new billing so they do not pay twice for the same period. Do not cancel an old subscription merely because an import succeeded.

Here is a template to adapt after you have tested the process:

We are moving [software name] to our Telegram store. Your existing license remains available through [date or original entitlement terms]. Restore your purchase at [store restore link] using your purchase email or license key; restoring it costs nothing.

If you choose the new subscription, it costs [price] Stars every 30 days and includes [specific benefits]. You must approve this payment in Telegram. The first payment gives you a new license key in My Orders; use it in [application instructions]. Later successful renewals extend that same new key.

Your old payment agreement does not move into Stars. [Explain the agreed old cancellation date and new start date.] You can manage the new renewal in My Subscriptions. If you prefer not to subscribe, [explain what remains available under the original purchase]. Contact [support] before subscribing if the dates would overlap.

Do not paste this unchanged into a mass announcement: the bracketed entitlement, billing and support details are the substance of the notice.

Is this the same as Lemon Squeezy’s Stripe migration?

No. Lemon Squeezy’s official migration page describes a Stripe path for eligible card subscriptions. It currently gives December 2, 2026 for migration tools and March 31, 2027 for stopping transactions. Check that page for updated dates and eligibility before making a plan.

That card migration and a move to Telegram Stars are different choices. Existing Lemon Squeezy payment authorization cannot be imported into an AvaGuru Stars subscription. Buyers must authorize Stars themselves. Licensing and product delivery also need their own migration plan even when a payment provider can move eligible card subscriptions.

Choose based on your customers and business model: preserving card billing may be more valuable than moving checkout into Telegram. For an audience comfortable buying in Telegram, the Stars route can bring software sales and renewal management into your existing community.

What should you verify before inviting every customer?

Test one complete path from restored entitlement to the application accepting it. Then test a new Stars subscription, its new key, cancellation, expiry and refund behavior with controlled accounts. Observe an actual renewal at Telegram’s 30-day interval before describing automatic renewal as proven in your live store.

Our November 17 review used automated API coverage for licensing and subscription lifecycles, plus a migration rollback check against a populated D1 database. These checks provide implementation evidence. They do not establish customer retention, a successful production migration, or a completed real Stars renewal. We have no customer results to quote here yet.

Before a broader move, your team should be able to answer four practical questions:

  • Can an already activated customer use the updated application with the imported entitlement?
  • Does a new subscriber receive the right key, and does the application enforce its entitlement?
  • Do customers understand which key to use and when the old billing stops?
  • Can support explain cancellation, missed renewals and refunds without guessing?

Start with the export and restore guide, then contact AvaGuru to discuss your software’s licensing assumptions and feature availability before scheduling the cutover.

Back to Blog

Related Posts

View All Posts »