Features

Bring everything.
Keep it linked.

Import your Notion pages and databases with the tree intact, then let linked pages sync both ways on web while your team transitions at its own pace.

The pitch, honestly

Not a jailbreak.
A door that stays open.

Notion holds years of your team's knowledge, and pretending you will migrate in a weekend is how migrations fail. NoteX takes the calmer path: connect your Notion account, see your pages inside NoteX, and bring them over at whatever pace reality allows, hierarchy intact.

On the web surface, imported pages can even stay linked to their Notion originals while you transition, so nobody has to declare a hard cutover day.

PAGE
Team Wiki44 sub-pages · 6 levels
DB
Product wiki (database)128 rows · views preserved
PAGE
Meeting notes 2024-2026310 pages
68%
PAGE
Design system docsqueued
8%

A workspace import in progress: trees, icons, and databases arrive as themselves.

How import works

Your tree arrives
as a tree.

Connect with OAuth (or an integration token), and NoteX lists every page your integration can see, nested exactly as Notion nests them. Import one page, a branch, or everything. Icons, structure, and content convert to NoteX blocks; databases arrive as NoteX databases on the web surface.

Re-import a page later and it updates in place rather than duplicating, which makes gradual migrations sane.

From Notion · imported
📗Team Wiki
🧭Onboarding
📐Engineering standards
🗂️Product wikidatabase
📒Meeting notes

Two-way · web

Linked pages:
pull theirs, push yours.

On NoteX web, an imported page can stay linked to its Notion original. Pull to bring Notion edits in, push to send your NoteX edits back, and get a conflict flag when both sides changed so nothing silently overwrites. Teams run both tools during a transition, or keep one shared surface with a Notion-native partner team, without copy-paste diplomacy.

DirectionWhat happens
ImportNotion page becomes a NoteX pageBoth surfaces
PullNotion edits update the NoteX copyWeb
PushNoteX edits go back to NotionWeb
ConflictBoth changed: flagged, you decideWeb

Desktop imports one-way today; the linked push-and-pull loop is the web surface.

What survives the move

Content converts cleanly: headings, lists, to-dos, toggles, callouts, quotes, code, tables, images, and page nesting. Databases keep their rows, properties, and views on the web surface. What does not transfer from any tool: Notion-side permissions and comment history, which live in Notion's systems rather than in the pages. Plan for those separately; the migration lesson has a checklist.

And because NoteX's own API mirrors Notion's conventions, automations you built against Notion have a familiar shape waiting on the other side. See API & MCP.

Frequently asked questions

How do I connect my Notion account?

Through Notion's standard OAuth flow (sign in with your browser), or by pasting an integration token if your workspace prefers explicit integrations. NoteX sees only the pages you share with it.

Does the hierarchy really survive?

Yes. Pages import with their nesting, sub-pages, and icons preserved, so a six-level wiki lands as a six-level wiki, not a flat pile.

Do databases import?

On the web surface, yes: rows, properties, and views arrive as NoteX databases. Desktop imports pages and their content; open the web workspace for database-heavy imports.

Is two-way sync available on desktop?

Desktop import is one-way (Notion into NoteX), with re-import updating in place. The linked pull-and-push loop with conflict flags is the web surface.

What does not transfer?

Notion-side sharing permissions and comment threads stay in Notion; they are platform features rather than page content. Everything in the page body converts.

Your notes deserve a better engine.

A Notion-style block editor on the engine behind the world's most popular code editor. Notes stay files you own, extensions add what you need, and AI plugs in natively. Free to start, on web and desktop.

Free to start · Your files, your disk · Windows desktop & web