SharePoint is rarely one system in practice. It is a document library, an intranet, a set of lists, and a workflow engine that happen to share a login, and most teams lean on only one or two of those while paying to operate all of them. That bundling is why a switch feels daunting, and why open source usually splits the job in two: document management on one side, an intranet and team portal on the other. Running those as separate self-hosted services means you own the files and the database outright, authenticate against your own directory, and can back up and audit each piece without keeping an entire collaboration platform alive to serve one workload.
HumHub is open-source software for organizations that need an intranet, social network, knowledge base, or internal communication platform. It helps people connect, stay informed, and share content across teams.
Teedy is an open source document management system for individuals and businesses. It is built to store, organize, search, and share documents in one place, with support for common office files and video files.
Mayan EDMS is a free open source document management system that stores and organizes documents, PDFs, and scans in one central place. It is built to scale and is positioned as a mature option for teams managing large document collections.
Uwazi is a web-based, open-source database application for capturing and organizing collections of information, with a particular focus on document management. HURIDOCS built it and supports its use by dozens of human rights organizations worldwide.
OpenDocMan is a web-based document management system written in PHP for storing and organizing files in the browser. It is designed to comply with the ISO 17025 and OIE standards for document management, with fine-grained control over who can access each file.
Match the tool to the SharePoint job you are actually replacing.
Intranet and team portal: HumHub HumHub replaces the intranet half of SharePoint: spaces for departments and projects, each with its own permissions, plus member profiles, wikis, posts, and tasks. Around 80 installable modules extend it, including Advanced LDAP and JWT single sign-on to plug into your directory. It is available in more than 30 languages, so a company portal does not depend on Microsoft 365 seats.
Document management with search: Teedy Teedy is a well-rounded document system with OCR, full-text search, tags, and file versioning, plus a review workflow. It authenticates through LDAP with optional two-factor login, keeps an audit log, and encrypts stored files with 256-bit AES. A REST API and webhooks feed other systems, and it self-hosts with Docker.
Large document repository: Mayan EDMS Mayan EDMS is aimed at teams managing large document collections, running every file through OCR so its text is indexed and searchable. It is self-hosted through a Docker Compose deployment and also ships as a container image and a Python package, which suits organizations that want a scalable, file-centric repository rather than a broad collaboration suite.
Controlled document processes: OpenDocMan OpenDocMan focuses on controlled documents, with department and per-user permissions, revision tracking, and a review step before files are published. It is built around the ISO 17025 and OIE document standards, so it fits regulated environments where who approved which version has to be provable. It runs on a standard PHP and MySQL or MariaDB stack.
Most SharePoint migrations stall on the same discovery, which is that nobody can say which parts are load-bearing. Before choosing a tool, separate the document repository from everything else. If the real value is stored files with versions, metadata, and access control, a document management system covers it. If it is the intranet - team spaces, pages, announcements, and directories - that is a different product. The tools here fall cleanly into those two camps, and picking one that matches the wrong camp is the most common way a replacement disappoints.
For the file side, weigh how documents are found and controlled. Mayan EDMS and Teedy both run text through OCR so scans and PDFs become searchable, which matters if your libraries hold contracts and forms rather than office files. OpenDocMan leans toward controlled document processes, with department and per-user permissions and a review step before a file is published. What will not transfer neatly is SharePoint's tangle of inherited and broken permissions, so treat the move as a chance to design a clean group model rather than copy the old one.
The intranet side is where HumHub fits, with spaces for departments and projects, member profiles, wikis, and an LDAP module to plug into your existing directory. Lists and form-driven workflows are the weakest thing to reproduce, because SharePoint lists behave like small applications; plan to rebuild the few that still earn their keep and retire the rest. Pilot one library or one space, compare file counts, check that search returns what people expect, then cut over department by department.
Split them by job. Mayan EDMS, Teedy, OpenDocMan, and Uwazi are document management systems that replace libraries, versioning, and file permissions. HumHub replaces the intranet side, with spaces, pages, member directories, and wikis. No single tool here does both well, so most teams run one document system plus HumHub rather than hunting for one platform that covers everything SharePoint did.
Yes, if you pick a tool built for it. Mayan EDMS and Teedy both run documents through OCR so the text inside PDFs and scanned pages becomes searchable, not just filenames and tags. Uwazi indexes full text through ElasticSearch across structured collections. Test search with your real documents before committing, since SharePoint users often rely on search to compensate for messy folder structure.
Not one to one, and that is usually a feature. OpenDocMan controls access by department or per user, and HumHub gives each space its own permission and notification rules. SharePoint's inherited and individually overridden item permissions rarely translate cleanly, so rebuild a deliberate group model instead of exporting the old one. The migration is a good moment to remove one-off access nobody can explain.
Some do. HumHub offers an Advanced LDAP module and JWT single sign-on among its add-ons, and Teedy supports LDAP authentication with optional two-factor login. Confirm directory integration for the specific tool before you migrate accounts, because it affects how users, groups, and disabled accounts carry across. Where it is missing, you will be managing local accounts inside the new system.
These are the hardest to reproduce, because SharePoint lists act like small applications with validation, lookups, and routing. The tools here are document and intranet systems, not list builders: Teedy and OpenDocMan offer document review workflows, and HumHub has tasks, but form-driven business logic will need rebuilding elsewhere. Inventory which lists still run real processes and recreate only those.
Yes, every option here is self-hosted. Mayan EDMS deploys through Docker Compose, Teedy and OpenDocMan both ship Docker setups, and HumHub runs on a standard PHP and database stack. Self-hosting is the point for teams leaving SharePoint's Microsoft 365 dependency, but it moves backups, updates, and uptime onto your team, so confirm you can operate a server before committing.
It varies, so check the tool. Teedy encrypts stored files with 256-bit AES, while most of the others rely on the security of the server and disk you run them on. If your libraries hold sensitive contracts or personnel records, decide where encryption, backups, and administrator access controls come from before migrating, rather than assuming the new system matches SharePoint's governance defaults.
