-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Space - Import from other tools (3rd party)
-
None
-
1
-
Severity 3 - Minor
Issue Summary
When importing a Notion HTML ZIP export into Confluence, the import process completes and displays a "partial success" status, but no pages, spaces, or attachments are created. The user receives a generic email stating "we couldn't get content from your export file" with no explanation of what went wrong or how to recover. The issue occurs repeatedly across multiple attempts.
Steps to Reproduce
- Export a Notion workspace or teamspace as an HTML ZIP file (issue could possibly occur on larger exports 16+ GB))
- Go to Confluence → Settings → Import data → Notion
- Upload the ZIP file without any modification
- Wait for the import to complete
- Import displays "partial success" in the UI
- No pages, spaces, or attachments appear in Confluence
Expected Results
- Content from the Notion export appears in Confluence after a successful or "partial success" import
- If the import fails, the user receives a clear error message explaining what went wrong
- Actionable recovery steps or guidance are provided to the user
Actual Results
- Import status shows "partial success" in the UI
- No pages, spaces, or attachments are created in Confluence
- User receives a generic email: "we couldn't get content from your export file"
- No diagnostic information or recovery steps are provided
- Issue repeats across multiple retry attempts
- Smaller exports (1–8 GB per teamspace) appear more reliable
Workaround
Exporting individual Notion teamspaces separately in smaller ZIPs, rather than bulk exporting the entire workspace, has been reported as more reliable. This is a partial mitigation only — not a guarantee.