Last edited 5 days ago
by Richard Heigl

Confluence migration: Difference between revisions

No edit summary
Tag: 2017 source edit
mNo edit summary
 
Line 1: Line 1:
''HalloWelt!'' 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.
''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==
==Migration tool==

Latest revision as of 20:13, 8 November 2024

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.

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
  • Comments
  • Various macros
  • Various layouts
  • Blog posts
  • Files in an area that cannot be assigned to a page

More information



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