Beacons to store.fan: What Actually Transfers (and What You'll Have to Rebuild)
Your media kit doesn't move automatically — a clear inventory of what carries over and what needs a fresh setup on store.fan.
Nobody switches link-in-bio platforms on a whim. You switch because something is actively costing you money or sanity — a fee structure that eats into every sale, a delivery flow that confuses buyers, or a dashboard you've simply outgrown. But the second you decide to move, a very practical question takes over: what actually comes with you, and what has to be rebuilt from zero? The honest answer is some of both, and pretending otherwise is how creators end up losing subscribers, orphaning old customers, or going a week without being able to sell anything at all. This is the item-by-item inventory — files, pricing, email list, and payments — so you can move with a plan instead of a scramble.
Start with the win: your product files move easily
The good news first. Whatever you're actually selling — the ebook PDF, the Lightroom presets, the Notion template, the course video files — those assets are just files sitting somewhere, and files are portable. Download everything from your current platform's product library before you cancel anything, organize it into one clearly labeled folder, and you're most of the way to rebuilding your catalog. There's no lock-in on the content itself; the lock-in only shows up in the surrounding systems (pricing pages, checkout, delivery automation) that you built around those files.
This is a good moment to actually audit what you're bringing over, rather than dumping everything back in unchanged. Kill the product that sold twice in eight months. Consolidate three overlapping template packs into one bundle. A platform switch is one of the few natural checkpoints where cleaning house doesn't feel like extra work — you're already touching every file.
| What you're moving | Transfers automatically? | What to do instead |
|---|---|---|
| Product files (PDF, ZIP, video, presets) | Yes — just files | Download from old platform, re-upload on your new store |
| Product pricing and descriptions | No | Manually recreate on each product page |
| Email subscriber list | No | Export CSV, re-import into your new customer list |
| Stripe/PayPal connection | No | Reconnect fresh — existing keys don't carry over |
| Active subscriptions/memberships | No | Keep billing on old platform until migrated or canceled per-customer |
| Store theme, cover photo, links | No | Rebuild using the new store designer |
| Past order history | Usually exportable, not importable | Export as records for your own bookkeeping |
Pricing and product pages: manual, but faster than you think
There's no import button that reads your old pricing page and recreates it — every price, description, thumbnail, and bundle rule gets typed in again by hand. That sounds tedious, but in practice it's an afternoon, not a week, if you prep first. Before you touch the new dashboard, write out a simple spreadsheet: product name, price, one-line description, file to attach. Then when you sit down to actually build in the new store, you're copy-pasting from your own notes instead of tab-switching between two platforms trying to remember what you charged.
This is also your chance to fix pricing decisions you've been putting off. If you've been meaning to test a higher price point, bundle two low-sellers into a package deal, or add a cheap lead magnet to grow your list, do it during the rebuild rather than after — you're already in the product editor. If you want ideas for what a well-organized catalog looks like in practice, a live example store is worth a look before you start building your own.
Your email list: the one thing you must not forget
This is the transfer step creators most often skip, and it's the costliest one to skip. Your subscriber list — everyone who bought a product, signed up for a lead magnet, or gave you their email for a webinar — represents the actual relationship you built. It does not follow you automatically to a new platform. If you don't export it, you lose the ability to email hundreds or thousands of people who already trust you enough to have handed over their address.
- 1Log into your current platform and find the subscriber/customer export option — it's almost always a CSV download.
- 2Check the export includes email address, name (if collected), and ideally purchase history or tags — you'll want that context later.
- 3Import that CSV into your new store.fan customer list before you send your first broadcast email.
- 4Send a short, warm 'we moved' email from the new platform within the first week — don't let the list go cold during the switch.
- 5Segment past buyers separately from freebie subscribers so your first campaign on store.fan can speak to each group differently.
Once your list is imported, store.fan's broadcast and campaign email tools let you announce the move, re-share your best lead magnet, and get your first sale on the new platform within days rather than starting from zero. Your customer list also feeds the built-in inbox, so replies from that first email land somewhere you'll actually see them.
Payments: always a fresh connection, never a transfer
This one trips people up because it feels like it should be automatic — it isn't, on any platform, ever. Stripe and PayPal connections are account-specific integrations, not portable settings. Moving to store.fan means reconnecting Stripe in one click or adding your PayPal email fresh; Apple Pay and Google Pay then work automatically off whichever you connect. Money goes straight to your own Stripe or PayPal account either way — store.fan never holds a wallet balance you'd need to withdraw from, so there's no float sitting somewhere you need to chase down during the switch.
The part that actually needs planning is existing subscriptions and memberships. If someone is on a recurring membership charge through your old platform's payment connection, canceling that platform outright can also cancel their billing — or worse, leave it running invisibly while you've stopped delivering the membership content there. Handle this per customer: either let existing subscribers finish their current billing cycle on the old platform while all new signups go through your new store, or reach out individually to migrate them with a clear start date. Don't let this be a mystery you discover from a refund request.
Migration day checklist
0/9Why the rebuild is worth the afternoon it costs
It's fair to ask whether a few hours of manual re-entry is actually worth it. The reason creators go through this is almost always the same: fee structure. Paid plans on store.fan carry 0% platform fees, so every sale keeps more of what it's worth, and there's a free plan if you want to test the setup before committing. Over a year of consistent sales, that difference compounds into real money — often more than the rebuild time is worth on an hourly basis, let alone as an ongoing tax on every future sale.
The migration itself takes an afternoon. Losing your email list because you forgot to export it can cost you months of relationship-building.— store.fan team
Beyond fees, it's also a chance to tidy the whole operation: a cleaner store designer setup, discount codes for a launch-week push, custom checkout fields if you need extra buyer info, and Google Analytics on the Pro plan to actually see where traffic converts. None of that existed on day one of your old store either — you built it up over time, and you'll build it up again here, just faster because you already know what worked.
Ready to stop losing a cut of every sale to platform fees — rebuild your storefront on store.fan today.
Start freeFAQ: switching from Beacons or a similar platform
Keep your old platform's storefront live until your new one is fully built and tested — don't take it down first. Once your new storefront at store.fan/username is ready, update the link in every bio at once so there's no gap where a broken link costs you sales.
There's no automatic catalog import between platforms — you'll re-upload files and re-enter pricing and descriptions manually. Prepping a spreadsheet of your existing products first makes the actual rebuild in the dashboard fast.
Their billing keeps running on whatever payment connection processed it originally — switching storefront platforms doesn't move an active subscription. Handle existing members individually: let them finish their cycle on the old setup or reach out with a clear migration date.
You can usually export order history from your old platform for your own records, but it won't import into the new one as active data — treat it as a bookkeeping archive, not a live dashboard.
Yes — start on the free plan, rebuild a few products, and test the checkout flow before deciding whether to move your whole catalog and email list over. Check pricing and the FAQ for specifics, and contact support if you hit anything unclear during the move.
The one-line takeaway
Files move. Pricing, payments, and your customer relationship don't move themselves — you carry them over on purpose, in the right order, so nothing goes quiet in between. Do the export-before-cancel sequence above, and the switch reads to your audience as an upgrade, not an interruption. For more on getting a new storefront right from day one, the blog has setup guides that pair well with this one, and open your store.fan whenever you're ready to stop planning and start building.
Turn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



