Skip to main content

A copy you control, outside the app

Back Up Testimonials to a CSV

Customer praise takes years to gather and seconds to lose: a deleted space, a teammate who tidied too hard, a laptop that died with the only spreadsheet on it. A backup is not the export itself. It is the habit around it: who runs it, where the file lives, and whether anyone has proved it can be restored. Tick through the routine below and you will know.

  • One owner, one schedule, every space included
  • Open and count the file before you file it away
  • A restore drill so the copy is proven, not hoped for

The problem, solved

Why a testimonial library goes unprotected, and the fix for each gap

  • The app is our only copy

    Nobody thinks of quotes as data until a space is removed by mistake or a login is lost, and then there is nothing to go back to.

  • We backed up one brand and forgot two

    Accounts with several brands keep separate libraries, and a backup that covers the busiest one feels complete when it is not.

  • Only the person who left knew how

    A backup habit that lives in one head stops the week that person changes role.

  • We have files but never restored one

    An untested backup is a guess. Encoding problems or a missing space only show up when you need the file.

  • Not sure the clips are covered

    Video and audio testimonials are often the most valuable items, and a spreadsheet may not hold them at all.

Flip the switch to see how StoryProof handles each one.

Backup routine

The testimonial backup checklist

Work through it once to set the routine up, then again each time you run a backup. Anything left unticked is the weak point in your copy.

Set it up once
Each backup run
Prove and prune

Ticks stay in this browser tab. Nothing is stored or sent anywhere.

How often to back up

Match the rhythm to how much you would lose between runs. These are suggestions, not rules.

Your librarySuggested rhythmExtra trigger
New testimonials most weeksMonthlyBefore any bulk tidy-up of tags or approvals
A few a monthQuarterlyBefore a teammate with settings access leaves
Mostly imported, rarely changesTwice a yearAfter every large import
Several brand spacesSame day for all spacesWhen a space is added or retired

In StoryProof

Run your first backup

  • You will need
  • Access to workspace settings
  • A list of your brand spaces
  • Two storage locations you control
  1. 1

    Export every space

    From the workspace settings, export each space’s testimonials to a CSV file. Do them in one sitting so the files describe the same moment.

  2. 2

    Open and count

    Open each file in a spreadsheet, check the header row and special characters, and compare the number of rows with what the app shows.

  3. 3

    Store two copies

    Save the dated files to both locations and limit who can open them. They hold your customers’ names and words.

  4. 4

    Rehearse a restore

    Upload one file into a spare space and match its columns. Imported rows wait in the approval queue, so nothing appears on a widget or wall.

What happens next: Restore drills are imports, and Imported reviews count toward the same monthly allowance as collected ones: Free 25, Starter 100, Pro unlimited. Keep the drill sample small.

Before you start

What a CSV backup does not cover

  • The file layout is not described here

    This page does not list which columns the export contains or whether media is inside it. Export once and read the file before you rely on it.

  • No automatic schedule is claimed

    Nothing here says StoryProof exports on a timer. The rhythm is a calendar reminder and a person.

  • Widgets and walls are settings, not rows

    Which testimonials sit in which widget, and how each looks, are not part of a testimonial list. Note your key widget choices separately if you would need to rebuild them.

  • A restore re-enters the approval queue

    Rows you upload start unapproved, so a full restore means approving again before anything is public.

  • Backups are personal data

    A file of customer names and quotes needs the same care as any customer list: narrow access and a keep period you can explain.

FAQ

Questions people ask

Short answers to what usually comes up next.

Is the trial a reason to back up in a hurry?

No. What you collected stays readable and exportable after the trial ends, even without a paid plan. Back up because copies outside any tool are good practice, not because of a deadline.

Can one file cover all my brands?

The export runs per space, so expect one file for each. Keep them together in a dated folder rather than merging them, so a restore can go back to the right space.

How long should we keep old backup files?

Long enough to recover from a mistake you might notice late, and no longer. A simple rule is to keep the last few runs plus one file per year. Write your choice down so it is applied the same way each time.

Should the restore drill use our live space?

Use a spare space. A drill in the live space would add duplicates to the library you actually publish from.

Does this replace keeping consent records?

No. A backup copies the testimonials; a consent record shows each customer agreed to their use. Keep both, in separate places.

Still have a question? Ask the StoryProof team or book a demo.

Keep one library, and a copy you control

Collect and approve in StoryProof, then export each space to CSV whenever your routine says so.

Last updated 2026-11-19.