Workspace migration

Move a Notion workspace into a different Notion workspace

Notion can duplicate a page. It cannot move a workspace. Restora rebuilds one inside another account — databases, relations, rollups, views and page hierarchy — and names anything that couldn’t come with it.

Backups are free. You only pay when you restore.

Why this is hard in the first place

Notion has no “move to another workspace” action for a whole workspace. The two official routes each cost you something:

Export and re-import

Markdown and CSV exports flatten the structure. Relations become plain text, rollups stop computing, views and filters are gone, and databases arrive as loose files you rewire by hand.

Rebuild by hand

Recreate every database, every property, every view, then re-link every relation row by row. It works. It also takes days, and every missed link is silent.

Restora takes the third route: it reads your backup and rebuilds the structure through Notion’s API in the destination workspace — creating the databases, restating the schemas, re-linking the relations, and recreating the views.

Measured, not claimed

What one real cross-workspace restore did

Run on 8 August 2026 against a purpose-built edge-case workspace — linked Projects, Tasks and People databases carrying self-relations, two-way relations, rollups computed from them, formulas, unique-ID columns and a file attachment. The destination was a separate Notion workspace that could not see the source: the destination’s own token returns 404 on the source database, which is how we know the rebuild used nothing but the backup file.

Databases rebuilt16 / 16
Views recreatedtable, board, list, calendar, timeline, gallery20 / 20
Relation links writtenincluding a self-relation and three two-way pairs across three databases13 · 0 dropped
Rollupsrecreated, then recomputed by Notion against the restored relations2
Standalone pagesnesting preserved under a single container page23
Blocks skipped0
Reported exceptionsthree unique-ID prefixes — see the list below3, each named

These are counts from one run on one workspace — not a benchmark, not an average, and not a promise about yours. Your workspace produces its own numbers and its own report naming anything that didn’t come across. We publish no percentages, because a percentage hides which item you lost.

How to move it

1

Back up the source workspace

Connect Notion and run a backup. It captures databases, rows, pages, blocks, views, relations and file bytes. Backups are free and unlimited, and they never modify the workspace they read.

2

Connect the destination workspace

Sign in to the workspace you’re moving into and share one page with Restora. That page becomes the parent for everything restored, so the copy lands somewhere you chose.

3

Restore into it

Restora rebuilds the databases, restates the schemas, re-links the relations in a second pass once every row exists, recreates the views, then rebuilds the page tree. You get a report naming every exception.

What crosses, and what doesn’t

A restore is a faithful rebuild, not a byte-for-byte clone — because Notion’s API genuinely cannot write some things. Here is the whole list. Any tool that gives you a shorter one is leaving something out.

Comes across
  • Databases and their full schemas
  • Every property type Notion’s API can write
  • Rows, in their original creation order
  • Relations — including self-relations and two-way pairs
  • Rollups and formulas, recomputed by Notion
  • Views with their filters, sorts and quick filters
  • Page hierarchy and nesting
  • Files and attachments, within your plan’s size cap
  • Standard emoji, page icons and covers
  • Status columns with their groups intact
Doesn’t — and why
  • Page IDs — everything is newly created, so old links and automations pointing at the originals break
  • Created and edited timestamps, and authors — Notion assigns these itself
  • Edit history — no API exists for it
  • Comments — captured and readable in your backup, but Notion’s API cannot write them back anywhere
  • People-property values — the column returns, empty
  • Sharing and permissions — not exposed by the API; the copy inherits the parent page’s sharing
  • Unique-ID prefixesTSK-42 comes back as 42, and the numbering restarts at 1
  • Custom workspace emoji — a different workspace has no such emoji to display
  • Page-layout views — the one layout Notion’s API still can’t create; named in the report
  • @-mentions of pages outside the backup — links to pages you did include are remapped to the copy; the rest still point at the source

Who moves a workspace

Splitting personal from work

One workspace grew into two lives. Move the work half into its own workspace and leave the personal one where it is.

Selling or handing over a business

The buyer needs the operating system, not your account. Rebuild it in theirs and keep your personal pages out of the deal.

Cloning a system for a client

Agencies and consultants rebuild the same setup per client. Restore one backup into each client’s workspace instead of rebuilding it each time.

Leaving a company

Take the pages that are yours to take into a workspace you own — before the account is closed.

One honest caution: only move content you have the right to move. Restora rebuilds whatever is in the backup you made — deciding what is yours to take is your call, not ours.

Questions

Does the original workspace change?

No. A restore only creates — it never edits or deletes anything in the source. The source workspace is untouched, so you can move first and clean up afterwards once you have checked the copy.

Do my relations survive the move?

Yes, for every relation whose target is also in the backup. Restora writes relations in a second pass, after all rows exist, so links between databases reconnect to the restored copies rather than pointing back at the source. Links to anything outside the backup are counted and named, never dropped silently.

Can I move only part of a workspace?

Yes — choose the databases and pages to include when you back up. Bear in mind that a relation pointing at a database you left out cannot be rebuilt; the report names each one, so you know exactly what you traded away.

Does the destination need a paid Notion plan?

Only for larger files. A free Notion workspace caps uploads at 5MB, so files above that are named as skipped and stay safe in your backup until you restore into a paid workspace. Everything else restores on a free plan.

Is this a sync between two workspaces?

No, and deliberately so. This is a one-time rebuild. Restora stores nothing of yours — backups go to your own Google Drive or S3, and a restore reads from that file. There is no ongoing connection between the two workspaces afterwards.

What does it cost?

Backing up is free. Restoring is paid — $6.99 a month, or a one-time $9.99 pass if you only need to move once. You can back up and inspect everything before paying anything.

Start with the backup

It’s free, it doesn’t touch your source workspace, and it tells you exactly what it captured before you decide to move anything.

Connect Notion — free