First, the data is analyzed and a migration plan is created. This involves determining which data will be migrated and how it will be mapped in the wiki. Potential challenges and their resolution are also discussed. We support you with a migration questionnaire and, if necessary, a planning meeting.
The data is exported from the source system. Ideally, it is possible to export the data in a machine-readable format such as HTML, XML, JSON or CSV.
In an intermediate step, the data is prepared to meet the requirements of the wiki. In particular, the data is segmented, i.e., split into units that are later imported as wiki articles. The content is converted into WikiText. Images and other documents are linked to wiki articles.
Then the data is imported into the wiki via import scripts.
Depending on the complexity of the imported data, a small amount of manual post-processing of the content is necessary.
Of course. Migration from Confluence is done with the help of migration scripts. Therefore, we have developed and also published a migration script from Confluence to MediaWiki or BlueSpice. This means that this script can be freely used by others by IT professionals with appropriate experience. However, experience has shown that this script must still be adapted to the respective source system and the target system. For example, customers use very different macros or additional plugins have been booked, which must be taken into account during a migration project. You have to talk about the authorization system and the roles beforehand and about what should be migrated at all.
Contact us: We plan with you the migration from Confluence, from small instances to large systems with thousands of Spaces. Here you can find a somewhat older, but in principle still current blog post about it.
Individual plugins can already be replaced without any problems, other functions we still have to develop via projects. We will inform you about the current status in our consultation, if you let us know your requirements in advance.