Get your Notion back —
relations and all.

Many backup tools focus on exporting or archiving data. Restora is designed to rebuild complex Notion workspaces, including relations, rollups, views (table, board, list, calendar, timeline and gallery — only page layouts are named in the restore report), and hierarchy. It actively recreates your databases, recomputes rollups, and reconnects relations automatically.

No. Backing up is completely free. You can also run a sandbox demo restore for free to watch Restora rebuild sample relational databases in real time before ever entering a credit card.

You back up first — free, about a minute, on the web or with the CLI. Then you choose how to restore it. The one-time Restore Pass ($9.99) unlocks restoring your Restora backups for 30 days — ideal if you just need to recover once. Pro ($6.99/month) adds automatic cloud backups, 24/7 drift monitoring, and a full backup timeline, plus ongoing restore. Either way, restore works on a backup made with Restora — a plain Notion export or an old .zip won't work, because those don't carry the relations, rollups and views Restora rebuilds.

Because the backup itself is the hard part — and it's useful long before you ever restore. A Notion export .zip gives you text with the relations, rollups and views stripped out; a free Restora backup captures that structure, so a restore can actually rebuild it later. On the free tier you keep unlimited backups on your own drive, browse and verify them any time, and run the Drift Auditor to see what silently changed since your last one — no card, nothing to restore. You only pay the day you actually hit restore.

Straight to your own local drive or cloud bucket. We have a strict store-nothing policy: no backups ever touch or reside on Restora's servers. Your credentials and backups remain entirely yours.

Open the Coverage Report on your dashboard. It lists what's in your latest backup — databases, rows, pages, views, relation links, files, comments, and the scope you selected — as counts with named exceptions, never a percentage. If a file was skipped you get its name, its size, and the reason: over your plan's per-file cap, or a download that failed and will probably succeed on the next run. Those two are listed separately, because only one of them is a limit. If something couldn't be read, it says so rather than rounding it into a green check — and a backup taken before a given check existed reads unknown, not zero. It's free, on every backup.

A restore creates new databases, so page IDs change and old links and automations break. Not restored: edit history, and timestamps and authors (reset to restore time). Comments are replayed, as new comments authored by the Restora integration with the original author named — but resolved threads and comments anchored to selected text can't be re-anchored. People values are restored when the person still resolves or an exact email match exists in the destination, and named in the report when they don't. Custom emoji are matched by name in a different workspace, falling back to the emoji's image; ambiguous names are never guessed. Also not restored: files over your capture cap (20MB per file on Free, 150MB on Pro), page- and feed-layout views (table, board, list, calendar, timeline and gallery all restore), sharing and permissions, and multi-column layouts. Restoring any file over 5MB needs the destination workspace on a paid Notion plan. Backups over 80MB restore via a background job from your Drive or S3 rather than in the browser. The full list is shown in-app before every restore.

Both. Restora backs up your databases (all rows, properties, relations, rollups and views) and your pages — wiki pages, dashboards and nav pages. The pages you select come back with their hierarchy rebuilt between them. The one thing Notion's API can't recreate is a database embedded on a dashboard page; Restora restores that as a clear link to the rebuilt database instead, so nothing is silently lost. (A view deleted in Notion's UI also can't be detected — that's a Notion API limit, not a Restora one.)

Only if you select them too. Each page is its own item in the picker, so ticking a parent page backs up that page alone — its sub-pages and any databases inside it are listed separately. Every row with children has a “+ N inside” button that selects the whole branch in one click, and “Select everything” backs up every database and page you've shared with Restora. If you do leave a sub-page out, the restored parent page says so with a note where that sub-page used to be — nothing goes missing silently. The free CLI does the same with restora backup --all.

You can, and it works — until it doesn't. A manually duplicated workspace is only as fresh as the last time you remembered to do it, it's still inside Notion (so a Notion-side outage, ban or account issue takes both copies with it), and it's one snapshot, not a history — you can't go back to last Tuesday. Restora runs automatically on a schedule, stores your backup outside Notion (your own Drive or S3), keeps a full point-in-time timeline so you can restore any past version, and lets you restore just one database or page instead of the whole workspace.