Get your Notion roadmap into Roadmap OS in under an hour. Keep Notion for everything else.

If you've been running your product roadmap in a Notion database, this guide gets your data into Roadmap OS in under an hour.

The migration philosophy

Don't leave Notion entirely. Notion is excellent for documentation, meeting notes, specs, and team wikis — keep using it for those. We're migrating only the roadmap database, not your whole knowledge base.

After migration:

Notion → docs, specs, meeting notes, wiki
Roadmap OS → roadmap, capacity, plans, products, feedback

Each Roadmap OS initiative has a "Documents" field where you can link the matching Notion spec URL. The two tools work together.

Step 1: Export your Notion roadmap database (5 minutes)

In Notion:

Open your roadmap database
Click the ... menu → Export
Choose CSV (or Markdown + CSV — we'll use the CSV)
Download the ZIP and unzip — you'll have a .csv file

Step 2: Map your Notion fields to Roadmap OS (10 minutes)

Open the CSV. Your columns probably look something like:

Notion column	Roadmap OS field
Name	Initiative name
Status	Status
Priority	Priority
Pillar / Theme / Section	Section
Owner / Assignee	Owner
Start Date	Date range start
End Date	Date range end
Description	Description
Labels / Tags	Labels

If your Notion statuses don't match Roadmap OS statuses (Strategy / In Progress / Released / At Risk / Delayed), you'll be prompted to map them during import.

Step 3: Import into Roadmap OS (5 minutes)

In Roadmap OS:

Go to Roadmap → ⋮ menu → Import
Click From Notion CSV
Upload your .csv file
The import wizard auto-detects columns; review the mapping
Click Import

Up to 500 initiatives import in under a minute. Bigger imports take 2-5 minutes.

Step 4: Reconcile what didn't import cleanly (10-30 minutes)

Common issues:

Statuses with custom names

Notion users often have statuses like "Doing," "Shipping Soon," "Iceboxed." Map them to Roadmap OS's 5 statuses during import.

Hierarchical pillars

If your Notion roadmap had nested groups (e.g., "Mobile / iOS / Onboarding"), Roadmap OS uses flat sections. Decide which level becomes the section.

Custom fields

Notion lets you add arbitrary properties. Roadmap OS has a fixed schema for initiatives. Custom fields go into the "Description" or "Labels."

Missing dates

Initiatives without start/end dates default to the current quarter. Edit them manually after import if needed.

Step 5: Connect Notion specs to initiatives (15 minutes)

For each initiative that has a corresponding Notion spec page:

Open the initiative in Roadmap OS
Click + Add document
Paste the Notion spec URL
Save

Now your roadmap and your specs are linked. Stakeholders see the roadmap in Roadmap OS, click through to the spec in Notion.

Step 6: Archive your Notion roadmap database (don't delete)

Don't delete the Notion database for at least 90 days — keep it as a backup in case you need to reference history.

In Notion:

Move the database to an "Archive" page
Add a header note: "Migrated to Roadmap OS — not actively maintained as of [date]"
Keep read access for the team

What gets better after migration

Sort by priority without losing your section structure (Notion can't do this reliably)
Today line on the timeline — see what's slipping in 5 seconds
Capacity check next to roadmap — know if your team can ship before you commit
PDF / PPT export for board reviews
Audit log — every roadmap change is tracked

What stays in Notion

All your specs, PRDs, meeting notes, knowledge wiki
Anything that's not a roadmap database

Common pattern after migration:

Each Roadmap OS initiative links to its Notion spec
Each major customer-facing decision lives as a Notion doc, linked from Roadmap OS

Get help

If your Notion database is messy and the import doesn't go cleanly, email sabelo@roadmapos.com. I personally help with migrations for paying customers — usually a 30-minute screenshare resolves it.

Migrating from Notion