Notion Workspace Migration Plan

One-time migration tasks: create the new SecurityV0 Notion workspace (notion-securityv0) with correct structure from the start, then migrate content from existing workspaces. Once complete, this document should be archived.

For the permanent operating workflow (how ideas flow from Notion → PRD → GitHub → Ship), see SV0 Workflow Plan.

Migration Approach

Instead of reorganizing existing workspaces in-place, we create a new workspace with the correct structure and pull data from both source workspaces.

MCP Server	Workspace	Role
notion-sergey	Sergey's existing workspace	Source — read existing pages, feedback, strategy docs
notion-securityv0	SecurityV0 (new)	Target — correctly structured from day one

Migration is done interactively via Claude Code using both Notion MCP servers — no custom scripts needed. The old scripts/notion-sync/ infrastructure has been archived.

Current State

Workspace Tree (as of 2026-03-16)

🏠 WORKSPACE ROOT
├─ 📄 Product (root)
│  ├─ 📄 Sprint: 2026-02-25 – 2026-03-12  ← only sprint, no older/newer
│  │  ├─ 📄 Clarity: so what?/ what do i do now?
│  │  │  ├─ 📄 Authority Path Page — Required Changes (Spec Only)
│  │  │  ├─ 📄 Risk Cluster / Authority Exposure Brief — Eng Feedback 2026-03-10
│  │  │  ├─ 📄 UX Details: Overview page (Authority Prioritization)
│  │  │  ├─ 📄 UX Details: Authority Path Detail (Authority Evidence)
│  │  │  └─ 📄 UX Details: Authority Exposure Brief
│  │  ├─ 📄 Actionability and remediation guidance (W1)
│  │  └─ 📄 Drift intelligence (W1)
│  │     └─ 📄 Drift UX
│  ├─ 📄 Authority Paths - Primer
│  ├─ 📄 Wedges - Feb 2026
│  ├─ 📄 Foundry Agent → LLM → Azure App Logic → ServiceNow
│  ├─ 📄 Setup steps in SN / Azure
│  ├─ 📄 ServiceNow + Azure Automation: Scheduled Job
│  ├─ 📄 Demos
│  │  └─ 📄 2026-02-23
│  ├─ 📄 W1: Agentic AI exposure discovery & assessment
│  ├─ 📄 W2: AI Product Approval Gate
│  ├─ 📄 W3: Control plane for NHI in autonomous systems
│  └─ 📄 Mapping to OWASP Top 10 for Agentic Applications
├─ 📄 Partner & Customer Space
│  ├─ 📄 Partner Questionnaire
│  └─ 📄 Securityv0 Deployment Integration Requirements
└─ 📄 AI Exposure Incident Monitor

Orphaned Pages (17 pages — parents not shared with integration)

These pages are accessible but their parent pages are not, making them appear disconnected:

Category	Pages	Last Edited
GTM / Strategy	GTM Plan, ICP, Q1 Wedges, Q1 customer/partner GTM, Eng Implications	2026-03-13 – 2026-03-16
Assessments	Inetum: NHI & Automation Exposure, ServiceNow Workflow Exposure, Internal Wedge: ServiceNow Automation	2026-03-15
Partner	3. Deloitte-internal Q&A, Reviewer Feedback — Assessment Response	2026-03-14 – 2026-03-16
UX Feedback (historical)	6x UX Feedback pages (2026-02-20 through 2026-02-23)	2026-02-27
General Feedback	Feedback (container), 2026-02-12 feedback	2026-02-16 – 2026-03-13

Problems Identified

P1: No idea/feedback lifecycle tracking

UX feedback pages have no status field. There's no way to know which items were adopted, deferred, rejected, or superseded. The 6 UX Feedback pages from Feb 20-23 mix font suggestions, layout changes, interaction patterns, and data model questions — all with equal weight and no resolution markers.

P2: Flat structure with no databases

Everything is pages. No Notion databases are used — no filterable/sortable views, no status properties, no structured fields.

P3: Orphaned content from missing parent pages

17 pages (39% of all content) have parents that aren't shared with the integration. This creates a disorienting flat list when querying via API.

P4: Mixed content types in "Product" root

The Product root is a catch-all: product strategy, sprint planning, technical references, demo materials, and UX specifications — no separation between reference material and active work.

P5: Naming inconsistencies

