Import From Notion

Bring a Notion export in as pages: what comes across, what changes and what is left out.

Applies To

liveknowledge

Moving from Notion? Export your pages from Notion as Markdown, and liveknowledge reads the export as a page tree.

Export From Notion

In Notion, open Settings, then Export.

Choose the format Markdown & CSV, include subpages, and export. Notion gives you a .zip. Keep it zipped.

Import It

In liveknowledge, press the Knowledgebase's name at the top of the sidebar and choose Import.

Choose A Whole Knowledgebase, then Notion.

Drop the .zip on the drop area, or press Choose a .zip.

Review what was found, choose where it lands, and press the Import button, which counts the pages (such as Import 320 Pages). The review and the choices are the same for every source: see Import From a Markdown Folder.

Import, A Whole Knowledgebase: Notion is one of the three sources.

What Comes Across

In NotionIn liveknowledge
Pages and their nestingPages and subpages, without Notion's 32-character ids
A page's titleIts first # heading, else the file name, id removed
Links between pagesPage links
A databaseA table on its page
A calloutA quote
A toggleA heading with its content under it
Pictures in the exportPictures in the writing
Other attachmentsNamed at the foot of the page under Attachments

Good to Know

  • A toggle comes across as a heading only where Notion's export writes it as a toggle. One it writes as a plain list item stays a list item: nothing in the export tells the two apart.
  • A link to a page you did not export stays an ordinary link.
  • Imported pages are Never Verified, owned by nobody.
  • The limits are the same for every source: 200 MB an archive, 500 pages in a Knowledgebase, 8 levels, 10 MB a picture. See Import From a Markdown Folder.
  • The CLI imports a Notion export too: liveknowledge import notion-export.zip --source notion --to Handbook.

Who Can Do What

ActionEditorParticipantViewer
Import from NotionYesNoNo

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us