Migration
Start off with your existing content in place.
Our experts support you in moving your data from MediaWiki, Office and many other systems into your BlueSpice wiki.
Many data sources, one BlueSpice
BlueSpice has a variety of options for migrating data from other systems. These include ata migration from MediaWiki and other wiki systems, from a CMS such as WordPress, from Lotus Notes, from Office formats such as Word, Excel or PowerPoint, or from other formats such as ODT, CSV or XML.
MediaWiki
The migration from a MediaWiki is a standard procedure and easily possible. Even migrations from very old MediaWiki versions are no problem and can be done with very manageable effort.
More at mediawiki.org
Word documents
For Word documents, an import tool has been available since BlueSpice 4.2, which greatly simplifies the transfer of Word documents. For more complex migration sources, we are of course available to support you.
More in our helpdesk
Confluence
For migration from Confluence, there is a publicly available migration tool that allows easy migration of content. However, many Confluence migrations still require a well-planned migration project, as missing features need to be replaced and a custom handling of existing Spaces needs to be found. Please contact us for more information.
- Our standard migration tool for Confluence can be found on GitHub
- Further descriptions can be found on YouTube
- See also our blogpost: Migration from Confluence to BlueSpice MediaWiki
Migration project
A good migration from another system requires a well-planned project.
With the help of a migration checklist, a careful examination can determine whether migrating the existing data makes technical sense or whether a manual import of the data is more economical for the customer. We evaluate, among other things, the following aspects:
- Structural migration: How do the technical basis and the storage logic of the source and target systems differ?
- Content migration: How can content be transferred from the source to the target format (wikitext)?
- Data homogeneity: How homogeneous is the data in its structure?
- Language: What is the target language for the migration?
- Media: How should linked and embedded media such as photos be treated?
Data migration and data synchronization options
Data migration using a script
If the basic feasibility has been determined, we will clarify further details in an individual workshop. This may involve renaming documents and files or assigning content to wiki categories. After programming a precisely tailored migration script, a multi-stage shutdown or handover process follows with the aim of minimizing customer downtime.
At the end of the migration process, we find the activation of BlueSpice and the shut-down of the old system. And a satisfied customer, who can now easily and conveniently manage content in BlueSpice.
Data synchronization in real-time
Do you need ongoing data reconciliation between a source system and BlueSpice? No problem. Our software enables just-in-time synchronization via interfaces (API) or database dumps. And we can program the necessary interfaces for you on request.
