Move a Confluence space, or individual pages, into a Dokki workspace.
What arrives
From Confluence | In Dokki |
|---|---|
Page or blog post | An editable Dokki document, with a link back to the original at the top |
Attachments | Stored files you can open and search |
Headings, bold, italic, inline code, links | Kept |
Tables | Kept as tables |
Images placed in a page | Kept |
Numbered and bulleted lists, including nested ones | Kept, with numbering and indent levels |
Code blocks | Kept, with the language still set |
Info, note, warning, and tip panels | Kept as quoted callouts |
Task lists | Kept as checklists |
What does not come across:
Not imported | What to do |
|---|---|
The page tree | Pages arrive side by side in the folder you chose. Rearrange them in the sidebar afterwards. |
Links between Confluence pages | The link text is kept, but it will not open the other page. Re-link the ones that matter after everything has landed. |
Comments | Copy any that still matter into the document body before you migrate. |
Page labels | Add Dokki tags after import. |
Page restrictions and permissions | Set up sharing in Dokki after import. Nothing is shared until you share it. |
Version history | The Dokki copy starts fresh. Keep the Confluence space read-only for a while if you may need to look back. |
Other macros keep the text inside them, but lose the special display. A table-of-contents macro produces nothing, because its content was generated from the page.
Import a space
The pages land wherever you start from, so begin at the folder you want them in.
In the sidebar, point at the folder you want the pages to land in and select the + beside it. To import into the top level of the workspace, use the + at the top of the sidebar instead.
Choose Import….
Under Source, choose Confluence, then connect your Atlassian account or pick a connection someone has already set up. Connections are added and reconnected under Manage sources.
Under What to bring in, choose the space you want.
Under After importing, choose Copy once — that is what a migration wants. Keep in sync keeps pulling changes from Confluence and can overwrite edits made to the Dokki copy.
The bottom of the dialog shows where the content will land. Check it, then select Import.
The results view lists every page and attachment as it is processed. Completed items link straight to the new Dokki resource.
Import a single page
At What to bring in, paste the page's Confluence URL instead of choosing a space. Use this to see the result on one representative page before committing to the whole space.
Try one page first
Pick the ugliest page you have — the one with a wide table, a couple of screenshots, and a code block — and import just that. Open it next to the original. You will know within a minute how much tidying the full space will need, and which pages deserve a manual pass.
Who can do this
You need permission to edit the destination Dokki workspace, and an Atlassian account that can read the space. Workspace admins manage shared connections; other members can import when their workspace role allows it.
If something fails
Open the failed item's error details before retrying. Running the same import again does not clear the original cause.
Reconnect the Atlassian account if authorization has expired.
Confirm you can open the page in Confluence and edit the destination workspace in Dokki.
Files larger than 50 MB are skipped. Attach those manually.
A large space takes time. Watch the results view rather than starting the import a second time.