A team imports its Notion wiki into Confluence and sees the page titles arrive. Then someone opens a private hiring document, a database is only a table and a comment has moved away from the sentence it discussed. The archive transferred, but the working system did not. A useful migration plan checks content, people and access as separate deliverables.
Define the knowledge base you are moving
Start with an inventory of teamspaces, shared pages, private material, attachments and database-dependent work. Assign a business owner to each area. Mark whether it should move, remain available as an archive or be replaced by another workflow. This inventory is a recommended migration control, not an output the importer guarantees.
Notion exports only content the exporting user can access. Other users' private pages are not automatically included, and teamspace settings can also affect coverage. Compare the planned inventory with the actual export. A workspace owner running an export is not proof that every page in the organization is present.
Include linked operating processes in the inventory. A team might use a database to manage approvals, track owners or publish a filtered customer view. Copying its visible content is not the same as preserving those operations. Ask the owner what must still work after the move.
Export HTML with the intended scope
Notion supports HTML export for pages and databases. For a selected page, turn on Include subpages when its children are in scope. The downloaded ZIP contains HTML files, with subpage folders and associated assets. For a workspace export, select the workspace export action and choose the appropriate format. Use HTML for the Confluence Notion import route described here.
Record which account produced the archive, its export scope and the extraction date. Keep a protected copy of the original ZIP. If content changes before cutover, identify the changed areas explicitly. Do not assume a later import will update earlier pages without duplication. Prove repeat-import behavior in a test area before relying on it.
Notion's database export lets users choose the current view or the default view, not all views at once. Capture the intended view coverage in the inventory. Do not use a successful file download as evidence that every view and workflow has been preserved.
Use the Notion importer in Confluence Cloud
Atlassian's importer requires a Notion workspace owner and create space permission in Confluence. In Confluence, open Spaces, Import from other tools, then Notion. Choose an entire workspace or a selected page with subpages and upload the Notion ZIP. This guide addresses Confluence Cloud, not a separate Data Center migration process.
Transferring users requires an organization admin. The user mapping step uses Notion authorization to map people on content such as mentions, comments, creator and editor information. Select the same content during authorization that was included in the uploaded file. An archive and an authorization selection covering different pages create a scope mismatch.
Decide how people and permissions will transfer
User mapping, adding remaining members and copying page permissions are separate choices. Enabling Add remaining members to Confluence creates accounts for Notion members without matching accounts. Atlassian warns that those users are added to the plan when the import starts and may affect billing. They do not automatically receive invitation emails. Review the proposed membership change before starting.
Notion guest accounts are not imported. Build a separate guest access list with an owner and approved destination spaces. Avoid turning former guests into broad internal members simply to make their names appear on content.
Copying Notion page permissions requires an access token. Atlassian states that permissions map at Start import, not at the earlier ZIP upload. Record the review point and avoid changing source permissions during that interval without reassessing the result.
Each Notion teamspace becomes a Confluence space. Available restriction choices include Restricted to you, Default space permissions and Notion permissions when the permission-copying step was selected. Default permissions can expose private content if the organization uses open defaults. Restricted to you is a cautious starting choice, but Atlassian says pages and comments under that option are labeled as created by the importing user. Agree that authorship tradeoff before selecting it.
Test content transformations explicitly
| Source content | Documented behavior | Acceptance check |
|---|---|---|
| Headings, lists and table data | Supported formatting | Compare structure and readable content |
| Inline comments | Become page comments | Check whether the discussion still makes sense |
| Database child page properties | Become table content | Test the replacement operating workflow |
| Mermaid diagrams and equations | Plain text | Provide an approved readable replacement |
| Buttons and synced blocks | Unsupported | Rebuild required behavior or record the exclusion |
| Reminders | Become dates | Check any required follow-up mechanism |
Atlassian also lists attachments, images, page links and several embedded content types among supported content. Supported does not mean every external dependency will remain usable by every target user. Open important files and linked pages using actual reader accounts. Confirm that readers have the intended access to the destination and any external service.
Private and shared page coverage needs special attention. Atlassian describes importing private and shared pages created by the importing user into a restricted private space, while pages not created by that user are not created under that rule. Reconcile those exceptions against the source inventory. Do not summarize this as universal private-page preservation.
Validate before moving daily work
- Reconcile expected pages against imported pages and explain every missing area.
- Open representative parent and child pages, attachments and cross-page links.
- Check comments, mentions and author labels with content owners.
- Test allowed and denied access using ordinary employees and guest scenarios.
- Ask each team to perform its real knowledge-base tasks in the target.
- Record unsupported features and approve replacements before cutover.
Review the import completion email for errors and partial failures. Treat it as a transfer report, not a security or functional sign-off. Keep unresolved exceptions in one migration register with the source page, target page, owner and next action. This makes a missing attachment different from a blocked permission and prevents both from disappearing into a generic completed status.
Cut over the wiki with an edit plan
Set a clear point when new edits move to Confluence. Capture source changes made after the validated export and reconcile them before announcing the new location. Keep Notion available under the agreed archive policy until owners accept the target. If access tests fail, hold the affected area closed instead of opening the entire space to get around a missing permission.
Common mistakes include importing with open defaults, overlooking other users' private pages, assuming databases preserve their behavior and rerunning archives without checking duplication. These are operational decisions around the tool, not problems an import progress bar can resolve.
How Remqa helps with knowledge-base migrations
Remqa helps teams plan and execute data migrations with explicit scope, validation and cutover checks. For Notion to Confluence, a practical starting point is a representative content area containing private pages, files and database-backed work. See our broader migration services, or walk an engineer through the pages and workflows your team cannot afford to lose.