Before leaving Gumroad, map every file, licence and customer promise
Create a migration inventory so essential products, permissions and fulfilment details do not disappear between platforms.

You have decided to leave Gumroad. The tempting part is copying each product into a new shop and changing the link in your bio. The risky part is everything around the product: which file a buyer received, what they were promised, who can access it, and what should happen when a payment fails. Before you move anything, create an inventory that another person could use to rebuild the customer experience without guessing.
Start with an offer register
Make one row for every thing a customer can buy or receive. That includes a paid download, a bundle, a free bonus attached to a product, a course, a membership, a coaching session and an active pre-order. Do not group items merely because they share a folder. A bundle may contain files with different licences, update schedules or access rules.
| Field to record | What to write down |
|---|---|
| Offer identity | Product name, old URL, internal name and whether it is active, paused or retired |
| Promise | The exact outcome, contents, format, update wording and refund wording shown at purchase |
| Delivery | Download, email, course lesson, community, call booking or manual fulfilment |
| Access | One-time access, time-limited access, recurring access, buyer-only or public |
| Current state | File version, last update date, known defects and the replacement product |
| People affected | Customers, subscribers, affiliates, collaborators and anyone waiting for delivery |
Use the customer-facing wording, not just your own description. A line such as “future updates included” creates a continuing obligation even if you no longer want to maintain the product. Put unclear promises in a review column rather than quietly removing them during the move.
Map every file and its right to use
Next, inspect the files behind each offer. Create a folder or spreadsheet entry for the master file, exported file, cover image, sales images, captions, transcripts, source assets, licence documents and any instructions the buyer needs. Open the actual download, not only the file sitting in your working folder. This catches an old PDF, missing bonus or broken link before customers find it.
- 1Give each file a stable name and record its format, size, version and checksum or other internal identifier.
- 2Write the source of every third-party asset, including fonts, photographs, music, templates, code and datasets.
- 3Record whether the buyer may use the item personally, commercially, for clients, for a team or for resale.
- 4List restrictions on editing, sharing, sublicensing, attribution and use in artificial intelligence tools where your licence contains them.
- 5Match each file to the product, bundle or lesson where it is delivered, then note whether older buyers should receive the replacement.
This is also where you separate your rights from your customers’ rights. Owning a copy of a photograph does not necessarily give you permission to include it in a template that buyers can redistribute. If a licence is missing, pause that part of the migration until you can verify it. A clean storefront cannot repair an unclear chain of permission.
Record fulfilment, access and support
A buyer experiences a sequence, not a product record: payment, confirmation, access, download, reminder, update and support. Write that sequence down for each offer. Note every automatic email, redirect, hidden page, coupon, onboarding message and manual step. If a customer previously received a download link by email, moving the file alone does not recreate the fulfilment.
| Checkpoint | Migration question |
|---|---|
| Payment | Which currency, tax setting, payment method and receipt wording applied? |
| Confirmation | What did the buyer receive immediately, and where did the link lead? |
| Access | Could the buyer download, stream, revisit or cancel, and for how long? |
| Updates | How were new versions announced and delivered to earlier buyers? |
| Support | What address, response promise, troubleshooting steps or replacement policy applied? |
| Exceptions | What happened after a refund, failed payment, duplicate order or lost email? |
For downloads, test the complete click-to-file path on a phone and a computer. For courses, test a new student account, an existing student and a buyer whose access should end. For coaching or live events, record the calendar, joining instructions, replay access and no-show policy. Store.fan supports several of these sales formats, including digital downloads and online courses, but your migration inventory still needs to define the rules.
Protect the customer record
Export your customer, order and product records before changing the old storefront. Keep the raw export unchanged, then make a working copy for cleaning. Useful fields include name, email, product, order date, amount, currency, refund status, subscription status, consent record and support notes. Keep a separate list of affiliates, collaborators, suppliers and people who have opted out.
Do not assume every contact is a marketing subscriber. A person who downloaded a free file, bought once or asked a support question may not have given permission for promotional email. Record the basis on which you can contact each segment and suppress people who should not be imported into a campaign. If you are unsure, get advice rather than treating the largest possible list as the safest option.
A customer relationship tool such as store.fan’s customer CRM can help you organise records after the move. It does not remove the need to check consent, retention and deletion requirements. Preserve the original export securely, restrict access to it and note when it was created.
Rebuild, test and announce in order
Build the new product before you announce its address. On store.fan, you can use a storefront for your offers and connect payments so money goes straight to your own Stripe account; store.fan takes 0% of sales, while Stripe’s own processing fee still applies. Check the current plan details before choosing a setup: the free plan is link-in-bio only, and paid plans begin with a 14-day trial.
Use a small test purchase to check the full journey. Confirm the price, payment result, receipt, access email, file permissions, mobile layout, refund route and customer support address. Then test an update: replace or add a file, send the intended message and confirm that an earlier buyer receives the right access. If you sell a course, test lesson order and video playback. If you run recurring access, test cancellation and what remains available afterwards.
- Publish the new destination while the old one still explains the change.
- Place a clear migration message on the old product pages and in the next relevant customer email.
- Keep a dated record of which old URL points to which new offer.
- Monitor support for missing files, duplicate charges, lost access and unexpected licence questions.
- Close the old storefront only after the promised transition period and open issues have been reviewed.
If you use email marketing, discount codes, hosted course video or creator-run affiliate programmes, check whether your selected store.fan plan includes what you need. These are Pro features, so they may be useful for the rebuild but they are not free-plan assumptions. You may also want the payments and iOS app details in front of you when you test alerts and checkout.
Export and secure the customer and transaction records first, then map products and fulfilment. Without the record, you cannot reliably identify who should retain access, receive an update or be excluded from marketing.
Not immediately. Keep the original files, licence evidence, exports and fulfilment notes until the new setup has passed testing and your support, refund and access obligations are settled. The right retention period depends on your records and legal responsibilities.
Do not silently change it. Mark the promise in your inventory, decide whether you can provide it another way, contact affected buyers where appropriate and document the decision. If the offer is no longer workable, pause sales rather than creating a new group of customers with the same problem.
Start rebuilding your storefront with an inventory you can check, test and hand over.
Start with store.fanTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



