Drupal Review

Migration from one version to the next requires significant effort, but our key metrics have improved dramatically.

Valuable Features

<ol> <li>Feature-rich</li> <li>Open source </li> <li>Highly extendable</li> <li>Being actively developed</li> <li>Helpful, collaborative community</li> <li>free</li> </ol>

Improvements to My Organization

Significantly less time spent on production issues and maintaining existing functionality, translating into significantly more time adding new and enhanced functionality.

Room for Improvement

Migration from one major version to the next major version requires significant effort.

Use of Solution

I have been using this solution for 5 years.

Deployment Issues

No issues with deployment.

Stability Issues

No issues with stability.

Scalability Issues

Initially, yes. Help from experienced consultants ameliorated this.

Customer Service and Technical Support

Customer Service: Excellent. There are always people in the community online and willing to have discussions. Each individual “module” (i.e., extension) has an issue queue where questions and issues can be brought up, discussed, and resolved. And there are consultancies available for contracted support.Technical Support: Excellent. The technical level of the community is high, as is that of consultancies.

Previous Solutions

Yes, several. Moved one site from flat files and homegrown systems, and others from Microsoft CMS 2002, all to enhance our ability to provide new and improved features and to decrease risk. Moved another from a customized (and therefore unmaintainable) version of Xoops. Moved others from hosted services to improve supportability.

Initial Setup

Setting up Drupal itself is straightforward. Implementing all the functionality required for a large, complex site becomes a large work effort. There are thousands of community modules available to add functionality, so determining the best way to add functionality (if you do not have trusted, experienced Drupal developers in-house) becomes a multi-pronged activity of discussions with the community, searching and comparing existing modules, and decisions about using them versus building custom modules.

Implementation Team

Our largest sites have been implemented using blended teams of consultancies and in-house developers. Our smaller sites have been implemented by in-house developers. The vendors we have used have high levels of expertise.


I can’t provide numbers, but I can say that our key metrics have improved dramatically.

Pricing, Setup Cost and Licensing

Zero setup cost for most of our sites. We acquired servers to ensure our largest sites could handle large volumes of visitors. Our ongoing day-to-day cost is just the cost of employee time. We have a small devops team managing the infrastructure and several small teams of developers creating new and improved functionality.

Other Solutions Considered

We evaluated hundreds of other options.

Other Advice

Do NOT implement your first site without the aid of an experienced, collaborative expert. It is very easy to build a Drupal site extremely poorly, and an expert will guide you toward using Drupal the way it works best.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Sign Up with Email