Running & Maintaining a Site

Data Export

Definition

A data export is a copy of what you hold in a service, produced in an open format you can store and re-import elsewhere. For a hosting account it covers three different things, and they rarely come out the same way. The content — HTML, images, PDFs, whatever you uploaded — usually arrives as a ZIP archive with the original folder structure intact. Configuration, meaning redirects, custom headers, domain settings and access rules, may come as a config file, may be readable through an API, or may exist only in a settings screen you have to copy by hand. Statistics are the awkward one: view and download counts are often visible but not downloadable, or downloadable only as a rolling window rather than the whole history. A useful export is complete, dated, and in a format still readable in five years, which in practice means CSV, JSON or plain files rather than a proprietary bundle.

Why It Matters

An export you have never run is a guess. The failure people hit is discovering, at migration time, that the archive holds the pages but not the redirects, or 90 days of figures rather than the three years they were counting on. Running one early, unpacking it and looking inside turns vendor lock-in from an abstract worry into a short list of things to record separately. It is also the cheapest insurance against an account problem — a suspension, a lapsed card, a deletion made by the wrong person.

How It Works

Exports come in roughly three shapes. A one-click archive builds a ZIP in the background and emails a download link, normally valid for a day or two. A REST API lets you enumerate files and settings programmatically, which is the right route for anything you want on a schedule, since a script can run monthly and drop the result into storage you control. Failing both, a recursive download tool can mirror the public site, which captures the pages but nothing private and none of the configuration. Whichever route you take, check the result against the live account: count the files, open a few, confirm the figures cover the period you expected. Then store it somewhere that is not the same provider, because an export sitting inside the account it came from protects you against nothing.

Real-World Example

A membership organisation keeps twelve years of newsletters at archive-nl.99helpers.site, about 900 PDFs. Once a quarter they pull the whole set down as a single ZIP and keep the last four copies on a machine in the office. When they eventually rebuild on a different structure, that archive is what they build from, and the folder names become the new URL paths. The one thing they had to start doing separately was saving a monthly CSV of download counts, because the reporting window only reached back a year.

Common Mistakes

  • Trusting an export you have never opened — the archive that turns out to be empty, truncated or missing the configuration is discovered at the worst possible moment
  • Keeping the export inside the account it came from — the scenarios where you need it are mostly scenarios where you have lost access to that account
  • Exporting content but not statistics — files can be re-uploaded from your own machine, while a lost view and download history cannot be reconstructed from anywhere

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →