guide

How to Back Up an Online Business That Lives on Other People's Platforms

Published July 29, 2026

Part of: Choosing Your Tools — our full guide on this topic.

Disclosure: Some links below are affiliate links. If you sign up through them we may earn a commission at no extra cost to you. We only recommend tools we'd genuinely suggest to a friend. See our full disclosure.

Every guide on this site that mentions exporting your data assumes the same thing without ever saying it: that you can still log in.

Look at where the instruction actually appears. It shows up in migration guides and in the FAQ of nearly every tool comparison — yes, you can export your subscribers as a CSV and import them into the new tool. It is offered as reassurance. It is there to tell you that a decision is reversible, that you are not trapped, that leaving is possible.

That is a migration. You decided to go, you opened the account, you clicked Export. Every part of that sequence requires access.

The one moment you would genuinely need your data is the one moment you cannot get to it. An account suspended while you appeal. A card that expired quietly and a payment that failed while you were away. A login you cannot recover because the recovery address is an inbox you stopped using two years ago. A service that stops trading and gives you thirty days notice, most of which you spend not reading the email. In every one of those, the data is intact, safe, perfectly backed up — by them, for them — and completely out of your reach.

So this is the other article. Not how to export in order to leave. How to keep a copy while nothing is wrong, which is a different job with different priorities, and takes about an hour to set up properly.

The quick version

The only question that sorts everything

You do not need a taxonomy of your business. You need one question, applied to each thing you own:

If this platform stopped letting me in tomorrow, where is the only remaining copy?

Ask that about ten things and the whole business sorts itself into three piles, and the piles need three completely different responses.

Pile one: you already have it. Course videos you filmed and edited. The PDF you designed. Product images. The article drafts you wrote somewhere before pasting them in. For these the platform holds a copy — the original is on your machine. This pile needs no work at all, only verification, because the assumption fails more often than you would like. The file was on the laptop you replaced. It was in a cloud folder you cleaned out. It was exported at low quality because that was the version you uploaded. Verify, do not assume — and verification here means opening the file, not seeing its name in a folder listing.

Pile two: it exists only because a platform recorded it. This is the pile that matters, and it is smaller than people fear:

Pile three: it cannot be backed up. Covered properly below, because pretending otherwise is the single most common mistake in this whole area.

Pile three: the things no export will save

An hour spent exporting is wasted if you finish it believing you are covered when you are not. These are genuinely uncopyable:

The correct response to an asset you cannot back up is not a better export. It is a second place where the same value exists.

Which is, finally, the honest reason so much advice — including this site’s, repeatedly — tells you to build an email list. Not because email is virtuous. Because the email list is the one audience asset where the reachability itself is portable: the addresses come with you, and so does the ability to actually send something. Every other audience you have is a permission granted by a company, revocable, and non-transferable. Treating your list as the backup of your audience is a strictly more useful framing than treating it as a marketing channel, and it is the same reason having somewhere you actually own keeps being worth the trouble.

Why the platform’s own backups are not your backup

This is worth stating plainly because it is the belief that stops most people from ever starting.

Your platforms almost certainly maintain excellent backups. Redundant storage, point-in-time recovery, the lot. And it is entirely irrelevant to your situation, because their backups solve their problem — a failed server, a bad deploy, a corrupted table — by restoring your account back into their system.

Your problem is not that their database might lose your rows. It is that you might lose the ability to reach them. Suspension, a failed payment, a recovery address you no longer control, a company winding down. In every one of those the data is perfectly safe and entirely inaccessible.

Their backup protects them from data loss. Yours protects you from lost access. Those are different failures with no overlap, which is why a well-run platform being well-run changes nothing about whether you need your own copy.

The account layer sitting above all of it

Before the exports, one thing that is upstream of everything and takes five minutes.

Nearly every platform in a solo business is recoverable through a single email account. That inbox is the master key. If it is also the thing you might lose — and it is the single most likely thing to be lost, because it is the account with the most ways in and the most ways to be locked out — then no amount of exporting helps, because you will be locked out of the exports too.

Two cheap things, and this article deliberately does not go further, because security advice that gets specific gets stale:

  1. Know which email address each platform account is under, especially the older ones. This is more often unknown than people expect, and it is a five-minute answer today and an unanswerable one later.
  2. Make sure your recovery method survives losing the device you use every day. If your second factor and your recovery codes both live only on your phone, you have one failure that takes out everything at once.

The specifics of how to store those safely are a security question, not a business one, and your platform’s own documentation is the right source rather than a general article — including this one.

What actually goes in the folder

Concretely, once, so it is done:

A subscriber export in CSV. Not just addresses — include the custom fields, tags and signup dates you actually use, because those are what your segments are built from and rebuilding them from memory is grim.

