Weekly data exports: own your data on any plan

By the Onsites AI team · Last updated August 28, 2026 · 4-minute read

Data ownership is the least glamorous promise in support software and the only one you will remember on the day you need it. A workspace full of conversations, contacts and quote documents represents months of institutional memory; the difference between "we have it all" and "we lost the spring" is a five-minute weekly ritual and one honest rule: a backup that exists in exactly one place is not a backup. This guide is that ritual, sized for a small team on any plan.

Why exports matter more on free cloud

Be straight about the trade you are making on the free tier. Paid cloud workspaces get automatic encrypted backups server-side; free-tier cloud workspaces are deliberately not backed up on the server — that is one of the ways the tier stays permanent and free. The software is identical, the data is encrypted in transit and at rest, but if an accidental bulk delete or a lost credential ever happens, the server-side copy that would rescue you on a paid plan does not exist. The export ritual is what stands between your queue and that scenario — five minutes a week, Friday before close.

This is also, quietly, the negotiation position: when you eventually need a fourth seat or extra storage, the first payment is trivially small ($15 per seat, packs from $1/GB — see the free vs paid guide), and automatic backups are part of what payments buy. Until then, the export is your backup, so treat it as infrastructure rather than housekeeping.

The Friday ritual, end to end

Step one — export. In Settings, run the export. It packages your conversations, contacts, CRM records and settings into an archive. The desk tells you what each export includes; the first time, open the archive and page through it so you know what lives where — an unexamined backup format discovered during an emergency is a second emergency.

Step two — store it twice, in two places. The office laptop plus a second location: an external drive, another machine, or a storage bucket in your own cloud account. Two places, not two copies in the same drawer — the file that lives only on the machine that also fails is the lesson everyone learns exactly once. Name the file with the date; you will want to answer "what did we have last Friday?" without a forensics session.

Step three — keep the recent window. Retention for a small team: the last eight weeks locally, the last twelve months in the second location, then rotate. Conversations age into decisions ("what did we promise this account in March?") more often than anyone expects, so yearly archives earn their storage costs. And keep them encrypted — archives of customer conversations are a sensitive document, not a folder to leave on a shared desktop.

Step four — the quarterly restore drill. Once a quarter, take the oldest available export onto a spare machine and confirm you can actually read it: conversations intact, contacts complete, attachments openable. Ten minutes, four times a year, and the export stops being a superstition and becomes insurance with a verified payout. A backup whose restore has never been tested is a hope, and hopes do not survive contact with actual data loss.

What the exports are good for beyond insurance

The weekly archive quietly becomes the desk's memory in other ways. Migrations: when you outgrow free — a fourth seat, more storage, or the decision to move tracks — exports are the luggage that carries history between setups, as covered in the migration guide and the cloud-to-self-hosted move. Analysis: because text conversations are tiny, months of history fit in megabytes, and the tag-and-topic record from your tag vocabulary rides along in every export — an end-of-year "what did customers ask about" deck requires nothing more than the twelve Fridays you already did.

Compliance and customers ask too. "Where does our data live, who else can see it, and how do we get it out?" is a standard procurement question; "exports are in settings, every Friday, here is last week's file" is one of the strongest answers available on any tier. The compliance checklist guide lists the full set of questions to be ready for.

The five export mistakes worth skipping

One ritual, five ways to do it wrong — all common, all cheap to avoid. Exporting only conversations and discovering too late that contacts, CRM records and settings live separately: run the full export and glance through it the first time. Keeping both copies on machines that share one power strip, one office or one owner: the second location should be a different failure domain, not a different folder. Naming files export.zip every week, so the moment of need turns into a matching game against timestamps nobody trusts; the date goes in the filename, always. Storing archives unencrypted in a shared drive where every future ex-colleague can read years of customer conversations — encrypt, then share access deliberately. And the quietest one: writing the ritual down nowhere. The person who owns Friday's export is on holiday exactly once before someone else must know the steps; one page of documentation in the internal wiki is the difference between a ritual and a superstition that only one person can perform.

The upgrade paths, honestly stated

When exports feel like a chore rather than a ritual, that is the paid feature paying for itself. Two routes: move to paid cloud — the first payment (any seat beyond three, or anything from the pricing page's calculator) switches the workspace to automatic encrypted backups and removes the widget watermark permanently; or own the whole machine — self-hosting runs the desk on your own servers, where backups are scripts on your infrastructure and the data never leaves your network in the first place, with the disaster recovery guide covering the restore side. Free stays free either way you come back to it. What never changes is the principle this guide started with: your conversations are your company's memory, and memory belongs in more than one place.