# What a restore changes

> A restore replaces a project's content with a backup's, keeps five kinds of configuration the backup doesn't hold, and can leave follow-ups for a person.

Source: https://docs.uniform.app/docs/apps/backup-restore/restore-a-backup/what-a-restore-changes

A restore replaces the content of the project it writes into with the content of a backup. It doesn't merge the two, so most work saved after the backup was taken is gone. To start a restore, see [Restore a project](https://docs.uniform.app/docs/apps/backup-restore/restore-a-backup).

## What's replaced and what's kept

For items and the content model, a restore makes the project match the backup and removes anything the backup doesn't hold. An item is a composition, an entry, or a pattern.

Other parts of the project are only ever created or updated, never deleted:

- **Kept:** the assets, data sources, integrations, webhooks, and releases the project has that the backup doesn't hold.
- **Removed:** everything else the backup doesn't hold.

So a colleague who added an asset or a webhook after the backup still has it. A composition or an entry they edited is back as the backup had it. Tell everyone who edits the project which backup you restored, and which of their work that covers.

## Why some items read Modified

A restore doesn't rewind the project's database. It rebuilds the project through Uniform's APIs, with the same `uniform sync push` the [Uniform CLI](https://docs.uniform.app/docs/guides/cli) uses.

Uniform sets each item's save time when the restore writes it, and reads those times to show an item as **Published** or **Modified**. So some restored items read **Modified** although their content matches the backup.

## The safety backup and roll back

Before a restore into a target project or into this project changes anything, it takes a safety backup of that project. A restore into a new project takes none, because the project is new and empty.

A roll back restores the safety backup into the project it was taken of. A safety backup can't be restored anywhere else.

A roll back is itself a restore, so it keeps what every restore keeps. The releases a restore created stay in place after a roll back.

## Follow-ups

A restore that finished can read **Needs attention**. It then left follow-ups, lines of work for a person, grouped by the part of the project they're about. Each group links to the page in Uniform where you do the work.

| Group | Follow-up | What to do |
| --- | --- | --- |
| **Data sources** | A data source the restore created or overwrote has no secrets, because no backup holds them. | Enter the credentials again on the project's **Data types** page. |
| **Webhooks** | Created webhooks are switched off. | Turn each one on when you're ready. |
| **Webhooks** | A created webhook has a new signing secret, because the backup didn't hold the old one. | Give the new secret to the service that receives the events. |
| **Webhooks** | Sensitive headers, such as Authorization, are missing. | Enter them again before you turn the webhook on. |
| **Webhooks** | Some webhooks couldn't be restored, or the webhook step stopped before it finished. | Check the webhook settings, and add what's missing by hand. |
| **Releases** | A release was restored without its schedule or its lock. | Set the schedule or lock again, if you still want it. |
| **Releases** | A release wasn't restored, because it had launched, or its copy couldn't be read or created. | Read the reason in the follow-up. A launched release can't be created again. To rebuild one from the backup's copy, contact Uniform support. |
| **Releases** | Release items were missing from the backup. | Check those items in the release, and add the content by hand where it's missing. |
| **Releases** | The release step stopped before it finished. | Check the project's releases. One that was partly restored is open with no schedule. |

The **Restore notes** of a restore record what it did to the data sources. They count the ones it updated, created, and skipped, and give the reasons.

## Limits

Some things are in no backup, so neither a restore nor a roll back can bring them back:

- Release editions.
- The secrets of a data source, and sensitive webhook headers.
- Release items that point to an edition, or that have a type the app can't read yet.
- Configuration that a backup taken with content access didn't save.

## Related

- [Restore a project](https://docs.uniform.app/docs/apps/backup-restore/restore-a-backup)
- [Backup contents](https://docs.uniform.app/docs/apps/backup-restore#backup-contents)
