Aeion Workspace + Notion Import
Point the importer at a Notion integration token and it walks your whole page-and-database tree over the Notion API — recursive sub-pages, database schemas and rows, live progress, and a dry-run preview that writes nothing until you confirm. It's a one-shot migration built to move your content, not a live two-way sync. Full OAuth-based Notion connection is available through Aeion Singularity.
What Connects
`
Setup — Connect with a Notion Integration Token
The workspace import wizard authenticates with a Notion internal integration token, not an OAuth redirect:
Block Types — What Converts to Native Workspace Blocks
These Notion block types map to a native editor block, preserving structure and, where relevant, nested children:
Databases — Schema and Rows
A Notion database imports as a workspace database: its property definitions become workspace fields, and every row becomes a workspace record. Property-type mapping:
Dry-Run, Discovery, and Live Progress
Every import can preview before it commits, and long imports report progress as they run:
Also Real — CSV / Excel for Exported Tables
If part of your Notion workspace lives as exported CSVs or spreadsheets, the same import pipeline ingests them. CSV and Excel (.xlsx) imports are wired end-to-end: header detection with type inference, per-column field mapping, and transforms for date, number, boolean, array, and JSON values on the way in. Both target a workspace database and support the same dry-run preview.
FAQ
The workspace import wizard is token-based — you create a Notion internal integration, share your content with it, and paste its secret. That's the mechanism that ships in the module today. A full OAuth2 Notion connection (hosted authorize + token exchange) is available through Aeion Singularity, the platform's import hub.
Either. Leave the page and database lists empty and the importer calls the Notion Search API to discover everything your token can reach, then imports it. Or pass specific page/database IDs to scope the migration.
Yes — child pages import recursively (when sub-pages are enabled) and the parent/child relationships are rebuilt in Aeion. Each imported page also records its original Notion ID.
They're captured as a preserved text block rather than converted to a native table/embed/file block. Nothing is dropped, but plan on recreating a small number of tables or embeds after a large import. Comments are not imported.
Run a dry-run first — it reports counts and writes nothing. For live runs, database rows carry an external-ID key that makes them traceable and de-duplicatable; page-level re-import currently creates fresh pages rather than updating in place, so re-import a scoped set rather than the whole workspace when iterating.
No. It's a one-shot migration built to move your content into Aeion. There's no continuous polling or write-back to Notion.
Formula and rollup columns come across with their configuration captured and their current values populated. They don't re-run Notion's formula engine — recreate live calculations with Aeion's own formula engine (50+ functions, rollups across relations) after import.
Move your Notion workspace in one pass.
Whole-workspace discovery, recursive page + database import, dry-run preview, and live progress — token-based today, OAuth via Singularity.