Grouped by destination bucket. Hover for hover-state. Status reflects what's actually been copied so far. Pending = will be picked up in the next pass.
The duplicate tool doesn't accept a parent. The 53 pages currently live next to their originals in the old hubs. Cleanup pass = move each into its assigned bucket landing inside the new OS 2026 hub.
Each card below is a workflow I can launch right now. Or you can sanity-check the mapping above first and tell me what's wrong before I run another pass.
You wanted a new Notion "Teamspace" — like Drive's NEW STRUCTURE. Notion API can't create teamspaces (admin/UI action only), but the practical effect is the same: the Nordic Pirates — Operating System 2026 page is a self-contained hub with its own 6 bucket pages + 4 DBs. After cleanup, it works exactly like a teamspace.
If you want it to be a literal Teamspace (with its own sidebar entry, member roster, permissions): 30 seconds in the Notion UI. Click + Add teamspace → name it "Operating System 2026" → drag the OS 2026 page into it. Members and permissions live there.
Tell me when you want me to walk you through the click path, or just do it from the sidebar.
Completely untouched. Every file, every page, every database still lives at its original ID. You can work in either world today — old or new — without breaking the other.
The plan: when the deep-pass is done + you've spot-checked the new structure for a week, we set old folders to read-only (or move to 99 - Archive). Cutover happens on your signal, not automatically. Nothing destructive.
When you say cutover, we lock old structure. Until then it stays live.