The customer records worth exporting before you close an old storefront
Prioritise contact details, purchases, consent, refunds and support history while each platform still grants access.

You have decided to close an old storefront. The products are backed up, the new site is nearly ready and the final sales are still coming in. Then a former customer asks for an invoice, someone wants access to a purchase from two years ago, and you realise the platform may stop showing the records as soon as you cancel. Before you shut anything down, export the customer information you may need to deliver, refund, answer and contact people lawfully.
Start with a record inventory
Do not begin by downloading the first CSV you find. First write down the records your business uses to fulfil a promise. A digital product seller may need the purchase and delivery record. A coach may need booking and attendance details. A membership creator may need subscription status and cancellation dates. The aim is not to keep every field forever; it is to avoid losing the context that lets you serve an existing customer.
- 1List every product, course, membership, coaching service or event sold through the old storefront.
- 2For each one, note where its customer, order, payment, refund, consent and support records live.
- 3Record the export format, date range and filters used. A file called customers.csv is less useful than customers_paid_products_2022-2026.csv.
- 4Download the files, then open them in a spreadsheet or database before cancelling anything.
- 5Keep a read-only copy and a working copy, with access limited to the people who need them.
Export the customer and purchase core
The minimum useful record connects a person to a transaction. Export the customer’s name and email address where available, the order or transaction ID, product name, purchase date, amount, currency, payment status and delivery status. If the platform provides a customer ID, keep it too: names and email addresses can change, while an internal identifier can help you join several exports.
| Record | Why keep it | Check before closing |
|---|---|---|
| Contact details | Lets you identify a customer and answer a later request | Check whether the file includes the latest address and duplicate contacts |
| Purchase history | Shows which promise was made and what the customer paid for | Match product names, dates, amounts and currencies to sample orders |
| Delivery or access status | Helps you restore a download, course or membership entitlement | Confirm whether active, expired, refunded and cancelled states are included |
| Payment reference | Helps you trace a transaction without storing card details | Keep transaction IDs and processor references, never exported card numbers |
Keep consent separate from contact details
An email address tells you how to contact someone. It does not, by itself, tell you that they agreed to receive marketing. Export the consent status, the type of consent, the date and time if provided, the source or form, and any unsubscribe or suppression status. Keep transactional messages distinct from promotional newsletters: a customer may need information about an order without wanting future product announcements.
When you move to a new storefront, import only the contacts and fields you can use for the stated purpose. A tool such as store.fan’s email marketing can help you manage future campaigns, but it does not turn an old list into a permission slip. If the old platform cannot provide reliable consent records, send only messages you have another lawful basis for sending, or ask people to opt in again.
Preserve the awkward records
Refunds, disputes and support tickets are easy to ignore because they are not part of the happy-path sale. They are also the records most likely to matter later. Export refund dates, amounts, reasons and linked order IDs. Keep chargeback or dispute status and the evidence submitted. Save support conversations, attachments, promised fixes and the final resolution. If a customer received a replacement file, extension or partial refund, record that against the original order.
- Refunds: preserve the original amount, refunded amount, date and status.
- Chargebacks: keep the dispute reference, deadline, outcome and evidence location.
- Support: retain the question, your answer, dates and any promised follow-up.
- Access changes: note upgrades, cancellations, extensions and manual grants.
- Tax and finance: keep the reports and transaction references your accountant or records policy requires.
Make the new storefront usable on day one
A clean export is only useful if you can act on it. Create a simple mapping between the old product names and the new ones. For each product, record its new URL, fulfilment method, price, refund policy and the customer group that should retain access. If you are moving files, test a purchase or preview as a customer rather than assuming that a successful upload means delivery works.
For a creator selling downloads, store.fan’s digital downloads can give you a new place to deliver files. Course creators may instead need hosted online courses, with access rules and video assets checked separately. store.fan sends sales money straight to your own Stripe account and takes 0% of sales; Stripe’s own processing fee still applies. The practical benefit here is a clearer handover between your storefront records and your payment records, not a reason to skip the audit.
Use a final verification pass
- 1Open every export and check that it has rows, column headings and the expected date range.
- 2Choose several orders: one successful, one refunded, one cancelled and one with a support issue if available.
- 3Find each example in the relevant customer, purchase, payment and support files.
- 4Check that consent and unsubscribe fields are present before importing any marketing contacts.
- 5Confirm that product links, download permissions and course or membership access work in the new storefront.
- 6Keep the old storefront accessible until you have answered any known open cases and completed your retention review.
Not automatically. Exporting contact details is different from proving marketing consent. Keep the consent and suppression fields, follow the rules that apply to your business and ask people to opt in again where the old records are incomplete.
No. Keep the order and processor references needed to reconcile or investigate a payment, not card numbers or security codes. Your payment processor should remain responsible for sensitive card data.
Take screenshots or reports of essential totals, download invoices and product files, and contact platform support before cancellation. You may need to reconstruct a smaller operational record from payment reports, support messages and your own bookkeeping.
Once the records are checked, choose the smallest new setup that fulfils the existing promise. store.fan can provide a storefront at store.fan/yourname; its free plan is link-in-bio only, while paid plans start with a 14-day trial. Pro adds tools such as email marketing, discount codes, hosted course video and creator-run affiliate programmes. Those features are useful when they match your next workflow, but you do not need to recreate every old platform setting just because it existed.
When your exports are checked, start building the new storefront around the records and promises you actually need to carry forward.
Try 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.