A customer and order export. Who bought what, when, at what price, and their contact address. Take it from whichever platform is the system of record for sales rather than from three places that half-overlap.

The source files for every product you sell, in the format you would need to edit it, not just the format you deliver. A flattened PDF is a delivery artifact. The editable original is the asset, and the difference only becomes visible the day you need to update the product and cannot.

A plain text file of anything you wrote directly into a platform. Copy and paste is fine. This is unglamorous and takes twenty minutes and is the item people skip, right up until they are trying to reconstruct a sales page from a screenshot.

A one-page written description of your automations — trigger, order, delays, what each email is for. Sequences rarely export in a form you can re-import anyway, so the useful artifact is the map, not the file.

A list of your published URLs. Where the internet currently points at you.

And the single most valuable page in the folder: what lives where. One plain document listing each platform, what it holds, which email address the account is under, and what would need to happen for the business to keep running without it. It is not a backup in the technical sense. It is better than one, because the realistic failure in a solo business is not a platform vanishing — it is you not remembering where things are, which is the same underlying problem as the accounts you forgot you opened. You cannot back up an account you have forgotten exists.

Check what is actually inside the file

A backup you have never opened is a belief, not a backup — and in a solo business the test is not a rehearsal or a drill, it is ten minutes with a file manager.

Open each export and check three things:

  1. Does it contain the data or a reference to it? Some exports are a manifest of links rather than the things themselves, which works fine while the account is live and is worth precisely nothing afterwards. If a “course export” is a small file and your videos are large, you have a list, not a backup.
  2. Are the columns you assumed actually there? The tags, the signup dates, the purchase amounts, the currency. Discovering the missing column now costs a minute; discovering it later costs the data.
  3. Does it open? Encoding damage in a CSV — names with accents turning into rubbish — is quiet, common and survivable if you catch it while the source still exists.

That is the whole test. It is the difference between having a file and having a backup, and the fact that it is this cheap is the reason there is no excuse for skipping it.

Do not schedule it. Attach it.

Here is where most backup routines die: someone sets a monthly reminder, does it twice, and then starts dismissing the notification. A standalone recurring task with no external pressure behind it loses to everything else in the week, every week.

So do not create one. Attach each export to something that already happens.

For most solo businesses, the resulting rhythm is roughly quarterly, which is genuinely enough. The gap you would lose is a quarter of new subscribers and a quarter of orders — recoverable, annoying, not fatal. Chasing weekly backups for a business with a handful of sales a week is effort spent for no reduction in real risk, and effort spent on theatre is effort that stops being spent at all.

Where it goes, and the trap in the obvious answer

Two copies, two places, and at least one of them not reachable from the same account as everything else.

That last clause is the whole point, and it is where careful people still get caught. Someone does everything right — exports diligently, files it neatly in cloud storage — and the cloud storage is attached to the same email address that every platform recovers through. One lost account, and the business and its backup go together. The backup was real; the isolation was not.

A folder on your own machine plus one cloud copy is enough, provided those are genuinely independent. Dated subfolders, obvious names. Do not over-engineer it: a plain structure you can find things in beats a clever system you abandon in two months, and this whole task earns its keep by being boring enough to actually repeat.

The part nobody mentions: your exports are a responsibility

A spreadsheet of customer names, email addresses and purchase history is personal data about other people. It does not stop being your responsibility because it moved from a platform to your laptop — arguably the opposite, because the platform had a security team and your downloads folder does not.

This is not an argument against making the backup. It is an argument for making it deliberately:

What the specific rules are where you and your customers live genuinely varies, and it is not something to take from a general article. Check the guidance for your own jurisdiction — the same discipline that applies to what you promise buyers and what your contracts say.

What this does and does not buy you

Worth being straight about, because the whole subject attracts fear-selling.

This does not make you platform-independent. If a platform you sell on disappears, you still have to rebuild the store, the checkout, the pages and the automations, and that is real work measured in days. Nothing in this article prevents that — what to actually do in that fortnight is a separate job, and the part of it that costs real money is not the rebuilding.

It does not protect your revenue during an outage. Your copy of the subscriber list does not send email. Restoring elsewhere takes as long as it takes.

What it buys is that nothing is permanently gone. It converts a catastrophe into an inconvenience — from my business no longer exists to my business is offline for a week and I am irritated. That is a smaller promise than the subject usually gets sold with, and it is the true one.

It also has a quiet second effect that shows up much sooner than any disaster. Businesses that know where their assets are move faster: they change tools without dread, retire a product cleanly, and raise a price knowing every place the old one is written. The confidence to change things is downstream of knowing what you have — which, for most people, is the return they actually collect on the hour this takes.

