Commerce migration

Gumroad → Lemon Squeezy

Move Gumroad digital products, files, buyers, subscribers, memberships, licenses, discounts, posts, receipts, analytics, tax records, and integrations into Lemon Squeezy with an explicit re-subscription and entitlement plan.

Typical timeline15–35 business days65–125 hours active work

Statusneeds review

Source testedGumroad documentation reviewed 2026-07-19

Destination testedLemon Squeezy documentation reviewed 2026-07-19

Last reviewed2026-07-19

Sources3

Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Gumroad

Reasons to stay

Creators can launch simple digital products with very little setup
Checkout, subscriptions, tax, and customer records are consolidated

Reasons to leave

Branding, checkout control, reporting, and advanced subscription logic are limited
Billing state and compliance responsibilities make switching unusually sensitive

New platform

Lemon Squeezy

What gets better

Merchant-of-record handling simplifies global tax and digital-product sales
Checkout, subscriptions, tax, and customer records are consolidated

What gets worse

Platform eligibility, payout control, and customization are more constrained than direct billing
Billing state and compliance responsibilities make switching unusually sensitive

Best of the move

Lemon Squeezy: Merchant-of-record handling simplifies global tax and digital-product sales. This removes a major source-side concern: Branding, checkout control, reporting, and advanced subscription logic are limited.

Worst of the move

What you lose: Creators can launch simple digital products with very little setup. What you inherit: Platform eligibility, payout control, and customization are more constrained than direct billing.

01At a glance

Know the shape of the move.

Transfer outcome12 features audited

Clean0

Partial8

Manual2

Lost2

Mapping route9 of 9 fields have a destination path

SourceGumroad9 mapped fields

Automatic0

Transform7

Manual2

Unsupported0

DestinationLemon Squeezy9 supported paths

This timeline assumes

Up to 100 products, 100,000 sales, 25,000 subscribers, and 100 GB of delivery files
Store, finance, support, fulfillment, SEO, and engineering owners approve the destination operating model.
The source remains available through at least one full refund, fulfillment, payout, and renewal cycle.
A complete test catalog and buyer cohort run before production data.
The migration team records evidence for every blocking verification check.

02Loss matrix

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

Item	Outcome	Impact	What happens	Mitigation
Products, files, pages, and delivery	manual	critical	There is no documented first-party Gumroad store importer in Lemon Squeezy.	Rebuild each product and verify every file and buyer delivery path.
Historical sales and customer access	partial	critical	Gumroad sales CSV is evidence, not destination-native orders and customer libraries.	Create a durable entitlement ledger and support path for prior buyers.
Active memberships and payment methods	lost	critical	Gumroad billing credentials cannot be self-imported as Lemon Squeezy subscriptions.	Use an approved customer re-subscription campaign and prevent overlap.
Ratings, affiliates, posts, workflows, and analytics	lost	high	Gumroad-native growth and engagement objects do not transfer.	Archive required evidence and rebuild only current operations.
Products and variants	partial	critical	Core catalog data can move while option, bundle, custom-field, and digital-product models differ.	Reconcile every product and variant against an approved catalog map.
Images, files, and digital delivery	partial	critical	Exports may contain URLs rather than durable binaries or customer entitlements.	Copy originals, compare hashes, and test delivery as a buyer.
Customers and accounts	partial	critical	Profiles can move while passwords, account identity, consent, addresses, and tax details vary.	Use secure activation and never promise password transfer.
Orders, refunds, and transaction history	partial	critical	Historical orders may import without becoming editable payment transactions.	Preserve source IDs and reconcile gross, tax, discount, refund, and net totals.
Active subscriptions and payment methods	partial	critical	Recurring billing ownership requires provider cooperation or customer reauthorization.	Choose a documented takeover or managed re-subscription path and prevent double billing.
Discounts, coupons, and gift balances	partial	high	Eligibility, stacking, expiry, redemption, and stored balances use different models.	Map active rules and test boundary conditions.
Taxes, invoices, and merchant records	manual	critical	Merchant-of-record, registration, calculation, invoice, and filing responsibilities can change.	Obtain finance and legal approval before accepting destination sales.
Shipping, inventory, and fulfillment	partial	critical	Locations, stock states, backorders, rates, carriers, and fulfillment workflows differ.	Freeze stock movement briefly and reconcile every location.

03Field and feature mapping

Where each thing goes.

