Try or ByeTry or Bye

Tana Import Stuck or Imported Notes Missing

Workaround available Web, Mac, Windows, Linux Updated October 21, 2026

Quick answer

A stalled import usually means the export file is too large or has structures that time out; don't retry the same file, export a smaller part instead. If the import finished but the workspace looks empty, look in the Library or the daily pages.

Most likely fix: Import smaller chunks.

Symptoms

Import spinner runs for minutes, import fails, or the new workspace looks empty after importing from Notion, Roam, Logseq or Workflowy.

Why it happens

  • Notion export over 1,500 Markdown files
  • Complex structures that cause timeouts
  • Imported content placed in the Library or on daily pages
  • Roam imports always create a separate workspace

How to fix it

Try these in order — the most common fix is first.

  1. 1. Import smaller chunks

    1. Don't retry the same file
    2. Export a smaller section from Notion (Markdown or CSV)
    3. Import a few sections at a time

  2. 2. Find the imported content

    1. Open the new workspace's Library
    2. Check the daily page for the import date
    3. Search for a page title you know was imported

  3. 3. Use the right Roam import path

    1. In Roam choose Export all > JSON
    2. In Tana go to the User icon > Import content > Roam and drop the JSON
    3. Expect a new, separate workspace

  4. 4. Rebuild Notion relations

    1. Database relations aren't carried over
    2. Recreate them with supertags and instance fields after import

This guide also covers

  • tana import stuck
  • tana import notion
  • tana import roam
  • tana imported content missing

Still not working?

If Tana keeps failing, you're not alone. See every Tana problem users report or the alternatives people switch to.

Other Tana errors