Confluence migration: Difference between revisions

Created page with "''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. ==Migration tool== The [https://github.com/hallowelt/migrate-confluence?tab=readme-ov-file#migrate-confluence-xml-export-to-mediawiki-import-data migration tool can be found on GitHub] and is [https://github.com/hallowelt/migrate-confluence?t..."
 
Tag: 2017 source edit
 
(4 intermediate revisions by 3 users not shown)
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==
Line 16: Line 16:
==Macro check==
==Macro check==
On the BlueSpice website, you can use a [https://bluespice.com/confluence-migration-process/#confluence-migration-input-desktop 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.
On the BlueSpice website, you can use a [https://bluespice.com/confluence-migration-process/#confluence-migration-input-desktop 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.
[[File:Confluence macro check.png|alt=Textarea for adding a list of macros (with step-by-step instructions)|center|thumb|650x650px|Macro check]]


 
== Not migrated ==
[[File:Confluence Macro Check.png|alternative text=Macro-Check input field with step-by-step instructions|centered|mini|650x650px|Macro-Check]]
 
==Not migrated==
The following Confluence elements are excluded from the migration:
The following Confluence elements are excluded from the migration:


Line 29: Line 27:
*Blog posts
*Blog posts
*Files in an area that cannot be assigned to a page
*Files in an area that cannot be assigned to a page
== Roadmap ==
* March '26: Provide Docker Container (ERM46685) - Eases installation and allows for better automation
* March/April '26: Allow for parallel processing (ERM45405) - Speeds up conversion of large Confluence exports
* March/April '26: Migrate blogs posts to [[mw:Extension:SimpleBlogPage]] pages (ERM46628) - Additional content
* March/April '26: Migrate page comments to [[mw:Extension:CommentStreams]] threads (ERM46627) - Additional content
* April '26: Add support for historic page and file revisions (ERM35013) - Additional content


==More information==
==More information==
Line 35: Line 40:
*https://bluespice.com/mediawiki-versus-confluence-not-a-question-of-features/
*https://bluespice.com/mediawiki-versus-confluence-not-a-question-of-features/


[[en:Confluence migration]]
[[de:Confluence Migration]]
[[Category:Setup]]
[[Category:Setup]]

Latest revision as of 09:59, 27 February 2026

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

Roadmap

  • March '26: Provide Docker Container (ERM46685) - Eases installation and allows for better automation
  • March/April '26: Allow for parallel processing (ERM45405) - Speeds up conversion of large Confluence exports
  • March/April '26: Migrate blogs posts to mw:Extension:SimpleBlogPage pages (ERM46628) - Additional content
  • March/April '26: Migrate page comments to mw:Extension:CommentStreams threads (ERM46627) - Additional content
  • April '26: Add support for historic page and file revisions (ERM35013) - Additional content

More information


PDF exclude - start

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

PDF exclude - end