WHAT YOU WILL LEAVE WITH

Choose and verify document recovery without overstating the scope of an export.

Name the Recovery Object

Grist’s export guide describes a downloadable SQLite-based .grist document. Sharing information is excluded; external attachments require separate handling. Restoring a document therefore has a narrower scope than recovering users, workspaces and server configuration.

Write the recovery goal in ordinary language. “Recover the quoting document after an accidental change” and “rebuild the whole service after losing its server” require different inventories. Calling both a backup can conceal the work that remains after a file is downloaded.

Documentation: Grist: Exports and Backups

Choose a Document You Can Verify

Use a hypothetical quoting document containing three synthetic quotes, one calculation, a linked customer and an example file. Record each expected value independently. A restore check needs facts you can compare; merely opening a document only confirms that something opened.

Also record the intended owner and who should be able to view or edit it. Keep the access expectations separate from the downloaded document. That makes the excluded-sharing boundary visible instead of treating a new owner or missing collaborator as a surprising software defect.

Rehearse in a Separate Destination

The official guide describes importing a downloaded .grist file again. Use a separate test destination, not the only working document, for the rehearsal. Follow the current documented procedure and retain the original recovery artifact.

  1. Record the download time, source document and attachment placement.
  2. Store the artifact in an access-controlled recovery location.
  3. Import the copy into a separate test destination.
  4. Compare records, relationships and calculation results.
  5. Open the example attachment or follow the separate attachment procedure.
  6. Restore only the intended sharing after reviewing it.

Documentation: Grist: Exports and Backups

Record the Recovery Boundary

A successful rehearsal should produce a short record: which artifact was used, what was restored, what was manually recreated and which checks passed. If the procedure relies on knowledge held by one person, write down those decisions before calling the backup operational.

Set a retention and review policy appropriate to the document’s importance and rate of change. This guide does not prescribe a universal recovery time or backup interval. No restoration was executed for this article, and no recovery success rate is claimed.

WORKING EXAMPLE / SYNTHETIC DATA

Hypothetical quoting-document restore acceptance

This is an illustrative worksheet to adapt to your own evaluation. It is not a measured product test or a claim about results in your installation.

Hypothetical quoting-document restore acceptance
ObjectExpected After RestoreSeparate Work
Three quotesSame identities and valuesCompare source manifest
Quote calculationSame expected resultCheck exceptional inputs
External fileAvailable after separate restorationRetain attachment artifact
Collaborator accessOnly intended rolesReapply reviewed sharing

A document backup is useful when a separate restoration demonstrates its scope and explicitly accounts for everything it excludes.

Inspect the official interface evidence

These previously captured interfaces provide orientation. Their versions and dates are distinct from the documentation review above.

INTERFACE SPECIMENS / ANNOTATED

Inspect the interface, with its context.

Open a specimen to see the source image and the observations it supports. A vendor demonstration is distinct from a self-hosted installation.

GristOfficial public demo · Demo identifies v1.7.20
Official public demoDemo identifies v1.7.20
Grist official Lightweight CRM demo showing a contact list, selected contact card and interactions table with fictional sample data.
The official Lightweight CRM template combines a contact grid, a detail card and an interactions table. The demo identifies its sample data as fictional. This hosted v1.7.20 demo is separate from the v1.7.21 core licence check.
  1. Contact gridThe left widget lists sample companies and follow-up tasks.
  2. Detail cardThe upper-right widget presents fields for the selected contact.
  3. Related interactionsThe lower-right widget displays the sample interaction history.
Interface and sample template © Grist Labs. Browser capture by OwnStack Atlas; numbered annotations are separate overlays. Reviewed 25 October 2026.Open official source ↗Enlarge original ↗
SOURCE REGISTER

Check the facts and their boundaries.

Official documentation supports the product statements. The evaluation procedures and synthetic examples are editorial guidance. We have not independently run the installation, migration or recovery procedures described here.

Grist: Exports and BackupsPrimary source ↗

Document downloads, excluded sharing information and separate external-attachment restoration. Reviewed 2026-11-01.