Skip to main content
Your Confluence content lives in Collabase Docs, in Spaces your members already know, with the page tree they are used to. Collabase has no automatic importer for whole Confluence sites: you rebuild the structure and import the content page by page. Follow the phases in order. Every phase ends with a checkpoint and a link to the next one.

At a glance

Two ways bring the content of a page across. Choose per page in phase 1:
  • Confluence page import: the page body in Confluence storage format. Keeps Confluence macros such as info panels, code blocks and task lists. This is the default.
  • Word import: the page exported as a Word document. Use it when you cannot get the storage format.

Requirements

In Collabase

  • A system administrator account to create Spaces and add members.
  • Edit rights in each target Space for whoever imports the pages.
  • The document processor running. It ships with Collabase and converts the files. Without it the import fails, see Troubleshooting.

In Confluence

  • Read access to every page you move.
  • A way to save a page’s body in Confluence storage format, or to export it as a Word document. Which menu offers this depends on your Confluence version and your permissions there. Check Atlassian’s documentation for your version.

Files

  • Storage format files saved as .html, .xml or .txt.
  • Word files as .docx, at most 10 MB each.

Overview

Phase 1: Plan

Phase 1 of 5, about 30 minutes. Next: Phase 2, Set up Spaces.

Map Confluence to Collabase

What the Confluence page import converts

The Word import converts headings, paragraphs and tables. It does not bring images across either.

Decide

  • One Collabase Space per Confluence space is the default. Merge small spaces only if the same people work in them.
  • Leave out pages nobody has opened for a long time. Moving fewer pages is the fastest migration.
  • Choose the Confluence page import for every page you can get in storage format, and the Word import for the rest.
Checkpoint. You have a list of the Confluence spaces to move, the Collabase Space each one goes to, and the pages in each, with the import way for each page. If you are unsure which pages are still used, ask the space owners before you go on.
Next: Phase 2, Set up Spaces.

Phase 2: Set up Spaces

Phase 2 of 5, about 15 minutes per Space. Previous: Phase 1. Next: Phase 3, Rebuild the page tree.
1

Bring people in

Make sure everyone who works in the moved content has a Collabase account. Create accounts on the Users page, or connect your directory, see Users and groups.
2

Create the Spaces

Create one Space for each line of your plan. Choose the visibility that matches the Confluence space. See Spaces.
3

Assign roles

Give the members and groups of each Space their roles, so the people who import in phase 4 have edit rights. See Permissions.
Checkpoint. Each Space from your plan exists, and the people who import can create and edit pages in it. If someone cannot create a page, check their Space role.
Next: Phase 3, Rebuild the page tree.

Phase 3: Rebuild the page tree

Phase 3 of 5. Previous: Phase 2. Next: Phase 4, Import the content.
1

Start at the top

In each Space, create the top-level pages first, with the titles they have in Confluence. See Pages.
2

Add the child pages

Create each child page under its parent, in the Confluence order. Keep the titles: they are what you search for when you fix links in phase 5.
Checkpoint. The page tree of each Space matches the Confluence tree, with empty pages. If the order is off, move the pages in the tree before you import content.
Next: Phase 4, Import the content.

Phase 4: Import the content

Phase 4 of 5, a few minutes per page. Previous: Phase 3. Next: Phase 5, Repair and check. The import is done in the page editor, one page at a time, by anyone with edit rights in the Space. It inserts the converted content at the cursor position, so start with an empty page.
1

Save the page body

In Confluence, save the page’s body in storage format as a file ending in .html, .xml or .txt.
2

Open the target page

In Collabase, open the empty page in the editor and click into the page body.
3

Open the import

In the editor toolbar, click Import, then Import Confluence Page. The dialog Import from Confluence opens.
4

Choose the file

Click Browse Files and select the file.
5

Convert

Click Process Transformation. The button shows Transforming… while it works, and the dialog closes when the content is in the page.
Checkpoint. The page shows the Confluence content with its headings, tables and callouts. If an error appears instead, see Troubleshooting.
Next: Phase 5, Repair and check.

Phase 5: Repair and check

Phase 5 of 5. Previous: Phase 4. Next: Keep it running.
1

Replace the images

Delete each image placeholder and insert the image again from your Confluence export.
2

Upload the attachments

Add files that were attached to the Confluence page as page attachments. See Pages.
3

Fix links between pages

Each link to another Confluence page carries that page’s title. Point it to the Collabase page with the same title.
4

Ask the space owners to check

Let the owners of each moved space read their pages before you announce the move.
Checkpoint. Every moved page shows its images, attachments and working links, and the space owners have confirmed their pages. Tell your members where the content lives now.

Keep it running

Nothing in this guide expires. Two things need a decision once the move is done:

Troubleshooting

In the import dialog

On the page

Pages

Create pages, move them in the tree and add attachments.

Spaces

Create Spaces and choose their visibility.

Users and groups

Bring the people of your Confluence spaces into Collabase.

Move work from Jira

The matching guide for Jira projects.
Last modified on October 13, 2026