Confluence works well as an internal wiki, but public-facing product documentation benefits from a faster, branded, AI-native site. This guide moves your Conflue...
Confluence works well as an internal wiki, but public-facing product documentation benefits from a faster, branded, AI-native site. This guide moves your Conflue...
Confluence works well as an internal wiki, but public-facing product documentation benefits from a faster, branded, AI-native site. This guide moves your Confluence spaces into Doxbrix — converting pages, macros, and attachments into Doxbrix blocks and a clean navigation structure.
Who this is for
Teams whose documentation lives in Confluence and who want a dedicated docs site with custom branding, public access control, AI Ask, and review workflows.
What carries over
| Confluence | Becomes in Doxbrix |
|---|---|
| Space | A [space](/organize/spaces-and-navigation) or project |
| Page tree | [Groups](/organize/spaces-and-navigation) and pages |
| Headings, lists, tables | Native blocks |
| Info / Note / Warning panels | [Callouts](/write/blocks-and-components#callout-blocks) |
| Expand macro | [`<Accordion>`/`<Expandable>`](/write/blocks-and-components#accordion-and-expandable-blocks) |
| Code macro | Fenced code blocks |
| Attachments & images | Uploaded media |
Step 1 — Export from Confluence
In Confluence, go to Space settings → Content tools → Export.
Export to HTML (most complete) or, if available, Markdown. Include attachments.
You'll get a .zip containing your pages and a folder of attachments.
Step 2 — Import into Doxbrix
Import the exported folder:
# Import an exported space (HTML or Markdown)
dxb import repo ./confluence-exportOr use Import document in the app for individual pages. Doxbrix converts each page to a draft, maps the page tree to groups, and uploads attachments. See Import files.
Step 3 — Convert Confluence macros
Confluence's macros are its trickiest export artifact. After import, upgrade them:
Info/Note/Tip/Warning panels become the matching callout block.
Expand macros become <Accordion>.
Code macros become fenced code blocks; add the language for highlighting.
Status macros become <Badge>.
<Embed>, replace them with static content, or link out to the source system.Step 4 — Rebuild navigation
Confluence page trees are often deep and organic. Use the migration to create deliberate structure:
- Map major sections to spaces.
- Flatten overly deep nesting into clean groups.
- Drop outdated pages rather than carrying them over — migration is a good audit moment.
Step 5 — Handle access
If your Confluence space was internal, decide on Doxbrix visibility:
- Public for external product docs.
- Private with reader authentication (password, email domain, or SSO) to keep it internal.
Step 6 — Polish and publish
Run Scan with AI across imported pages.
Clean up converted prose with Improve with AI.
Brand and go live.