How to Back Up and Export Your Online Course Content
Here is the email no course creator wants to open: your platform is “streamlining plans,” and the tier you are on disappears in 60 days. Or the price doubles. Or — and this happens more than anyone admits — your account gets flagged by an automated system over a weekend and you cannot log in to the thing that holds your entire business. In every one of those moments, one question decides whether you lose a night’s sleep or a year’s work: what can you actually take with you?
Most creators assume the answer is “my videos.” It usually is not the problem. The parts that are genuinely hard to pull out are the ones you never think about until you need them — the student roster, the record of who paid for what, and the email relationship you spent years building. This guide is about owning those assets before you are forced to, so that platform trouble becomes an inconvenience instead of a catastrophe.
“Owning” your course is not the same as hosting it
There is a quiet distinction underneath every hosted course platform: some of what sits in your dashboard you own, and some of it you merely rent access to. The source video file you uploaded is yours — you have the original on your drive (you do have the original, right?). The polished player experience, the drip schedule, the completion certificates, the tidy CSV of every student’s progress — those are features of the platform, and they can leave with the platform.
This is the mechanism behind what Wikipedia calls vendor lock-in: a situation that “makes a customer dependent on a vendor for products, unable to use another vendor without substantial switching costs.” The switching cost in online courses is rarely a fee. It is the quiet realization that the data describing your business lives in a format you cannot easily move. The healthier counterweight is what is formally known as data portability — the ability to export your data “to usable files” so you are not “trapped in closed systems.” Backing up your course is really just practicing data portability on purpose, before anyone forces the issue.
The three things you must be able to get out
Forget a full “download everything” button — very few platforms have one, and the ones that do often give you a tangle you cannot reassemble. Focus instead on the three assets that actually determine whether you could rebuild elsewhere.
1. Your source media. Not the streaming version — the original files. If your only copy of a lecture is the one playing inside the platform, you do not own that lecture; you are licensing it back from your own account. Re-downloaded streaming files are frequently transcoded, which (to borrow the lock-in framing) is “in effect a switching cost”: every re-encode is a small, permanent loss of quality.
2. Your student and sales records. Who enrolled, who finished, who refunded, who bought the upsell. This is the data that tells you what is working, and it is also what a new platform needs to recreate access for paying customers. If you cannot export it as a clean file, you cannot migrate without emailing hundreds of people to re-register.
3. Your email list. This is the one most people forget, and it is the only asset that makes you truly platform-proof. Your course can die and your list survives; your list dies and nothing you build next has an audience. Treat the list as the crown jewel — more on where it should live below.
What you can realistically export — by asset, not by platform
Platforms change their export tools constantly, so a “Teachable does X, Thinkific does Y” table goes stale in a month. The durable way to think about it is by asset type. Here is the honest state of what hosted course platforms typically let you take, what format you get, and the catch that bites people.
| Asset | Usually exportable? | Typical format | The catch |
|---|---|---|---|
| Source videos & files | Yes, if you kept originals | MP4 / PDF / original | Streaming re-downloads are often transcoded, not the master |
| Student / enrollment roster | Usually | CSV | Passwords never export; students must re-set access elsewhere |
| Purchase & refund history | Usually | CSV | May split across a separate billing/Stripe export |
| Quiz results & completion/progress | Sometimes | CSV, if at all | Progress state rarely imports into a new platform — it resets |
| Certificates issued | Rarely in bulk | Individual PDFs | The certificate design is a platform feature; you keep records, not the generator |
| Email / marketing contacts | Depends on the tool | CSV | If the platform is your email tool, you are most exposed here |
The pattern is clear once you see it: the things that export cleanly (files, rosters as CSV) are the things you could have kept yourself anyway. The things that do not travel — progress state, the certificate engine, the player experience — are exactly the platform features you were paying for. That is fine. Just do not confuse “I can see it in my dashboard” with “I have a copy.”
A backup routine that fits in one afternoon a quarter
You do not need automation or a developer. You need a repeatable ritual four times a year. Put it on the calendar the same week you review your numbers.
Step 1 — Pull the CSVs. From your platform’s admin area, export your student/enrollment list, your orders/transactions, and (if the platform hosts it) your email contacts. Name them with the date: students_2026-Q4.csv. Dated filenames are the difference between a backup and a pile.
Step 2 — Verify your masters. You are not re-downloading from the platform; you are confirming that the original video and PDF files you uploaded still exist, in full quality, in a place you control. Spot-check that last quarter’s new lessons made it into your archive.
Step 3 — Export the email list separately. If your contacts live inside the course platform, export them and import a fresh copy into a dedicated email service. If they already live in a standalone email tool, this step is done — which is the whole point of keeping them there.
Step 4 — Store in two places, one of them offline-capable. A single cloud folder is one outage away from being zero copies. The old “3-2-1” instinct is enough here: the working copy, a second cloud copy under a different account, and an occasional drive you can hold in your hand.
Handling student data in these exports comes with responsibilities, not just logistics — the same privacy obligations covered in our guide to data privacy and GDPR compliance for online courses apply to a CSV sitting in your Downloads folder.
Where your copies should actually live
A backup is only insurance if the insurer is not the same company you are insuring against. Two moves make you structurally harder to lock in.
First, own the front door. When your course is served through your own address rather than a platform subdomain, you can move the course underneath it without your audience ever seeing a broken link. We walk through the trade-offs in whether a custom domain for your course platform is worth it — for portability specifically, it almost always is.
Second, keep the list off the platform. An email list you control is the asset no platform can hold hostage, because it is the one that lets you tell every student “we’re moving — here’s the new link” on a Tuesday afternoon. This is also the EU’s logic in granting a formal right to data portability under GDPR, which requires providers to hand your data back “in a format that lets people transfer it to another provider.” You can grant yourself that right regardless of where you live, simply by keeping your own copy.
When this is not worth your time (yet)
Honesty cuts both ways. If you have not launched — if your “course” is three draft lessons and no paying students — building a quarterly backup ritual is premature optimization. The only thing that matters at that stage is keeping your source files on your own drive. Everything else you are backing up does not exist yet.
The routine earns its place the moment money and people are attached to the course: real students, real transactions, real revenue you would have to reconstruct. That is also, not coincidentally, the moment a platform problem stops being annoying and starts being existential. If you have already decided you are leaving rather than merely insuring yourself, backing up is only step one — the full move is its own project, and our step-by-step guide to migrating your course to a new platform picks up where this leaves off.
Think of all of this as an exit you hope never to use. You buy fire insurance not because you expect a fire, but because the cost of being wrong is total. A quarterly hour spent exporting CSVs and confirming your masters is the cheapest insurance in your business — and the one you will be most grateful for on the day you open that email about “streamlining plans.”
Thanks for making your ideas so easy to follow. The article feels organized, and the transitions help the discussion move along naturally.