• Trailing spaces in titles: "Sprint: 2026-02-25 - 2026-03-12 ", "UX Feedback 2026-02-20 "
• Inconsistent date formats
• Missing prefixes/tags to indicate content type
• Informal titles that don't describe the content

P6: Stale sprint container

Only one sprint exists (2026-02-25 – 2026-03-12), already past its end date. Sprint tracking belongs in GitHub Projects — this page should be archived, not replaced.

Migration Tasks

Task 1: Create the SV0 Ideas database

Create the SV0 Ideas database in the new notion-securityv0 workspace. This is the single database for all ideas, feedback, and feature requests — as defined in SV0 Workflow Plan.

Property	Type	Values
Title	title	Idea name
Status	select	💡 Idea, 🔬 Research, ✅ Approved, 🏗️ Building, 🚀 Shipped, ❌ Killed
Owner	person	CEO / Ivan / Dev
Source	select	Brainstorm, Meeting, Customer, UX-Review, Research, Slack
Category	multi-select	Platform, Connectors, UI, Infra, GTM
Notes	text	Decision rationale, links, research doc links, context
Meeting Link	url	Granola meeting link (if from a call)

7 properties. 6 statuses. Feedback items use Source: UX-Review. No separate Feedback Tracker needed.

Task 2: Backfill existing content into SV0 Ideas

Migrate existing feedback and ideas into the new database:

• 6 UX Feedback pages (2026-02-20 through 2026-02-23) → split compound pages into individual rows with Source: UX-Review
• Engineering Feedback (2026-03-10) → individual rows with Source: Research
• Feedback container page → archive (only 1 child, blank content)
• Existing research docs from sv0-documentation → create rows linking to the git docs

For each backfilled item, set the appropriate status based on whether it was already implemented.

Task 3: Create the page hierarchy in notion-securityv0

🏠 SECURITYV0 WORKSPACE
├─ 📊 SV0 Ideas [DATABASE]                  ← all ideas/feedback as queryable rows
│
├─ 📁 Product Strategy                     ← long-lived reference material
│  ├─ 📄 W1: Agentic AI exposure discovery & assessment
│  ├─ 📄 W2: AI Product Approval Gate
│  ├─ 📄 W3: Control plane for NHI in autonomous systems
│  ├─ 📄 Wedges - Feb 2026
│  ├─ 📄 Authority Paths - Primer
│  ├─ 📄 Mapping to OWASP Top 10 for Agentic Applications
│  ├─ 📄 ICP
│  └─ 📄 GTM Plan
│
├─ 📁 Technical References                 ← setup guides, integration docs
│  ├─ 📄 Foundry Agent → LLM → Azure App Logic → ServiceNow
│  ├─ 📄 Setup steps in SN / Azure
│  └─ 📄 ServiceNow + Azure Automation: Scheduled Job
│
├─ 📁 Partner & Customer Space             ← (keep existing)
│  ├─ 📄 Partner Questionnaire
│  ├─ 📄 Securityv0 Deployment Integration Requirements
│  ├─ 📄 Deloitte-internal Q&A
│  └─ 📄 Reviewer Feedback — Assessment Response
│
├─ 📁 Demos                                ← demo materials
│  └─ 📄 2026-02-23
│
└─ 📄 AI Exposure Incident Monitor          ← (keep at root)

Task 4: Grant integration access

• Add the notion-securityv0 integration to all top-level pages in the new workspace
• Invite Sergey and Ivan as workspace members
• Configure bot access: update 1Password op://sv0-bots/notion-integration/credential with the new workspace token

Task 5: Clean up source content during migration

• Fix trailing spaces in page titles when copying to the new workspace
• Standardize date formats
• Do NOT migrate the stale sprint container page (sprint tracking lives in GitHub Projects)
• Do NOT migrate the empty "Feedback" container page

Task 6: Decommission old workspace access

After migration is verified:

• Remove old notion-sergey MCP server config (read access no longer needed)
• Archive old workspace or keep as read-only reference
• SV0 Ideas database content (PRDs, idea status) stays in Notion only — accessed via Notion MCP, no local sync needed

Quick Wins (can be done before full migration)

1. Fix trailing spaces in page titles
2. Share orphan parent pages with the Notion integration
3. Archive the "Feedback" container page — only 1 child, blank content
4. Archive the stale sprint page — sprint tracking lives in GitHub Projects