5 things to look for in an open source alternative to SharePoint

If you're considering an open source collaboration platform to meet your remote workforce's needs, here are five things to keep in mind.
64 readers like this.
Digital images of a computer desktop


We're entering a collaboration platform renaissance as remote work becomes the norm for enterprises large and small. Microsoft SharePoint—a collaboration platform available on premises or in the cloud—is the de-facto standard for corporations and government agencies. However, SharePoint implementations are infamous for the challenges that prevent their completion. Combine those common speedbumps with shrinking IT budgets and rising collaboration requirements because of remote work, and open source alternatives to SharePoint become well worth a look.

Here are five things to consider in an open source alternative to SharePoint.

Is it easy to install, set up, and use in the cloud?

Looking beyond installation and initial configuration, you want an open source alternative that's easy to set up. Treat open source collaboration tools as something you must take responsibility for, particularly in setup and user support, whether you have your IT department's approval or you're going shadow IT.

Chances are you'll be installing the platform in a public or private cloud space, so look for an open source collaboration platform that's cloud-friendly. For example, if your organization is running Amazon Web Services (AWS), you can install open source wikis, including MediaWiki, DokuWiki, and TikiWiki, from the AWS Marketplace. After installing them, you can get an idea of how much using the platform will affect your organization's cloud bill.

Is it friendly to end-users?

Show me a complex collaboration site, and I'll show you the developers and other staff who are doing their darndest to work around it. You don't want to make this mistake.

Keep it simple if you want to spin up an open source collaboration platform to replace or augment SharePoint for your remote workers. The easier the collaboration platform is for your users, the better chance you have of winning them over as allies.

With features like a Configure Sites wizard, TikiWiki is an example of an open source collaboration platform that's end-user friendly.

Are the content-editing tools easy to use?

Editing options are a major benefit to the diverse communities of open source contributors building these technologies. MediaWiki is one example of how open source collaboration platforms approach authoring tools. The project has an Editing team that focuses just on editing and authoring tools. Some of its projects include WikiEditor, VisualEditor, and CodeEditor extensions. You're bound to find an editor that fits your users' workstyle.

This feature becomes especially important for developers, who have been known to rebel against SharePoint because it lacks Markdown support. Get feedback from your developers about their authoring needs. If Markdown is one of their requirements, make sure you choose an open source collaboration platform that supports it.

Also be sure to follow open source adoption best practices by ensuring the technology has an active community. For example, some DokuWiki editor plugins, such as Ace Editor and Editor Plugin, haven't been updated in years.

What kind of access control is available to protect content?

If you're dealing with project documentation or any type of sensitive corporate information, examine the access control options in any open source collaboration platform you're considering. Look for support for read-only pages and access-control lists (ACLs).

Open source wikis are open by default. That's not necessarily a bad thing, depending on your security posture. SharePoint permissions are a known trouble spot, even in the eyes of SharePoint experts. In contrast, DokuWiki has a well-documented ACL feature.

Is it integration-friendly for your organization?

Even if you're moving to an open source collaboration platform as a last-minute replacement for an ailing SharePoint implementation, you can't ignore your integration requirements.

MediaWiki and TikiWiki use a MySQL backend. DokuWiki doesn't require a database; it uses plain text files. Databases can be an integration consideration, based on your team members' database chops.

Integration with an authentication backend such as LDAP will also be necessary for some organizations. Security and compliance people get worried about new platforms that aren't aligned with corporate standards. Users often resent having yet another password to remember.

Deploy with care

Open source collaboration alternatives have a unique growth opportunity, as organizations find their once-ignored collaboration tools aren't serving their burgeoning remote workforces. Regardless of your goals, deploy your open source SharePoint alternative with care.

Have you moved to an open source collaboration platform to better serve your remote workers? If so, please share your experiences in the comments.

What to read next
User profile image.
Will Kelly is a product marketer and writer. His career has been spent writing bylined articles, white papers, marketing collateral, and technical content about the cloud and DevOps. Opensource.com, TechTarget, InfoQ, and others have published his articles about DevOps and the cloud. He lives and works in the Northern Virginia area. Follow him on Twitter:@willkelly.


I've been using Redmine with comercial addons and gives us far more agility, usefullness then Sharepoint. Moreover I think our tool curently is so feature reach that it is difficult to chose other option on the market both from features as well as costs point of view.

I never thought a wiki would be a sharepoint alternative. I aways thought NextCloud, Seafile and the like were sharepoint alternatives. I think the use case is important to make a distinction here

Thanks for this list. It is very useful for students and admins looking for a change.

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.