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
HubSpot Content Hub
Score 7.9 out of 10
N/A
Hubspot Content Hub is used to take control of content assets. The unified platform is used to manage, update, and distribute content from a central location, ensuring everyone has access to the most up-to-date and relevant materials.
$20
per month
Percussion CMS
Score 8.6 out of 10
N/A
Percussion Software's content management system is used by higher education, government agencies, and business organizations - SMB to Enterprise. Marketers use Percussion CMS to create, publish, and share multi-channel content.
N/A
Pricing
Drupal
HubSpot Content Hub
Percussion CMS
Editions & Modules
No answers on this topic
Starter
$20
per month per seat
Content Hub Professional
$500
per month 3 seats included, $50 for each additional seat
Content Hub Enterprise
$1500
per month 5 seats included, $75 for each additional seat
No answers on this topic
Offerings
Pricing Offerings
Drupal
HubSpot Content Hub
Percussion CMS
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
Annual commitment required. A discount is offered for annual billing.
—
More Pricing Information
Community Pulse
Drupal
HubSpot Content Hub
Percussion CMS
Considered Multiple Products
Drupal
No answer on this topic
HubSpot Content Hub
No answer on this topic
Percussion CMS
Verified User
Technician
Chose Percussion CMS
No contest. I can't wait to get off of Percussion CMS.
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.
If you want all your marketing activities to be in one place, where your CRM and customer data exist, go for Hubspot's entire suite, which could include CMS, depending on your needs. If you have to create a company blog, marketing landing pages for events or lead generation, or send decently designed newsletters, Hubspot does the job well. Any company that has grown to enterprise level or has fragmented marketing should probably not use Hubspot CMS because of the fragmented activities that might occur. Hubspot's reporting can also break. Also, if you want your designed pages to be very creative with many animations, Hubspot CMS is probably not the way to go. But for anyone who is still finding their footing, go for it.
Best suited for large organizations where everyone knows how to deal with Java in an increasingly Java unfriendly world. Said organization should be willing to pay a huge price for a piece of dinosaur technology
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.
Although you can integrate it with Google Analytics, there is still a significant difference between what each tells you about [a] number of visitors to a given page, etc.
There's a lot to the program and it's not always intuitive where to go for a feature. Though the help center and academy are good and usually have the answers, having to look things up isn't.
One word: JAVA! We don't live in the 1990's anymore! An AJAX/DHTML environment seems a long time coming.
Horrible end-user experience, learning curve. Our end users' inability to easily use the archaic, Java-based interface, means they send the web developer their content requests. This creates a huge bottleneck and completely defeats the purpose of a CMS.
Image mangement and integration with content is aweful and time consuming. An image processing tool called ImedImage was developed for Percussion at one point, and left completely stagnant with very little support.
Implementation is extremely complicated, given the complexity of the system. Sure, scalability is a good thing, but there is very little out-of-the box function. Don't expect to implement a site as quickly as with other CMS platforms.
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.
I don't think we justify the amount of usage we have of CMS Hub professional. We might discontinue it to save some bucks. But if we ever need an extensive solution, we'll come back to it, as we already other products of Hubspot (Sales Hub, Reporting, Automations)
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.
HubSpot CMS HUB is well-rounded and brings a robust list of capabilities while maintaining an ease-of-use that beginners can engage. HubSpot is by far the best at doing this among the half-dozen or so CMS platforms I've used in my 20+ years experience. It turns glorified business card websites into purposeful marketing machines that become a key part of a marketing strategy rather than a complicated and frustrating mess.
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).
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.
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.
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.
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.
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%
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.
We have about 10 seats that were needed. Wanted a sales platform that had good status and reputation. HubSpot was the best choice for me given Salesforce not being the best in the past. Price was appealing and our team liked the overlay. Other options do not provide the same ability with data
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.
We are locked into Percussion CMS simply due to the expense and complexity of migrating to another solution (and the lack of time and budget to do so). I long for the day when I am no longer required to support Percussion CMS, to say the least.
