End of Life for Drupal 7: What's Next?

Drupal continues to evolve. Drupal 7, first released in January 2011, is now approaching its official end of life, set for January 5, 2025. At that time, official Drupal 7 support from the Drupal community will end, including support for updates, security fixes, and enhancements from the Drupal Association and the Drupal Security Team. This will be the final extension of Drupal 7 end of life. 

This is neither the first nor the last such transition for Drupal users. After all, the first iteration of Drupal was released back in 2001, when it wasn’t yet called Drupal. Over the next 20+ years, our favorite content management system has become more sophisticated with each update. We'll review the platform's history, highlight developments in modern versions of Drupal (now on version 10!), explain why migrating off older versions is important, and point to a free and handy guide for that process.

The many versions of Drupal

To appreciate how the platform has evolved, it helps to look back at its history.

• In its infancy, Drupal was known as Dorp (the Dutch word for “village”), and it was far from the versatile tool we use today. In 2000, Dorp (soon to be named Drop, thanks to perhaps the most infamous typo in the tech world) was primarily a place for then-college student Dries Buytaert and the social network at his university to talk about current events and organize get-togethers.
   
• Drupal 1.0: It wasn’t long before Dries decided to formalize his creation and release it as software. It was based on Slash, another CMS, and it included 18 core modules. This version of Drupal was code-intensive — everything was accessed via PHP files, but even then, it was flexible, elegant, and simple to use. Not surprisingly, any user could contribute to Drupal.
   
• Drupal 2.0: By 2001, Dries began listening and, in turn, responding to user demand. He started allowing people to create or translate their Drupal-based website into other languages. The release, which only took two months, also featured minor additions, such as the ability to edit a comment after it was posted. The core modules now numbered 22.
   
• Drupal 3: The release of Drupal 3 was a watershed moment for our CMS, because it marked the arrival of nodes. All kinds of content were nodes, and all were interconnected. The number of modules increased to 26 as a healthy number of websites adopted Drupal for their framework.
   
• Drupal 4: In June 2002, Drupal 4, which then had four different releases over four and a half years, hit a major milestone and officially became an international open source movement. Metatags, attributes, and taxonomy became part and parcel of the platform. In other words, Drupal finally began to look like an enterprise-ready CMS. Not surprisingly, Drupal experienced a 300% increase in content in 2003, which preceded the first official Drupal conference in 2005.
   
• Drupal 5: The various releases of Drupal 4 attracted a wealth of interest from the development community. Almost 500 developers contributed 1,173 patches and 2,500 modules for Drupal 5, which was released in January 2007. Drupal 5, comprising 29 core modules, was one of the first adopters of jQuery and included a web-based installer that decreased site-installation time and a CSS preprocessor that improved loading times.
   
• Drupal 6: Drupal 6 brought more improvements in 2008, such as drag-and-drop administration and new systems for menus and security. During the Obama administration, the White House adopted Drupal 6 as its CMS of choice, while users contributed 7,000 modules and 600 custom themes.
   
• Drupal 7: Drupal 7 was all about powering web applications, and it ushered in the age of Drupal as a preferred choice for building any kind of website. Drupal 7 included more than 11,000 contributed modules, 600 themes, and 200 distributions.
   
• Drupal 8: Introduced in November 2015, Drupal 8 completely reworked the underlying architecture of the CMS to stay ahead of an ever-changing web. This included a revamped release cycle, which keeps Drupal efficiently up-to-date, such that Drupal 7 is now considered obsolete.
   
• Drupal 9: Released in June 2020, Drupal 9 removed deprecated code and updated core dependencies, like Symfony and Twig. Also, Layout Builder and PHPUnit replaced PlaceBlocks and SimpleTest in Drupal core. However, one of the biggest improvements was the introduction of a smoother upgrade path from Drupal 8 to Drupal 9 – which then makes future upgrades just as simple. 
   
• Drupal 10: Drupal’s latest version expands on the platform’s well-loved capabilities and continues to make it a compelling solution for site builders. New features include: Olivero front-end theme, Claro back-end theme, CKEditor5, decoupled navigation, and more! Plus, Drupal 10 has the easiest upgrade path of any other version of Drupal.

Looking ahead to a bright future

Now, we must prepare for the upcoming transition when Drupal 7 reaches end of life on January 5, 2025. It may seem like an obvious choice to stay up-to-date with your CMS, but many Drupal-powered websites have yet to embrace the latest version of Drupal. This is primarily because the transition to upgrade to a new version of Drupal is not a one-size-fits-all process. 

