How to bring your Notion workspace into Nexus in under an hour

The biggest reason teams don't switch knowledge tools isn't price or features — it's the cost of moving years of documentation. We've tried to make that cost as low as possible.

What imports cleanly

Paste any Notion page URL into the Nexus import dialog and it arrives as a native Nexus document. Paragraphs, headings, bullet and numbered lists, checkboxes, code blocks, quotes, tables, and images all transfer. Inline formatting — bold, italic, code, links — comes through as you'd expect.

Nested pages work too. If a Notion page has sub-pages, Nexus creates child nodes for each one, preserving the hierarchy. You can import a top-level Notion section and get the full tree in one pass.

What to watch for

A few Notion-specific constructs don't have a direct Nexus equivalent yet. Databases with filtered views, rollup properties, and relation columns don't import — these are structured data features we're building toward. If you rely heavily on Notion databases, you'll want to export those separately as CSV while you're transitioning.

Synced blocks also don't carry over — they arrive as static copies of their content at import time, which is usually what you want anyway.

The practical workflow

For most teams, the simplest approach is to import section by section rather than all at once. Start with your most-used pages — the docs your team touches every week. Get comfortable with the Nexus structure. Then import older reference material in batches.

Don't try to recreate your Notion structure exactly in Nexus. Use the import as an opportunity to clean up. Move things that belong together into the same teamspace. Archive pages that haven't been touched in a year. A fresh structure in Nexus is often worth more than a faithful copy of the old one.

The goal isn't to have Notion in a different interface. It's to have a workspace that works the way you actually think.