Automated Notion backup, stored remotely.

A Notion backup service is a tool that automatically saves copies of your Notion workspaces at regular intervals.
This ensures that you have secure and up-to-date backups of your data, which can be restored in case of accidental deletion, data corruption, or any other issues that might cause data loss.

Everything Notion exposes through its API: pages, databases, blocks, and database properties, including formulas, relations, rollups, and unique IDs. Files and attachments, comments, and the people directory are captured as well when you enable them on the backup. The one category Notion withholds from every integration is interactive AI blocks, such as a live AI summary.

Coverage follows access. The archive contains exactly what has been shared with the SimpleBackups integration, so a teamspace or page nobody shared with it is not in the backup.

SimpleBackups connects to Notion via OAuth. You authorize the connection directly from your Notion account, we never ask for your password, and you can revoke access at any time from your Notion settings.

What that connection can see is what gets backed up. Share every teamspace and top-level page you want covered with the SimpleBackups integration, and share new ones as you create them so the next run picks them up.

Your backups are stored in the storage provider you choose — your own S3 bucket, SFTP server, Backblaze B2, Cloudflare R2, Hetzner Storage Box, or SimpleStorage (our managed storage). We never store your Notion data on our servers.

Pick the run you want from the SimpleBackups dashboard, choose a destination page in a connected workspace, and start the restore. We rebuild your content through the Notion API: pages, blocks, databases, and the relations between them are recreated one by one, rather than handed to you as files you re-import by hand.

Restore into a new, empty destination page so recovered content never mixes with what is live, and expect a full-workspace restore to run longer than the backup it came from.

Usable, in most cases without manual cleanup. The restore is not an export followed by an import: it is a structured, block-by-block reconstruction against the Notion API, so page hierarchy, block types, databases, and nested relations come back the way Notion models them.

Database properties are rebuilt too, including formulas with their expressions recomputed, relations relinked to their related databases, rollups, and unique IDs. What you should expect to redo by hand is short, and worth reading before you need it.

Some of this is Notion's API and some of it is ours, and it is better known now than during a recovery. Database views do not keep their filters, sorts, or grouping. Comments and the people directory are captured in the backup when you enable them, but Notion gives integrations no way to write them back, so they are not recreated. Original timestamps and authorship cannot be restored: recreated pages are stamped with the restore. Verification properties cannot be recreated, and a few block types are simplified or skipped, including the interactive AI blocks Notion withholds from all integrations. Root-level workspace pages are restored under a destination page rather than at the workspace root.

The full list lives in our Notion backup documentation.

Yes. A restore targets whatever destination page you point it at, in any workspace you have connected with write access, so you can recover into a fresh workspace, a sandbox, or a different Notion account entirely.

That is also the safe way to rehearse a recovery: restore into an empty page, check the result against what you expected, and leave production untouched.

Not once you enable encryption. You supply a public key, your archive is encrypted with it, and only your private key opens it. At restore time you paste that private key into the restore form: it is used for that run and never stored.

The tradeoff is worth stating plainly. With encryption on we cannot inspect your archive, validate it, or run a restore on your behalf, and a key only you hold cannot be reissued by anyone. Store it somewhere safe before your first run.

Notion's built-in export is a manual download you have to remember to run, and what it gives you is files, not a workspace. Restoring from it means re-importing by hand and accepting that links, relations, and dynamic content arrive flattened. It also stops being practical at scale: very large workspaces often fail to export natively at all.

SimpleBackups runs on the schedule you set, stores each run off-platform in storage you own, keeps multiple restore points, and puts your content back into Notion through the API instead of handing you a folder.

We do not cap how much data you back up. On a very large workspace the practical constraint is run time rather than size: a full backup takes hours, and a restore takes longer than the backup that produced it.

If your workspace needs more than a standard run allows, talk to us. We raise run limits case by case, and a very large workspace can also be split into one backup per top-level section so each job finishes faster.

It depends on how many Notion workspaces you back up. Workspaces are included with the plan on Lite (5), Plus (10) and Max (unlimited). On the free Basic plan, Notion backup comes as a $10/month addon per workspace, ideal when Notion is all you need. Extra workspaces beyond your plan's allowance are $10/month each on any plan.

Every plan starts with a 7-day free trial, no credit card required. See our pricing page for the full comparison.