Source	Destination	Method	Notes
Gumroad product	Lemon Squeezy product	transform	Preserve source ID, title, status, and URL.
Variant, option, or tier	Destination variant, option, or plan	transform	Map cardinality and price explicitly.
Image, file, or media	Destination media or delivery asset	transform	Copy and compare hashes.
Customer	Destination customer	transform	Preserve identity, consent, and source ID.
Order or sale	Destination historical order or ledger record	transform	Preserve amounts, currency, tax, discount, and status.
Subscription or membership	Destination subscription or entitlement	manual	Use supported billing transfer or customer reauthorization.
Coupon or discount	Destination discount	transform	Map eligibility, expiry, limits, and redemption.
Inventory location and quantity	Destination location and inventory	transform	Freeze and reconcile at cutover.
Public route	Destination route and redirect	manual	Preserve or redirect every indexed URL.

04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Gumroad data, configuration, and operating evidence before any destination write.

Export Gumroad products, variants, assets, customers, orders, subscriptions, discounts, inventory, taxes, payouts, and settings.
Crawl storefront routes, metadata, checkout, account, fulfillment, support, and integration behavior.
Record counts and signed financial totals by status, currency, tax, discount, refund, location, and billing state.
Hash exports and downloadable assets.

Proof to capture: A signed manifest reconciles every scoped record class, runtime dependency, export file, count, and hash.

Transformation · Official exports, ETL workbook, and schema validator

Catalog, customer, and order map

Preserve identity, commercial meaning, and financial totals.

Inventory source values and exceptions.
Define explicit destination mappings.
Reject unmapped critical records.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Staging store, crawler, test payments, and reconciliation scripts

Storefront and operating cutover

Rebuild customer journeys, fulfillment, billing, URLs, and integrations.

Normalize encoding, dates, identifiers, and blanks.
Run a representative pilot.
Reconcile accepted, rejected, and transformed rows.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Cutover

Orders or inventory change during the final copy

criticalpossible likelihood

Customers buy, refund, or fulfill while destination data is loading.

Consequence: Stock and financial ledgers diverge.
Mitigation: Freeze affected writers and apply a reconciled final delta.

Stop if: Any unexplained post-freeze commercial event exists.

Billing

Both stores sell or renew

criticalpossible likelihood

Old checkout, subscriptions, or automations remain active.

Consequence: Customers are double charged or receive conflicting fulfillment.
Mitigation: Move one production owner at a time and monitor test buyers.

Stop if: Any buyer can complete duplicate production actions.

Launch

Routes work but checkout fails

criticalpossible likelihood

Storefront pages render while tax, shipping, payment, delivery, or account paths fail.

Consequence: Revenue and customer trust are lost.
Mitigation: Run end-to-end orders for every critical market and product type.

Stop if: A blocking buyer journey fails.

06Precise timeline

Do the work in this order.

Estimate forUp to 100 products, 100,000 sales, 25,000 subscribers, and 100 GB of delivery files

Total elapsed15–35 business days

Active work65–125 hours

BufferAdd time for memberships, license keys, large files, many product versions, affiliates, or historical tax evidence.

Days 1–3Inventory and decisions2–3 days

Days 3–5Backup and reconcile1–3 days

Days 5–12Map and pilot3–8 days

Days 10–20Final delta and switch1–5 days

Days 12–40Observe and close3–10 days

1
Days 1–3 · inventory
Inventory and decisions
6–12 hours active2–3 days elapsedOwner review waiting
- Inventory Gumroad data, features, users, domains, and integrations.
- Approve scope, owners, mappings, and exclusions.
Depends on: Gumroad and Lemon Squeezy administrator access
Stop / go checkpoint
Export?
Go when: Every critical item has an owner and disposition.
Stop when: Consent, billing, access, or system ownership is unclear.
2
Days 3–5 · backup
Backup and reconcile
5–10 hours active1–3 days elapsedExport processing waiting
- Create immutable exports and configuration evidence.
- Reconcile counts, totals, and hashes.
Depends on: Approved inventory
Stop / go checkpoint
Transform?
Go when: Source totals and export manifests agree.
Stop when: Any critical dataset or configuration is absent.
3
Days 5–12 · pilot
Map and pilot
10–35 hours active3–8 days elapsedDestination processing and review waiting
- Configure Lemon Squeezy and transform representative data.
- Run a pilot containing normal records and every critical edge case.
Depends on: Verified backup
Stop / go checkpoint
Scale?
Go when: Pilot mappings, behavior, access, and evidence pass.
Stop when: Any critical check fails or produces unexplained variance.
4
Days 10–20 · cutover
Final delta and switch
5–25 hours active1–5 days elapsedDNS, import, or sync propagation waiting
- Freeze production writes in Gumroad.
- Apply the final delta, switch ownership, and run blocking checks.
Depends on: Passed pilot and approved rollback
Stop / go checkpoint
Open production?
Go when: Counts reconcile and one destination system owns production.
Stop when: A source writer remains active or a blocking check fails.
5
Days 12–40 · observe
Observe and close
3–18 hours active3–10 days elapsedOperating-cycle evidence waiting
- Monitor one complete operating cycle.
- Sign the verification report and close rollback only after stability.
Depends on: Verified cutover
Stop / go checkpoint
Close rollback?
Go when: No trigger occurs during the agreed observation period.
Stop when: Data, access, delivery, routing, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Lemon Squeezy the only production system without losing the final Gumroad delta.

