Database backup and restore

Restore an environment to an earlier point in time, or copy your database between environments.

This page lives in Data & API → Settings → Database. It’s mainly used when you need to troubleshoot an issue, undo a mistake, or refresh one environment with data from another.

When to use this

Common reasons to use database backup and restore:

• You deleted or updated records by mistake and want to roll back.
• You want Staging to match Production for testing.
• You want to copy your Editor database to another environment while you debug.

Open the Database settings page

1. Go to Data & API.
2. Click Settings in the left sidebar.
3. Select Database.

Point-in-time restore

Point-in-Time Restore lets you restore an environment to exactly how it was at a specific time.

WeWeb shows how far back you can restore (for example “last 24 hours”). This time window can vary by project.

Restore an environment

1. In Environment, choose what you want to restore: Editor, Staging, or Production.
2. In Time preset, choose how far back you want to go:
   • 5 minutes ago
   • 1 hour ago
   • 6 hours ago
   • 1 day ago
   • Custom
3. If you choose Custom, pick a Custom date and time.
4. Click Restore Environment.
5. In the confirmation popup, type RESTORE and confirm.

Restoring replaces the environment

Restoring will replace the selected environment with its earlier state. Any changes made after that time will be lost in that environment.

Timezone

If you use Custom, WeWeb shows your timezone under the date picker so you can double‑check you picked the right time.

Copy environment

Copy Environment copies data and schema from one environment to another, and fully overwrites the target environment.

Copy one environment into another

1. In Source environment, choose the environment you want to copy from.
2. In Target environment, choose the environment you want to overwrite.
3. Read the warning message carefully.
4. Click Copy <Source> to <Target>.
5. In the confirmation popup, type COPY and confirm.

Copying overwrites the target

Copying replaces all data in the target environment with data from the source environment.

If you copy Production → Staging, your current Staging data will be replaced.

Common pitfalls

I can’t restore or copy yet

If an environment was recently created, restored, or copied, WeWeb may block another operation for a waiting period (for example 24 hours).

If this happens, try again later.

My custom date is rejected

If you choose a custom time:

• It can’t be in the future.
• It can’t be older than the restore window shown on the page.

FAQs

Does Copy Environment include schema?

Yes. Copy Environment copies data and schema and overwrites the target environment completely.

Which environments can I restore or copy?

You can choose between Editor, Staging, and Production (depending on what’s available for your project).

CONTINUE LEARNING

Learn how environments work in WeWeb (Editor, Staging, and Production).

Environments and deploy →