-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Space - Import from other tools (3rd party)
-
1
-
Severity 3 - Minor
Issue Summary
When importing a Notion export ZIP file into Confluence Cloud, the importer incorrectly identifies any file named index.html within the ZIP structure as the primary Notion index file. If a regular page or database export happens to be named index.html (which is common in Notion's HTML export format), the importer fails to create the space and content, even though the migration status in Dashboard reports "SUCCESS".
Steps to Reproduce
- Export a Notion workspace/page in HTML format.
- Ensure the resulting ZIP file contains an index.html file that is NOT the root index (e.g., a sub-page or database named "index").
- Upload this ZIP file to the Confluence Notion Importer.
- Run the import process.
Expected Results
The importer should correctly distinguish between the root Notion index file and other index.html files, successfully creating the space and all pages.
Actual Results
- The import process completes with a "SUCCESS" status in Dashboard.
- No Confluence space is actually created.
- The notification email is sent but lacks the "Go to space" link.
Workaround
Manually unzip the export, delete the problematic index.html file (ensuring it's not the actual root index), re-zip the folder, and then run the import.