The alternative to the SharePoint wiki Microsoft no longer develops.
The classic SharePoint wiki is no longer being developed, the Teams wiki has been switched off since 2024, and Loop is more a shared workspace than a wiki. Anyone whose knowledge is scattered across SharePoint pages, OneNote and Word files gets, with ThurWiki, one place with a page tree, search, rights and a history.
What SharePoint users run into. And what ThurWiki changes about it.
Voices from public forums and reviews, some of them shortened. More reasons for switching stand on the migration page.
-
Microsoft switches things off instead of improving them.
«Instead of developing a better product, they kill it.» – Microsoft Tech Community, April 2023, on the retirement of the Teams wiki
ThurWiki: A product that is built to be a wiki. Links within a Markdown archive are rewritten during the import.
-
The wiki gets buried in the search.
«Wiki content gets buried among emails, Teams messages, and unrelated documents. There is no wiki-specific search.» – the MassiveGRID blog, comparison of XWiki and SharePoint
ThurWiki: A search for the wiki alone, by sound and by meaning, right into attachments: PDF and Office, including scans and archives.
-
Good rights, but an administrator from the very first user.
«Sharepoint has the best permissioning but basically requires an admin from user #1.» – Hacker News, 2019
ThurWiki: Create spaces, invite users, write. The administration has a question mark beside every field.
How the move out of SharePoint works.
- Route
- Export SharePoint pages and OneNote sections as Word or Markdown; Word files are shown as an attachment on the page and are searchable, and a Markdown archive becomes the page tree. We help with the move.
- Comes across
- From the Markdown archive, folders as the page tree, pages, images and rewritten links; Word files as searchable attachments.
- Check afterwards
- Whether a Word instruction stays an attachment or should become a page; rights per space.
Pages that quietly go stale no longer exist.
The most common ailment of a wiki is not the missing page but the wrong one: an instruction that has not been right for two years, and nobody notices. A review date turns that into an appointment.
- A name, a date, a rhythm. Per page a responsible person, a date and, if you want, a repetition: every 30 days, quarterly, half-yearly or yearly.
- The notice stands on the page, not only in a mailbox. Once the date is reached, everyone who opens the page sees it – including the engineer who needs the instruction right now. A reminder only one person gets does not help the reader.
- Confirming is one click. The responsible person is reminded and confirms right in the notice. With a repetition the next date counts from today – anyone confirming three months late is not immediately due again.
- Two overviews. “My reviews due” for the individual, and in the wiki administration all the reviews due across the wiki. The responsible person is an organisational note and not a right: they get no access they do not have anyway.
And back out again: as one PDF.
A wiki you cannot get out of is a trap – you know that, moving out of SharePoint right now. That is why the exit lies open.
- One document out of many pages. Tick across spaces, up to 300 pages per export; each begins in the PDF on a new sheet, in the order of the page tree. You choose how large it prints: 45 to 100 per cent, for type and content at once.
- Just as the page looks. What is printed is the real view, not a second rendering: macros, charts, draw.io drawings and tables stand in the PDF as they do in the browser.
- With your rights, not with everybody’s. A page you are not allowed to read stops the export rather than quietly going missing. An export that drops pages would be worse than one that never arrives.
- And by machine. Through the API every page as Markdown, with attachments – for an archive or for the move to the next system.
ThurWiki and SharePoint side by side.
| ThurWiki | the SharePoint wiki, the Teams wiki, OneNote | |
|---|---|---|
| A page tree as deep as you like | yes, as deep as you like | a page library, not a wiki tree |
| Search inside PDF, Word and Excel attachments, tolerant of typing mistakes | attachments yes, including scans and archives; typing mistakes yes, and by meaning | attachments yes; search across the whole tenant, not only the wiki |
| An editor without markup | yes, a ribbon like Word’s | yes |
| Simultaneous editing | yes | yes |
| Four-eyes approvals | yes, without an add-on | an approval flow through Power Automate |
| Invoices, tickets, issues and files from other systems on the page | yes, 41 connectors, from bexio, Odoo and Jira to Zabbix and Proxmox | the Microsoft world |
| SSO (OIDC, SAML) without a price per user | yes, included | Entra ID |
| An AI assistant | yes, with your rights, without credits | Copilot, an extra licence |
| Operation, backup and updates by the provider, data in Switzerland | yes, ThurData in Switzerland | cloud, provider in the USA |
| Run it yourself (open source) | no, run by ThurData | only SharePoint Server; not open source |
| Export chosen pages and whole branches as PDF | yes, chosen pages and whole branches as one PDF; every page as Markdown through the API | as Office files |
| A review date per page with a reminder | yes, a responsible person, a date, a repetition, a notice on the page | through retention policies |
| Price | per wiki, from CHF 4.90 a month | per user, within the Microsoft subscription |
As of September 2026, based on the makers’ public statements and on user reports, without warranty. We also write down where we are not ahead.
Questions from SharePoint users
We have Microsoft 365. Why a wiki of our own?
Because SharePoint is above all a document store: no page tree, web parts instead of wiki macros, approvals only through Power Automate, a search across the whole tenant instead of only the wiki. Your users sign in to ThurWiki with their Microsoft account through Entra ID.
How do SharePoint pages and OneNote come across?
Export them as Word or Markdown. Word files become attachments that are shown on the page and searched; Markdown becomes the page tree. There is no direct SharePoint importer; we help with the move.
We record meetings in OneNote. Does that work in ThurWiki?
Yes, with the macro “Voice note or meeting”: record in the browser or upload a file, play it back on the page, optionally with a transcript through Whisper in your own house or through ChatGPT. Audio and transcript are attachments carrying the page’s rights, and the transcript is searchable.
How do we stop pages going stale?
With a review date per page: a responsible person, a date and, if you want, a repetition (30 days up to yearly). Once the date is reached, a notice stands at the top of the page – visible to everyone who opens it, not only to the responsible person – and that person is notified. Confirming is one click in the notice; with a repetition the next date counts from today. Whoever administers the wiki sees all the reviews due in one place, and each person sees their own in the user menu.
How do we get back out of ThurWiki?
In the interface as PDF: you tick in the page tree what should come along – per row either the page alone or the page with all its sub-pages – across spaces, up to 300 pages in one document. What is printed is the view you see, so with macros, charts and drawings. Through the API, additionally every page as Markdown, with attachments. There is no bulk export of the whole wiki as an archive today; we would rather say so beforehand.
More alternatives pages: Confluence · MediaWiki · DokuWiki · XWiki · BookStack · Wiki.js · Docmost · Outline · Notion
ThurWiki is an alternative to the SharePoint wiki, to the retired Teams wiki and to OneNote as a company wiki: a page tree, search into attachments, rights per space, approvals, sign-in through Microsoft Entra ID, operation in Switzerland.
Anyone wanting to replace the SharePoint wiki, rescue Teams wiki content or build a company wiki alongside Microsoft 365 finds the route and the comparison here.
Twenty of your SharePoint pages in ThurWiki, before you decide.
We set up a demo wiki and import a slice of your collection, with a preview. You see search, macros and the editor working on your own content.