Microsoft SharePoint vs. Plone

SharePoint Document Management excels as a central repository for storing, organising, and retrieving documents. It supports version control, metadata tagging, secure access, and integration with tools like Power Automate. At our organisation, it's used for managing contracts, policies, and supplier documents. SharePoint Workflow Automation integrates with Power Automate to streamline approvals, gather feedback, and automate recurring tasks. This reduces reliance on email chains and manual trackers.

Incentivized

The larger your organization, the more appropriate Plone will be. This is not to say that Plone is a worse choice for small websites, only that the minimum investment for a Plone site is certainly higher than for other platforms. If you already use Plone for your site and are looking for a redesign or an overhaul, I would only advise switching to a different platform such as WordPress or Drupal if your organization is downsizing. For any other situation, Plone is the natural choice for your growth.

• Making collaboration easier via a better connection between accounts. You can share anything from a file to events with just a couple of clicks.
• All services are connected and switching between services is a breeze[.]
• Solutions to the majority of everyday business problems.

Incentivized

• Rock-solid technology stack. The python/Zope/Plone stack is as solid as anything else out there.
• Highly customizable TTW, if needed, via the Zope Management Interface, or Diazo XSL-transform theme design.
• Good support from core developers, lots of solid add-ons which address just about any needs.
• Amazingly customizable workflow, permissions and security management.

Incentivized

• There are far too many good features to choose from, and advanced features are noticeably absent.
• There is room for improvement in terms of integration with non-Microsoft products, as well as developer Story.
• It is challenging to provide easier access via file explorer while also granting outside users and guests access.

• Bullets and formatting sometimes make it difficult to add text to an existing paragraph. The 'code' button is useful in those cases, but only to those who know html.
• Sometimes the pages don't save correctly and you use information.
• Uploading and displaying images is a bit too much work.

We have too much invested at this point to do anything different and there are too many reasons as a company our size to keep it. We are heavily licensed out for Microsoft and have 12 years of SharePoint development baked into who we are. Extracting that as a tool at this point would be dumb and devastating. There are no like-kind competitors to it at an enterprise level that scale and integrate as well.

Incentivized

Plone has been used for more than ten years and it already has an interesting roadmap for its future. I do not know any other open source CMS with the same story of continuous evolution and security track. Interesting new features are added at each release and new modules are created continuously

No usability issues reported. Individual teams also have allocated areas which replace legacy shared drives on local LANs. Access to Sharepoint resources is fully integrated with corporate Active Directory with additional two-factor authentication required for administrative users. Users have access to Microsoft Services Hub which allows you to create, manage, and track support requests while staying current on Microsoft technologies with access to select self-paced learning paths

Incentivized

Compared to the amount of Plone sites, users and customizations we have in our organization, the amount of support requests and training needed is really small.

The new user interface in Plone 6 is even better, it is super fast, has lots of different blocks for enhancing the page, has flexible layout system and is easy to extend with more features.

Our Plone sites are very robust. We have critical systems on Plone and we have been running sites on Plone for over 20 years with very little unexpected downtime.

Plone is very intensive in its operations, and if not configured well it can be slow. However it is designed and built with speed in mind and with proper use of coding, templates and caching can perform extremely well under high loads. It is capable of scaling to very high load availability environments with no specific coding requirements.

Support for SharePoint is quite good. Microsoft provides good support. Microsoft offers

• Quick turnaround time for issues
• A range of support services
• Access to a network of resources
• Escalation of issues
• Ongoing development and commitment to produce enhancement

The majority of support is required for initial installation. Once complete and the system is operating we have had very few support issues.

Incentivized

There are not too many Plone companies in the world. But the ones who are, are high level professionals

The face to face training I received was on SharePoint Administration. It was rushed as there was a lot of information to cover and the application of the labs weren't that great either. I like to be able to relate what I am learning to what I am currently doing.

I have been participating Plone training and the trainers have always been professional. Materials were good and the instructions clear

I like to learn at my own pace and online training allows for that. Additionally, you can skip through pieces of content that you already know or are already comfortable with. Microsoft actually offers great videos on their website for basic fundamental SharePoint Training. I have used these training videos in some of my own training sessions with end users.

Well organized, professional training with good materials and instructions

Planning to the last detail would be advised. SharePoint is a very large application that takes a lot of finesse to get operational

The reasons for selecting MS SharePoint are: SharePoint provides ease of use and web design assistance and support SharePoint helps you schedule your content for publishing. enables users to share documents with external parties and offers a better internal structure of the content and better indexing and searching capabilities.

Incentivized

Plone is much harder to learn then Wordpress. Development in Wordpress is learnt in day's, where development in Plone really takes years to get to the full depth. That said, once you're able to develop in Plone, is it a rock solid system, with readable code. In my experience Wordpress websites need to be updated so often, and the code feels bad organised. I have been building Wordpress websites, choosing Wordpress only when the client has almost no money. But I can never deliver the quality I want to deliver when using Wordpress. Plone does offer the possibility to deliver professional websites. As for Joomla, in the past I have done some Joomla development, but the whole CMS-paradigm could not settle in my brain. Being a web developer for over 15 years now, Joomla always felt contra-intuitive. Let alone the task of teaching this to my clients. Plone is now my only choice. It gives me a fast development-cycle, a user-friendly CMS and a rock stable and very secure system.

Plone has no limits. We have massive sites and can run them just fine

• We've recently implemented Microsoft SharePoint access via iPads for our Template teams out on job sites. They can easily upload CAD / Laser files into Microsoft SharePoint for our production team to review in real time. Serious ROI when we don't have to wait for our Template team to get back to the shop!
• We have multiple physical locations. Microsoft SharePoint allows users at each location to collaborate by working on documents simultaneously. Allowing us to solve multi-site problems & strategize on multi-site initiatives much faster!
• We can also share key information with external partners. As long as they have a registered MS account (not necessarily an O365 account) we can share our information with them in a variety of ways. This allows consistent & concise communication with our partners.

Incentivized

• We thought that tapping into the user/content management tooling of Plone would be a good and useful thing, however it turned out to be a major pain to tie into those parts of Plone.
• I wish we would have built the extra functionality completely outside Plone and found a way to integrate it. It would have been much easier.