Import failing silently / No data after import (Notion & Confluence)

Last updated: June 15, 2026

If your Notion or Confluence import completes without errors but no data appears, the most common cause is a nested ZIP file structure in the export.

Why this happens

Notion and Confluence exports often contain a nested ZIP file inside the main export ZIP. Plane's importer expects the inner ZIP, not the outer one. If you upload the outer ZIP directly, the importer has nothing to work with and completes silently.

The Fix - Extract and upload the inner ZIP

  1. Download your export ZIP from Notion or Confluence

  2. Extract it

    unzip your-export.zip

  1. Look inside the extracted folder. You should find another ZIP file

  2. Upload that inner ZIP file to Plane

Still not working? Check for __MACOSX Issues

If you extracted and re-zipped the contents using Mac's built-in zip tool before uploading, that could be the problem. macOS often adds __MACOSX metadata folders when zipping, which can confuse the importer.

To check what's inside your zip before uploading:

unzip -l file.zip

If you see __MACOSX entries or another zip listed inside, your zip was created incorrectly. In that case, go back to the original downloaded export and extract that instead, don't re-zip anything.

For self-hosted instances

If you're on a self-hosted instance and the above steps haven't resolved it, check that your Silo service has the correct S3 credentials configured. Specifically, make sure AWS_REGION and your other S3-related environment variables are set correctly in the Silo container. Missing or incorrect S3 credentials will cause the importer to fail silently when trying to upload extracted files.

Still having trouble?

Reach out to support with:

  • The output of unzip -l file.zip

  • Which tool you're importing from (Notion or Confluence)

  • Your workspace slug (Plane Cloud) or the Silo container logs (self-hosted Plane instance) around the time of the import attempt