What CMS Consolidation Can and Cannot Solve

Website portfolios spread across several content management systems can turn one shared capability into several implementation projects. In a 20 July 2026 blog post, Dries Buytaert, founder of Drupal and co-founder of Acquia, argues that organisations can reduce this duplication by standardising on Drupal while choosing software-as-a-service (SaaS) or platform-as-a-service (PaaS) operating models for individual sites. His post supplies the current Drupal argument, while public-sector guidance and Drupal programmes provide a broader test of when consolidation works.

The decision cannot be judged by the number of CMS platforms alone. Consolidation produces savings only when teams can reuse integrations, design systems, security practices, content models, and expertise across sites. Migration work, local requirements, provider dependence, and weak portfolio governance can offset those gains.

Dries cites a nearly $100,000 estimate to connect a digital asset management system to websites running on Drupal, WordPress, and Contentful. He also says Acquia has helped some customers save millions of dollars each year by reusing capabilities instead of rebuilding them for separate platforms. The post does not identify the organisations, publish its calculation methods, or separate migration expenditure from recurring savings. The figures therefore remain vendor claims rather than independent evidence for consolidation.

Application rationalisation offers a more neutral framework for assessing the decision. A January 2025 US Government Accountability Office report describes rationalisation as streamlining software portfolios to improve efficiency, reduce complexity and redundancy, and lower ownership costs. Its cited process covers governance, application inventories, business value, technical fit, total cost of ownership, and future placement. Although the report does not address CMS platforms specifically, those criteria provide a practical basis for deciding which sites should migrate, remain, or receive an exception.

LocalGov Drupal shows what collaborative reuse can look like within a shared Drupal distribution. Its developer documentation says councils and suppliers develop common publishing functionality together, while individual councils still need resources for installation, configuration, hosting, and continuing security updates. The model supports shared investment without eliminating local delivery work or the need to govern custom development.

GovCMS provides a second Drupal example with different operating responsibilities on one platform. Under its published service model, GovCMS manages Drupal security updates, application maintenance, infrastructure, and accreditation for SaaS sites. PaaS customers retain responsibility for the application layer and website security in exchange for greater control and customisation. The model demonstrates operational flexibility within a common platform, but it does not by itself prove a lower total cost.

Migration and portability must be tested separately from the consolidation argument. GovCMS migration guidance states that hosting plans do not cover the cost of building, modifying, or migrating a website, and it expects sites not already using Drupal to be rebuilt. Unsupported modules require PaaS, while greater customisation increases testing and security-assessment work. Dries says Acquia Source sites can export their code, database, and files to Acquia Cloud or another Drupal environment, but that does not establish that every integration, workflow, deployment tool, or support arrangement will transfer intact. UK government guidance distinguishes open-source software from open standards and links practical interoperability to common rules, data formats, and APIs.

The combined evidence supports a preferred-platform policy with governed exceptions rather than an absolute one-CMS mandate. Each site should be assessed for business value, technical fit, lifecycle, compliance requirements, migration cost, and the capabilities it can genuinely share. Consolidation succeeds when it produces measurable reductions in total cost and repeated work without replacing visible fragmentation with hidden operational dependence.