Extra Block Types (EBT) - New Layout Builder experience❗

Extra Block Types (EBT) - styled, customizable block types: Slideshows, Tabs, Cards, Accordions and many others. Built-in settings for background, DOM Box, javascript plugins. Experience the future of layout building today.

Demo EBT modules Download EBT modules

❗Extra Paragraph Types (EPT) - New Paragraphs experience

Extra Paragraph Types (EPT) - analogical paragraph based set of modules.

Demo EPT modules Download EPT modules

Scroll

Upgrage from Drupal 6/7 to Drupal 11

13/04/2025, by Ivan
Upgrading a Drupal site means changing its major version, such as going from Drupal 6 to Drupal 11 or from Drupal 7 to Drupal 11. This documentation guide focuses on upgrading a Drupal 6 or 7 site to Drupal 11.

 

Updating a Drupal site means updating from one minor version to another, such as from “8.0.2” to “8.3.0”. Please refer to the Drupal 11 site update documentation for more details about updating.

Upgrading to Drupal 11 Uses a Migration-Based Approach

Upgrading your site from Drupal 6/7 to Drupal 11 uses a fundamentally different approach than in previous versions. When upgrading from Drupal 6 to Drupal 7, the same database was directly updated from Drupal 6’s structure to Drupal 7’s, as illustrated below.

d6-d7-upgrade

When upgrading from Drupal 6/7 to Drupal 11, you must first install a clean Drupal 11 site. Then, you migrate your site's configuration and content to the new Drupal 11 site. Your existing Drupal 6/7 site remains completely unchanged and untouched.

d6-d7-to-d8-upgrade

Examples of configuration migration: Node content types and field definitions are configuration objects that can be migrated to Drupal 11 so you don’t need to manually recreate them on the Drupal 11 site.

Examples of content migration: Actual nodes, users, and taxonomy terms are examples of content entities that can be migrated to Drupal 11 so you don’t need to manually copy and paste content to your new site.

Although you may hope or expect your new Drupal 11 site to be nearly identical to your old one—just with better features—that may not be the case. For instance, some contributed modules you need may not have an automated upgrade path. Therefore, it's important to carefully review the results of the migration. You may also conclude that it’s easier to copy and paste content manually from your old site to the new one, or that you want to take a custom migration approach.

More Information

Drupal’s online documentation is © 2000-2020 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0. PHP code is distributed under the GNU General Public License.