Skip to content

Import from Confluence

The Confluence importer migrates Confluence spaces and their pages into SetGet pages. Page hierarchy, content formatting, and inline images are preserved during migration. This importer is designed for teams moving their documentation and knowledge base from Confluence to SetGet.

What gets imported

Confluence elementSetGet equivalentNotes
SpaceProject pages sectionPages imported under a parent page named after the space
PageSetGet pageContent converted from Confluence storage format
Page hierarchyNested pagesParent-child relationships preserved
Inline imagesEmbedded imagesRe-uploaded to SetGet storage
AttachmentsFile assetsRe-uploaded to SetGet storage
Page labelsPage tagsMapped if supported

Prerequisites

  • A Confluence Cloud instance or Confluence Server/Data Center with API access.
  • A Confluence account with read access to the spaces you want to import.
  • Admin or Owner role in your SetGet workspace.

Setup steps

Step 1 -- Connect to Confluence

  1. Go to Settings > Import.
  2. Select Confluence.
  3. Enter your Confluence instance URL (e.g., https://yourcompany.atlassian.net/wiki).
  4. Enter your email and API token.
  5. Click Connect.

Step 2 -- Select the space

  1. SetGet lists all accessible spaces.
  2. Select the space you want to import.
  3. SetGet scans the space and shows: page count, hierarchy depth, attachment count.

Step 3 -- Choose the target project

Select the SetGet project where imported pages will be stored. Pages are added to the project's pages section.

Step 4 -- Configure options

OptionDescriptionDefault
Preserve hierarchyMaintain parent-child page structureOn
Import attachmentsRe-upload attached filesOn
Import page labelsConvert labels to page tagsOn
Import archived pagesInclude pages in the archiveOff

Step 5 -- Start import

Click Start Import and monitor progress. Large spaces with many pages and attachments may take several minutes.

Content conversion

Confluence storage format (XHTML) is converted to SetGet's editor format. The following elements are supported:

Confluence elementSetGet rendering
Headings (h1-h6)Headings
ParagraphsParagraphs
Bold, italic, underlineText formatting
Bulleted listsBulleted lists
Numbered listsNumbered lists
TablesTables
Code blocksCode blocks with syntax highlighting
ImagesInline images
LinksHyperlinks
Info/warning panelsCallout blocks

WARNING

Confluence macros (e.g., Jira issue macro, Table of Contents macro, custom macros) are not converted. They appear as placeholder text in the imported page. Review imported pages for macro placeholders and recreate the content manually.

Post-import validation

  • Verify the page count matches the Confluence space.
  • Check that the hierarchy (parent-child nesting) is correct.
  • Open several pages to verify formatting and images.
  • Confirm attachments are accessible.

Multi-space import

To import multiple Confluence spaces:

  1. Run the importer once for each space.
  2. Choose the same or different target projects depending on your structure.
  3. Pages from different spaces are kept separate by project or by parent page.

TIP

If you have a large Confluence instance with many spaces, prioritize the most active spaces first. Archive inactive Confluence spaces rather than importing them.

Confluence vs. SetGet pages

FeatureConfluenceSetGet
Page hierarchyUnlimited nestingUnlimited nesting
Rich text editingAtlassian editorSetGet block editor
Macros100+ macrosSlash commands and embeds
CommentsPage comments and inline commentsPage comments
VersioningFull version historyFull version history
PermissionsSpace and page levelProject level
SearchGlobal searchGlobal search

After migrating, your team will find the SetGet page editor familiar. The main difference is that Confluence macros need to be recreated using SetGet's slash command system (e.g., /table, /code, /diagram).

Troubleshooting

ProblemCauseSolution
Connection failsWrong URL or credentialsVerify instance URL and API token
Space not listedInsufficient permissionsUse an account with space read access
Images missingPrivate attachmentsEnsure the API token account can access the images
Macros showing as textExpected behaviorRecreate macro content manually
Hierarchy flatOption disabledEnable "Preserve hierarchy"
Large space timing outToo many pagesImport in batches by selecting subsets