ThurWiki imports from Confluence, MediaWiki, DokuWiki, XWiki, BookStack and Notion, with a preview before anything is written. Whatever the wiki cannot convert, it tells you about, instead of quietly leaving it out.
Atlassian announced the end in September 2025 (the deadlines at Atlassian). The route Atlassian offers leads into the Atlassian cloud: more expensive for many customers according to reports (The Register, September 2025), and to a provider based in the United States, even where the data sits in a region you choose. There is a second route.
Voices from public forums and reviews, 2025 and 2026, some of them shortened.
“The search is so bad that I wasn't able to find many important process documents and just assumed it had never been created.” – Atlassian Community, March 2025
ThurWiki: search by sound (Cologne phonetics) and by meaning (embeddings), across titles, text and the content of PDF, Word and Excel attachments. Only what you may see.
“Documentation goes stale silently. Unlike code, there's no test suite that goes red when your runbook references a deprecated service.” – Atlassian Community, February 2026
ThurWiki: a review date per page: a responsible person, a date, and a repetition if you want one. When the date arrives, a notice stands at the top of the page – visible to everyone who opens it – and the responsible person is reminded; confirming takes one click. On top of that, the page fetches whatever sits in bexio, Jira, Git or the CRM through a macro from the source, instead of having it typed out: one click brings the latest state, and every refresh appears in the history.
“Editing hundreds of pages in the new editor was just too painful.” / “Out of 110,000 pages, 85,000 are affected.” – Atlassian Community, July and August 2025, on the retirement of the legacy editor
ThurWiki: one editor, one document format. Tables with merged and split cells, header row and header column, sorting and filtering while reading. No build step, no forced migration, no apps that fall away at the next update.
“… on average, we can expect those who migrate from DC to Cloud to pay around 28 percent more.” – Rodney Nissen, independent Atlassian consultant, quoted in The Register, September 2025
ThurWiki: one price per wiki, from CHF 4.90 a month, with no surcharge per user. Two-factor authentication, all 85 macros, all 41 connectors and draw.io are included; SSO belongs to the Enterprise package, there with no extra subscription and no price per head. AI on your own key, without credits.
“Review reminders can't be done ootb.” / “There's nothing like an expiration date in Confluence.” – Atlassian Community
ThurWiki: included without a marketplace are a review date per page with a responsible person and a reminder, four-eyes approvals, charts from tables, draw.io, Excel and Word attachments on the page, and content from Git.
“We cannot migrate to cloud (tested this a lot and it does not work). For us this will mean: bye bye Atlassian.” – The Register, September 2025
ThurWiki: run in Switzerland on ThurData GmbH's own infrastructure. ThurData is a Swiss company with no US parent; the US CLOUD Act does not apply. No tracking, one contact with a name, data processing under Swiss data protection law.
“Too hard to edit to the point that documentation will tend to fall out of date.” – Hacker News, on MediaWiki
ThurWiki: a ribbon like Word's, tables like Excel's, no markup. Help at the question mark next to every field, 60 topics for end users. The greatest gain from a move is the day somebody outside IT writes a page for the first time.
Confluence is a good tool, and so are MediaWiki, DokuWiki and BookStack. The differences lie where a company works every day.
| ThurWiki | Confluence Cloud | MediaWiki | DokuWiki | BookStack | |
|---|---|---|---|---|---|
| A page tree as deep as you like, sub-pages beneath sub-pages | yes | yes | flat, sub-pages only through a slash in the title | namespaces | no: shelf, book, chapter, page |
| Search inside PDF, Word and Excel attachments, tolerant of typing mistakes | yes | attachments yes, typing mistakes no | through extensions | through extensions | attachments no, typing mistakes no |
| An editor without markup, a ribbon like Word's | yes | yes | VisualEditor as an extension | through extensions | yes, WYSIWYG |
| Tables: sort, filter and number while reading | yes | sorting | sorting | through extensions | no |
| Content from bexio, WHMCS, Abacus on the page | yes, 13 macros | no | no | no | no |
| Jira, Git, CRM, calendar, e-mail on the page | yes, 17 macros | Jira yes, the rest through apps | through extensions | through extensions | no |
| A documented API (REST) for your own connections | yes, 36 endpoints, API keys as service accounts | yes | yes | XML-RPC, JSON-RPC | yes |
| Four-eyes approvals | yes | through apps | through extensions | through extensions | no |
| Simultaneous editing | yes | yes | no | no; a page lock: one writes, the others wait | no; it warns about simultaneous editing but does not merge |
| SSO (OIDC, SAML) without a price per user | yes, in the Enterprise package | Atlassian Guard, separate and per user | through extensions | through extensions | yes |
| An AI assistant with the rights of the user, a model in your own house possible | yes, without credits | Rovo, only in the Atlassian cloud, a credit allowance per user and plan | no | no | no |
| draw.io in our own house | yes | through an app | through an extension | through an extension | embeds diagrams.net, can be self-hosted |
| Operation, backup and updates by the provider | yes | yes | yourself | yourself | yourself |
| Data in Switzerland, on the provider's infrastructure | yes, ThurData | data residency per region, provider in the USA | if self-hosted | if self-hosted | if self-hosted |
| Run it yourself | no, run by us only | only Data Center, which ends in 2029 | yes | yes | yes |
| Open source | no | no | yes | yes | yes |
| Export whole spaces | yes: chosen pages and whole branches as one PDF; every page as Markdown through the API | yes: PDF, HTML, XML (Atlassian format) | yes: XML, wikitext | yes: text files | yes: books as PDF, HTML, Markdown |
| A review date per page with a reminder | yes: responsible person, date, repetition, a notice on the page | through apps | through extensions | no | no |
| Price | per wiki, from CHF 4.90 a month | per user per month, plus Guard, apps, credits | free, you run it | free, you run it | free, you run it |
As of September 2026, based on the makers' public statements and without warranty. We also write down where we are not ahead.
Per source system: the route, what is carried over, and what you should check afterwards.
A wiki with an address and access, or an export as a file.
The wiki looks at what is inside and reports whatever it cannot read.
We recommend an empty one: that way you see what has arrived.
On the left the page tree of the source, on the right the chosen page as it would look after the import – with tables, attachments and a note about everything the wizard had to guess.
Repeatable: the wiki knows what it has already fetched and creates nothing twice.
Into an empty space. Look at what arrived. Only then the rest. We do this with you in the demo wiki, before you decide anything.
A move is the best opportunity to throw things out. Whatever nobody has opened in three years needs no new home.
Let the old wiki run on read-only until the new one has settled in. The import picks up changes made in the meantime.
Confluence Cloud, Confluence Server and Data Center, MediaWiki, DokuWiki, XWiki, BookStack, Notion (export) and Markdown files. For the wikis through their own API with an address and access, for Notion and Markdown as a file; Wiki.js, Docmost and Outline through their Markdown export, SharePoint and OneNote through Word files. The import runs in five steps with a preview; nothing is written before the last one. A run can be repeated without pages appearing twice.
The common ones are converted: columns, code, sections, info, warning, note, tip, panel, table of contents, sub-pages, draw.io, attachment preview, gallery, status (as a coloured highlight in the text), anchors, mentions, recently updated, page lists, excerpts, contributors. A macro ThurWiki does not know leaves a visible line with its name and an entry in the import report. Nothing quietly disappears.
Rights, groups and users are not carried over by the import today. You set them afterwards per space in the rights matrix; we help with the transfer. Also not carried over: embedded third-party content (widget, iframe); those leave a note on the page.
For a collection of a few hundred pages the import takes one afternoon. It does the bulk of the work; after it come a few days of follow-up, during which you can sort out the old material at the same time. We recommend bringing twenty pages into an empty space first.
Yes. The import leaves the source system untouched. Many companies keep the old wiki running read-only until the new one has settled in. The import can be repeated to pick up changes made in the meantime.
Yes, directly: ThurWiki reads BookStack through its API with an address and an access key, with a preview. In the import wizard you choose a shelf; every book becomes a top-level page in the chosen target space, chapters become pages with sub-pages, pages stay pages. Text, tables, images, attachments and links all come along. What you gain afterwards: sub-pages as deep as you like instead of shelf, book, chapter, page; simultaneous editing in which the changes flow together, rather than a mere warning about overwriting; operation and updates done by us.
Yes, through the Markdown export of those systems: Wiki.js keeps pages as Markdown, Docmost and Outline export spaces as a Markdown archive. ThurWiki reads the archive in as a page tree with images and links, with a preview.
You take chosen pages and whole branches out as one PDF, up to 300 pages per export; and every page additionally as Markdown through the API, with attachments. There is no bulk export of the whole wiki as an archive today; we would rather say so beforehand than afterwards. Your data sits in Switzerland and belongs to you.
Looking for a Confluence alternative? ThurWiki is the Confluence replacement from Switzerland for companies that need a way out before Confluence Data Center ends on 28 March 2029 – one that does not lead into the Atlassian cloud. The import carries over spaces, page tree, attachments, links and the common macros from Confluence Cloud, Server and Data Center; MediaWiki, DokuWiki and XWiki come through their APIs, Notion through its export, Markdown as an archive.
Anyone looking for a BookStack alternative because shelf, book, chapter and page allow no deeper sub-pages and two people cannot write on one page at once; anyone looking for a Wiki.js alternative because they do not want to carry operation and updates themselves; anyone looking for an XWiki alternative because scripts and running a Java server do not fit every company's daily work; anyone looking for a DokuWiki alternative because important functions hang on plugins; or anyone looking for a Docmost or Outline alternative with SSO at no surcharge and operation in Switzerland: ThurWiki reads BookStack directly through its API, and for the others the route runs through the Markdown export. Anyone looking for a MediaWiki alternative or a Notion alternative for their company finds the same here: import with a preview, an editor without markup, search right into attachments, approvals, SSO with no price per head, and operation in Switzerland.
Twenty of your pages in a demo wiki, imported with a preview, before you decide.