--- url: 'https://dri.es/the-cms-fragmentation-tax' title: 'The CMS Fragmentation Tax' author: name: 'Dries Buytaert' url: 'https://dri.es/about' date: '2026-07-20T18:10:58-04:00' license: 'https://creativecommons.org/licenses/by/4.0/' type: blog summary: 'Running multiple CMS platforms duplicates integrations, security, governance, and expertise. Standardizing on Drupal with different operating models reduces that cost while preserving flexibility.' tags: - Drupal - Acquia - 'Acquia Cloud' - 'Acquia Source' image: blog/platform-fragmentation discussions: - { platform: LinkedIn, url: 'https://www.linkedin.com/feed/update/urn:li:share:7485104101832224768/' } published: true featured: true id: 6271 --- # The CMS Fragmentation Tax ![A lone traveler walks along a path toward a massive floating cracked planet surrounded by vibrant colors and smaller celestial bodies.](https://headers.dev/files/cache/blog/platform-fragmentation-640w.jpg) In recent months, a number of [Acquia](https://www.acquia.com) customers have independently made the same strategic decision: to migrate hundreds of websites from [WordPress](https://wordpress.org) and other platforms to [Drupal](https://www.drupal.org). Some of these sites will move to Acquia Cloud, our Drupal PaaS, while others will move to Acquia Source, our Drupal SaaS. Drupal CMS played an important role in these decisions by making Drupal more approachable to marketers and site builders. Why are different organizations making the same choice? One key reason is the cost of CMS fragmentation. A few months ago, a CMO told me that her team had purchased a new digital asset management system (DAM). The estimate to connect it to the organization's websites came back at nearly $100,000 and three months of work. Why so much? The organization ran three CMS platforms: Drupal, WordPress, and Contentful. The DAM had to be integrated with all three. That meant not only three integrations, but also three sets of expertise, three rollout plans, and three ongoing maintenance responsibilities. One new capability had become three separate projects. Organizations are under pressure to move faster and reduce costs. CMS fragmentation creates a recurring tax through duplicated integrations, security practices, governance policies, infrastructure, technical expertise, and more. It also fragments attention and makes it harder to share improvements across teams and websites. Organizations pay that tax every day through higher operating costs and slower execution, not only when they introduce new capabilities. When it consistently slows their ability to improve digital experiences, it can become a competitive disadvantage. Some of this duplication can be reduced by standardizing hosting and portfolio governance across multiple CMS platforms. That is valuable, but it addresses only one layer of the problem. Each CMS still has its own extension model, editorial experience, security considerations, and required expertise. This fragmentation usually happens for understandable reasons. Teams often make technology decisions independently, and different sites can have genuinely different requirements. A marketing team may need to launch a campaign site in days without involving developers, making SaaS solutions attractive. A team responsible for a high-traffic enterprise application with custom integrations may need the flexibility and control of an Open Source solution running in a PaaS environment. Each decision can make sense for the individual project while creating significant duplication across the organization. More than 15 years ago, I argued in a post about [Acquia's product strategy](https://dri.es/acquia-product-strategy-and-vision) that organizations should standardize on a common CMS while choosing the right operating model for each site. Today, the case is even stronger. Websites depend on more integrations, digital experiences are more complex, and AI is becoming another shared capability that organizations need to deploy across their portfolios. With multiple CMS platforms, every new capability becomes harder and more expensive to deploy safely. Standardizing on a single CMS lets teams reuse more of their design systems, security practices, integrations, and expertise across sites. Marketers get a more consistent way to create and manage content, while developers spend less time implementing the same capabilities on unrelated platforms. But standardizing on Drupal does not mean forcing every site into the same architecture or operating model. Organizations can share a common CMS foundation while choosing a different balance of convenience and control for each site. That is where Acquia Source and Acquia Cloud fit together. Acquia Source provides the SaaS operating model. It is designed for teams that value speed and simplicity. Acquia manages the underlying platform, while marketers and site builders customize experiences through the user interface, reusable components, and supported integrations. Developers can extend sites through custom components, APIs, webhooks, and other supported tools without managing the Drupal codebase or installing arbitrary modules. Acquia Cloud provides the PaaS operating model. It is designed for sites that need deeper customization and more developer control. Teams can build custom Drupal modules, use contributed modules, manage code through Git, run CI/CD pipelines, and integrate Drupal more deeply with other systems. Both are built on Drupal. This gives organizations a shared foundation for skills, content practices, design systems, security, and integrations, while allowing each site to choose the right balance of speed, simplicity, flexibility, and control. A site can begin on Acquia Source when speed and simplicity matter most. If its requirements later grow to include custom modules, deeper integrations, or more developer control, the organization can export its source code, database, and files and move to Acquia Cloud or another Drupal environment without adopting a different CMS. I have been calling this "Open SaaS": the convenience of SaaS combined with the ownership and portability of Open Source. Organizations can choose a different operating model without leaving Drupal or surrendering control of their sites. When organizations standardize this way, the economics change dramatically. We have helped some customers save millions of dollars each year by reusing shared capabilities instead of rebuilding them for different platforms. The goal is not to operate every website in the same way. A campaign site and a mission-critical application require different levels of speed, flexibility, and control, but they do not need unrelated CMS platforms. The goal is to create operating leverage across an organization's digital portfolio. Each site can use the operating model that fits its needs, while teams reuse investments in content, design, integrations, security, and expertise. Then, when the organization adds a DAM, a personalization engine, an analytics platform, or an AI capability, teams can build on shared work rather than start over for each CMS. The result is faster execution, greater returns on digital investments, lower costs, and less risk. One CMS foundation with multiple operating models makes that possible. PS: Follow the discussion on [LinkedIn](https://www.linkedin.com/feed/update/urn:li:share:7485104101832224768/).