Automated Notion Backup and Restore.

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.

The full list of what we capture, and of what a restore can and cannot put back, lives in our Notion backup documentation. It is worth reading before you need it rather than during a recovery.

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.

As long as you decide. Retention is the number of runs we keep in your storage before the oldest one rotates out, and you set it per backup. Keep a handful of recent restore points, or keep a year of them.

This is the part Notion's own recovery cannot offer. Trash and Page History run on fixed windows tied to your plan, 7 days on Free and up to 90 on Business and Enterprise, and they close whether or not you noticed. Because your runs live in storage you own, retention is a policy you choose rather than a deadline you inherit.

Yes. Notion maintains SOC 2 Type II, ISO 27001 and ISO 27017, and you can pull the current reports from the Notion Trust Center.

That covers Notion's platform, not your use of it. An auditor assessing your organisation asks a different set of questions: what your retention schedule is, where an independent copy of the workspace lives, who can reach it, and when you last proved a restore works. Notion's certificate answers none of those, because none of them are Notion's to answer. That is the half you own, and it is the half a backup gives you.

Deleting the data in Notion takes care of the live workspace, and the next scheduled run will not contain it. What stays behind is the runs already taken, because each one holds the workspace as it stood on the day it ran.

Those copies leave on the retention window you set for that backup, which is the number of runs kept before the oldest rotates out. If you need them gone sooner, the files sit in a storage provider you own rather than on our infrastructure, so you can remove a run from your own bucket directly. Where you have encrypted a backup with a key only you hold, nobody at SimpleBackups can open or alter that archive.

Whether a copy waiting to rotate satisfies the request is a question for your DPO or your counsel rather than for us. What we give you is the part they tend to ask for: the retention schedule you set, and a record of the runs it applied to.

Start with Notion, because that gate comes first. Notion supports HIPAA only on the Enterprise plan, and only once an admin accepts Notion's Business Associate Agreement and follows their HIPAA configuration guide. On Free, Plus or Business there is no BAA with Notion at all, so PHI does not belong in the workspace however it is backed up.

Once your workspace is in scope, backup is one of the controls you have to evidence: HIPAA's Security Rule asks for a data backup plan and a disaster recovery plan under §164.308(a)(7). We are ISO 27001 certified and can supply the certification and security review reports your assessor asks for, alongside the retention schedule and restore history for your own backups. A business associate agreement is not part of the standard subscription, so talk to us about the paperwork before you put a HIPAA-scope workspace on a schedule.

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.

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.

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.

We do not use any propriety backup software - so if decide to leave SimpleBackups at any time, your backups are always there and accessible on your own storage. No need for SimpleBackups to retrieve them.