Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Plone
Score 10.0 out of 10
N/A
Plone is a free and open source content management system built on top of the Zope application server. Plone can be used for any kind of website, including blogs, internet sites, webshops, and internal websites.
N/A
Agentforce Sales
Score 8.7 out of 10
N/A
Salesforce' Agentforce Sales (formerly Salesforce Sales Cloud) is the company's flagship CRM platform. The AI CRM for Sales features data built right in.
$25
per month
Pricing
Drupal
Plone
Salesforce Agentforce Sales
Editions & Modules
No answers on this topic
No answers on this topic
Starter
$25.00
per month per user
Professional
$80.00
per month per user
Enterprise
$165.00
per month per user
Unlimited
$330.00
per month per user
Agentforce 1 Sales
$550
per month per user
Offerings
Pricing Offerings
Drupal
Plone
Agentforce Sales
Free Trial
No
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
—
—
—
More Pricing Information
Community Pulse
Drupal
Plone
Salesforce Agentforce Sales
Considered Multiple Products
Drupal
Verified User
Employee
Chose Drupal
Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you …
Compared to its close rivals, Drupal should be considered a more flexible and slightly advanced solution. WordPress, while being great for out of the box solutions, is limited compared to Drupal and is not as highly customizable. Squarespace provides even more out of the box …
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and …
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
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.
Obviously, for any business, there are two main areas to focus on — the sales path and the service path. Sales Cloud wouldn’t be suited for a company that’s primarily into support services. For those kinds of companies, Salesforce has a different product — Service Cloud. So, for anyone in the support or service space, Sales Cloud isn’t the right fit.
Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
Plone is secure. It is the most secure CMS you can get your hands on.
Plone is flexible, and makes fast development easy.
The customizations - We have an organization that operates differently from most companies, so we’ve had to implement quite a few customizations — and Salesforce allows us to do that quite quickly. Most of the time, delays come from dependencies on other internal parties rather than the system itself.
From my perspective as a consultant, one of the biggest advantages is that everything is in Salesforce — all the details, all in one place. The ability to customize it easily is a big plus; there’s really a lot you can do with it.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).
We still need to include the production part. We started using Salesforce to sell the seeds — our inventory is in SAP — and from there we handle sales and track the process of planting, harvesting, selling, and then collecting payments. But we don’t yet manage the earlier production processes, like production planning. We handle allocation, but not full production planning, and that’s an area where we still have room for improvement.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
There are days when I wish we hadn't switched, but I know that if we put in the time, we will get to where we want to be with the software and that it has many more capabilities than anything else we looked at. However, the amount of time and onboarding we need to do is also far greater than we realized/were told when we originally bought the product. They told us we should hire onboarding support, but at the end, after we had already reached our budget maximum for this, so it's been slower than we had hoped.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
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.
Because I think it could be easier. We have different standards today since we’re used to interacting with consumer apps like Starbucks, where all you do is scan your card. Then, when you use Sales Cloud, there are still a lot of manual inputs. So my mission with AI is really about figuring out how to make that easier.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
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.
Salesforce is always available securely from any internet-capable device anywhere in the world, UNLESS you choose to set security measures so that ONLY trusted IP ranges may access the system at certain times of the day. It's all about choice and flexibility with Salesforce products.
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
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.
Salesforce performance in general is excellent. "The cloud infrastructure beneath Force.com has been fine-tuned over the past 10 years. It powers nearly 100,000+ businesses running more than 185,000 applications that 3 million users count on every day." Points per Salesforce - 1) Multitenant kernel - With a multitenant platform, each business that uses the app doesn’t have its own copy. Instead, all businesses share a single copy and then customize it for their specific needs. 2) ISO 27001 certified security - You can’t compromise when it comes to enterprise-level security. Force.com is road-tested and trusted by nearly 100,000+ companies, including many of the world’s most security-conscious organizations, such as banks and health care providers. 3) Proven reliability - All Force.com apps run on world-class data centers with backup, failover, and disaster-recovery facilities. Force.com has had a proven 99.9 percent uptime record for years. 4) Proven, real-time scalability - Force.com is used by many of the world's largest enterprises, including Cisco, Japan Post Network, and Symantec. Applications can automatically scale from a few users to millions of page views, as needed. 5) Real-time query optimizer - You need fast access to your data. The Force.com query optimizer delivers under 300ms response time, at a massive scale. 6) Real-time transparent system status - You can always see real-time system performance, availability, and security information at trust.salesforce.com. 7) Real-time upgrades - Unlike traditional software platforms, our upgrades never break your customizations, code, or integrations. We upgrade the platform for you 3 to 4 times each year. As a result, you’re always on the latest version, with access to the latest features, performance, and security enhancements. 8) Real-time sandbox environments - With a single click, you can create copies of your applications, configuration, and data in separate environments for development, testing, and training. 9) Three global production data centers and disaster recovery - Force.com runs on three geographically dispersed, mirrored data centers with built-in replication, disaster recovery, a redundant network backbone, and no single points of failure
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
The overall support has been good. More and more features are being released quite frequently. Very small features are also making big difference in how the tool can be adapted and used better. If there is anything we need or are stuck, the support team sets up a call and helps in resolving the issue/provides workarounds.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
I attended two training sessions. I would rate them a 4 as an advanced user. It was very basic – great for someone new – would give 8+ for new person.
I had 3 years of experience at the time. I skipped basic and went onto advanced and still not helpful. A lot of it was best practices that didn’t feel relevant for our business
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
I have gone through multiple. The content that’s delivered is quite basic – I wish they had more advanced training.
We are grandfathered into premium support plus training. We get unlimited access to instructor led and online training for free. We have taken advantage of this
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Just from an organizational standpoint - we standardized our data prior to moving to Salesforce. But we essentially standardized it wrong. That's created a big disgusting mess for us know that I'll have to deal with as the Admin. Be sure you think through use cases prior to doing something like that - seek outside opinions on how the data will work best, especially depending on what else you're going to integrate with Salesforce.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and web content where Plone is much better
So I've evaluated, implemented Microsoft Dynamics in the past. I've used Oracle CRM solutions. I've used Daylight, which is a very niche CRM system the last couple of years. And I've evaluated a variety from Legacy Microsoft Ones to Zoho and Sugar when making implementation decisions at other companies. But usually I've gone with Salesforce. I'd say it's better than most. The only one that I generally prefer, and last time I chose an implementation from scratch, I did Microsoft Dynamics. And the reason is for small mid-size organization, Microsoft Dynamics, if you already have Microsoft Office products, it's much better integrated to all of the Excel, Word, OneNote, Outlook email than what you get from Salesforce. And so that's the only one that if someone's a Microsoft organization and small sized company, it'll save a lot of integration things, a lot of security, a lot of login and access and IT management by just sticking within the Microsoft ecosystem. But outside of that, if you don't use Microsoft or if you're a large organization or have other needs that you want, Salesforce I'd say is better than all of the other CRM offerings out there. It's the easiest to use and the most robust and the most vendors and products for the ecosystem.
Salesforce is the most widely used CRM system. Professionalism tends to increase when things go wrong for market leaders. Salesforce considers us as users because they own the market. Having all of our data in one place and all of our teams working within Salesforce. Anyone who uses Salesforce is impacted by it, even if they don't.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
It's very scalable as it has a ton of features (but you do need an admin who understands how to leverage these features). Because of the various features, we've also needed to host onboarding sessions with our users so that they can familiarize themselves with the platform, which isn't always super user-friendly or intuitive.
Using Salesforce.com has made my daily routines more efficient and simplified the manual tasks I had to perform independently. I can now access data from any device, online or offline, and provide better guidance to my team about the forecasts provided by the built-in artificial intelligence (AI). A chat with a Salesforce support specialist would be great. The knowledge base has a community forum where Salesforce users can ask questions and learn more about the product.
The impact Plone has had at the University of Oshkosh is as follows: this software allows student workers to learn about IT departments and CMS's in a user-friendly way. It gives many students great jobs that look great on their resumes.
Since there are great training manuals for Plone, there is increased employee efficient in the workplace. Training doesn't take long, and if there's ever a question, the Plone manual is a great tool to refer to.
If an employee using Plone quits, its easy to find someone to replace them with quick training and great resources.
It allows me to keep a close eye on all of my performance metrics through the Dashboard Reporting, ie what my sales pipeline looks like, how much it's changed in the last 60 days, new opportunities created in the last 7 days, # of emails sent for the week, etc. The ease of the design and output make it really easy to check my progress throughout the day to find where I have holes and am falling short on my personal and work goals. It's resulted in greater transparency with my Mgmt Team and shorter 1-on-1 mtgs with my boss as he can see exactly where I am at all times (to be fair, I'm a senior sales rep, so he pretty much lets me do my job completely unfettered), but it does prove that I am continually producing which recently resulted in a raise I didn't even ask for.
The SF repository is so detailed that I don't have to spend tons of time finding frequently used websites attached to a client or see what all interactions with the company look like. Even though I don't use SF for my bulk emails and email sequences, SF provides me with an email to use in the bcc of these emails which links everything back to SF. I find that extremely helpful. This really impacts my efficiency and I can honestly say that once I started using all the functionality of data management, it saved me about 20% of my time/week that I could then allocate towards other revenue-generating tasks like prospecting and account management. The more time I have for those, the better. My year-over-year on accounts 1 year and older just grew by 17% this last year.