For some teams, such a transition will be a seamless experience. For others, it will be more challenging, requiring a significant investment in time, talent, and resources. Any Drupal user will say that this particular investment is a wise one, though, and the benefits overwhelmingly outweigh the challenges. 

Beginning in 2015, Drupal 8 made significant progress with each and every subsequent release, thanks to the dedication of the Drupal community. Today, Drupal is recognized for several key features and benefits:

• Authoring is the hallmark of Drupal — fast, simple, and powerful. The authoring experience in Drupal today is far easier than ever before. In addition to a WYSIWYG editor, it provides in-line and in-context editing on the page. This is a major advantage for teams that edit and manage content.
   
• Out-of-the-box responsiveness means you can use Drupal to deliver experiences on a web browser, phone, tablet, or anywhere else content and data need to flow – today and in the future.
   
• Flexible content delivery is a key tenet of Drupal. Using Drupal as a content management platform is powerful because it enables you to create and deliver content as a service to any channel, device, or application. The same applies to receiving content from other sources into Drupal. In the emerging API economy, Drupal is the engine that will enable businesses to execute on this vision.
   
• Translation and localization services are much easier to manage with Drupal today. The platform was built to support any language from the authoring side, and the interface can be customized to several languages. It can also support business processes regarding language translation and localization, e.g., integration with external translation service providers.
   
• Integrations matter greatly in a growing ecosystem of disparate but connected digital technologies for marketing. Drupal is a great foundation for web content management and digital experience management because it enables integrations with your best-of-breed technologies. Furthermore, Drupal has vast capabilities to integrate with your existing marketing technologies, providing the freedom and flexibility to choose which technologies you want to use when integrating marketing automation or email marketing software.
   
• A "continuous innovation" development model means new features are rolled out as soon as they're ready instead of being held until the next major release. This reduces the total cost of ownership and allows organizations to spend less time maintaining the platform and more time investing in features that will grow the business.
   
• The ability to embed remote content, such as YouTube and Vimeo videos, as well as a native media library module allow users to add existing media assets.
   
• Layout Builder, a visual layout tool in core, allows site administrators to visually configure content in Drupal in the admin user interface (UI). Acquia takes it a step farther with Site Studio, the low-code site-building tool.
   
• An API-first platform means Drupal can be a central content store on a decoupled front end using JSON:API. Ultimately, headless or hybrid headless solutions can be easier in Drupal. Data can be easily passed to any API-friendly solution, seamlessly integrate other platforms, and create composable architectures with Drupal and the Acquia platform. 
   
• Added enhancements include a modernized administrative theme, improved multilingual support, customizable workflow tools, and robust configuration management.
   

This is by no means an exhaustive list of Drupal’s new and improved capabilities. And, as the platform matures, it will only get better. From improved SEO friendliness, accessibility, and tighter security built right into the platform, there's plenty to discover. 

Migrating off Drupal 7: Keep calm and carry on

If you're still on Drupal 7, there's no need to panic. The Drupal community will support Drupal 7 until January 2025. That said, we recommend beginning the upgrade process as early as possible to ensure plenty of time to prepare and plan. 

As a resource, Drupal.org has outlined a concise list of what to expect when transitioning off Drupal 7:

• No support from the community at large. The community will no longer create new projects, fix bugs in existing projects, or write documentation for Drupal 7.
• No further core commits to Drupal 7.
• No more support or security advisories from the Drupal Security Team for Drupal 7 core or contributed modules, themes, or other projects. Reports about Drupal 7 vulnerabilities might become public.
• All Drupal 7 releases on all project pages will be flagged as not supported. Maintainers will be able to change the flag status if they choose to.
• On Drupal 7 sites with the Update Status module, Drupal core will show up as unsupported.
• After January 2025, using Drupal 7 may be flagged as insecure during third-party scans because it will no longer receive support.
   

It's best practice to avoid unsupported software, and as you can see from the list above, Drupal 7 is reaching that critical threshold. Building new Drupal 7 sites is unadvisable. Plan your migration to Drupal 9 or 10 now.

Upgrading your version of Drupal 

Keeping your website current and up-to-date is a journey, not a destination. Take this opportunity to integrate consistent updates into your work plan to ensure your site runs smoothly and securely as iterations are released. 

The upgrade process in future versions of Drupal will be much easier once you take this first step off Drupal 7. In fact, Drupal 11 code will be exactly like the last minor version of Drupal 10, just stripped of all deprecated code, ensuring your website won't break or need monumental custom code. The best is truly yet to come. For more help as you migrate to Drupal 10, check out this guide.

Note: this blog was originally published in 2019 and has been updated to remain current.