Last edited 3 hours ago
by Manuel Strehl

Confluence migration

Hallo Welt! has created a migration tool that can be used to import Confluence spaces into a MediaWiki or BlueSpice installation. This is a command line tool and you need access to your MediaWiki or BlueSpice server environment.

Migration tool

The migration tool can be found on GitHub and is documented there.

It is also available as docker container for ease of installation and better automation.

Features

The migration tool converts much of the content automatically into a format that can be easily imported into BlueSpice.

  • Pages, including hierarchies of child pages
  • Blog posts
  • Revision histories of content
  • Page comments from users
  • Images, attached files, and their revisions
  • Migration of several spaces at once, preserving links between them
  • A growing list of Confluence macros is mapped onto BlueSpice functionality and oftentimes directly usable from within the Visual Editor
  • Basic page layouts are converted
  • The tool can parallelize several steps, e.g., analyzing several entities.xml at once or converting content with several cores to speed up large migrations. Look for the --workers parameter in the documentation.

Extensions

The output generated by the tool contains certain elements that require additional extensions to activate. These extensions are already included in a BlueSpice Pro installation:

  1. TemplateStyles
  2. ParserFunctions
  3. SimpleTasks
  4. Semantic MediaWiki
  5. HeaderTabs
  6. SubPageList

Macro check

On the BlueSpice website, you can use a macro check to see which Confluence macros are not automatically converted. If an important macro is marked as unsupported, the content can most likely still be transferred.

Textarea for adding a list of macros (with step-by-step instructions)
Macro check

Not migrated

The following Confluence elements are excluded from the migration:

  • User identities. The tool creates an informative users.xml file to support admins migrating user accounts.
  • Inline comments (see roadmap)
  • Unsupported macros are placed as HTML comments in the imported pages, together with their parameters. The information is preserved and can be converted manually, if needed.
  • Some complex page layouts cannot be migrated.
  • Files in an area that cannot be assigned to a page are not migrated.
  • Some files cannot be imported into MediaWiki. Particularly attachments of the types .html, .js and .exe are excluded. This is a hard limitation of MediaWiki.

Roadmap

  • July ’26: Create an enhanced sidebar ordered in the same way as in Confluence (ERM49075)
  • July ’26: Support Page Excerpts (ERM48929)
  • August ’26: Add support for migrating into several wikis at once, including automatically resolving interwiki links (ERM46910)
  • August ’26: Add support for custom code to be loaded. This allows fine-tuning results on a per-migration base (ERM48560)
  • August ’26: Add full support for inline comments (ERM48281)
  • August ’26: Enhance performance by running the conversion as service instead of once per file (ERM48011)
  • September ’26: Support output profiles for target wiki versions (ERM48895)

More information


PDF exclude - start

To submit feedback about this documentation, visit our community forum.

PDF exclude - end