[GH-ISSUE #7227] [FR] Import individual notion pages (with both .html and assets folder) as alternative to workspace import #3200

New issue

Open

opened 2026-03-23 21:28:20 +00:00 by mirror · 0 comments

mirror commented

2026-03-23 21:28:20 +00:00

Owner

Originally created by @MarcusDelvecchio on GitHub (Jan 16, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7227

Description

Considering it seems like a common experience where Notion workspace exports often fail to complete successfully (I have been waiting for mine for hours), implementing an alternative import method would be highly valuable.

Providing support to import the .html file alongside its corresponding assets folder—or offering a workaround to treat the exported .html file and assets as a single-file workspace—would significantly improve usability. Currently, I can export a single Notion page as a .html and an associated assets folder. While importing the .html file into AppFlowy is possible, the assets are not included, which leads to incomplete imports.

This limitation is hindering my ability to effectively migrate to AppFlowy as a viable alternative to Notion. Given Notion’s challenges with data export and the current dependency on its slow and unreliable export service, a robust alternative import method would enhance the migration experience.

Impact

Users interested in transitioning from Notion to AppFlowy face significant barriers due to Notion’s unreliable export process. Without the ability to fully import workspace data—including assets—into AppFlowy, the platform cannot function as a true drop-in replacement for Notion, especially for those who rely on rich media content in their notes and projects.

Additional Context

A similar feature request was previously raised here, but it was closed in favor of the current workspace import functionality. However, this specific request adds value by addressing the need for alternative import mechanisms. I have also left comments on the referenced thread to further highlight this issue.

In summary, introducing a method to import .html files with their corresponding assets folder or a workaround for treating these exports as single-file workspaces would significantly enhance the platform's accessibility and ease of migration for new users.

Originally created by @MarcusDelvecchio on GitHub (Jan 16, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7227 ### Description Considering it seems like [a common experience](https://www.reddit.com/r/Notion/comments/mpt7aj/your_data_is_stuck_in_notion/) where Notion workspace exports often fail to complete successfully (I have been waiting for mine for hours), implementing an alternative import method would be highly valuable. Providing support to import the `.html` file alongside its corresponding assets folder—or offering a workaround to treat the exported `.html` file and assets as a single-file workspace—would significantly improve usability. Currently, I can export a single Notion page as a `.html` and an associated assets folder. While importing the `.html` file into AppFlowy is possible, the assets are not included, which leads to incomplete imports. This limitation is hindering my ability to effectively migrate to AppFlowy as a viable alternative to Notion. Given Notion’s challenges with data export and the current dependency on its slow and unreliable export service, a robust alternative import method would enhance the migration experience. ![Example of Exported HTML and Assets Folder](https://github.com/user-attachments/assets/58d3408b-c86d-434a-8602-8d2cef1c92f5) ### Impact Users interested in transitioning from Notion to AppFlowy face significant barriers due to Notion’s unreliable export process. Without the ability to fully import workspace data—including assets—into AppFlowy, the platform cannot function as a true drop-in replacement for Notion, especially for those who rely on rich media content in their notes and projects. ### Additional Context A similar feature request was previously raised [here](https://github.com/AppFlowy-IO/AppFlowy/issues/2911), but it was closed in favor of the current workspace import functionality. However, this specific request adds value by addressing the need for alternative import mechanisms. I have also left comments on the referenced thread to further highlight this issue. In summary, introducing a method to import `.html` files with their corresponding assets folder or a workaround for treating these exports as single-file workspaces would significantly enhance the platform's accessibility and ease of migration for new users.

Rows
Columns