Bringing your old buyer list across with a single CSV import

Somewhere on your laptop there is a file with the people who have already paid you. It might be a marketplace export, a set of rows you typed by hand after each payment notification, or a mailing list that has drifted a little out of date. Starting a new storefront can feel like walking away from all of that and beginning again at zero. You do not have to. The customer list on store.fan imports from any CSV, so someone who bought from you two years ago ends up in the same place as the person who buys tomorrow.

The list is the part that is genuinely hard to replace

Followers are borrowed. A list of people who have paid you once is not. It is the shortest route to a second sale you will ever have, and it is the only asset that travels with you when a platform changes its mind about how it works. That is why the customer list fills itself on store.fan from every purchase, membership and free download, with lifetime value shown per person.

The awkward truth is that the list you are bringing across is probably worse than you remember. Marketplace exports often hide the buyer's email behind a forwarding address or leave it out entirely. Names arrive as usernames, or as the name on a card rather than the name a person answers to. Rows are duplicated because the same person bought twice under two addresses. Some of it is three years stale and will bounce the first time you use it.

None of that is a reason to skip the import. It is a reason to spend twenty minutes on the file before you upload it, and to be honest with yourself about which rows are real. A clean list of 180 people you can actually reach beats a messy list of 900 you cannot.

What changes once the list lives in one place

Most creators end up with the same scattered arrangement: buyers in a marketplace dashboard they cannot export properly, subscribers in an email tool, free-download recipients in a form service, and a spreadsheet holding whatever fell through the gaps. Here is what that looks like next to a single list that keeps updating itself.

Shaping the file before you upload it

Do the tidying in a spreadsheet, not in your head. Everything below takes one sitting, and the file you end up with is worth keeping as your own backup regardless of what you do next.

1. 1Export from wherever the buyers live now. Ask for the widest export the platform offers, even if most columns are useless to you, because you cannot go back for them once your account there is closed.
2. 2Open the file and delete every column you cannot name a use for. Order IDs, internal status codes and shipping zone numbers are noise. Email, name, and perhaps the product they bought are enough.
3. 3Fix the email column first. Trim stray spaces, drop anything that is obviously a forwarding or anonymised address, and sort by email so duplicates sit next to each other and can be merged.
4. 4Decide on missing names before you upload rather than after. A blank is better than a placeholder like Customer, because a blank looks like a blank and a placeholder eventually gets used in a greeting.
5. 5Split full names into first and last only if your file already has them cleanly. Guessing where a name breaks is how people end up being addressed by their middle name.
6. 6Save the file as CSV with UTF-8 encoding so accented characters survive the trip.
7. 7Open the customers area of your store.fan dashboard, choose the import option and match your columns to the fields on screen. Read the preview rather than skipping past it.
8. 8Spot-check ten rows after the import against the original file. Check the ones with unusual characters, long names and old dates, not the easy ones at the top.
9. 9Export the list straight back out as a CSV and keep that file somewhere safe. That is your baseline, and it costs nothing on any plan.

What a real import tends to look like

Say you export 412 rows from two places: 340 from a marketplace and 72 from an old newsletter. Sorting by email shows 24 duplicates, because plenty of your newsletter people bought from you as well. That leaves 388 unique addresses. Of those, perhaps 60 have no usable name, because the marketplace only ever recorded a display handle. You leave those name fields blank, upload the file, and 388 people appear in the customer list.

From that moment the list behaves like a live thing rather than an archive. Every new purchase adds a person or attaches to one who is already there. Lifetime value starts at zero for imported contacts, because store.fan has no record of what they paid you elsewhere, and climbs as they buy again. Six weeks later the useful question is no longer how many rows you have. It is which of them have bought twice, and that is a column you can now sort by.

The mistake most people make

They wait. The storefront is not finished, the pricing is not decided, the cover photo is wrong, so the import stays on the to-do list until the old platform is already closed and the export is no longer available. Import first. The list does nothing harmful while it sits there, and having it changes what you build, because you stop designing for strangers and start designing for people whose names you can read. The Free plan holds the list and exports it without asking for a card.

The import is a small piece of admin that removes a large piece of dread. Once the names are in, moving your selling somewhere new stops feeling like abandoning the people who already trusted you, and starts feeling like telling them where you have gone. If you want to see how the rest of the move fits together, the migration notes cover products and links, and the FAQ answers the smaller questions this piece skipped.