Skip to content
Help center

Your published site's data is kept safe

Sign-ups, bookings, orders: your live site's database survives restarts and republishes. See it, and start over from the preview if you need to.

Updated 3 min read
On this page
  1. What happens at each publish
  2. See your live site's data
  3. Start over from the preview's data
  4. If a change to the structure doesn't go through
  5. For a shop
  6. FAQ
  7. Related

Your live site has its own database, separate from the preview's. When a visitor signs up, books a table or places an order, that's where it's stored. It sits on permanent storage, so it survives site restarts and republishes.

What happens at each publish

When What happens to the live site's database
First publish It's created from the preview's database (your test data)
Republish It's kept; new tables and columns from your code are added to it
Site restart Nothing changes
Unpublishing It's kept; it's only deleted along with the project

Note

so after the first publish, your tests in the preview no longer reach the live site, and real sign-ups are never overwritten by a republish.

See your live site's data

  1. Open Dashboard › Data (or App users).
  2. At the top, switch from Preview to Published site.
  3. The tables shown are those of the live site. Actions (blocking a user, resetting a password…) apply to the live site right away.

The Published site data card shows the storage size, where the database came from ("Created from the preview", with the date) and a History: volume created, database kept at each republish, resets.

The Published site data card
The live site's data.db, created from the preview.

To learn about viewing tables, searching and exporting to CSV, see App users and data.

Start over from the preview's data

Done testing and want a clean start, or did you fill the preview with your real catalog?

  1. In the Published site data card, click Reset with the preview.
  2. Read the warning, then confirm with Replace the data.

The live site's database is replaced by the preview's.

Warning

the sign-ups, orders and messages received on the live site are then lost. Export them to CSV first from Data.

If a change to the structure doesn't go through

When you republish, only safe additions are applied to the live database: new tables, and new columns that are optional or have a default value. If your code needs something else (a required column, a rename), the Data section shows Schema to check with the list of changes. Click Ask the agent: it adapts the code to work with the existing database, without losing any data. Then republish.

For a shop

A shop's database (products, customers, orders) follows the same rules: a republish no longer replaces the live catalog with the preview's. To publish a catalog you changed in the preview, use Reset with the preview: the shop restarts with the preview's data as saved at the last publish, and its orders and customers are lost. See Publish a shop.

FAQ

My site was published a long time ago. Is its data protected?

A banner in Data warns you if the database is still in the old location. Click Republish: it's moved to permanent storage, with nothing lost.

Are the files my visitors upload kept too?

Not yet: only the database is kept. For photos and documents sent by your visitors, connect storage such as S3 or Cloudinary (see Connect services).

Was this page helpful?