Recommended window: A low-volume weekday morning with platform, data, DNS, and business owners available.

Freeze production writes and scheduled actions in Gumroad.
Export, transform, and reconcile the final delta.
Apply the approved delta to Lemon Squeezy.
Switch domains, forms, integrations, sending, or sync ownership as applicable.
Run every blocking verification check and keep the source intact.

Proof to capture: Lemon Squeezy owns production, totals reconcile, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Gumroad without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, or billing are changed.

Stop new writes and scheduled actions in Lemon Squeezy.
Restore the prior Gumroad routing, forms, integrations, sending, or sync ownership.
Export the Lemon Squeezy post-cutover delta.
Review and apply safe destination-era changes to Gumroad.
Run the same blocking checks against the restored source.

Proof to capture: Gumroad again owns production with current data and no duplicate destination action.

Rollback immediately when

Unexplained critical count or value variance
Missing or exposed critical data
Duplicate production action
Failed access, routing, delivery, or integration check
A critical feature has no safe destination replacement

08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

ID	Check	Method	Expected result	Evidence
`V-01`Blocking	Product and variant reconciliation	Compare counts, fields, media, prices, status, and inventory.	Every scoped catalog object is accounted for.	Catalog ledger.
`V-02`Blocking	Identity and account activation	Compare profiles and exercise secure account access.	Approved customers can access only their data.	Customer report.
`V-03`Blocking	Commercial and financial history	Reconcile counts and signed totals by status, currency, tax, discount, and refund.	Every order and amount is accounted for.	Order ledger.
`V-04`Blocking	Subscriptions and entitlements	Test every lifecycle state through renewal or reauthorization.	One correct charge and entitlement owner.	Subscription report.
`V-05`Blocking	Location and fulfillment parity	Place, fulfill, cancel, return, and refund test orders.	Stock and fulfillment outcomes reconcile.	Fulfillment evidence.
`V-06`Blocking	Buyer journeys	Complete every product, payment, tax, shipping, and market path.	One valid order, receipt, delivery, and account result.	Test-order matrix.
`V-07`Blocking	Storefront and SEO	Crawl old and new routes, metadata, canonicals, and redirects.	Every indexed route resolves correctly.	Route diff.
`V-08`Blocking	Single store authority	Inspect checkout, inventory, subscriptions, integrations, and support.	Lemon Squeezy alone accepts production orders.	Cutover checklist.

09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check.

Create final Gumroad exports and archive verification evidence.
Revoke temporary credentials, API keys, webhooks, and elevated roles.
Remove obsolete embeds, forms, jobs, integrations, and DNS records.
Keep the source intact through the approved retention window.
Cancel paid plans only after billing, legal, and recovery review.
Schedule the next Lemon Squeezy backup, access, and migration-playbook review.

Sources and maintenance

Built to be reviewed.

Tested 2026-07-19. Next scheduled review: 2026-10-19.

Gumroad: export sales CSVAccessed 2026-07-19
Lemon Squeezy: import subscribersAccessed 2026-07-19
Gumroad: account deletion and backupsAccessed 2026-07-19

Know the shape of the move.

This timeline assumes

What survives the move.

Where each thing goes.

Make the move recoverable.

Create the source-of-truth backup

Catalog, customer, and order map

Storefront and operating cutover

The things most likely to hurt.

Orders or inventory change during the final copy

Both stores sell or renew

Routes work but checkout fails

Do the work in this order.

Inventory and decisions

Export?

Backup and reconcile

Transform?

Map and pilot

Scale?

Final delta and switch

Open production?

Observe and close

Close rollback?

Cut over with a way back.

Cutover

Rollback

Prove the migration worked.

Remove the scaffolding safely.

Built to be reviewed.