There is a cheaper cousin of this worth starting today alongside it: a dated log of what you change, not just an inventory of what you own. One line per edit — moved a page, updated the theme, deleted a batch of old posts, switched hosts. It costs nothing until the month your traffic falls and you need to know what you did five weeks ago, at which point it turns a two-week investigation into a two-minute one.

The one-hour pass, in order

  1. List your platforms — every one holding something you would miss. Ten minutes, and the forgotten ones are the point.
  2. For each, note which email address the account is under. Five minutes now, unanswerable later.
  3. Ask “where is the only copy?” of each asset and sort it into the three piles.
  4. Verify pile one by opening the files, not by seeing their names.
  5. Export pile two — subscribers with fields, customers with orders, published text, the automation map, the URL list.
  6. Open every export and check what is inside it.
  7. Write the what-lives-where page. One page. It will be the most useful file in the folder.
  8. Put it in two places, one of which is not reachable from your main account.
  9. Attach each export to an existing habit rather than to a calendar reminder.
  10. Delete the superseded copies.

Then go back to work. The whole point of this task is that it is boring, cheap, and done — and that the version of you who needs it will not be in a position to do it then.

Frequently asked questions

What should I actually back up from my online business?

Sort everything you own by one question — where is the only copy? Things you made and still hold the source file for are already safe, so you only need to confirm the file is genuinely on your own machine and opens. The real exposure is everything that exists only because a platform recorded it: your subscriber list with its custom fields and tags, your customer and order records, the testimonials and reviews people wrote on your product pages, the text of your published pages and posts, and the logic of any automation that runs without you. Those are the ones to export. Everything else on the list is either already in your hands or cannot be exported at all, and knowing which is which is most of the job.

How often should I back up my email list and customer records?

Often enough that losing the gap would not hurt, which for most solo businesses means quarterly rather than weekly. The bigger problem is not the interval but that a reminder in a calendar gets dismissed, so attach each export to something that already happens instead of scheduling it on its own. Export your customer and order records when you do your bookkeeping, since you are already in that account looking at those numbers. Export your subscriber list when you next do anything substantial to your list. Save the source file for a product at the moment you finish it, which is the only time you are certain to have it open. A routine attached to an existing habit survives; a standalone one does not.

Isn't my platform already backing everything up for me?

Almost certainly yes, and it does not help you in the situation you are worried about. A platform's backups exist to protect the platform from losing data — a failed server, a bad deploy, a corrupted database. They restore your account back into their system. They do nothing at all for the failure that actually affects small businesses, which is losing access to the account: a payment that fails while your card is expired, a login you cannot recover because the recovery address is an inbox you closed, a suspension you are appealing, or a service that stops trading and gives you thirty days notice. In every one of those cases the data is perfectly safe and completely out of reach. Their backup protects them from data loss. Yours protects you from lost access.

What can't be backed up?

More than people expect, and it is worth naming honestly rather than pretending a file covers it. Your handle on a platform, the age of the account, your search rankings, the reviews sitting on someone else's product page, the backlinks pointing at a platform URL, and your followers as a group you can actually reach — you can export a list of names, but not the ability to put something in front of them. None of these can be copied to a folder. The correct response to an asset you cannot back up is not a better export; it is a second place where the same value exists. That is the real reason so much advice tells you to build an email list: not ideology, but that it is the one audience asset where the reachability itself is portable.

Is it risky to keep exports of customer data on my own computer?

It carries a real responsibility, yes, and it is worth thinking about before you build the habit rather than after. A spreadsheet of customer names and email addresses is personal data about other people, and it stays your responsibility wherever it sits — including in a downloads folder you forgot about. That is an argument for doing the backup deliberately rather than not doing it: keep the current export, delete the one it replaced, store it somewhere access-controlled rather than on a shared or unlocked machine, and do not scatter copies across services. If you are unsure what rules apply to you and the people on your list, check the guidance for your own jurisdiction, because that genuinely varies and is not something to take from a general article.

Where should I store the backups?

Two copies in two places, and at least one of them somewhere that is not reachable from the same account as everything else. The common failure is subtle: someone diligently exports everything and files it in the cloud storage attached to the same email address that all their platform logins recover through, so a single lost account takes out both the business and its backup at once. A local folder on your own machine plus one cloud copy is enough, as long as those are genuinely separate. Beyond that, do not over-engineer it. A plain folder with dated subfolders that you can actually find things in beats a clever system you abandon in two months.

Explore the full topic Choosing Your Tools: Honest Comparisons for Solopreneurs → Pick the right platform the first time — course hosts, email, funnels, and stores compared.