Using Sharepoint as a Wiki replacement + migrating data from an Old Wiki

I'm currently looking into setting up a Sharepoint site to be used as a Wki. It looks like it would be possible but would be pretty clunky to update as it doesn't seem to be a current fully supported feature. It looks like this would work via a Communication Site with multiple subsets.

Has anyone had look using Sharepoint as a Wiki? Have you run into any issues that make you regret this decision?

And has anyone successfully migrated another Wiki to Sharepoint? It looks like I can export our current Wiki as Markdown or Docx files.
 

SplatMan_DK

Ars Tribunus Angusticlavius
8,063
Subscriptor++
I'm currently looking into setting up a Sharepoint site to be used as a Wki. It looks like it would be possible but would be pretty clunky to update as it doesn't seem to be a current fully supported feature. It looks like this would work via a Communication Site with multiple subsets.

Has anyone had look using Sharepoint as a Wiki? Have you run into any issues that make you regret this decision?

And has anyone successfully migrated another Wiki to Sharepoint? It looks like I can export our current Wiki as Markdown or Docx files.
We used it at our company, but regretted it. A lot.

Teams and SharePoint Online used tk have a Wiki module from Microsoft. We started out using that. It wasn't great but still better than nothing. Then Microsoft killed it, a we moved content to regular SP Online.

The thing is: SharePoint is overly complex and has a billion features you might not need for a Wiki. It's great for some other things, and especially document sharing, co-authoring Office files, and creating lists that can be shared with others through a browser or API. But it just sucks as a simple page-based information source.

After attempting to move to SP Online, the "wiki project" effectively died. Management refused to consider other tools, so now stuff is shared through different means - scattered and with complex processes to govern them (half the stuff moved to KB articles in Service Now).

If I were to start over, I'd look at self-hosting something in Digital Ocean (likely 10-20 bucks a month), something that can run cheaply in Azure, or using a SaaS service for it.

I'd stay far away from any SharePoint solution.

For specific products to use, consider:

MediaWiki (used by Wikipedia)
Dokuwiki
Outline (getoutline.com)

If you're a startup, you could also consider one of the startup-friendly packages from Atlassian that includes Confluence.
 

invertedpanda

Ars Tribunus Militum
2,293
Subscriptor
The thing is: SharePoint is overly complex and has a billion features you might not need for a Wiki. It's great for some other things, and especially document sharing, co-authoring Office files, and creating lists that can be shared with others through a browser or API. But it just sucks as a simple page-based information source.
This. A previous employer had it, and I ended up developing a PowerApp that utlized Sharepoint as a data source for some common stuff we needed.. Which it did well, but this was in a larger-scale corporate MS-heavy environment where Sharepoint made a sort of sense. A lot of the "average user" type folks only learned enough to get the commonly-needed info from it, but only a handful of us were actually using it to any real serious potential.
 

gregorerlich

Ars Scholae Palatinae
1,612
If you're a startup, you could also consider one of the startup-friendly packages from Atlassian that includes Confluence.
Agreed with everything up until there and had a similar story but will just say, fuck Atlassian and Confluence suuucks unless you need its integration with other Atlassian products, and even then, I'd say do what you can to not need that lol. If you don't need that, any of the major open-source wikis are both much cheaper and much better.
 
  • Like
Reactions: SplatMan_DK